ISO/IEC/IEEE 26512:2018 システムおよびソフトウェアエンジニアリング—ユーザー向けの情報の取得者および提供者に対する要件 | ページ 6

3.1

accessibility

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

Note 1 to entry: Although “accessibility” typically addresses users who have disabilities, the concept is not limited to disability issues.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 2 to entry has become Note 1 to entry, original Note 1 to entry has been deleted.]

3.2

analysis

investigation and collection phase of development that aims to specify types of users and their informational needs

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

3.3

audience

category of users sharing the same or similar characteristics and needs (for example, reason for using the information, tasks, education level, abilities, training, experience)

Note 1 to entry: There can be different audiences for information for users (for example, management, data entry, maintenance) that determine the content, structure, and use of the information.

[SOURCE:ISO/IEC 26514:2008, Note 1 to entry modified and editorially revised:"intended documentation" has become"information."]

3.4

change control procedure

actions taken to identify, document, review, and authorize changes to a software or information product that is being developed

Note 1 to entry: The procedures help to ensure that the validity of changes is confirmed, that the effects on other items are examined, and that those people concerned with the development are notified of the changes.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 1 to entry editorially revised.]

3.5

configuration management

3.6

contract

relationship between acquirer and supplier, which in broad terms prescribes that one party will provide defined goods and services and the other party will pay a defined fee for them

Note 1 to entry: In many countries, contracts do not have to be written but the terms of the contracts referred to in this document are defined in writing.

Note 2 to entry: The contract relationship can have other names, such as “agreement.” The acquirer determines which term is to be used in the application of this document.

3.7

customization

adaptation of a software or information product to the needs of a particular audience

[SOURCE:ISO/IEC 26514:2008]

3.8

design

stage of information development that is concerned with determining what information for users will be provided in a product and what the nature of the information will be

[SOURCE:ISO/IEC 26514:2008]

3.9

development

activity of preparing information for users after it has been designed

[SOURCE:ISO/IEC 26514:2008]

3.10

document

uniquely identified unit of information for human use

Note 1 to entry: A document can be a single information item or part of a larger information item.

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

3.11

documentation

information that explains how to use a product

Note 1 to entry: The information can be provided as documentation that can be used independently of the system or embedded within the product and accessible as an integral part of it, or both. In this document, the term"information for users” is synonymous with the terms “documentation” and “software user documentation.” Other forms of documentation (for example, “system documentation”) are clearly identified as such.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 1 to entry combined with Note 2 to entry and editorially revised, Note 3 to entry has become an example and has been editorially revised.]

3.12

illustration

graphic element set apart from the main body of text and normally cited within the main text

Note 1 to entry: In this document, the term “illustration” is used as the generic term for tables, figures, exhibits, screen captures, flow charts, diagrams, drawings, icons, and other types of graphics.

[SOURCE:ISO/IEC 26514:2008, Modified, definition now includes the word"element," after"graphic" and Note 1 to entry editorially revised.]

3.13

internationalization

process of developing information so that it is suitable for an international audience

Note 1 to entry: See 3.14 localization.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 1 to entry added.]

3.14

localization

creation of a national or specific regional version of a product

Note 1 to entry: See 3.13 internationalization.

Note 2 to entry: Localization can be performed separately from the translation process.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 1 to entry modified original"cf", Note 2 to entry added.]

3.15

on-screen information

information that is intended to be read on the screen by the user while using software

[SOURCE:ISO/IEC 26514:2008, Modified, term was previously"on-screen documentation", definition now includes"information" while previous version included"documentation." Note 1 to entry has been editorially revised and has become an example.]

3.16

printed documentation

documentation that is either provided in printed form, or provided in electronic form for the customer or user to print

[SOURCE:ISO/IEC 26514:2008]

3.17

process

set of interrelated or interacting activities that transform inputs into outputs

[SOURCE:ISO 9000:2005]

3.18

product

result of a process

[SOURCE:ISO/IEC/IEEE 15288:2015]

3.19

product authority

person or persons with overall responsibility for the capabilities and quality of a product

[SOURCE:ISO/IEC 26514:2008]

3.20

project

set of activities for developing a new product or enhancing an existing product

[SOURCE:ISO/IEC 26514:2008]

3.21

quality management

coordinated activities to direct and control an organization with regard to quality

[SOURCE:ISO/IEC/IEEE 15288:2015]

3.22

software

all or part of the programs, procedures, rules, and associated documentation of an information processing system

Note 1 to entry: For the purposes of this document, the term “software” does not include on-screen documentation.

[SOURCE:IEEE Std 828-2012]

3.23

style

set of language-specific editorial conventions covering grammar, terminology, punctuation, capitalization, and word choice

[SOURCE:ISO/IEC 26514:2008]

3.24

technical contact

person responsible for providing an information developer with technical information about a product or for checking the technical accuracy of drafts of information for users

Note 1 to entry: Technical contacts are often also known as subject-matter experts.

[SOURCE:ISO/IEC 26514:2008, Modified,"information developer," replaced"documentation developer,""so-called subject matter expert" removed, and Note 1 to entry added.]

3.25

topic

small part of a document that deals with a single subject

Note 1 to entry: In printed information for users, a topic is equivalent to a section (heading, subheading) and its content. In on-screen information, a topic consists of a title (heading) and information about a subject (typically, a task or a concept or reference information). For on-screen information, the system might present a topic without user intervention.

[SOURCE:ISO/IEC 26514:2008, Modified, Note 1 to entry includes content of previous Note 2 to entry with editorial modifications ("on-screen information" replaces"on-screen documentation"), Note 3 to entry has become an example.]

3.26

tutorial

instructional procedure in which the user exercises system functions, often using sample data that is supplied with the system or information for users

[SOURCE:ISO/IEC 26514:2008]

3.27

usability

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

[SOURCE:ISO/IEC 25064:2013]

3.28

user

person who performs one or more tasks with an automated system; a member of a specific audience

[SOURCE:ISO/IEC 25064:2013]

3.29

user interface

ensemble of software and hardware that allows a user to interact with a system

[SOURCE:ISO/IEC 26514:2008]