ISO/IEC TS 24748-6:2016 システムおよびソフトウェアエンジニアリング—ライフサイクル管理—パート6：システム統合エンジニアリング | ページ 6

3.1.1

acquirer

stakeholder that acquires or procures a product or service from a supplier (3.1.9)

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

3.1.2

aggregate

composition of several implemented system elements (3.1.11) that are assembled (3.1.3) , on which a set of verification actions (3.1.17) and/or validation actions (3.1.15) is applied

3.1.3

assemble

activities for combining and connecting implemented system elements (3.1.11) or aggregates (3.1.2) to support specific goals, i.e. integration (3.1.5) , verification (3.1.16) , validation (3.1.14) , manufacturing and production.

3.1.4

enabling system

system (3.1.10) that supports a system-of-interest (3.1.12) during its life cycle stages, but does not necessarily contribute directly to its function during operation

Note 1 to entry: Each enabling system has a life cycle of its own. ISO/IEC/IEEE 15288 is applicable to each enabling system when, in its own right, it is treated as a system-of-interest.

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

3.1.5

integration

activities of combining several implemented system elements (3.1.11) and activating the interfaces (3.1.8) to form a realized system (product or service) that enables interoperation between the system elements and with other systems (3.1.10) to satisfy system requirements, architecture characteristics and design properties

Note 1 to entry: In this document, the term “integration” is limited to the integration of the implemented system elements which compose a system and the necessary life cycle related activities. Integration may occur to connect a system-of-interest (3.1.12) with external interoperating systems and/or enabling systems (3.1.4) .

Note 2 to entry: The process of combining software components, hardware components or both into an overall system (ISO/IEC/IEEE 24765).

3.1.6

integration engineering

set of activities that defines, analyzes and executes integration (3.1.5) across the life cycle, including interactions with other life cycle processes

Note 1 to entry: The application of the system life cycle processes and knowledge of the system-of-interest (3.1.12) are necessary in order to integrate a set of system elements (3.1.11) into a system (3.1.10) .

3.1.7

integration management

set of activities that plans, assesses and controls the integration activities and all related activities

Note 1 to entry: It helps ensure that the process outcomes are achieved and that the integration related information items are identified, documented, maintained, communicated and traced throughout the life cycle of the concerned system (3.1.10) .

3.1.8

interface

set of logical and/or physical characteristics required to exist at a common boundary or connection between system elements (3.1.11)

Note 1 to entry: As examples of interface definition, refer to ISO/IEC/IEEE 24765.

3.1.9

supplier

organization or individual that enters into an agreement with the acquirer (3.1.1) for the supply of a product or service

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

3.1.10

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.

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

3.1.11

system element

member of a set of elements that constitute a system (3.1.10)

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

3.1.12

system-of-interest

system (3.1.10) whose life cycle is under consideration in the context of this document

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

3.1.13

user

individual or a group that benefits from a system (3.1.10) during its utilization

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

3.1.14

validation

confirmation, through the provision of objective evidence, that the requirements for a specific intended use or application have been fulfilled

Note 1 to entry: A system (3.1.10) is able to accomplish its intended use, goals and objectives (i.e. meet stakeholder requirements) in the intended operational environment. The right system was built.

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

3.1.15

validation action

action that describes what is to be validated (the element as reference), on which item the action is performed, the expected result from the performance of the action, the validation technique to apply and at which level of decomposition of the system-of-interest (3.1.12)

3.1.16

verification

confirmation, through the provision of objective evidence, that specified requirements have been fulfilled

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

3.1.17

verification action

action that describes what is to be verified (the element as reference), on which item the action is performed, the expected result from the performance of the action, the verification technique to apply and at which level of decomposition of the system-of-interest (3.1.12)