Summary

5.8 Summary

Defects can and do occur in any phase of the SLC. Recording and tracking defects in the software makes sure that all found defects are, in fact, addressed. An important aspect of the trouble report, in whatever manner it is implemented, is that it provides a means to ensure that each defect is addressed and the solution recorded.

Changes require careful control. Every time a change is made, there is the chance that a new defect will be introduced with the change. In projects under formal CM, trouble report closures that require CM processing, and especially including formal change approval, will reflect any CM action involved.

Classification of defects aids in the use of defect data to guide defect resolution now and identify software development process weaknesses. Future problem areas can also be predicted using error or defect trend analysis.

As defects are found and eliminated, a body of data about the defects can be accumulated. These data become input for quality assurance analysis. Such analysis as trends and metrics can be conducted to help depict the development process in use and its potential weaknesses. While finding and fixing defects is the quality control role, and defect analysis aids in the repair of defects, the quality assurance practitioner needs defect data to help identify potential process flaws. The defect data is also useful as empirical information that can aid decision-making, action-capable management in its process modifications.



Practical Guide to Software Quality Management
Practical Guide to Software Quality Management (Artech House Computing Library)
ISBN: 1580535275
EAN: 2147483647
Year: 2002
Pages: 137
Authors: John W. Horch

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net