BS ISO IEC 25010:2011 pdf – Systems and software engineering-Systems andsoftware Quality Requirements and Evaluation (sQuaRE)—System and software quality models.
NOTE 2 Satislaction Is the user’s response to interaction with the product or system, and mctudes attitudes towards use of the product.
4.1.3.1
usefulness
degree to which a user is satisfied with their perceived achievement of pragmatic goals, indud.ng the results of use and the consequences of use
4,1.3.2
trust
degree to which a user or other stakeholder has confidence that a product or system will behave as intended
4.1,3.3
pleasure
degree to which a user obtains pleasure from fulfilling their personal needs
NOTE Personal needs can include needs to acquire new knowledge and skiSs, to corThliij’ilcate personal identity and to provoke pleasant memories.
4.1.3.4
comfort
degree to which the user Is satisfied with physical comfort
41,4
freedom from risk
degree to which a product or system mtigates the potential risk to economic status, human life, health, or the environment
NOTE Risk is a function of the probability of o,ience of a given threat and the potential adverse consequences of that threars oa’rence
4.1.4.1
economic risk mitigation
degree to which a product or system mitigates the potential flsk to financial status, efficient operation. commercial property. reputation or other resources in the intended contexts of use
4.1.4.2
health and safety risk mitigation
degree to which a product or system mitigates the potential risk to people in the intended contexts of use
4.1.4.3
environmental risk mitigation
degree to which a product or system mitigates the potential risk to property or the environment in the intended contexts of use
4.1.5
context coverage
degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in both specified contexts of use and in contexts beyond those initially explicitly identified
NOTE Context of use m relevant to both quality in use and some product quality (sub)chatacteristics (where it is referred to as specified conditions’).
4.1.5.1
context completeness
degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in all the specified contexts of use
NOTE Functional suitability Is onfy concerned with whether the functions meet stated and lmpAed needs, not the functional specification (see C 6).
4.2.1.1
functional completeness
degree to which the set of functions covers all the specified tasks and user obiectives
4.2.12
functional correctness
degree to which a product or system provides the correct results with the needed degree of precision
4.2.1.3
functional appropriateness
degree to which the functions facilitate the accomplishment of specified tasks and objectives
EXAMPLE A ow only presented with the necessary steps to complete a task. escluding any unnecessery steps NOTE Functional appropnaleness corresponds to suitabdity for the task in ISO 9241-110.
4,2.2
performance efficiency
performance relative to the amount of resoiwces used under stated conditions
NOTE Reecu-ces can rndude other software products, the software and hardware conflgixabon of the system, and matenats (e.g. print paper, storage media).
4.2.2.1
time behaviour
degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements
4.2.2.2
resource utilization
degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements
NOTE Human resources are included as pt of efficiency (4.1.2).
4.2,2.3
capacity
degree to which the maximum limits of a product or system parameter meet requirements
NOTE Parameters can include the number of items that can be stored, the number of concurrent users, me communication bandwidth, throughput of transactions, arid size of database
4.2.3
compatibility
degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment
NOTE Adapted from ISO/IEC11EEE 24765.
4.2.3.1
co-existence
degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products. without detrimental impact on any other product.