ISO/IEC 25064:2013 システムとソフトウェアエンジニアリング—ソフトウェア製品の品質要件と評価（SQuaRE）—使いやすさのための一般的な業界フォーマット（CIF）：ユーザーニーズレポート | ページ 6

4.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]

4.2

action

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

[SOURCE:ISO/IEC TR 11580:2007]

4.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]

4.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]

4.5

effectiveness

accuracy and completeness with which users achieve specified goals

[SOURCE:ISO 9241-11:1998]

4.6

efficiency

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

[SOURCE:ISO 9241-11:1998]

4.7

goal

intended outcome

[SOURCE:ISO 9241-11:1998]

4.8

information item

separately identifiable body of information that is produced, stored, and delivered for human use

Note 1 to entry: “information product” is a synonym.

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

[SOURCE:ISO/IEC/IEEE 15289:2011]

4.9

performance deficiency

difference between the required (or desired) level of performance and the actual performance

Note 1 to entry: Deficiency data is only obtainable in environments where specific performance requirements exist

Note 2 to entry: Performance refers to effectiveness and efficiency in the definition of usability

Note 3 to entry: Performance deficiencies can include deficiencies in measured customer satisfaction

4.10

product

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

[SOURCE:ISO 9241-11:1998]

4.11

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: Formally imposed documents could include user needs reports.

[SOURCE:ISO/IEC 24765:2010]

4.12

satisfaction

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

[SOURCE:ISO 9241-11:1998]

4.13

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

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]

4.15

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.

4.16

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:2010]

Note 1 to entry: This definition of usability is similar to that used to define quality in use in ISO/IEC 9126-1:2001.

4.17

user

person who interacts with a system, product or service

Note 1 to entry: A person who uses an output or service provided by a system, such as a bank customer who receives a paper or electronic statement, visits a branch, or carries out telephone banking using a call centre, is considered to be a user.

[SOURCE:ISO 26800:2011]

4.18

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]

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

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 considering the context of use, user priorities, tradeoffs with other system requirements and constraints

4.20

usage requirements

user 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]

4.21

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]