Open Access Open Access  Restricted Access Subscription or Fee Access

Improving Software Quality through Effective Defect Management Process: A Review

Dr. Yudhvir Singh, Kamna Solanki


With the development of modern information science and technology, complexity of software system is higher than ever before. With the software‟s scale and complexity improving, people are paying more attention on software‟s quality and functional reliability. Software Process Improvement based on an effective Defect Management Process (DMP) is one method of improving software quality. Software Industry is seriously deficient on effective DMP. The understanding of DMP is still in initial stage. Therefore, earnest study of software DMP in software engineering and correctly using it during software development seems to be the demand of time. This paper basically covers each aspect of DMP in detail. The paper deeply study and analyze the theory, technology, methodology and tools of defect management system. Firstly, the paper describes the role and necessity of DMP in the software development. Secondly, it explains the phases, stages and importance of good defect management process.


Requirements Engineering, Requirement Elicitation, Requirement Validation and Management

Full Text:



Aaen, I. (2003). Software Process Improvement: Blueprints Versus Recipes. IEEE Software 20(5), 86–93.

Adeel, K., (Aug. 2005). Defect prevention techniques and its usage in requirement gathering – industry practices , Proceedings of Engineering Sciences and Technology, ISBN 978-0-7803-9442-1, SCONEST, IEEE Computer Society Publisher, pp 1-5.

Boehm, B. and V. Basili (2001). Software Defect Reduction Top 10 List. Computer 34(1), 135–138.

Bassin, K. and P. Santhanam (2001). Managing the maintenance of ported, outsourced, and legacy software via orthogonal defect classification. In Proceedings of the IEEE International Conference on Software Maintenance, Washington, DC, pp. 726. IEEE Computer Society.

Boehm, B. , Basili,V., (2001) Software Defect Reduction Top 10 List Journal Computer archive Volume 34 Issue 1, IEEE Computer Society,, CA, USA

Boehm, B. and V. Basili (2001). Software Defect Reduction Top 10 List. Computer 34(1), 135–138.

Børretzen, J.A. , Conradi, R., (2003). “Results and Experiences From an Empirical Study of Fault Reports in Industrial Projects”, Proceedings of the 7th International Conference on Product Focused Software Process Improvement, Amsterdam, pp. 389-394

Børretzen, J.A. , (Sept. 2009) .Investigating the Software Fault Profile of Industrial Projects to Determine Process Improvement Areas: An Empirical Study”, Proceedings of the 14th European Systems & Software Process Improvement and Innovation Conference, Potsdam, Germany, pp. 212-223.

Card, D. N. (2002). Managing software quality with defects. In Proceedings of the 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopmentpp. 472–474.

Card, D.N., (October 2006). Myths and Strategies of Defect Casual Analysis, Proceedings of twenty-fourth Annual Pacific Northwest Software Quality Conference, Portland, Oregon, pp 469-474.

Chillarege, R. and K. Prasad (2002). Test and Development Process Retrospective -A Case Study Using ODC Triggers. In Proceedings of the International Conference on Dependable Systems and Networks, Florence, Italy, pp. 669–678. IEEE Computer Society Press.

Drago, J., (2011). “Role of Defect Management Software in Software Development Life cycle”, Available at -

Fredericks, M., Basili ,V.,(1998). “Using defect tracking and analysis to improve software quality”. Report DACS-SOAR-98-2, Experimental Software Engineering Group, University of Maryland, College Park, MD, USA

Fairley, R. E. and M. J. Willshire (2005). Iterative rework: The good, the bad, and the ugly. Computer 38(9), 34–41.

Howles, T. and S. Daniels (2003). Widespread Effects of Defects. Quality Progress 36(8), 58–62.

Humphrey, W. (2002). Winning with Software. Addison-Wesley Longman Publishing Co., Inc., Boston, MA.

IEEE (2004). IEEE Standard for Verification and Validation/IEEE Std. 1012-2004.

Jones, C.(2009),” Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies”. McGraw-Hill, New York, NY, USA, 2009. ISBN 007162161X.

Khilman, A., (2005). “Defect Management Process in Software Testing”, Thesis submitted in Faculty of Information Technology, MERA Technical University.

Lars Ola Damm (2007) "Early and Cost-effective Fault Detection", Dissertation submitted to Blekinge Institute of Technology, Sweden

Leszak, M., D. Perry, and D. Stoll (2000). A Case Study in Root Cause Defect Analysis. In Proceedings of the 22nd Int. Conference on Software Engineering, Limerick, Ireland, pp. 428–437. ACM Press.

Leszak, M. (2002). Classification and evaluation of defects in a project retrospective. Journal of Systems and Software 61(3), 173–187.

Lyu, M.,(2007) “Software reliability engineering: A roadmap”. In FOSE ‟07: 2007 Future of Software Engineering, pages 153–170, Washington, DC, USA, 2007. IEEE Computer Society. ISBN 0-7695-2829-5.

MacCormack, A., etal (2003). Trade-offs between Productivity and Quality in Selecting Software Development Practices. IEEE Software 20(5), 78–86.

Madsen, P. (2004). A Software Development Process based on Test-Driven Development and Testing by Contract. In Proceedings of the 11th NordicWorkshop on Programming and Software Development Tools and Techniques, Turku, Finland, pp. 225–240.

Mast, J. (2004). A Methodological Comparison of Three Strategies for Quality Improvement. International Journal of Quality & Reliability Management 21(2), 198–213.

Mathiassen, L., J. Pries-Heje, and O. Ngwenyama (2002). Improving Software Organizations: From Principles to Practice. Addison-Wesley Longman Publishing Co., Inc., Boston, MA.

Maximilien, E. M. and L. Williams (2003). Assessing Test-Driven Development at IBM. In Proceedings of the 25th International Conference on Software Engineering, Portland, Oregon, pp. 564–569. IEEE Computer Society Press.

McGarry, J., D. Card, C. Jones, B. Layman, E. Clark, J. Dean, and F. Hall (2001). Practical Software Measurement: Objective Information for Decision Makers. AddisonWesley Professional, Boston, MA.

Mohagheghi, P., R. Conradi, and J. A. Bretzen (2006). Revisiting the problem of using problem reports for quality assessment. In Proceedings of the 2006 international workshop on Software quality, New York, NY, pp. 45–50. ACM Press.

(Myers, 2004) G. Myers, The art of software testing, Wiley and Sons, 2004

Ngwenyama, O. and P. A. Nielsen (2003). Competing Values in Software Process Improvement: An Assumption Analysis of CMM from an Organizational Culture Perspective. IEEE Transactions on Engineering Management 50(1), 100– 112.

Niazi, M., D.Wilson, and D. Zowghi (2005).A Maturity Model for the Implementation of Software Process Improvement: An Empirical Study. Journal of Systems and Software 74(2), 155–172.

Ostrand, T.J., Weyuker E.J., (2005), "A Tool for Mining Defect-Tracking Systems to Predict Fault-Prone Files", 1st International Workshop on Mining Software Repositories, pp. 85-89.

Purushotham Narayan (2003), Software Defect Prevention in a nutshell, isixsigma Publisher, Publishing date 11 june 2003.

Runeson, P., C. Andersson etal (2006). What do we know about defect detection methods? IEEE Software 23(3), 82–90.

Runeson, P., M. H. Jonsson, and F. Scheja (2004). Are found defects an indicator of software correctness? an investigation in a controlled case study. In Proceedings of the 15th International Symposium on Software Reliability Engineering (ISSRE‟04),Washington, DC, pp. 91–100. IEEE Computer Society Press.

Shull, F., V. Basili etal (2002). What we have learned about fighting defects. In Proceedings of the Eight IEEE Symposium on Software Metrics, Ottawa, Canada, pp. pp. 249–258. IEEE Computer Society.

Suma, V., Gopalakrishnan, T.R., (2010). “Impact Analysis of Inspection Process for Effective Defect Management in Software Development”, American Society for Quality (ASQ) Journal, Software Quality Professional, USA, Vol. 12, No. 2.

Tian, J. (2001). Quality assurance alternatives and techniques: A defect-based survey and analysis. Software Quality Professional 3(3), 6–18.

Tian, J., (Feb 2005). Software Quality Engineering: Testing, Quality Assurance and Quantifiable Improvement, Wiley John & Sons Publisher, ISBN 13-9780471713456

Tomaszewski, P. and L.-O. Damm (2006). Comparing the fault-proneness of new and modified code: an industrial case study. In Proceedings of the 2006 ACM/IEEE international symposium on International symposium on empirical software engineering, Rio de Janeiro, Brazil, pp. 2–7. ACM Press.

Vasudevan, S., (2005). Defect Prevention Techniques and Practices, Proceedings of fifth annual International Software Testing Conference, Banglore, India

Van Solingen, R. (2004). Measuring the ROI of Software Process Improvement. IEEE Software 21(3), 32–38.

Voas, J. (1999). Software Quality‟s Eight Greatest Myths. IEEE Software 16(5), 118–121.

Wagner, S. and T. Seifert (2005). Software quality economics for defect-detection techniques using failure prediction. In Proceedings of the third workshop on Software quality, pp. 1–6. ACM Press.

Watts, S.H., (1989). Managing the Software Process, Defect Prevention, ISBN 0102180952, 9780201180954, Addison Wesley Professional Publisher.

Wagner, S.,( Sept.2008). A literature survey of the quality economics of defect-detection techniques, Proceedings of the 2008 ACM/IEEE International Symposium on Empirical Software Engineering, Rio de Janeiro, Brazil.

Westland, J. C. (2004). The cost behavior of software defects. Decision Support Systems 37(2), 229–238.

Zimmermann, T., Battenberg, N., Premraj, R., Kim, S., (2010). “Extracting Structural Information from Bug Reports” .


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.