ISO/IEC 25010

System and Software Quality Models

1. Overview of ISO/IEC 25010, the Standard for Software Quality Evaluation

    flowchart LR
    A["Subjective quality evaluation"] -- "Shift to a quantitative, systematic quality model" --> B["ISO/IEC 25010"]

Definition: An international standard (the successor to ISO/IEC 9126) that defines quality characteristics and sub-characteristics for evaluating the quality of a software product.

Characteristics: (Dual model) Evaluates SW quality from multiple angles through a dual model of product quality (8 characteristics) and quality in use (5 characteristics). (Quantitative measurement) Provides objective, quantitative measurement metrics for each quality characteristic, supporting quality comparison and tracking. (International standard) As the successor to ISO 9126, it provides a common language for global SW quality evaluation.

2. The 8 Product Quality Characteristics of ISO/IEC 25010

a. Product Quality Model

    flowchart TD
  ISO25010n["ISO/IEC 25010"]
  ISO25010n --> FunctionalSuitability["Functional Suitability"]
  ISO25010n --> PerformanceEfficiency["Performance Efficiency"]
  ISO25010n --> Compatibility["Compatibility"]
  ISO25010n --> Usability["Usability"]
  ISO25010n --> Reliability["Reliability"]
  ISO25010n --> Security["Security"]
  ISO25010n --> Maintainability["Maintainability"]
  ISO25010n --> Portability["Portability"]

Characteristic	Detailed Description	Example Sub-characteristics
Functional Suitability	How well the specified requirements are met	Functional completeness, functional correctness
Performance Efficiency	The level of performance relative to resources used	Time behavior, resource utilization
Usability	How easily and comfortably users can operate the product	Learnability, operability, user error protection
Reliability	Whether performance is maintained under specified conditions and duration	Maturity, availability, fault tolerance
Security	Whether information and data are protected	Confidentiality, integrity, non-repudiation, accountability
Maintainability	How easily the product can be modified and improved	Modularity, reusability, analyzability, testability

b. Quality in Use Model

    flowchart LR
    subgraph USE["Quality in Use"]
        A["Effectiveness"]
        B["Efficiency"]
        C["Satisfaction"]
        D["Freedom from Risk"]
        E["Context Coverage"]
    end

    style USE fill:#F9FAFB,stroke:#374151

Characteristic	Description	Notes
Effectiveness	The degree to which users achieve specific goals accurately and completely	Outcome-focused
Efficiency	Accuracy relative to the resources consumed to achieve the goal	Economy of the process
Satisfaction	The degree to which user needs are met	Includes psychological satisfaction
Freedom from Risk	The degree to which economic, health, safety, and environmental risk is minimized	Risk management

3. Expected Benefits and Application of ISO/IEC 25010

Category	Expected Benefits	Application and Practical Use
Requirements definition	Derives clear quality requirements	Used as a basis for quality metrics when writing an RFP
Quality verification	Enables objective software testing and evaluation	Basis for test case design in the V&V (Validation & Verification) stage
Communication	Establishes a common language among stakeholders	A tool for agreeing on quality goals among developers, users, and QA
Process improvement	Quality-centered management of the development lifecycle	Refines and matures the development process by analyzing discovered quality defects

PDCA Six Sigma