ISO/IEC TR 29110-5-6-2:2014 システムおよびソフトウェアエンジニアリング—超小規模エンティティ（VSE）のライフサイクルプロファイル—パート5-6-2：システムエンジニアリング—管理およびエンジニアリングガイド：一般的なプロファイルグループ：基本的なプロファイル | ページ 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 15288:2008]

3.2

critical system

those 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

Note 1 to entry: Examples of critical items include safety critical items, fracture critical items, mission critical items, key characteristics, etc.

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

3.3

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 15288:2008, modified]

3.4

operator

entity that performs the operations of a system

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

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

Note 3 to entry: In the context of this specific definition, the term entity means an individual or an organization.

[SOURCE:ISO/IEC 15288:2008]

3.5

Systems Engineering Plan

SEP

top‐level plan for managing the SE effort which, as such, defines how the project will be organized, structured, and conducted and how the total engineering process will be controlled to provide a product that satisfies stakeholder requirements

Note 1 to entry: Also called Systems Engineering Management Plan (SEMP).

[SOURCE:INCOSE:2010]

3.6

Small and Medium Enterprise

SME

enterprises which employ fewer than 250 persons and which have an annual turnover not exceeding 50 million euro, and/or an annual balance sheet total not exceeding 43 million euro)

[SOURCE:OECD 2005]

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 15288:2008]

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 15288:2008]

3.9

user

individual or group that benefits from a system during its utilization

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

[SOURCE:ISO/IEC 15288:2008]

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 15288:2008]

3.11

statement of work

SOW

document used by the acquirer that includes the needs and expectations, the scope, objectives and deliverables

[SOURCE:ISO/IEC 12207:2008]

3.12

work breakdown structure

WBS

[Output/Input] deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables

Note 1 to entry: It organizes and defines the total scope of the project.

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