The defect management process is based on the following general principles:
The
primary goal is to prevent defects. Where this is not possible or
practical, the goals are to both find the defect as quickly as possible
and minimize the impact of the defect.
The defect management process should be http://www.defectmanagement.com/defectmanagement/risk.htm - risk driven -- i.e., strategies, priorities, and resources should be based on the extent to which http://www.defectmanagement.com/defectmanagement/risk.htm - risk can be reduced.
Defect
measurement should be integrated into the software development process
and be used by the project team to improve the process. In other
words, the project staff, by doing their job, should capture
information on defects at the source. It should not be done
after-the-fact by people unrelated to the project or system
As much as possible, the capture and analysis of the information should be automated.
Defect
information should be used to improve the process. This, in fact, is
the primary reason for gathering defect information.
|