Abstract
This paper presents a case history of Mentor Graphics using a set of quality metrics to track development progress for a recent major software release. It provides background on how Mentor Graphics originally began using software metrics to measure product quality, how this became accepted, and how these metrics later fell out of favour. To restore these metrics to effective use, process changes were required for setting quality and metric targets, and for the way the metrics are used for tracking development progress. With these process changes in place, and the addition of a new metric, the case history demonstrates that the metric set could be used effectively to indicate problems in this release and help manage changes to the plan for completion of the release. The lessons learned in this case history are presented, along with subsequent data that further validates these metrics.
Similar content being viewed by others
References
Brooks, F.P.Jr (1982) The Mythical Man-Month (Reading, MA, Addison-Wesley).
Fagan, M. (1976) Design and code inspections to reduce errors in program development. IBM Systems Journal, 5, 3.
Fagan, M. (1986) Advances in software inspections. IEEE Transactions on Software Engineering, SE-12, (7).
Grady, R.B. and Caswell, D.L. (1987) Software Metrics: Establishing a Company-wide Program (Englewood Cliffs, NJ, Prentice Hall).
Grady, R.B. (1992) Practical Software Metrics for Project Management and Process Improvement (Englewood Cliffs, NJ, Prentice Hall).
Hetzel, W.C. (1988) The Complete Guide to Software Testing, Second Addition (Wellesley, MA, QED Information Sciences).
Humphrey, W.S. (1989) Managing the Software Process (Reading, MA, Addison-Wesley).
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Johnson, M.A. A case study of tracking software development using quality metrics. Software Qual J 4, 15–31 (1995). https://doi.org/10.1007/BF00404647
Received:
Issue Date:
DOI: https://doi.org/10.1007/BF00404647