Chapter 3 Software Quality Requirements
After completing this chapter, you will be able to:
- – describe the history of the concepts conveyed by software quality models;
- – understand the different characteristics and sub-characteristics of software quality as outlined in the ISO 25010 international standard;
- – use the concepts to specify the software quality requirements of a software product;
- – explain the positive and negative interaction between the quality characteristics of software as described in the ISO 25010 international standard;
- – understand the concept of software traceability.
3.1 Introduction
All software is an element of a system, whether it be a computer system in which the software may be used on a personal computer, or in an electronic consumer product like a digital camera. The needs or requirements of these systems are typically documented either in a request for quote (RFQ) or request for proposal (RFP) document, a statement of work (SOW), a software requirements specification (SRS) document or in a system requirements document (SRD). Using these documents, the software developer must extract the information needed to define specifications for both the functional requirements and performance or non-functional requirements required by the client. The term “non-functional,” as applied to requirements, is deprecated and is not used in the Institute of Electrical and Electronics Engineers (IEEE) 730 standard [IEE 14].
Get Software Quality Assurance now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
