Page 234 -

CHAPTER 8 SOFTWARE QUALITY ASSURANCE 205

FIGURE 8.3 Preliminary design
Defect 0
amplification, Detail design
no reviews 0 0% 10 6 6 Code/unit test
10 4 4 × 1.5 0% 3710 10
x = 1.5
27 27 × 3 94
25 20%
x = 3
94 Integration test 25
Validation test
47 To integration
0 50%
System test
24
0 0 50%
0 0 50% 12

0

Latent errors
FIGURE 8.4 Preliminary design
Defect 0
amplification, Detail design
reviews 0 70% 32
conducted 2 Code/unit test
10 1 1 1.5 50% 15 5 5
•
10 24
25 10 3 60%
•
Integration test
24 25
Validation test
12 To integration
0 50%
System test
6
0 0 50%
0 0 50% 3

0
Latent errors

nical reviews (for design and other technical activities) provide a demonstrable cost
benefit. They should be conducted.

8.5 FORMAL TECHNICAL REVIEWS

A formal technical review is a software quality assurance activity performed by soft-
ware engineers (and others). The objectives of the FTR are (1) to uncover errors in
function, logic, or implementation for any representation of the software; (2) to verify