User:Malevan/sandbox
ISO/IEC 25010 System and Software Quality Models is an international standard for the evaluation of software quality.[1] It forms part of the SQuaRE (Software product Quality Requirements and Evaluation) set of standards, with numbers of the form ISO/IEC 250nn.[2] and replaced ISO/IEC 9126
The objective of the ISO/IEC 25010:2011 standard is to determine the quality characteristics that should be accounted for in the evaluation of software.
Product Quality Model[edit]
The ISO/IEC 25010 quality model itemises eight characteristics of software:
Functional Suitability[edit]
"Degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions"
With subcategories of:
- Functional completeness
- Functional correctness
- Functional appropriateness
Performance Efficiency[edit]
"Performance relative to the amount of resources used under stated conditions"
- Time behaviour
- Capacity
Compatibility[edit]
"The degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment"
- Co-existence
- Interoperability
Useability[edit]
"The degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use"
- Appropriateness recognizability
- Learnability
- Operability
- User error protection
- User interface aesthetics
- Accessibility
Reliability[edit]
"The degree to which a system, product or component performs specified functions under specified conditions for a specified period of time"
- Maturity
- Availability
- Fault tolerance
- Recoverability
Security[edit]
"The degree to which a product or system protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization"
- Confidentiality
- Integrity
- Non-repudiation
- Accountability
- Authenticity
Maintainability[edit]
"The degree of effectiveness and efficiency with which a product or system can be modified to improve it"
- Modularity
- Reusability
- Analysability
- Modifiability
- Testability
Portability[edit]
"The degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another"
- Adaptability
- Installability
- Replaceability
Quality in Use Model[edit]
The standard also includes a quality in use model composed of five characteristics (some of which are further subdivided into subcharacteristics) that relate to the human-computer system, including both computer systems in use and software products in use.
Containing five characteristics:
Effectiveness[edit]
"Accuracy and completeness with which users achieve specific goals"
Efficiency[edit]
"Resources expended in relation to the accuracy and completeness with which users achieve specific goals"
Satisfaction[edit]
"The degree to which user needs are satisfied when a product or system is used in a specific context of use"
This contains subcatorgories of
- usefulness,
- trust,
- pleasure,
- comfort
Freedom from Risk[edit]
"The degree to which a product or system mitigates the potential risk to economic status, human life, health, or the environment"
Containing subcategories of
- economic risk mitigation,
- health and safety risk mitigation, and
- environmental risk mitigation
Context Coverage[edit]
Containing subcategories of
- context completeness
- flexibility
History[edit]
ISO/IEC 9126 was issued on December 19, 1991.
On June 15, 2001, ISO/IEC 9126:1991 was replaced by ISO/IEC 9126:2001 (four parts 9126-1 to 9126-4).
On March 1, 2011, ISO/IEC 9126 was replaced by ISO/IEC 25010:2011 Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models.
Differences from ISO 9126[edit]
ISO 25010 has eight product quality characteristics, in contrast to ISO 9126's six, and 31 subcharacteristics.[2]
- "Functionality" is renamed "functional suitability". "Functional completeness" is added as a subcharacteristic, and "interoperability" and "security" are moved elsewhere. "Accuracy" is renamed "functional correctness", and "suitability" is renamed "functional appropriateness".
- "Efficiency" is renamed "performance efficiency". "Capacity" is added as a subcharactersitic.
- "Compatibility" is a new characteristic, with "co-existence" moved from "portability" and "interoperability" moved from "functionality".
- "Usability" has new subcharacteristics of "user error
" and "accessibility" (use by people with a wide range of characteristics). "Understandability" is renamed "appropriateness recognizability", and "attractiveness" is renamed "user interface aesthetics".
- "Reliability" has a new subcharacteristic of "availability" (when required for use).
- "Security" is a new characteristic with subcharacteristics of "confidentiality" (data accessible only by those authorized), "integrity" (protection from unauthorized modification), "non-repudiation" (actions can be proven to have taken place), "accountability" (actions can be traced to who did them), and "authenticity" (identity can be proved to be the one claimed).
- "Maintainability" has new subcharacteristics of "modularity" (changes in one component have a minimal impact on others) and "reusability"; "changeability" and "stability" are rolled up into "modifiability".
- "Portability" has "co-existence" moved elsewhere.
See also[edit]
- List of International Organization for Standardization standards, 24000-25999
- Verification and Validation
- Non-functional requirements
- Squale
- ISO/IEC JTC 1/SC 7
References[edit]
- Scalet et al., 2000: ISO/IEC 9126 and 14598 integration aspects: A Brazilian viewpoint. The Second World Congress on Software Quality, Yokohama, Japan, 2000.
