Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — Quality requirements framework
Introduction: It is important to identify and specify quality requirements as part of system, software and data requirements, because finding the right balance of quality requirements, in addition to well-specified functional requirements, is a critical success factor to meet the stakeholders' objectives. Quality requirements are needed for: — specifying the system, including contractual agreements and call for tender; — planning the project, including feasibility analysis; — developing the system, including identification of architecture drivers or potential quality problems during development; and — evaluating the system, including objective assessment and certification of quality. This document focuses on defining, using and governing quality requirements. If not clearly defined, they can be viewed, interpreted, implemented and evaluated differently by the relevant stakeholders. This can result in systems that are inconsistent with user expectations and of poor quality; and time and cost overruns to rework the system. Therefore quality requirements for the system need to be specified clearly at the earliest stage of the development or acquiring process as possible, to provide a critical input to the development or acquisition. This document can be used to improve the quality of quality requirements, by providing requirements and recommendations for them, and provides guidance for the steps used to define and use them. Quality requirements can be categorized into characteristics/subchara
Scope: This document provides the framework for quality requirements for systems, software products and data, which includes concept of the quality requirements, and requirements and recommendations for the processes and methods to elicit, define, use and govern them. Intended readers of this document include, but are not limited to: — acquirers: evaluate if the system/software products/data fulfills their value proposition, i.e., meets the expected quality, — developers: design, implement and test the system/software products/data to ensure that it meets the expected quality, — testers: verify and validate that the system/software products/data meets the expected quality, — project managers: plan, monitor and control the achievement of the expected quality, and — independent evaluators: evaluate the system/software products/data with the objective criteria. This document complies with the technical processes defined in ISO/IEC/IEEE 15288, which are relevant for elicitation of stakeholders’ quality needs and for defining, analyzing and maintaining quality requirements. In this document, the quality models in ISO/IEC 25010 and ISO/IEC 25012 are used to categorize quality requirements and to provide a basis for quantifying them in terms of quality measures in the quality measure division of ISO/IEC 2502n. This document does not cover specification of the other requirements (such as functional requirements, process requirements, etc.), and prescribes neither any specific quality measure nor any specific development process.