ISO/IEC TR 25060:2010 システムとソフトウェアエンジニアリング—システムとソフトウェア製品の品質要件と評価（SQuaRE）—ユーザビリティのための共通産業フォーマット（CIF）：ユーザビリティ関連情報の一般的なフレームワーク | ページ 5

2.1

accessibility

usability of a product, service, environment or facility by people with the widest range of capabilities

[SOURCE: ISO 9241-171:2008]

2.2

action

user behaviour that a system accepts as a request for a particular operation

[SOURCE: ISO/IEC TR 11580:2007]

2.3

context of use

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

[SOURCE: ISO 9241-11:1998]

2.4

dialogue

interaction between a user and an interactive system as a sequence of user actions (inputs) and system responses (outputs) in order to achieve a goal

[SOURCE: ISO 9241-110:2006]

2.5

effectiveness

accuracy and completeness with which users achieve specified goals

[SOURCE: ISO 9241-11:1998]

2.6

efficiency

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

[SOURCE: ISO 9241-11:1998]

2.7

goal

intended outcome

[SOURCE: ISO 9241-11:1998]

2.8

information architecture

structure of an information space and the semantics for accessing required task objects, system objects and other information

Note 1 to entry: The appropriate combination of organization, labelling, navigation schemes and retrieval mechanisms within an information space will facilitate task completion and efficient access to content.

2.9

product

part of the equipment (hardware, software and materials) for which usability is to be specified or evaluated

[SOURCE: ISO 9241-11:1998]

2.10

satisfaction

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

[SOURCE: ISO 9241-11:1998]

2.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

[SOURCE: ISO/IEC 15288:2008]

2.12

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:2002, 4.17]

2.13

task

activities required to achieve a goal

[SOURCE: ISO 9241-11:1998]

Note 1 to entry: The term “task” is used here, as in ISO 9241-11, in its widest sense, rather than in reference to the specifics of use of the dialogue system.

2.14

usability

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

[SOURCE: ISO 9241-11:1998]

Note 1 to entry: The definition of usability in this Technical Report is similar to that used to define “quality in use” in ISO/IEC 9126-1:2001.

2.15

usability objective

stated level of usability expressed in terms of effectiveness, efficiency and satisfaction in a specified context of use which can be verified

Note 1 to entry: Usability objectives can be stated as user requirements, in which case the level to be achieved is a usability requirement, or they can be stated as desired “target levels” depending on their use in design and evaluation.

2.16

usability inspection

evaluation based on the considered judgment of evaluators who examine the usability-related aspects of an interface with respect to specified criteria

Note 1 to entry: The inspectors can include usability specialists, developers, end users or other types of professionals.

Note 2 to entry: The evaluative criteria can include good practice and/or documented principles, guidelines, requirements or standards.

Note 3 to entry: The evaluation can be conducted with or without the help of referenced documents.

Note 4 to entry: Usability inspection is the generic term for several methods, including but not limited to heuristic evaluation, cognitive walkthroughs, standards inspection, pluralistic walkthroughs, and consistency inspections.

2.17

usability testing

evaluation that involves representative users performing specific tasks with the system to enable the measurement of efficiency, effectiveness, and/or user satisfaction

2.18

usability walkthrough

usability evaluation in which one or more evaluators step through a scenario playing the role of a user and identifying usability problems associated with successful completion of the scenario

Note 1 to entry: The evaluators can include usability specialists, developers, end users or other types of professionals.

2.19

user

person who interacts with the interactive system

[SOURCE: ISO 9241-110:2006]

2.20

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 used to assess aspects of user experience.

[SOURCE: ISO 9241-210]

2.21

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.

2.22

user interaction

exchange of information between a user and an interactive system via the user interface to complete the intended task

Note 1 to entry: Adapted from ISO 11064-5:2008, 3.20.

Note 2 to entry: User interaction specifications focus on user interactions without considering implementation details.

2.23

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]

2.24

user interface element

entity of the user interface that is presented to the user by the software

Note 1 to entry: User interface elements can be interactive or not.

Note 2 to entry: Both entities relevant to the task and entities of the user interface are regarded as user interface elements. Different user interface element types are text, graphics and controls. A user interface element may be a visual representation or an interaction mechanism for a task object (such as a letter, a sales order, electronic parts, or a wiring diagram) or a system object (such as a printer, hard disk, or network connection). It may be possible for the user to directly manipulate some of these user interface elements.

Note 3 to entry: User interface elements in a graphical user interface include such things as basic objects (such as window title bars, menu items, push buttons, image maps, and editable text fields) or containers (such as windows, grouping boxes, menu bars, menus, groups of mutually exclusive option buttons, and compound images that are made up of several smaller images). User interface elements in an audio user interface include such things as menus, menu items, messages, and action prompts.

Note 4 to entry: User interface elements are also referred to as “user interface objects”.

[SOURCE: ISO 9241-171:2008]

2.25

user need

factor or condition necessary for a user to achieve desired results within a specified context of use

Note 1 to entry: Factors and conditions include the presence of a specific quality, quantity, information, process or service as well as particular social, organizational and physical environments.

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