The Software Quality Profile (Figures)


Figure 4. Defect Injection and Removal Rates |
|||
|---|---|---|---|
|
|
|||
PSP Phase |
Injected/hour |
Removed/hour |
Removed/Injected |
| DLD |
1.76 |
0.10 |
0.05 |
DLDR |
0.11 |
2.96 |
27.91 |
Code |
4.20 |
0.51 |
0.10 |
CDR |
0.11 |
6.52 |
59.78 |
Compile |
0.60 |
9.48 |
15.84 |
Test |
0.38 |
2.21 |
5.82 |
Figure 6. Quality Profile Dimensions | |
|---|---|
Dimension |
Meaning |
Design/Code Time |
The ratio of detailed design to coding time - when engineers do not take the time to produce a thorough design, they generally make more design errors. To reduce this risk, design time should equal at least 100% of coding time. |
Code Review Time |
The time spent in code review, compared with coding time - by doing a personal code review before they compile, engineering can find a large percentage of their defects. A thorough code review should take 50% or more of coding time. |
Compile Defects/KLOC |
The defects per KLOC found in compile - even with good review times and rates, the review still could have missed a lot of defects. For quality products, compile defects should be less than 10 defects/KLOC. |
Design Review Time |
Detailed design review time, related to detailed design time - a thorough detailed design review should take 50% or more of the time spent in detailed design. Anything less generally indicates an inadequate review. |
Unit Test Defects/KLOC |
The defects per KLOC found in unit test - the number of defects found in unit test is one of the best indicators of the number that will later be found. When the unit test defects/KLOC exceed 5, subsequent problems are likely. |












