The degree to which a system performs specified functions under specified conditions for a specified period.
Can actions or events be proven to have taken place, so they cannot be denied later?
Preventing unauthorized alterations to computer programs or data.
Acquiring the formal ISO/IEC 25010 PDF standard documentation allows engineering firms and software houses to implement strict QA governance. Having direct access to the official PDF provides several key advantages:
Create an Excel sheet with the 8 characteristics as columns. For each software requirement, mark which quality characteristics it impacts. iso iec 25010 pdf
| Feature | ISO/IEC 25010:2011 (First Edition) | ISO/IEC 25010:2023 (Second Edition) | | :--- | :--- | :--- | | | Two distinct models: a product quality model (8 characteristics) and a quality in use model (5 characteristics). | One unified product quality model (9 characteristics). Quality in use is a broader concept reliant on product quality. | | Core Characteristics | 8 characteristics : Functional Suitability, Reliability, Performance Efficiency, Usability, Security, Compatibility, Maintainability, Portability. | 9 characteristics : Adds "Security" as a full characteristic. | | Modularity | Less emphasis on the relationship with other SQuaRE standards for measurement. | Explicitly distinguishes between the "what" (quality characteristics) and the "how" (measurement, detailed in ISO/IEC 25023). | | Guidance & Examples | General guidance on application. | Significantly expanded. Includes an Annex C with detailed guidance on usage for measurement, plus a new Annex D providing an application example , such as applying the model to the cybersecurity of an EVSE charging station . | | Terminology | Terms defined for both models. | Focuses on product quality terms, aligning more closely with modern development contexts. | | Document Length | 34 pages . | 22 pages , reflecting a more concise presentation. | | Status | Withdrawn as of the publication of the 2023 edition. | Current and Active . |
The degree to which user needs are satisfied when using the product (includes trust, pleasure, comfort, and usefulness).
To tailor this guide or explore specific areas deeper, tell me:
Can the software operate alongside or exchange data with other systems? The degree to which a system performs specified
Integrate these quality checks into your CI/CD pipelines. Automated static code analysis tools (like SonarQube) can continuously track Maintainability metrics like modularity and complexity.
The frequency of software failures under normal operation.
The Product Quality Model is the most widely referenced part of the ISO/IEC 25010 standard. It categorizes software quality into , which are further broken down into 31 sub-characteristics . 1. Functional Suitability
Degree to which a product protects information and data. | Feature | ISO/IEC 25010:2011 (First Edition) |
This evaluates the performance of the software relative to the amount of resources it consumes.
Is the software accessible when users need it?
The degree to which a system performs specified functions under specified conditions for a specified period of time.