ISO 25062:2025 システムおよびソフトウェア エンジニアリング — システムおよびソフトウェアの品質要件および評価 (SQuaRE) — ユーザビリティ評価を報告するための Common Industry Format (CIF) | ページ 6

3.1

accessibility

extent to which products, systems, services, environments and facilities can be used by people from a population with the widest range of user (3.19) needs, characteristics and capabilities to achieve identified goals (3.6) in identified contexts of use

Note 1 to entry: Context of use (3.3) includes direct use or use supported by assistive technologies.

[SOURCE:ISO 9241-112:2017, 3.15]

3.2

conformity assessment

demonstration that specified requirements (3.9) are fulfilled

[SOURCE:ISO/IEC 17000:2020, 4.1, modified — Notes to entry deleted.]

3.3

context of use

combination of users (3.19) , goals (3.6) , tasks (3.13) , resources, and environment

Note 1 to entry: The “environment” in a context of use includes the technical, physical, social, cultural and organizational environments.

[SOURCE:ISO 9241‑11:2018, 3.1.15]

3.4

effectiveness

accuracy and completeness with which users (3.19) achieve specified goals (3.6)

[SOURCE:ISO 9241‑11:2018, 3.1.12]

3.5

efficiency

resources used in relation to the results achieved

Note 1 to entry: Typical resources include time, human effort, costs and materials.

[SOURCE:ISO 9241‑11:2018, 3.1.13]

3.6

goal

intended outcome

[SOURCE:ISO 9241‑11:2018, 3.1.10]

3.7

harm from use

negative consequences regarding health, safety, finances or the environment that result from use of the system

Note 1 to entry: The negative consequences can be for the user (3.19) or for any other stakeholder (3.11) .

Note 2 to entry: Although avoidance of harm from use, i.e. eliminating any exposure of risk that poses a potential harm, cannot be achieved completely, designing an interactive system (3.12) can aim at mitigating risks to an acceptable minimum.

[SOURCE:ISO 9241‑220:2019, 3.10]

3.8

information item

separately identifiable body of information that is produced and stored for human use during a system or software life cycle

Note 1 to entry: A document produced to meet information requirements (3.9) can be an information item, part of an information item, or a combination of several information items.

Note 2 to entry: An information item can be produced in several versions during a project or system life cycle.

[SOURCE:ISO/IEC/IEEE 15289:2019, 3.1.12]

3.9

requirement

condition or capability that must be met or possessed by a system, system component, product, or service to satisfy an agreement, standard, specification, or other formally imposed documents

Note 1 to entry: Requirements provide value when delivered, satisfied, or met.

Note 2 to entry: Requirements include the quantified and documented needs, wants, and expectations of the sponsor, customer, and other stakeholders (3.11) .

[SOURCE:ISO/IEC/IEEE 24765:2017, 3.3431, definition 2, modified — Notes to entry added.]

3.10

satisfaction

extent to which the user's (3.19) physical, cognitive and emotional responses that result from the use of a system, product or service meet the user’s needs and expectations

Note 1 to entry: Satisfaction includes the extent to which the user experience that results from actual use meets the user’s needs and expectations.

Note 2 to entry: Anticipated use can influence satisfaction with actual use.

[SOURCE:ISO 9241‑11:2018, 3.1.14]

3.11

stakeholder

individual or organization having a right, share, claim, or interest in a system or in its possession of characteristics that meet their needs and expectations

Note 1 to entry: Some stakeholders can have interests that oppose each other or oppose the system.

[SOURCE:ISO/IEC/IEEE 15288:2023, 3.44]

3.12

interactive system

combination of hardware and/or software and/or services and/or people that users (3.19) interact with in order to achieve specific goals (3.6)

Note 1 to entry: This includes ここで, appropriate, packaging, user documentation, online and human help, support and training.

Note 2 to entry: This definition emphasizes that the user interacts with the system. An interactive system provides feedback to user input and initiates further actions within the system or by other systems as required.

[SOURCE:ISO 25065:2019, 3.2.1]

3.13

task

set of activities undertaken in order to achieve a specific goal (3.6)

[SOURCE:ISO 9241‑11:2018, 3.1.11, modified — Notes to entry deleted.]

3.14

usability

extent to which a system, product or service can be used by specified users (3.19) to achieve specified goals (3.6) with effectiveness (3.4) , efficiency (3.5) and satisfaction (3.10) in a specified context of use (3.3)

[SOURCE:ISO 9241‑11:2018, 3.1.1, modified — Notes to entry deleted.]

3.15

usability defect

attribute of the interactive system (3.12) that leads to a usability problem (3.17)

Note 1 to entry: Usability defects are typically identified during inspections.

Note 2 to entry: Usability defects can originate from incorrect or missing interaction capabilities as well as poor task (3.13) support.

3.16

usability finding

identified usability defect (3.15) and/or usability problem (3.17) or positive usability-related (3.14) attribute

Note 1 to entry: Deviations of attributes of the interactive system (3.12) from specified criteria such as user (3.19) requirements (3.9) , principles, design guidelines or established conventions are also usability findings.

Note 2 to entry: Usability findings can lead to the identification of new user requirements (3.21) .

3.17

usability problem

situation during use, resulting in poor effectiveness (3.4) , efficiency (3.5) or satisfaction (3.10)

Note 1 to entry: Usability problems can be either directly observed during qualitative and/or quantitative usability (3.14) tests or are identified from analysis of use.

Note 2 to entry: Usability problems can lead to one or more use errors (3.18) .

Note 3 to entry: Usability problems are sometimes referred to as use difficulties.

3.18

use error

user (3.19) action or lack of user action while using the interactive system (3.12) that leads to a different result than that intended by the manufacturer or expected by the user

[SOURCE:IEC 62366‑1:2015, 3.21, modified —"Medical device" replaced by"interactive system", notes to entry deleted.]

3.19

user

person who interacts with a system, product or service

Note 1 to entry: Users include people who operate a system, people who use the output provided by a system and people who conduct support tasks (3.13) using the system (including maintenance and training).

Note 2 to entry: According to ISO/IEC 25010,"user" is defined as “individual or group that interacts with a system or benefits from a system during its utilization”.

Note 3 to entry: Primary and secondary users interact with a system, and primary and indirect users can benefit from a system. This definition includes a broader understanding of individuals and organizations that act as users.

[SOURCE:ISO 9241-11:2018, 3.1.7, modified — Notes 2 and 3 to entry added.]

3.20

user need

prerequisite identified as necessary for a user (3.19) , or a set of users, to achieve an intended outcome, implied or stated within a specific context of use (3.3)

Note 1 to entry: A user need is independent of any proposed solution for that need.

Note 2 to entry: User needs are identified based on various approaches including interviews with users, observations, surveys, evaluations, expert analysis, etc.

Note 3 to entry: User needs often represent gaps (or discrepancies) between what should be and what is.

Note 4 to entry: User needs are transformed into user requirements (3.21) considering the context of use, user priorities, trade-offs with other system requirements (3.9) and constraints.

[SOURCE:ISO/IEC 25064:2013, 4.19]

3.21

user requirements

set of requirements (3.9) for use that provide the basis for design and evaluation of interactive systems (3.12) to meet identified user needs (3.20)

Note 1 to entry: User requirements are derived from user needs and capabilities in order to allow the user (3.19) to make use of the system in an effective, efficient, safe and satisfying manner.

Note 2 to entry: User requirements are not requirements on the users.

Note 3 to entry: User requirements include user-system interaction requirements (3.22) and use-related quality requirements (3.23) .

Note 4 to entry: In software engineering terms, user requirements include both"functional" and"non-functional" requirements derived from user needs and capabilities.

[SOURCE:ISO 9241-220:2019, 3.46]

3.22

user-system interaction requirements

user requirements (3.21) that specify interactions (including: recognizing information, making inputs, making selections, and receiving outputs) required by the users (3.19) to achieve the goals (3.6)

Note 1 to entry: User-system interaction requirements (3.9) are generally stated in qualitative terms.

[SOURCE:ISO 25065:2019, 3.1.11, modified — Note to entry added.]

3.23

use-related quality requirements

user requirements (3.21) that specify the intended outcomes of use of the interactive system (3.12) and associated quality criteria

Note 1 to entry: Use-related quality requirements (3.9) are generally stated in quantitative terms.

[SOURCE:ISO 25065:2019, 3.1.12, modified — Note to entry added.]