ISO/IEC DIS 25000-2:2026(en)

ISO/IEC TC JTC 1/SC 7/WG 6

Secretariat: BIS

Date: 2025-12-23

Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Part 2: Vocabulary

© ISO/IEC 2026

All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester.

ISO copyright office

CP 401 • Ch. de Blandonnet 8

CH-1214 Vernier, Geneva

Phone: +41 22 749 01 11

Email: copyright@iso.org

Website: www.iso.org

Published in Switzerland

Contents

Foreword v

Introduction vi

1 Scope 1

2 Normative references 1

3 Terms and definitions 1

3.1 Terms related to quality 1

3.2 Terms related to quality model constructs 2

3.3 Terms related to entity 3

3.4 Terms related to roles 4

3.5 Terms related to quality measurement 5

3.6 Terms related to quality requirements 8

3.7 Terms related to quality engineering 8

3.8 Terms related to quality evaluation 8

4 Abbreviated terms 10

Annex A (informative) Categories of Terms and Structure of Clauses for Terms and Definitions 11

Annex B (informative) How Terms Are Selected from the Existing SQuaRE Standards 12

Annex C (informative) Guidance for Understanding Terms and Definitions in SQuaRE Documents 14

Bibliography 15

Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

ISO draws attention to the possibility that the implementation of this document may involve the use of (a) patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s) which may be required to implement this document. However, implementers are cautioned that this may not represent the latest information, which may be obtained from the patent database available at www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.

This document was prepared by Joint Technical Committee ISO/TC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

Communication is important in the implementation and operation of Systems and software Quality Requirements and Evaluation (SQuaRE). This communication will be most effective if there is a common understanding of the terms used.

To simplify the harmonization of terms and definitions in the field of Systems and software Quality Requirements and Evaluation (SQuaRE), each terminological entry in this document contains a generic term and its definition. Notes to entry and examples have been included only in a few cases to provide additional information or clarification.

This document has been developed in close cooperation with the committees and working groups involved in the development and revision of the SQuaRE family of International Standards. A list of published documents in the SQuaRE family of International Standards is presented in the Bibliography.

The purpose of this document is:

— To improve the reader's convenience by listing terms and their definitions in a single document, rather than spreading them across the SQuaRE family of International Standards,

— To ease the terminology-related maintenance problem by gathering the important terms common to the documents in the SQuaRE family into this document, minimizing the reference relationships, and

— To serve as the source to ISO/IEC/IEEE 24765, the common terminology standard of systems and software engineering, for the latest SQuaRE family terminologies.

This document is intended to be used in conjunction with the other documents in the SQuaRE family of International Standards.

In the organization of the SQuaRE family of International Standards, similar standards are grouped into divisions. Each division provides guidance and resources for performing a different function in ensuring system and software product quality. This document belongs to the quality management division, and extracts vocabulary related parts from ISO/IEC 25000:2014 and compiles terms defined in each standard developed by the working group in the SQuaRE family of International Standards.

This document is a part of the SQuaRE family of International Standards. The divisions within the SQuaRE family are as follows:

— ISO/IEC 2500n – Quality Management Division. These International Standards define common models, terms, and definitions referred to by other SQuaRE standards. This division provides requirements and guidance for supporting functions that are responsible for the management of requirements, specification, and evaluation of software product quality. Practical guidance on the use of the quality models is also provided.

— 25000: Guide to SQuaRE

— 25000-2: Vocabulary

— 25001: Planning and management

— 25002: Quality model overview and usage

— ISO/IEC 2501n – Quality Model Division. The International Standards within this division present quality models for computer systems and software products, data, IT services and quality-in-use.

— 25010: Product quality model

— 25011: Service quality models

— 25012: Data quality model

— 25019: Quality-in-use model

— ISO/IEC 2502n – Quality Measurement Division. These International Standards define a quality measurement framework, mathematical definitions of quality measures, and practical guidance for their application. Examples are given of quality measures for internal and external properties of products, data, IT services and quality-in-use. Quality Measure Elements (QME) forming foundations for quality measures for internal and external product properties are defined.

— 25020: Quality measurement framework

— 25021: Quality measure elements

— 25022: Measurement of quality in use

— 25023: Measurement of system and software product quality

— 25024: Measurement of data quality

— 25025: Measurement of IT service quality

— ISO/IEC 2503n – Quality Requirements Division. These International Standards specify quality requirements based on quality models and quality measures. These quality requirements can be used in the process of eliciting quality requirements for information systems and IT services to be developed or as input for an evaluation process.

— 25030: Quality requirements framework

— ISO/IEC 2504n – Quality Evaluation Division. These International Standards define requirements, recommendations and guidelines for software product evaluation and for documenting a measure as an evaluation module.

— 25040: Quality evaluation framework

— 25041: Evaluation guide for developers, acquirers and independent evaluators

— ISO/IEC 25050 to 25099 SQuaRE Extension Division. These International Standards define requirements for quality of ready-to-use software products, approaches to testing and requirements for quality of commercial-off-the-shelf software, common industry formats for usability reports, and quality models and measures for new technologies such as cloud and artificial intelligence. This International Standard defines a framework for quality engineering, which exists within the SQuaRE Extension Division.

— 25051: Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing

— 25052-1: cloud services — Part 1: Quality model

— 25052-2: cloud services — Part 2: Quality Measurement

SQuaRE standards can be used in conjunction with ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. SQuaRE standards can also be used in conjunction with ISO/IEC 15504 and ISO/IEC 33000, which are concerned with software process assessment to support quality review, verification, and validation and establishing quantitative quality characteristics. SQuaRE standards can also be used in conjunction with ISO 9001 or ISO/IEC/IEEE 90003 to support design reviews, verification, validation, and establishing of a management system for use within an organization.

Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Part 2: Vocabulary

This document provides the terms and definitions that constitute the conceptual framework related to quality as addressed in the Systems and Software Quality Requirements and Evaluation (SQuaRE) family of standards. It focuses on the fundamental concepts and terminology that are common across the SQuaRE family to ensure consistency and to facilitate understanding.

Terms and definitions specific to individual quality models — such as product quality, data quality, IT service quality, and quality-in-use — are outside the scope of this document.

Similarly, terms related to other types of qualities, such as process quality or AI-related quality, are not included.

There are no normative references for this document.

For the purposes of this document, the following terms and definitions apply.

ISO, IEC, and IEEE maintain terminology databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at https://www.iso.org/obp

— IEC Electropedia: available at https://www.electropedia.org/

— IEEE Standards Dictionary Online: available at: https://dictionary.ieee.org/

NOTE 1 All important definitions common to the SQuaRE family documents are found in this document. These definitions are not reproduced in the other SQuaRE documents for maintainability.

NOTE 2 Definitions for other system and software engineering terms can be found in ISO/IEC/IEEE 24765, available at www.computer.org/sevocab.

NOTE 3 Annex A provides the categories of terms and structure of clauses for terms and definitions.

NOTE 4 Annex B provides guidelines for selecting and classifying terms from the existing SQuaRE Standards.

NOTE 5 The terms defined in ISO/IEC/IEEE 15288:2023 and ISO/IEC/IEEE 12207:2017 are considered as default references in the SQuaRE family of standards, and are therefore omitted here.

3.1.1

quality

degree to which the target entity (3.3.11) satisfies or exceeds stakeholders (3.4.8)’ stated and implied needs (3.6.3)

3.1.2

quality-in-use

extent to which the target entity (3.3.11) when it is used in a specified context of use (3.2.2), satisfies or exceeds stakeholder (3.4.8) needs to achieve specified beneficial goals or outcomes

Note 1 to entry: Beneficial goals can be stated as targets, in predefined conditions with managed economic, environmental, organisational, and societal risks.

3.2.1

attribute

inherent property or characteristic of an entity (3.3.4) that can be distinguished quantitatively or qualitatively by human or automated means

3.2.2

context of use

combination of users, goals and tasks, resources, and environment

Note 1 to entry: The "environment" in a context of use includes the technical, physical, social, cultural and organisational environments.

[SOURCE: ISO 9241-11:2018, 3.1.15]

3.2.3

quality characteristic

category of quality (3.1.1)  attributes (3.2.1) that bears on the quality (3.1.1) of the target entity (3.3.11)

Note 1 to entry: Quality characteristics can be further divided into quality sub-characteristics. While characteristics typically represent one aspect of quality that is of interest to stakeholders, quality sub-characteristics can help subdivide quality characteristics into individual aspects that help map them to quality properties.

3.2.4

quality model

defined set of characteristics and of relationships between them, which provides a framework for specifying quality requirements (3.6.4) and evaluating the quality (3.1.1)

3.2.5

quality property

property of a target entity (3.3.11) that is related to a quality measure element (3.5.11), and which can be quantified by a measurement method (3.5.9)

Note 1 to entry: Quality properties can be used either in measurement of quality or just for providing qualitative feedback.

3.2.6

quality sub-characteristic

set of one or more quality (3.1.1) properties that represent a unique aspect of a quality characteristic (3.2.3)

3.2.7

quality sub-sub-characteristic

subdivision of a quality sub-characteristic (3.2.6) established by the user of a quality model (3.2.4) to provide more granular representation of the quality (3.1.1) attributes (3.2.1) of a target entity (3.3.11)

3.3.1

component

entity (3.3.4) with discrete structure, such as an assembly or software module, within a system considered at a particular level of analysis

Note 1 to entry: ICT products are composed from multiple entities including sub-ICT products, hardware, firmware, communication infrastructure, software, software components, and data

[SOURCE: ISO/IEC 19770-5:2015, modified — The term has been changed from "software component" to "component"; the original note 1 to entry has been replaced by a new one.]

3.3.2

data

reinterpretable representation of information in a formalized manner suitable for communication, interpretation, or processing

Note 1 to entry: Data can be processed by humans or by automatic means.

3.3.3

deliverable product

any unique and verifiable product used to perform a service that is subject to approval by the project sponsor or customer

3.3.4

entity

anything (physical or non-physical) having a distinct existence

[SOURCE: ISO/IEC 15459-3:2014, 3.1]

3.3.5

information and communication technology product

ICT product

requirement resulting from adoption of some information and communication technologies (ICTs) technical solutions in the design process

Note 1 to entry: ICT technical solutions include web-based technologies, cloud servers, and so on.

3.3.6

information system

system that is comprised of software, hardware, communication facilities, data (3.3.2), and the people who use it (users) in a given environment (user and system environment) to satisfy their information processing needs (goals)

Note 1 to entry: While information systems can be part of larger systems that include other electro-mechanical products and their users, this document considered these components as part of the context of use of the system only if they have a direct relevant relationship to the ICT products and users who are part of the information system. However, many of the quality attributes can be applied to these larger systems of systems as well.

Note 2 to entry: The quality-in-use model can be used as a guide to represent the user's expectations about the system's behaviour.

Note 3 to entry: Users of the quality-in-use includes direct and indirect users. When applied to direct users, quality-in-use appears as "effect"; and when applied to other stakeholders it appears as "influence".

3.3.7

information technology service

IT service

service that makes use of IT systems as tools to provide value to an individual user or a business by facilitating results the user or business wants to achieve

Note 1 to entry: IT services can be delivered remotely by people, or by an IT application that could be in a local or remote location.

3.3.8

Information technology service system

IT service system

system that is comprised of an IT service and the people who use it (users) in a given environment to satisfy their service needs

3.3.9

intermediate product

system or software product of the development process that is used as inputs to other stages of the development process

3.3.10

IT service provision system

system to provide IT service to users, including people, processes, technology, facilities and information

3.3.11

target entity

fundamental thing of relevance to the user, which can be measured and evaluated

Note 1 to entry: Target entities include ICT products and their components addressed by the product quality model, IT services addressed by the IT service quality model, and data addressed by the data quality model.

3.4.1

direct user

person who interacts with the product

Note 1 to entry: This includes primary users who use the system to achieve their goals and secondary users like content providers, system managers, administrators, operators and installers.

3.4.2

evaluator

person or organisation engaged in the verification or validation of the target entity (3.3.11)

3.4.3

indirect user

person who receives output from a system, but does not interact with the system

EXAMPLE: business managers, acquirers, product managers

3.4.4

primary user

user who interacts with the system to achieve the primary goals

3.4.5

secondary user

user who interacts with the product to support the primary users (3.4.4)

EXAMPLE: a) content provider, system manager, administrator, security manager; b) maintainer, analyser, porter, installer.

3.4.6

service provider

organisation that manages and delivers a service or services to customers

[SOURCE: ISO/IEC 20000-10:2018, 3.2.24]

3.4.7

society

people in general, living together in communities or in geo-political defined areas

Note 1 to entry: Society means civil society used in Sustainable Development Goals (SDGs) and geo-political society, i.e. society at large.

3.4.8

stakeholder

person or organisation that can affect, be affected by, or perceive itself to be affected by the target entity (3.3.11)

EXAMPLE: Stakeholders include customers, users, developers, maintainers, system integrators, business analysts, vendor and acquisition managers, product managers, business managers and responsible parties, independent evaluators, data owners, IT service providers, trainers, auditors, regulatory bodies, and other people affected by the system.

Note 1 to entry: Some stakeholders can have interests that oppose each other or oppose the system.

[SOURCE: ISO 9000:2015, modified — "a decision or activity" has been replaced by "the target entity"]

3.5.1

base measure

measure defined in terms of an attribute (3.2.1) and the method for quantifying it

Note 1 to entry: A base measure is functionally independent of other measures.

Note 2 to entry: Based on the definition of "base quantity" in the International Vocabulary of Metrology — Basic and General Concepts and Associated Terms, 2012.

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.3]

3.5.2

derived measure

measure defined as a function of two or more values of base measures (3.5.1)

Note 1 to entry: Adapted from the definition of "derived quantity" in the International Vocabulary of Metrology — Basic and General Concepts and Associated Terms, 2012.

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.8]

3.5.3

indicator

measure that provides an estimate or evaluation of specified attributes (3.2.1) derived from a model with respect to defined information needs (3.5.4)

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.10]

3.5.4

information need

insight necessary to manage objectives, goals, risks and problems

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.12]

3.5.5

measure, noun

variable to which a value is assigned as the result of measurement (3.5.7)

Note 1 to entry: The plural form "measures" is used to refer collectively to base measures, derived measures, and indicators.

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.15]

3.5.6

measure, verb

make a measurement (3.5.7)

3.5.7

measurement

set of operations having the object of determining a value of a measure

Note 1 to entry: Measurement can include assigning a qualitative category such as the language of a source program (C, C++, Ruby, etc.).

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.17, modified — The original note 1 to entry has been replaced by a new one.]

3.5.8

measurement function

algorithm or calculation performed to combine two or more base measures (3.5.1)

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.20]

3.5.9

measurement method

logical sequence of operations, described generically, used in quantifying an attribute (3.2.1) with respect to a specified scale

Note 1 to entry: The type of measurement method depends on the nature of the operations used to quantify an attribute. Two types can be distinguished: — subjective: quantification involving human judgment; — objective: quantification based on numerical rules.

Note 2 to entry: Based on the definition of "method of measurement" in the International Vocabulary of Metrology — Basic and General Concepts and Associated Terms, 2012.

[SOURCE: ISO/IEC/IEEE 15939:2017, 3.21]

3.5.10

quality measure

derived measure (3.5.2) that is defined as a measurement function (3.5.8) of two or more values of quality measure elements (3.5.11)

Note 1 to entry: Quality measures can be considered as derived properties of an ICT product or information system.

Note 2 to entry: Inherent (structural) quality measures quantify structural properties of the ICT product or information system, while behavioural quality measures quantify properties that can be identified and measured on the ICT product or information system as a whole and its behaviour in a context of use.

3.5.11

quality measure element

measure defined in terms of a property and the measurement method (3.5.9) for quantifying it, including optionally the transformation by a mathematical function

3.5.12

quality measure on external property

QM on external property

measure of the degree to which a system or software product enables its behaviour to satisfy stated and implied needs (3.6.3) for the system including the software to be used under specified conditions

Note 1 to entry: Attributes of the behaviour can be measured, verified and/or validated by executing the system or software product during testing and operation.

EXAMPLE: The failure density against test cases found during testing is a quality measure on external property related to the number of faults present in the computer system. The two measures are not necessarily identical since testing cannot find all faults, and a fault can give rise to apparently different failures in different circumstances.

3.5.13

quality measure on internal property

QM on internal property

measure of the degree to which a set of static attributes (3.2.1) of a software product satisfies stated and implied needs (3.6.3) for the software product to be used under specified conditions

Note 1 to entry: Static attributes include those that relate to the software architecture, structure and its components, data structure and its formats, structure and appearance of graphical display on screen and menus for users or recipients of service.

Note 2 to entry: Static attributes can be verified by review, inspection, simulation and/or automated tools.

Note 3 to entry: Quality measures on internal property are typically associated with quality requirements on static properties and attributes that can be specified in or derived from requirements.

EXAMPLE: Complexity measures and the number, severity, and failure frequency of faults found in a walkthrough are typical quality measures on internal property made on the product itself.

3.5.14

repeatability (of results of measurement)

closeness of the agreement between the results of successive measurements (3.5.7) of the same measurand carried out under the same conditions of measurement (3.5.7)

3.5.15

reproducibility (of results of measurement)

closeness of the agreement between the results of measurements (3.5.7) of the same measurand carried out under changed conditions of measurement (3.5.7)

Note 1 to entry: Repeatability and reproducibility can be expressed quantitatively in terms of the dispersion characteristics of the results.

3.6.1

deployment (of requirements)

translation and elaboration of requirements from one type of requirements to another in the same system level

Note 1 to entry: Types of requirements include quality-in-use requirements, product quality requirements and data requirements.

3.6.2

derivation (of requirements)

requirement originated from its application domain

3.6.3

implied need

need that has not been stated but is an actual need

Note 1 to entry: Some implied needs only become evident when the software product is used in particular conditions (context of use).

EXAMPLE: Implied needs include needs not stated but implied by other stated needs, and needs not stated because they are considered to be evident or obvious.

3.6.4

quality requirement

requirement for quality (3.1.1) properties or attributes (3.2.1) of a product, data (3.3.2) or service that satisfy needs which ensue from the purpose for which that product, data (3.3.2) or service is to be used

3.6.5

technical product quality requirement

product quality requirement (3.6.4) on its technically identified properties which are used in its development and maintenance processes

3.7.1

architecture

fundamental concepts or properties of a system in its environment embodied in its elements, relationships, and in the principles of its design and evolution

[SOURCE: ISO/IEC/IEEE 42010:2022]

3.8.1

assessment

action of comprehensively evaluating the target entity (3.3.11) based on documented criteria for a specific purpose

Note 1 to entry: Such purposes can include determining acceptance or release of the target entity.

3.8.2

conformity evaluation

systematic examination of the extent to which a product, process or service fulfils specified requirements

3.8.3

evaluation record

documented objective evidence of all activities performed and of all results achieved within the evaluation process

3.8.4

integrity level

degree of confidence that the system-of-interest meets the associated integrity level claim (3.8.5)

Note 1 to entry: An integrity level is different from the likelihood that the integrity level claim is met but they are closely related.

Note 2 to entry: The word “confidence” implies that the definition of integrity levels is a subjective concept.

Note 3 to entry: In this document, integrity levels are defined in terms of risk and hence cover safety, security, financial and any other dimension of risk that is relevant to the system-of-interest.

[SOURCE: ISO/IEC 15026-3:2023 —note 1 to entry has been deleted]

3.8.5

integrity level claim

proposition representing a requirement on a risk reduction measure identified in the risk treatment process of the system-of-interest

[SOURCE: ISO/IEC 15026-3:2023]

3.8.6

measurement source

set of artifacts used for quality measures (3.5.10) when performing a quality evaluation (3.8.9)

3.8.7

pass/fail criteria

decision rules that specify acceptable and unacceptable results of a test applied to the target entity (3.3.11)

3.8.8

quality analysis

interpretation of rating (3.8.11) results for multiple quality (3.1.1) properties to determine the objective score or acceptability of the quality (3.1.1) of the target entity (3.3.11)

3.8.9

quality evaluation

systematic examination of the extent to which an entity (3.3.4) is capable of fulfilling specified requirements

[SOURCE: ISO/IEC/IEEE 24765:2017]

3.8.10

quality rating module

set of quality measures (3.5.10), operational environment, and methods for conducting quality (3.1.1)  measurements (3.5.7) and quality (3.1.1)  ratings (3.8.11) on a specific category of target entities

3.8.11

rating

action of mapping the measured value to the appropriate rating level (3.8.12)

Note 1 to entry: It is used to determine the rating level associated with the target entity for a specific quality characteristic.

3.8.12

rating level

scale point on an ordinal scale used to categorise a measurement (3.5.7) result

Note 1 to entry: The rating level enables software product to be classified (rated) in accordance with the stated or implied needs.

Note 2 to entry: Appropriate rating levels can be associated with the different views of quality i.e. Users', Managers' or Developers'.

1. 
   (informative)
   
   Categories of Terms and Structure of Clauses for Terms and Definitions

The terms in this document are organized in Clause 3 according to categories that reflect their roles and relationships in the SQuaRE family of standards.

These categories include quality, quality model constructs, target entities, stakeholders, and activities related to quality, such as quality measurement, quality requirements definition, quality engineering, and quality evaluation.

The subclause headings correspond to these categories — for example, types of quality, entity, role, quality measurement, quality requirement, quality engineering, and quality evaluation.

Within each category, terms are arranged in alphabetical order.

NOTE: SQuaRE includes a division for quality management. Although quality management is clearly one of the activities related to quality, it was not included as a separate term category in this document because no corresponding terms exist in the current SQuaRE family standards.

These categories include quality, quality model constructs, target entities, stakeholders, and activities related to quality, such as quality measurement, quality requirements definition, quality engineering, and quality evaluation.

The subclause headings correspond to these categories — for example, types of quality, entity, role, quality measurement, quality requirement, quality engineering, and quality evaluation.

Within each category, terms are arranged in alphabetical order.

The terms defined in this subclause are not intended to be normatively referenced or modified when developing or revising other SQuaRE family standards.

1. 
   (informative)
   
   How Terms Are Selected from the Existing SQuaRE Standards

Table B.1 — Classification and Selection of Terms from the SQuaRE Standards

NOTE 1: The term, definition, note, and source have been reviewed and revised when necessary.

NOTE 2: For categories a and b, the Source have been omitted.

1. 
   (informative)
   
   Guidance for Understanding Terms and Definitions in SQuaRE Documents

When reading individual standards in the SQuaRE family, readers encounter terms and definitions that are specific to each quality domain. For consistent interpretation across the SQuaRE family, refer to this document, which maintains key and common definitions shared among the SQuaRE standards.

This document is available as a freely accessible document on the ISO website. For shared or fundamental terms, the definitions in this document can be used as the authoritative reference.

Bibliography

[1] ISO 9000:2015, Quality management systems — Fundamentals and vocabulary

[2] ISO 9001, Quality management systems — Requirements

[3] ISO 9241‑11:2018, Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts

[4] ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processes

[5] ISO/IEC/IEEE 12207:2017, Systems and software engineering — Software life cycle processes

[6] ISO/IEC/IEEE 15939:2017, Systems and software engineering — Measurement process

[7] ISO/IEC 19770‑5:2015, Information technology — IT asset management — Part 5: Overview and vocabulary

[8] ISO/IEC/TR 12182:2015, Systems and software engineering — Framework for categorization of IT systems and software, and guide for applying it

[9] ISO/IEC/IEEE 24765, Systems and software engineering — Vocabulary

[10] ISO/IEC 25001:2014, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Planning and management

[11] ISO/IEC 25002:2024, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality model overview and usage

[12] ISO/IEC 25010:2023, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Product quality model

[13] ISO/IEC/TS 25011:2017, Information technology — Systems and software Quality Requirements and Evaluation (SQuaRE) — Service quality models

[14] ISO/IEC 25012, Software engineering — Software product Quality Requirements and Evaluation (SQuaRE) — Data quality model

[15] ISO/IEC 25019:2023, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality-in-use model

[16] ISO/IEC 25020:2019, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality measurement framework

[17] ISO/IEC 25021:2012, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality measure elements

[18] ISO/IEC 25022:2016, Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — Measurement of quality in use

[19] ISO/IEC 25023:2016, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of system and software product quality

[20] ISO/IEC 25024:2015, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of data quality

[21] ISO/IEC/TS 25025:2021, Information technology — Systems and software Quality Requirements and Evaluation (SQuaRE) — Measurement of IT service quality

[22] ISO/IEC 25030:2019, Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — Quality requirements framework

[23] ISO/IEC 25040:2024, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Quality evaluation framework

[24] ISO/IEC 25041:2012, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Evaluation guide for developers, acquirers and independent evaluators

[25] ISO/IEC 25051:2014, Software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — Requirements for quality of Ready to Use Software Product (RUSP) and instructions for testing

[26] ISO/IEC/TS 25052‑1:2019, Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE): cloud services — Part 1: Quality model

[27] ISO/IEC/TS 25052‑2:2024, Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE): cloud services — Part 2: Quality measurement

[28] ISO/IEC 15459‑3:2014, Information technology — Automatic identification and data capture techniques — Unique identification — Part 3: Common rules

[29] ISO/IEC 20000‑10:2018, Information technology — Service management — Part 10: Concepts and vocabulary

[30] ISO/IEC/IEEE 42010:2022, Software, systems and enterprise — Architecture description

[31] ISO/IEC/IEEE 15026‑3:2023, Systems and software engineering — Systems and software assurance — Part 3: System integrity levels