Understanding quality costs is recognized as a prerequisite for decreasing the variability of the success of software development projects. This paper presents an empirical quality cost reduction (QCR) model to support the decision-making process for additional investment in the early phases of software verification. The main idea of the QCR model is to direct additional investment into software units that have some fault-slip potential in their later verification phases, with the aim of reducing costs and increasing product quality. The fault-slip potential of a software unit within a system is determined by analogy with historical projects. After a preliminary study on a sample of software units, which proves that we can lower quality costs with additional investment into particular verification activities, we examine the effectiveness of the proposed QCR model using real project data. The results show that applying the model produces a positive business case, meaning that the model lowers quality costs and increases quality, resulting in economic benefit. The potential to reduce quality costs is growing significantly with the evolution of software systems and the reuse of their software units. The proposed model is the result of a research project performed at Ericsson.
This is a preview of subscription content, access via your institution.
Buy single article
Instant access to the full article PDF.
Tax calculation will be finalised during checkout.
Subscribe to journal
Immediate online access to all issues from 2019. Subscription will auto renew annually.
Tax calculation will be finalised during checkout.
Andersson, C., & Runeson, P. (2007). A replicated quantitative analysis of fault distributions in complex software systems. IEEE Transactions on Software Engineering, 33(5), 273–286.
Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., & Grnbacher, P. (Eds.). (2006). Value-based software engineering. Heidelberg: Springer.
Boehm, B. W. (1997). COCOMO II model definition manual. Technical report, University of Southern California.
Boehm, B. W. (1981). Software engineering economics. New York: Prentice Hall.
Breyfogle, F. W. (2003). Implementing six sigma. Hoboken: Wiley.
Campanella, J. (1999). Principles of quality costs. Milwaukee: ASQ Quality Press.
Crosby, P. B. (1996). Quality is still free: Making quality certain in uncertain times. New York: McGraw-Hill.
Damm, L.-O., Lundberg, L., & Wohlin, C. (2004). Determining the improvement potential of a software development organization through fault analysis: A method and a case study. In: T. Dingsøyr (Ed.), Software process improvement, 11th European conference, EuroSPI 2004. Vol. 3281 of lecture notes in computer science (pp. 138–149). Berlin: Springer.
Damm, L.-O., Lundberg, L., & Wohlin, C. (2008). A model for software rework reduction through a combination of anomaly metrics. The Journal of Systems and Software, 81(11), 1968–1982.
Deissenboeck, F., Juergens, E., Lochmann, K., & Wagner, S. (2009). Software quality models: Purposes, usage scenarios and requirements. In B. Wong (Ed.), Proceedings of the seventh ICSE conference on software quality (WOSQ’09) (pp. 9–14). Washington, DC: IEEE Computer Society.
Deming, W. E. (1986). Out of crisis. Cambridge: MIT Center for Advanced Engineering Study.
Ebenau, R. G., & Strauss, S. H. (1994). Software inspection process. Workingham: McGraw Hill.
Fagan, M. E. (1976). Design and code inspections to reduce errors in program development. IBM Systems Journal, 15(3), 575–607.
Fenton, E. N., & Pfleeger, S. L. (1998). Software metrics: A rigorous and practical approach (2nd ed.). Boston, MA: PWS Pub. Co.
Fenton, N. E., & Ohlsson, N. (2000). Quantitative analysis of faults and failures in a complex software system. IEEE Transactions on Software Engineering, 26(8), 797–814.
Galinac Grbac, T., Car, Ž., & Huljenić, D. (2012). Quantifying value of adding inspection effort early in the development process: A case study. IET Software, 6(3), 249–259.
Galinac Grbac, T., Runeson, P., & Huljenić, D. (2013). A second replicated quantitative analysis of fault distributions in complex software systems. IEEE Transactions on Software Engineering, 39(4), 462–476.
Galinac, T., & Car, Ž. (2007). Software verification process improvement proposal using Six Sigma. In: J. Munch & P. Abrahamsson (Eds.), PROFES ’07: Proceedings of 8th international product-focused software process improvement conference. Vol. 4589 of lecture notes in computer science (pp. 51–64). Berlin: Springer.
Gondra, I. (2008). Applying machine learning to software fault-proneness prediction. The Journal of Systems and Software, 81(2), 186–195.
Hall, T., Beecham, S., Bowes, D., Gray, D., & Counsell, S. (2012). A systematic literature review on fault prediction performance in software engineering. IEEE Transactions on Software Engineering, 38(6), 1276–1304.
Jørgensen, M., Boehm, B., & Rifkin, S. (2009). Software development effort estimation: Formal models or expert judgment? IEEE Software, 26(2), 14–19.
Juran, J., et al. (1999). Juran’s quality control handbook (5th ed.). New York: McGraw-Hill.
Karg, L. M., Grottke, M., & Beckhaus, A. (2011). A systematic literature review of software quality cost research. Journal of Systems and Software, 84(3), 415–427.
Khoshgoftaar, T. M., Allen, E. B., Jones, W. D., & Hudepohl, J. P. (2001). Cost-benefit analysis of software quality models. Software Quality Journal, 9, 9–30.
Lessmann, S., Baesens, B., Mues, C., & Pietsch, S. (2008). Benchmarking classification models for software defect prediction: A proposed framework and novel findings. IEEE Transactions on Software Engineering, 34(4), 485–496.
Musa, J. D., Iannino, A., & Okumoto, K. (1987). Software reliability measurement, prediction, application. New York: McGraw-Hill.
Provost, F. (2000). Machine learning from imbalanced data sets 101. In Proceedings of learning from imbalanced data sets: Papers from the American Association for Artificial Intelligence workshop, Technical report WS-00-05.
Putnam, L. H. (1978). A general empirical solution to the macro software sizing and estimating problem. IEEE Transactions on Software Engineering, 4(4), 345–361.
Siy, H., & Votta, L. (2001). Does the modern code inspection have value? In Proceedings of the 17th IEEE international conference on software maintenance ICSM 2001 (pp. 281–291). Los Alamitos: IEEE Computer Society.
Slaughter, S. A., Harter, D. E., & Krishnan, M. S. (1998). Evaluating the cost of software quality. Communications of the ACM, 41(8), 67–73.
Tosun, A., Turhan, B., & Bener., A. (2009). Validation of network measures as indicators of defective modules in software systems, In Proceedings of the 5th international conference on predictor models in software engineering (PROMISE ’09). New York, NY: ACM, Article 5.
Villalba, M. T., Sanz, L. F., & Martinez, J. J. (2010). Empirical support for the generation of domain-oriented quality models. IET Software, 4(1), 1–14.
Westland, J. C. (2004). The cost behavior of software defects. Decision Support Systems, 37(2), 229–238.
Zimmermann, T., Nagappan, N., Gall, H., Giger, E., & Murphy, B. (2009). Cross-project defect prediction: A large scale experiment on data vs. domain vs. process. In Proceedings of the ESEC/FSE ’09 (pp. 91–100). New York, NY: ACM.
Zimmermann, T., & Nagappan, N. (2008). Predicting defects using network analysis on dependency graphs. ICSE, 2008, 531–540.
The first author is partially supported by the University of Rijeka research grant 13.09.2.2.16.
About this article
Cite this article
Galinac Grbac, T., Car, Ž. & Huljenić, D. A quality cost reduction model for large-scale software development. Software Qual J 23, 363–390 (2015). https://doi.org/10.1007/s11219-014-9240-8
- Quality cost
- Control model
- Fault detection
- Large-scale software