ISO/IEC 25010:2011
Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models
Ingénierie des systèmes et du logiciel — Exigences de qualité et évaluation des systèmes et du logiciel (SQuaRE) — Modèles de qualité du système et du logiciel
-
ISO/IEC 9126-1: Software Engineering - Product quality - Part 1: Quality model
(Génie du logiciel - Qualité des produits - Partie 1 : modèle de qualité) -
ISO/IEC TR 9126-2: Software Engineering - Product quality - Part 2 External metrics
(Génie du logiciel - Qualité des produits - Partie 2 : métrologie externe) -
ISO/IEC TR 9126-3: Software Engineering - Product quality - Part 3 Internal metrics
(Génie du logiciel - Qualité des produits - Partie 3 : métrologie interne) -
ISO/IEC TR 9126-4: Software Engineering - Product quality - Part 4: Quality in use metrics
(Génie du logiciel - Qualité des produits - Partie 4 : métriques de fonctionnement)
-
Functionality
Are the required functions available in the software?
A set of attributes that bear on the existence of a set of functions and their specified properties. The functions are those that satisfy stated or implied needs.-
Suitability
Attributes of software that bear on the presence and appropriateness of a set of functions for specified tasks. -
Accurateness
Attributes of software that bear on the provision of right or agreed results or effects. -
Interoperability
Attributes of software that bear on its ability to interact with specified systems.
Note: Interoperability is used in place of compatibility in order to avoid possible ambiguity with replaceability. -
Compliance
Attributes of software that make the software adhere to application related standards or conventions or regulations in laws and similar prescriptions. -
Security
Attributes of software that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs or data.
-
Suitability
-
Reliability
How reliable is the software?
A set of attributes that bear on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
Note: Wear or ageing does not occur in software. Limitations in reliability are due to faults in requirements, design and implementation. Failures due to these faults depend on the way the software product is used and the program options selected rather than on elapsed time.-
Maturity
Attributes of software that bear on the frequency of failure by faults in the software. -
Fault tolerance
Attributes of software that bear on its ability to maintain a specified level of performance in case of software faults or of infringement of its specified interface. -
Recoverability
Attributes of software that bear on the capability to re-establish its level of performance and recover the data directly affected in case of a failure and on the time and effort needed for it.
-
Maturity
-
Usability
Is the software easy to use?
A set of attributes that bear on the effort needed for use, and on the individual assessment of such use, by a stated or implied set of users.
Note 1: `Users' may be interpreted as most directly meaning the users of interactive software. Users may include operators, end users and indirect users who are under the influence or dependent on the use of the software. Usability must address all of the different user environments that the software may affect, which may include preparation for usage and evaluation of results.
Note 2: Usability defined in this International Standard as a specific set of attributes of software product differs from the definition from an ergonomic point of view, where other characteristics such as efficiency and effectiveness are also seen as constituents of usability.-
Understandability
Attributes of software that bear on the users' effort for recognizing the logical concept and its applicability. -
Learnability
Attributes of software that bear on the users' effort for learning its application. -
Operability
Attributes of software that bear on the users' effort for operation and operation control.
-
Understandability
-
Efficiency
How efficient is the software?
A set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used, under stated conditions.
Notes: Resources may include other software products, hardware facilities, materials, (e.g. print paper, floppy disks) and services of operating, maintaining or sustaining staff.-
Time behavior
Attributes of software that bear on response and processing times and on throughput rates in performances its function. -
Resource behavior
Attributes of software that bear on the amount of resource used and the duration of such use in performing its function.
-
Time behavior
-
Maintainability
How easy is to modify the software?
A set of attributes that bear on the effort needed to make specified modifications.
Note: Modifications may include corrections, improvements or adaptation of software to changes in environment, and in requirements and functional specifications.-
Analyzability
Attributes of software that bear on the effort needed for diagnosis of deficiencies or causes of failures, or for identification of parts to be modified. -
Changeability
Attributes of software that bear on the effort needed for modification, fault removal or for environmental change. -
Stability
Attributes of software that bear on the risk of unexpected effect of modifications. -
Testability
Attributes of software that bear on the effort needed for validating the modified software.
-
Analyzability
-
Portability
How easy is to transfer the software to another environment?
A set of attributes that bear on the ability of software to be transferred from one environment to another.
Note: The environment may include organizational, hardware or software environment.-
Adaptability
Attributes of software that bear on the opportunity for its adaptation to different specified environments without applying other actions or means than those provided for this purpose for the software considered. -
Installability
Attributes of software that bear on the effort needed to install the software in a specified environment. -
Conformance
Attributes of software that make the software adhere to standards or conventions relating to portability. -
Replaceability
Attributes of software that bear on opportunity and effort using it in the place of specified other software in the environment of that software.
Note 1: Replaceability is used in place of compatibility in order to avoid possible ambiguity with interoperability.
Note 2: Replaceability with a specific software does not imply that this software is replaceable with the software under consideration.
Note 3: Replaceability may include attributes of both installability and adaptability. The concept has been introduced as a subcharacteristic of its own because of its importance.
-
Adaptability