Iso 25010
Iso 25010
Iso 25010
SA A N D SD Weighted
Functional suitability Sub-Characteristics
5 4 3 2 1 Mean
Q1 8 6 Functional completeness 4.57
Q2 7 6 1 Functional correctness 4.43
Q3 9 4 1 Functional appropriateness 4.57
SA A N D SD Weighted
Performance efficiency Sub-Characteristics
5 4 3 2 1 Mean
Q4 7 7 Time behaviour 4.50
Q5 9 5 Resource utilization 4.64
Q6 4 10 Capacity 4.29
SA A N D SD Weighted
Compatibility Sub-Characteristics
5 4 3 2 1 Mean
Q7 6 7 1 Co-existence 4.36
Q8 8 5 1 Interoperability 4.50
SA A N D SD Weighted
Usability Sub-Characteristics
5 4 3 2 1 Mean
Q9 4 7 3 Appropriateness recognizability 4.07
Q10 8 5 1 Learnability 4.50
Q11 7 7 Operability 4.50
Q12 8 5 1 User error protection 4.50
Q13 9 4 1 User interface aesthetics 4.57
Q14 6 7 1 Accessibility 4.36
SA A N D SD Weighted
Reliability Sub-Characteristics
5 4 3 2 1 Mean
Q15 6 6 2 Availability 4.29
Q16 9 4 1 Fault Tolerance 4.57
Q17 9 4 1 Recoverability 4.57
SA A N D SD Weighted
Security Sub-Characteristics
5 4 3 2 1 Mean
Q18 4 9 1 Confidentiality 4.21
Q19 7 6 1 Integrity 4.43
Q20 6 5 3 Non-repudiation 4.21
Q21 7 6 1 Accountability 4.43
Q22 5 9 Authenticity 4.36
SA A N D SD Weighted
Maintainability Sub-Characteristics
5 4 3 2 1 Mean
Q23 8 6 1 3 Modularity 4.06
Q24 8 8 1 1 Reusability 4.28
Q25 12 5 1 Analysability 4.61
Q26 7 7 4 Modifiability 3.94
Q27 11 3 4 Testability 4.17
SA A N D SD Weighted
Portability Sub-Characteristics
5 4 3 2 1 Mean
Q28 4 8 1 Adaptability 4.23
Q29 7 5 1 Installability 4.46
Q30 9 3 1 Replaceability 4.62
Performance efficiency
4.48 A Agree
Compatibility 4.43 N Neutral
Usability 4.42 D Disagree
Reliability 4.48 SD Strongly Disagree
Security 4.33
Maintainability 4.21
Portability 4.44
This standards was last reviewed and confirmed in 2017. Therefore this version remains current.
Link References:
https://iso25000.com/index.php/en/iso-25000-standards/iso-25010
https://www.iso.org/obp/ui/#iso:std:iso-iec:25010:ed-1:v1:en
https://www.iso.org/obp/ui/#iso:std:iso-iec:25010:ed-1:v1:en
ms and software Quality Requirements and Evaluation (SQuaRE) -- System and software qualit
Total
responden
ts
14
Weighted Mean of System W
14
Functional suitability P
14
5 5
14 5
5
4 4
4 4
3 3
14 3 3
14 2 2
2 2
14 1 1
1 1
0 0
Functional completeness Functional correctness Functional appropriateness Time behaviour
14 System Sub-Characteristics
14
18 System Sub-Characteristics
18
18
Weighted Mean of System W
13
Maintainability
13 5 5
5 5
13
4 4
13 4 4
3 3
3 3
2 2
2 2
1 1
1 1
0 0
Modularity Reusability Analysability Modifiability Testability Adaptability
System Sub-Characteristics
System Sub-Characteristics
and software quality models
25010:2011
stem"
i ty li ty li ty
ur bi bi
a rta
in
nta Po
ai
M
ISO/IEC 25010:2011 defines:
1. A quality in use model composed of five characteristics (some of which are further subdivided into subch
outcome of interaction when a product is used in a particular context of use. This system model is applicab
computer system, including both computer systems in use and software products in use.
2. A product quality model composed of eight characteristics (which are further subdivided into subcharact
properties of software and dynamic properties of the computer system. The model is applicable to both com
products.
The characteristics defined by both models are relevant to all software products and computer systems. Th
subcharacteristics provide consistent terminology for specifying, measuring and evaluating system and sof
provide a set of quality characteristics against which stated quality requirements can be compared for com
Although the scope of the product quality model is intended to be software and computer systems, many o
relevant to wider systems and services.
ISO/IEC 25012 contains a model for data quality that is complementary to this model.
The scope of the models excludes purely functional properties, but it does include functional suitability.
The scope of application of the quality models includes supporting specification and evaluation of software
computer systems from different perspectives by those associated with their acquisition, requirements, dev
support, maintenance, quality assurance and control, and audit. The models can, for example, be used by
assurance and control staff and independent evaluators, particularly those responsible for specifying and e
quality. Activities during product development that can benefit from the use of the quality models include:
* identifying software and system requirements;
* validating the comprehensiveness of a requirements definition;
* identifying software and system design objectives;
* identifying software and system testing objectives;
* identifying quality control criteria as part of quality assurance;
* identifying acceptance criteria for a software product and/or software-intensive computer system;
* establishing measures of quality characteristics in support of these activities.