Customer Service:
Mon - Fri: 8:30 am - 6 pm EST

Product Quality

Product quality software engineering standards are published by ISO and IEC. They cover measurement of system and software quality and measurement of quality in use.


ISO/IEC 25023:2016

Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - Measurement of system and software product quality

ISO/IEC 25023:2016 defines quality measures for quantitatively evaluating system and software product quality in terms of characteristics and subcharacteristics defined in ISO/IEC 25010 and is intended to be used together with ISO/IEC 25010. It can be used in conjunction with the ISO/IEC 2503n and the ISO/IEC 2504n standards or to more generally meet user needs with regard to software product or system quality. ISO/IEC 25023:2016 contains the following: - a basic set of quality measures for each characteristic and subcharacteristics; - an explanation of how to apply software product and system quality measures. It includes, as informative annexes, considerations for the use of quality measures (Annex A), QMEs used to define product or system quality measures (Annex B), and detailed explanation of measurement types (Annex C). ISO/IEC 25023:2016 does not assign ranges of values of the measures to rated levels or to grades of compliance because these values are defined based on the nature of the system, product or a part of the product, and depending on factors such as category of the software, integrity level, and users' needs. Some attributes could have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors. The proposed quality measures are primarily intended to be used for quality assurance and improvement of system and software products during or post the development life cycle process. The main users of ISO/IEC 25023:2016 are people carrying out quality requirement specification and evaluation activities as part of the following: - development: including requirements analysis, design specification, coding and testing through acceptance during the life cycle process; - quality management: systematic examination of the software product or computer system, for example, when evaluating system or software product quality as part of quality assurance, quality control and quality certification; - supply: a contract with the acquirer for the supply of a system, software product or software service under the terms of a contract, for example, when validating quality at qualification test; - acquisition: including product selection and acceptance testing, when acquiring or procuring a system, software product or software service from a supplier; - maintenance: improvement of the software product or system based on quality measurement.


ISO/IEC 25022:2016

Systems and software engineering - Systems and software quality requirements and evaluation (SQuaRE) - Measurement of quality in use

ISO/IEC 25022:2016 defines quality in use measures for the characteristics defined in ISO/IEC 25010, and is intended to be used together with ISO/IEC 25010. It can be used in conjunction with the ISO/IEC 2503n and the ISO/IEC 2504n standards or to more generally meet user needs with regard to product or system quality. ISO/IEC 25022:2016 contains the following: - a basic set of measures for each quality in use characteristic; - an explanation of how quality in use is measured. It provides a suggested set of quality in use measures to be used with the quality in use model in ISO/IEC 25010. They are not intended to be an exhaustive set. It includes as informative annexes examples of how to measure context coverage (Annex A), options for normalising quality in use measures (Annex B), use of ISO/IEC 25022 for measuring usability in ISO 9241 11 (Annex C), a quality in use evaluation process (Annex D), the relationship between different quality models (Annex E), and quality measurement concepts (Annex F). The measures are applicable to the use of any human-computer system, including both computer systems in use and software products that form part of the system. It does not assign ranges of values of the measures to rated levels or to grades of compliance because these values are defined for each system or product depending, on the context of use and users' needs. Some attributes could have a desirable range of values, which does not depend on specific user needs but depends on generic factors, for example, human cognitive factors. The proposed quality in use measures are primarily intended to be used for quality assurance and management of systems and software products based on their effects when actually used. The main users of the measurement results are people managing development, acquisition, evaluation, or maintenance of software and systems. The main users of ISO/IEC 25022:2016 are people carrying out specification and evaluation activities as part of the following: - development: including requirements analysis, design, and testing through acceptance during the life cycle process; - quality management: systematic examination of the product or computer system, for example, when evaluating quality in use as part of quality assurance and quality control; - supply: a contract with the acquirer for the supply of a system, software product, or software service under the terms of a contract, for example, when validating quality at qualification test; - acquisition: including product selection and acceptance testing, when acquiring or procuring a system, software product, or software service from a supplier; - maintenance: improvement of the product based on quality in use measures.


ANSI Logo

As the voice of the U.S. standards and conformity assessment system, the American National Standards Institute (ANSI) empowers its members and constituents to strengthen the U.S. marketplace position in the global economy while helping to assure the safety and health of consumers and the protection of the environment.

CUSTOMER SERVICE
NEW YORK OFFICE
ANSI HEADQUARTERS