Software engineers and test specialists should follow the examples of engineers in other disciplines who make use of defect data. A requirement for repository development should be a part of testing and/or debugging policy statements.
Forms and templates should be designed to collect the data. Each defect and frequency of occurrence must be recorded after testing.
Defect monitoring should be done for each on-going project. The distribution of defects will change when changes are made to the process.
Figure 1.5 The Defect Repository and Support for TMM Maturity Goals
The defect data is useful for test planning. It is a TMM level 2 maturity goal. It helps a tester to select applicable testing techniques, design the test cases, and allocate the amount of resources needed to detect and remove defects. This allows tester to estimate testing schedules and costs.
The defect data can support debugging activities also. A defect repository can help in implementing several TMM maturity goals including
-
Controlling and monitoring of test,
-
Software quality evaluation and control,
-
Test measurement,
-
Test process improvement.
World Of CSE 