Software Defect Management Best Practices

by Khaled El Emam

Software defects are inevitable. Even high-reliability software that has been tested extensively still has defects. Defects can cause operational failures, which may have negative financial, human, or environmental consequences. In addition, the cost of fixing post-release defects can be tremendous. Good defect management practices allow projects to minimize the introduction of defects through preventive actions, monitor defect introduction and removal to anticipate changes in the software's quality, and use quality risk assessment in deciding where to focus inspection and testing.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Software Defect Management Best Practices April 2002