ISO/IEC 25063:2014 システムおよびソフトウェアエンジニアリング—システムおよびソフトウェア製品の品質要件と評価（SQuaRE）—使いやすさのための一般的な業界フォーマット（CIF）：使用状況の説明 | ページ 5

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 characteristics and capabilities to achieve a specified goal in a specified context of use

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

[SOURCE:ISO 26800:2011, 2.1]

3.2

context of use

users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a system, product or service is used

[SOURCE:ISO 9241‑11:1998, 3.5, modified — In the definition, “product” has been replaced by “system, product or service”.]

Note 1 to entry: In this International Standard, equipment is described as part of the technical and technological environment.

3.3

effectiveness

accuracy and completeness with which users achieve specified goals

[SOURCE:ISO 9241‑11:1998, 3.2]

3.4

efficiency

resources expended in relation to the accuracy and completeness with which users achieve goals

[SOURCE:ISO 9241‑11:1998, 3.3]

3.5

goal

intended outcome

[SOURCE:ISO 9241‑11:1998, 3.8]

3.6

human-centred design

approach to system design and development that aims to make interactive systems more usable by focusing on the use of the system; applying human factors, ergonomics and usability knowledge and techniques

Note 1 to entry: The term “human-centred design” is used rather than “user-centred design” in order to emphasize that this standard also addresses impacts on a number of stakeholders, not just those typically considered as users. However, in practice, these terms are often used synonymously.

Note 2 to entry: Usable systems can provide a number of benefits including improved productivity, enhanced user wellbeing, avoidance of stress, increased accessibility, and reduced risk of harm.

[SOURCE:ISO 9241‑210:2010, 2.7]

3.7

information item

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

[SOURCE:ISO/IEC 15289:2006, 5.11]

3.8

interactive system

combination of hardware, software and/or services that receives input from and communicates output to users

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

[SOURCE:ISO 9241‑210:2010, 2.8]

3.9

persona

representation of a type of user that includes a concise summary of the characteristics of the user that is most informative to the design or illustrative of specific user requirements

Note 1 to entry: A persona typically includes behaviour patterns, goals, skills, attitudes, and environment, with a few fictional personal details to make the persona a realistic character.

3.10

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 include the quantified and documented needs, wants, and expectations of the sponsor, customer, and other stakeholders.

[SOURCE:ISO/IEC/IEEE 24765:2010, 3.2506]

3.11

satisfaction

freedom from discomfort, and positive attitudes towards the use of the product

[SOURCE:ISO 9241‑11:1998, 3.4]

3.12

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

[SOURCE:ISO/IEC 15288:2008, 4.29]

3.13

system

combination of interacting elements organized to achieve one or more stated purposes

Note 1 to entry: A system may be considered as a product or as the services it provides.

Note 2 to entry: In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun, e.g. aircraft system. Alternatively the word system may be substituted simply by a context-dependent synonym, e.g. aircraft, though this may then obscure a system principles perspective.

[SOURCE:ISO/IEC 15288:2008, 4.31]

3.14

task

activities required to achieve a goal

[SOURCE:ISO 9241‑11:1998, 3.9]

3.15

usability

extent to which a system, product or service can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use

[SOURCE:ISO 9241‑210, 2.13]

3.16

user

person who interacts with a system, product or service

Note 1 to entry: A person who uses the output or service provided by a system. For example, a bank customer who visits a branch, receives a paper statement, or carries out telephone banking using a call centre can be considered a user.

[SOURCE:ISO 26800:2011, 2.10]

3.17

user experience

person's perceptions and responses that result from the use and/or anticipated use of a product, system or service

Note 1 to entry: User experience includes all the users’ emotions, beliefs, preferences, perceptions, physical and psychological responses, behaviours and accomplishments that occur before, during and after use.

Note 2 to entry: User experience is a consequence of brand image, presentation, functionality, system performance, interactive behaviour, and assistive capabilities of the interactive system; the user’s internal and physical state resulting from prior experiences, attitudes, skills and personality; and the context of use.

Note 3 to entry: Usability, when interpreted from the perspective of the users’ personal goals, can include the kind of perceptual and emotional aspects typically associated with user experience. Usability criteria can be established so as to assess aspects of user experience.

[SOURCE:ISO 9241‑210:2010, 2.15]

3.18

user interface

all components of an interactive system (software or hardware) that provide information and controls for the user to accomplish specific tasks with the interactive system

[SOURCE:ISO 9241‑110:2006, 3.9]

3.19

user need

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

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

3.20

user requirements

usage requirements

requirements for use that provide the basis for design and evaluation of interactive systems to meet identified user needs

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

Note 2 to entry: User requirements specify the extent to which user needs and capabilities are to be met when using the system. They are not requirements on the users.

Note 3 to entry: In software-engineering terms, user requirements comprise both “functional” and “non-functional” requirements based on user needs and capabilities.

[SOURCE:ISO/IEC TR 25060:2010, 2.21]