Abstract
This paper presents a simple cost-based method for managing software quality during the development process. The technique may apply conceptually to the management of quality for other processes, as well. A unifying metric for quality is defined to be the ratio of the cost expended at a given point in time to that which will be required to satisfy all requirements placed on quality attributes, such as correctness, reliability, etc. Unit quality then corresponds to a system that fulfills all of its quality attribute requirements. The paper indicates the need for developing cost-versus-attribute relationships for all quality factors of concern.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Belady, L.A. (1977), “Software Complexity”, Software Life Cycle Management Workshop, AIRMICS, Atlanta, GA, pp. 371–383.
Boehm, B.W.et al. (1978),Characteristics of Software Quality, Elsevier-North Holland Book Co., Amsterdam, Holland.
Boehm, B.W. (1981),Software Economics, Prentice-Hall, Inc., Englewood Cliffs, NJ, pp. 310–313.
Brooks, F.P. (1974), “The Mythical Man-Month”,Datamation 20, 12, 45–52.
Crosby, P.B. (1979),Quality is Free, Mentor Books, New York, NY.
Curtis, W. (1981), “The Measurement of Software Quality and Complexity”, InSoftware Metrics, A.J. Perliset al., Eds., MIT Press, Cambridge, MA, chapter 12.
Deming, E. (1989),Out of Crisis, MIT Center for Advanced Engineering Study, Cambridge, MA.
Elsayed, E.A., G. Taguchi, and T. Tsiang (1988),Quality Engineering in Production Systems, McGraw-Hill Book Co., NY.
Gilb, T. (1977),Software Metrics, Winthrop Press, Cambridge, MA.
Humphry, W. (1987), “Characterizing the Software Process—A Maturity Framework”, Technical Report CMU/SEI-87-TR-11, ESD-TR-87-112, Software Engineering Institute, Carnegie-Mellon University, Pittsburg, PA.
“Information Technology — Software Product Evaluation — Quality Characteristics and Guidelines for Their Use”, International Organization for Standardization, ISO/TEC 9126.
Koontz, O'Donnell, and Weihrich (1984),Management, McGraw-Hill Book Co., NY, Eighth Edition.
Lyu, M.R. (1991), “Measuring Reliability of Embedded Software: An Empirical Study with JPL Project Data”,International Conference on Probabilistic Safety Assessment and Management, Beverly Hills, CA, pp. 493–500.
Mosemann, L.K. (1993), “Creating a National Vision and Force in Software Through Software Measurement”, keynote address, Cooperstown I Workshop, Rome Laboratory, Griffiss AFB, NY.
Pall, G.A. (1987),Quality Process Management, Prentice-Hall, Inc., Englewood Cliffs, NJ.
Perlis, A.J.et al. (1981),Software Metrics, MIT Press, Cambridge, MA.
Phadke, M.S. (1989),Quality Engineering Using Robust Design, Prentice-Hall, Inc.
Press, W.H., Ed. (1987),Numerical Recipes: The Art of Scientific Computing, Cambridge University Press, New York, Chapter 10.
Stamm, S.L. (1981), “Assuring Quality Quality Assurance”,Datamation 27, 195–200.
Tausworthe, R.C. (1980), “The Work Breakdown Structure in Software Project Management”,Journal of Systems and Software 1, 181–186.
Thayer, R.H. (1983), “Software Engineering Project Management: A Top-Down View”,Software Engineering Project Management, IEEE Computer Society Tutorial 751, Computer Society Press, Washington, DC.
Walton, M. (1988),The Deming Method, Dodd-Mead, Inc., New York, NY.
Author information
Authors and Affiliations
Additional information
The research described in this paper was carried out by the Jet Propulsion Laboratory, California Institute of Technology, under a contract with the National Aeronautics and Space Administration.
Rights and permissions
About this article
Cite this article
Tausworthe, R.C. Software quality management through process and product modeling. Ann Software Eng 1, 119–139 (1995). https://doi.org/10.1007/BF02249048
Issue Date:
DOI: https://doi.org/10.1007/BF02249048