• Gerard O’Regan
Part of the Undergraduate Topics in Computer Science book series (UTICS)


The mission of a software company is to develop high-quality innovative products and services at a competitive price to its customers, and to do so ahead of its competitors. This requires a clear vision of the business, a culture of innovation, an emphasis on quality, detailed knowledge of the business domain, and a sound product development strategy.

Customers today have very high expectations on quality, and expect high-quality software products to be consistently delivered on time. The focus on quality requires that the organization define a sound software development infrastructure to enable quality software to be consistently produced.

This chapter discusses the fundamentals of software quality and includes a brief history of the quality field including the work of pioneers such as Deming, Juran and Crosby. The contribution of Watts Humphrey who is considered the father of software quality is discussed, as well as a brief discussion of important topics in the software quality field such as software inspections and testing; software process improvement; metrics and problem solving; appraisals; customer satisfaction, and the cost of quality.


Customer Satisfaction Control Chart Software Quality Total Quality Management Statistical Process Control 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 2.
    Basili V, Rombach H (1988) The TAME project. Towards improvement-oriented software environments. IEEE Trans Softw Eng 14(6):758–773CrossRefGoogle Scholar
  2. 10.
    Brooks F (1975) The mythical man month. Addison Wesley, ReadingGoogle Scholar
  3. 11.
    Brooks F (1986) No silver bullet. Essence and accidents of software engineering. In: Information processing. Elsevier, AmsterdamGoogle Scholar
  4. 14.
    Crosby P (1979) Quality is free. The art of making quality certain. McGraw Hill, New YorkGoogle Scholar
  5. 15.
    Deming WE (1986) Out of crisis. MIT Press, Cambridge, MAGoogle Scholar
  6. 20.
    Fagan M (1976) Design and code inspections to reduce errors in software development. IBM Syst J 15(3):182–210CrossRefGoogle Scholar
  7. 23.
    Gilb T (1976) Software metrics. Winthrop Publishers, Inc., CambridgeGoogle Scholar
  8. 29.
    Humphry W (1989) Managing the software process. Addison-Wesley, ReadingGoogle Scholar
  9. 31.
    ISO/IEC (1991) ISO/IEC 9126: Information Technology. Software Product Evaluation: quality characteristics and guidelines for their use. ISO/IEC, GenevaGoogle Scholar
  10. 33.
    Juran J (1951) Juran’s quality handbook. McGraw Hill, New YorkGoogle Scholar
  11. 38.
    Lions JL (1996) Ariane 5. Flight 501. Failure report by enquiry board, The MathWorks, Inc., NatickGoogle Scholar
  12. 41.
    Manley E (1995) Taurus: how I lived to tell the tale. Am Program Softw Fail 8:17MathSciNetGoogle Scholar
  13. 40.
    Manns T, Coleman M (1996) Software quality assurance. Macmillan Press Ltd., HampshireGoogle Scholar
  14. 58.
    Shewhart W (1931) The economic control of manufactured products. Van Nostrand, New YorkGoogle Scholar
  15. 64.
    Standish Group (1999) Estimating: art or science. Featuring Morotz Cost Expert. Standish Group Research NoteGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Gerard O’Regan
    • 1
  1. 1.SQC ConsultingMallowIreland

Personalised recommendations