: Can it exchange information with other systems? Usability : Is it easy for users to learn and operate?
From reviewing the standard, three common use cases emerge:
The is a comprehensive framework defining 8 key characteristics and 31 sub-characteristics. These are critical for developers and QA engineers to document in their PDF work specifications. iso iec 25010 pdf work
Defines (vs 6 in 9126):
Teams stop using vague phrases like "the software must be fast." Instead, they write: "The system must maintain Performance Efficiency (Time Behavior) with an average API response time of : Can it exchange information with other systems
: Does the software do what it's supposed to?
ISO/IEC 25010 is a foundational international standard for evaluating software and systems quality, forming part of the These are critical for developers and QA engineers
Mitigation of potential financial, health, or safety risks.
| Characteristic | Subcharacteristics (examples) | |----------------|-------------------------------| | | Functional completeness, correctness, appropriateness | | Performance Efficiency | Time behavior, resource utilization, capacity | | Compatibility | Co-existence, interoperability | | Usability | Appropriateness recognizability, learnability, operability, user error protection, user engagement, accessibility | | Reliability | Maturity, availability, fault tolerance, recoverability | | Security | Confidentiality, integrity, non-repudiation, accountability, authenticity | | Maintainability | Modularity, reusability, analyzability, modifiability, testability | | Portability | Adaptability, installability, replaceability |