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.
Executive Summary
Software Defect Management Best Practices (Executive Summary)
By Khaled Emam
Posted March 31, 2002 | Technology |
About The Author
Khaled El Emam is Professor at the University of Ottawa, Canada, Faculty of Medicine, where he previously held the position of Canada Research Chair in Electronic Health Information. He is also founder, President, and CEO of Privacy Analytics Inc. As an entrepreneur, Dr. El Emam has founded or cofounded five companies involved with data management and data analytics over the last two decades. He has worked in technical and management positions… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.