Skip to content

ISO 25000 · Software product quality

ISO 25000: quality in software engineering

Assess your software's quality, position it in the market and give your clients a reliable criterion for choosing it.

What is ISO 25000?

SQuaRE: software quality requirements and evaluation

Software is a fundamental tool in any activity, and its quality has become a key criterion when choosing products.

ISO/IEC 25000 (SQuaRE – Software Product Quality Requirements and Evaluation) sets criteria for specifying quality requirements, their metrics and their evaluation.

It includes a quality model that connects what the client means by quality with the attributes of the development process.

Quality model

The eight characteristics of quality software

01

Functional suitability

Completeness, correctness and appropriateness of functions for user needs.

02

Performance efficiency

Time behavior and resource utilization.

03

Compatibility

Coexistence and interoperability with other systems.

04

Reliability

Maturity, availability, fault tolerance and recoverability.

05

Usability

Learnability and operability, user error protection, aesthetics and accessibility.

06

Security

Confidentiality, integrity, accountability, authenticity and non-repudiation.

07

Maintainability

Modularity, reusability, analyzability, modifiability and testability.

08

Portability

Installability, replaceability and adaptability to other environments.

Structure of the standard

The divisions of the ISO/IEC 25000 family

2500n · Quality management2501n · Quality model2502n · Measurement2503n · Requirements2504n · Evaluation25050–25099 · Extensions

Evaluation

How software quality is evaluated

  1. 1Study of product quality, evaluating the software's properties.
  2. 2Study of performance, analyzing how the software behaves in production.
  3. 3Measurement of the software's effectiveness.

Functional Suitability Certificate

Functions that deliver what they promise

Measures the software's ability to provide functions that meet stated and implied needs under specified conditions.

01

Functional completeness

How well the functionality covers the user's tasks and objectives.

02

Functional correctness

Correct results with the required degree of precision.

03

Functional appropriateness

An appropriate set of functions for each task and objective.

Certify your software's quality

We support you through evaluation and certification under ISO 25000.