ISO/IEC/IEEE 24748-4:2016 システムとソフトウェア工学  —  ライフサイクル管理  —  パート4：システムエンジニアリング計画 | ページ 6

4.1

document

uniquely identified unit of information for human use

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

4.2

include

information

having either the information or a reference to the information present in the document

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

4.3

information item

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

Note 1 to entry: Synonym: information product.

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

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

4.4

information item content

information included in an information item, associated with a system, product or service, to satisfy a requirement or need

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

4.5

information item type

group of information items consistent with a pre-arranged set of generic criteria

Note 1 to entry: Synonym: generic document type.

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

4.6

integrated repository

planned and controlled storage of information pertinent to the systems engineering effort

Note 1 to entry: The integrated repository typically includes key data, e.g., schema, models, tools, technical management decisions, process analysis information, requirement changes, process and product metrics, trade-offs and other analyses.

4.7

measure of effectiveness

MOE

“operational” measure of success that is closely related to the achievement of the operational objective being evaluated in the intended operational environment under a specified set of conditions

[SOURCE:ISO/IEC TR 24748-2:2010, Table A.15 k)]

4.8

measure of performance

MOP

engineering parameter that provides critical performance requirements to satisfy a measure of effectiveness (MOE)

Note 1 to entry: An MOP typically characterizes physical or functional attributes relating to the system operation.

4.9

organization

group of people and facilities with an arrangement of responsibilities, authorities and relationships

Note 1 to entry: A body of persons organized for some specific purpose, such as a club, union, corporation, or society, is an organization.

Note 2 to entry: An identified part of an organization (even as small as a single individual) or an identified group of organizations can be regarded as an organization if it has responsibilities, authorities and relationships.

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

4.10

plan

information item that presents a systematic course of action for achieving a declared purpose, including when, how, and by whom specific activities are to be performed

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

4.11

project

endeavour with defined start and finish criteria undertaken to create a product or service in accordance with specified resources and requirements

Note 1 to entry: A project is sometimes viewed as a unique process comprising co-coordinated and controlled activities and composed of activities from the Technical Management processes and Technical processes defined in ISO/IEC/IEEE 15288.

[SOURCE:ISO/IEC/IEEE 15288:2015, modified Note 1 to entry]

4.12

system breakdown structure

SBS

system hierarchy, with identified enabling systems, and personnel that is typically used to assign development teams, support technical reviews, and to partition the assigned work and associated resource allocations to each of the tasks necessary to accomplish the technical objectives of the project

Note 1 to entry: The SBS can be used as a basis for cost-tracking and control.

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

4.14

systems engineering management plan

SEMP

top level technical plan for managing the systems engineering effort which defines how the technical aspects of the project will be organized, structured, and conducted and how the systems engineering processes will be controlled to provide a product that satisfies stakeholder requirements

[SOURCE:ISO/IEC TR 29110-5-6-2:2014, modified to specify technical aspects of the project]

4.15

technical performance measure

TPM

measure used to assess design progress, compliance to performance requirements, and technical risks for critical performance parameters

Note 1 to entry: TPMs are derived from the MOPs focusing on the critical performance parameters of specific architectural elements of the system as it is designed and implemented.

[SOURCE:ISO/IEC 29148:2011, 6.3.3.1]

4.16

work breakdown structure

WBS

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

[SOURCE:PMBOK Guide – Fifth Edition]