Academia.eduAcademia.edu

Outline

IMPORTANCE OF SOFTWARE QUALITY MODELS IN SOFTWARE ENGINEERING

https://doi.org/10.5281/ZENODO.1218182

Abstract

The purpose of this paper is to identify the importance quality in software engineering when the projects or products are developed. The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations is the quality. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs is software quality. Some even say that 'quality' cannot be defined and some say that it can be defined but only in a particular context. Some even state confidently that 'quality is lack of bugs'. In this paper we discuss about the quality and the quality models.

FAQs

sparkles

AI

What key differences exist between quality definitions by Crosby and Deming?add

Crosby defines quality as 'conformance to requirements', emphasizing prevention, while Deming sees it as 'meeting customer needs', highlighting customer satisfaction and continuous improvement.

How do McCall's and Boehm's models approach software quality evaluation?add

McCall’s model focuses on user-developer perspectives, defining quality across product revision and operation, while Boehm’s model emphasizes maintenance with seven attributes affecting overall quality.

What unique insights does Ishikawa provide regarding quality interpretation?add

Ishikawa considers quality dynamically, acknowledging that consumer requirements evolve and that quality extends beyond products to services, processes, and systems.

Why are traditional quality models viewed as limited compared to management philosophies?add

Quality models offer measurable attributes, which simplify quality assessment, yet may overlook the dynamic nature of evolving customer expectations that management philosophies address.

What implications arise from the ISO 9126 standard in software evaluation?add

ISO 9126 identifies six key quality factors including functionality and reliability, establishing a structured approach for understanding and improving software quality characteristics.

References (36)

  1. Hoyer, R. W. and Hoyer, B. B. Y., "What is quality?", Quality Progress, no. 7, pp. 52-62, 2001.
  2. Robson, C., Real world research: a resource for social scientists and practitioner-researchers, Blackwell Publisher Ltd., 2002.
  3. Crosby, P. B., Quality is free: the art of making quality certain, New York: McGraw-Hill, 1979.
  4. Deming, W. E., Out of the crisis: quality, productivity and competitive position, Cambridge Univ. Press, 1988.
  5. Feigenbaum, A. V., Total quality control, McGraw-Hill, 1983.
  6. Ishikawa, K., What is total quality control? : the Japanese way, Prentice-Hall, 1985.
  7. Juran, J. M., Juran's Quality Control Handbook, McGraw-Hill, 1988.
  8. Shewhart, W. A., Economic control of quality of manufactured product, Van Nostrand, 1931.
  9. McCall, J. A., Richards, P. K., and Walters, G. F., "Factors in Software Quality", Nat'l Tech.Information Service, no. Vol. 1, 2 and 3, 1977.
  10. Marciniak, J. J., Encyclopedia of software engineering, 2vol, 2nd ed., Chichester: Wiley, 2002.
  11. Kitchenham, B. and Pfleeger, S. L., "Software quality: the elusive target [special issues section]", IEEE Software, no. 1, pp. 12-21, 1996.
  12. Boehm, B. W., Brown, J. R., Kaspar, H., Lipow, M., McLeod, G., and Merritt, M., Characteristics of Software Quality, North Holland, 1978.
  13. Boehm, Barry W., Brown, J. R, and Lipow, M.: Quantitative evaluation of software quality, International Conference on Software Engineering, Proceedings of the 2nd international conference on Software engineering, 1976.
  14. Hyatt, Lawrence E. and Rosenberg, Linda H.: A Software Quality Model and Metrics for Identifying Project Risks and Assessing Software Quality, European Space Agency Software Assurance Symposium and the 8th Annual Software Technology Conference, 1996.
  15. Grady, R. B., Practical software metrics for project management and process improvement, Prentice Hall, 1992.
  16. Jacobson, I., Booch, G., and Rumbaugh, J., The Unified Software Development Process, Addison Wesley Longman, Inc., 1999.
  17. Kruchten, P., The Rational Unified Process An Introduction -Second Edition, Addison Wesley Longman, Inc., 2000.
  18. Rational Software Inc., RUP -Rational Unified Process, www.rational.com, 2003.
  19. Dromey, R. G., "Concerning the Chimera [software quality]", IEEE Software, no. 1, pp. 33-43, 1996.
  20. Dromey, R. G., "A model for software product quality", IEEE Transactions on Software Engineering, no. 2, pp. 146-163, 1995.
  21. ISO, International Organization for Standardization, "ISO 9000:2000, Quality management systems -Fundamentals and vocabulary", 2000.
  22. ISO, International Organization for Standardization, "ISO 9000-2:1997, Quality management and quality assurance standards -Part 2: Generic guidelines for the application of ISO 9001, ISO 9002 and ISO 9003", 1997.
  23. ISO, International Organization for Standardization, "ISO 9000-3:1998 --Quality management and quality assurance standards -Part 3: Guidelines for the application of ISO 9001_1994 to the development, supply, installation and maintenance of computer software (ISO 9000-3:1997)", 1998. [Ramulu et. al., Vol.5 (Iss.3): March, 2018] ISSN: 2454-1907 DOI: 10.5281/zenodo.1218182
  24. Http://www.ijetmr.com©International Journal of Engineering Technologies and Management Research [218]
  25. ISO, International Organization for Standardization, "ISO 9001:2000, Quality management systems -Requirements", 2000.
  26. ISO, International Organization for Standardization, "ISO 9004:2000, Quality management systems -Guidelines for performance improvements", 2000.
  27. ISO, International Organization for Standardization, "ISO 9126-1:2001, Software engineering - Product quality, Part 1: Quality model", 2001.
  28. Humphrey, W. S., Introduction to the Personal Software Process, Addison-Wesley Pub Co; 1st edition (December 20, 1996), 1996.
  29. Humphrey, W. S., Managing the software process, Addison-Wesley, 1989.
  30. Humphrey, W. S., Introduction to the team software process, Addison-Wesley, 2000.
  31. Paulk, Mark C., Weber, Charles V., Garcia, Suzanne M., Chrissis, Mary Beth, and Bush, Marilyn, "Capability Maturity Model for Software, Version 1.1", Software Engineering Institute, Carnegie Mellon University, 1993.
  32. Paulk, Mark C., Weber, Charles V., Garcia, Suzanne M., Chrissis, Mary Beth, and Bush, Marilyn, "Key practices of the Capability Maturity Model, version 1.1", 1993.
  33. Curtis, Bill, Hefley, Bill, and Miller, Sally, "People Capability Maturity Model® (P-CMM®), Version 2.0", Software Engineering Institute, Carnegie Mellon University, 2001.
  34. Carnegie Mellon, Software Engineering Institute, Welcome to the CMMI® Web Site, Carnegie Mellon, Software Engineering Institute, http://www.sei.cmu.edu/cmmi/cmmi.html, 2004.
  35. Garvin, D. A., "What does 'Product Quality' really mean?", Sloan Management Review, no. 1, pp. 25-43, 1984.
  36. *Corresponding author.