ISO/IEC TR 29110-5-6-1:2015 システムおよびソフトウェアエンジニアリング—超小規模エンティティ（VSE）のライフサイクルプロファイル—パート5-6-1：システムエンジニアリング—管理およびエンジニアリングガイド：一般的なプロファイルグループ：エントリプロファイル | ページ 6

3.1

acquirer

stakeholder that acquires or procures a product or service from a supplier

Note 1 to entry: Other terms commonly used for an acquirer are buyer, customer, owner, or purchaser.

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

3.2

agreement

mutual acknowledgment of terms and conditions under which a working relationship is conducted

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

3.3

critical system

items (e.g., functions, parts, software, characteristics, processes) having significant effect on the product realization and use of the product, including safety, performance, form, fit, function, producibility, service life, etc., that require specific actions to ensure they are adequately managed

[SOURCE:AS/EN/JIS Q 9100:2009]

3.4

disposed system

system that has been transformed (i.e., state change) by applying the disposal process

Note 1 to entry: A systems approach considers the total system and the total lifecycle of the system. This includes all aspects of the system and the system throughout its life until the day users depose of the system and the external enterprises complete the handling of the disposed system products.

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

3.5

operator

individual or organization that performs the operations of a system

Note 1 to entry: The role of operator and the role of user can be vested, simultaneously or sequentially, in the same individual or organization.

Note 2 to entry: An individual operator combined with knowledge, skills and procedures can be considered as an element of the system.

Note 3 to entry: An operator may perform operations on a system that is operated, or of a system that is operated, depending on whether or not operating instructions are placed within the system boundary.

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

3.6

Small and Medium Enterprise

SME

enterprise which employ fewer than 250 persons

[SOURCE:OECD 2005, modified]

3.7

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/IEEE 15288:2015, 4.1.46]

3.8

trade-off

decision-making actions that select from various requirements and alternative solutions on the basis of net benefit to the stakeholders

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

3.9

user

individual or group that interacts with a system or benefits from a system during its utilization

Note 1 to entry: The role of user and the role of operator are sometimes vested, simultaneously or sequentially, in the same individual or organization.

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

3.10

system structure

decomposition of a system of interest into a set of interacting systems and system elements

Note 1 to entry: The system structure is described in a System Breakdown Structure (SBS).

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

3.11

work breakdown structure

WBS

hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables

[SOURCE:ISO/IEC/IEEE 24765:2010, 3.3330, modified]