ISO/IEC/IEEE 24748-4:2016

Systems and software engineering - Life cycle management - Part 4: Systems engineering planning

The evolution of the harmonized set of ISO/IEC/IEEE 15288-12207 related standards and technical reports that are discussed in this International Standard provides detailed requirements and guidance on the application of system life cycle processes. This International Standard unifies technical and management requirements and guidance from several of these sources to specify the requirements for the content of a SEMP and to provide a common SEMP format. This International Standard also identifies the processes as defined in ISO/IEC/IEEE 15288 to perform the necessary project planning activities to accomplish the project's technical effort and to develop the project's SEMP. Due to close alignment with the content of ISO/IEC 24748, ISO/IEC 26702 is now Part 4 of the multi-part International Standard, ISO/IEC 24748 (Systems and software engineering ? Life cycle management).

Ingénierie des systèmes — Gestion du cycle de vie — Partie 4: Ingénierie des systèmes

General Information

• Status: Published
• Publication Date: 16-May-2016
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7/WG 7 - Life cycle management
• Current Stage: 9092 - International Standard to be revised
• Start Date: 20-Sep-2023
• Completion Date: 30-Oct-2025

Relations

• Revised: ISO/IEC/IEEE 24748-4 - Systems and software engineering - Life cycle management - Part 4: Systems engineering management planning
• Effective Date: 23-Sep-2023
• Revises: ISO/IEC 26702:2007 - Systems engineering - Application and management of the systems engineering process
• Effective Date: 10-Jul-2010

Overview

ISO/IEC/IEEE 24748-4:2016 - Systems and software engineering - Life cycle management - Part 4: Systems engineering planning - defines requirements and guidance for preparing a Systems Engineering Management Plan (SEMP) and for the project-level technical planning activities needed to execute systems engineering across a system life cycle. Aligned with ISO/IEC/IEEE 15288 and forming Part 4 of the ISO/IEC 24748 series, the standard unifies technical and management expectations and provides a common SEMP format and content baseline.

Key topics and requirements

• SEMP content and common format: Specifies required sections and information items for a SEMP (e.g., technical project summary, organization, technical definition planning, execution and control, supporting process plans).
• Technical management processes: Identifies the systems engineering planning processes to be applied, including:
  • Project planning
  • Project assessment and control
  • Decision management
  • Risk management
  • Configuration management
  • Information management
  • Measurement
  • Quality assurance
• Information item guidance: Defines front matter, references, definitions and detailed content expectations for each SEMP element (e.g., schedule and budget summary, technical baselines, verification & validation planning).
• Tailoring and conformance: Describes tailoring policies and processes so organizations can adapt the SEMP content to project size, complexity, and life cycle stage; provides conformance options (full or tailored).
• Life cycle considerations: Offers guidance for SEMP content across life cycle stages (concept, development, production, utilization, support, retirement) and cross-references Project Management Plan (PMP) elements.

Applications and who uses it

• Systems engineers and lead systems integrators use the standard to develop a SEMP that documents how systems engineering will be executed, controlled, and verified.
• Project managers and technical program offices apply it to ensure project planning integrates technical and management processes consistently with ISO/IEC/IEEE 15288.
• Acquirers, suppliers and contractors leverage the SEMP format to align expectations, demonstrate conformance, and support contract deliverables.
• Quality assurance and configuration teams use the process definitions and measurement guidance to implement control, verification, and audit activities.

Related standards

• ISO/IEC/IEEE 15288 - System life cycle processes (primary process framework referenced)
• ISO/IEC 24748 (Parts 1–5) - Life cycle management guidance (Part 1 guide; Part 5 software planning)
• ISO/IEC 16326 - Project Management Plan content cross-reference (see annex relationship)

ISO/IEC/IEEE 24748-4 is essential for organizations seeking a standardized, auditable approach to systems engineering planning, SEMP development, and life cycle-based technical project control. Keywords: ISO/IEC/IEEE 24748-4, SEMP, systems engineering planning, life cycle management, ISO/IEC/IEEE 15288, project planning.

Standards Content (Sample)

INTERNATIONAL ISO/IEC/
STANDARD IEEE
24748-4
First edition
2016-05-15
Systems and software engineering —
Life cycle management —
Part 4:
Systems engineering planning
Ingénierie des systèmes — Gestion du cycle de vie —
Partie 4: Ingénierie des systèmes
Reference number
ISO 24748-4:2016(E)
©
ISO/IEC 2016
© IEEE 2016
© ISO/IEC 2016
© IEEE 2016
Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without
prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the
country of the requester.
IEC Central Office Institute of Electrical and
ISO copyright office
3, rue de Varembé
Electronics Engineers, Inc.
Case postale 56  CH-1211 Geneva 20
CH-1211 Geneva 20 3 Park Avenue, New York
Tel. + 41 22 749 01 11
Switzerland
NY 10016-5997, USA
Fax + 41 22 749 09 47
E-mail [e-mail] E-mail [e-mail]
E-mail [e-mail]
Web www.iec.ch
Web www.ieee.org
Web www.iso.org
© ISO/IEC 2016 - All rights reserved
ii
© IEEE 2016 - All rights reserved

Contents Page
Foreword . v
Introduction . ix
1 Scope . 1
2 Conformance . 2
2.1 Intended usage . 2
2.2 Conformance to processes . 2
2.3 Conformance to information item content . 2
2.4 Full conformance . 2
2.5 Tailored conformance . 3
3 Normative references . 3
4 Terms and definitions . 3
5 Concepts . 5
5.1 Introduction . 5
5.2 System concepts . 6
5.3 Life cycle concepts . 6
5.4 Process concepts . 6
5.5 Organizational concepts . 7
5.6 Project concepts . 7
5.7 Information items concepts. 7
5.8 SEMP development concepts . 8
6 Technical management processes for systems engineering planning . 9
6.1 General . 9
6.2 Project planning process. 10
6.3 Project assessment and control process . 14
6.4 Decision management process . 16
6.5 Risk management process . 18
6.6 Configuration management process . 19
6.7 Information management process . 20
6.8 Measurement process . 21
6.9 Quality assurance process . 22
7 Information items . 23
8 Guidelines for information items . 23
8.1 Introduction . 23
8.2 Adaptation of ISO/IEC/IEEE 15288 . 24
8.3 Elements of the SEMP . 26
9 Information item content . 27
9.1 General . 27
9.2 Front matter . 28
9.3 Technical Project Summary . 28
9.3.1 General . 28
9.3.2 Purpose, scope and objectives . 28
9.3.3 Assumptions and constraints . 29
9.3.4 System description . 29
9.3.5 Schedule and budget summary . 29
9.4 References . 29
9.5 Definitions . 29
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
iii
9.6 Technical project organization . 29
9.7 Planning for technical definition . 30
9.7.1 General . 30
9.7.2 Process definition . 30
9.7.3 Infrastructure planning . 31
9.7.4 Technical project planning . 31
9.8 Technical project execution and control . 33
9.8.1 Performance assessment and control . 33
9.8.2 Measurement . 34
9.8.3 Quality assurance . 34
9.8.4 Reviews and audits. 34
9.8.5 Subcontractor management . 35
9.8.6 Project management controls . 35
9.8.7 Technical project closeout . 35
9.8.8 Technical baseline management . 36
9.9 Supporting process plans . 38
9.9.1 General . 38
9.9.2 Decision management . 38
9.9.3 Risk management . 39
9.9.4 Communications . 39
9.9.5 Verification and validation . 39
9.10 Specialty engineering activities and plans . 40
Annex A (informative) Project Management Plan (PMP) elements . 42
Relationship of ISO/IEC/IEEE 24748-4 SEMP content to ISO/IEC 16326 PMP content . 42
Annex B (informative) SEMP considerations for system life cycle stages . 49
B.1 Introduction . 49
B.2 Concept stage . 52
B.3 Development stage . 53
B.4 Production stage. 54
B.5 Utilization stage . 55
B.6 Support stage . 56
B.7 Retirement stage . 57
Annex C (normative) Tailoring policies . 59
C.1 Introduction . 59
C.2 Information item tailoring process. 59
C.2.1 Purpose . 59
C.2.2 Outcomes . 59
C.2.3 Activities and tasks . 59
Bibliography . 61
© ISO/IEC 2016  All rights reserved
iv
© IEEE 2016 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product.
Volunteers are not necessarily members of the Institute and serve without compensation. While the IEEE
administers the process and establishes rules to promote fairness in the consensus development process, the
IEEE does not independently evaluate, test, or verify the accuracy of any of the information contained in its
standards.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards adopted
by the joint technical committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this standard may require the use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. ISO/IEEE is not responsible for identifying essential
patents or patent claims for which a license may be required, for conducting inquiries into the legal validity or
scope of patents or patent claims or determining whether any licensing terms or conditions provided in
connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if
any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are
expressly advised that determination of the validity of any patent rights, and the risk of infringement of such
rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE
Standards Association.
ISO/IEC/IEEE 24748-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Systems and software engineering, in cooperation with the IEEE Computer Society
Systems and Software Engineering Standards Committee, under the Partner Standards Development
Organization cooperation agreement between ISO and IEEE.
This edition cancels and replaces the first edition of ISO/IEC 26702:2007 – IEEE Std 1220-2005, which has
been technically revised.
ISO/IEC 24748 consists of the following parts, under the general title Systems and software engineering —
Life cycle management:
 Part 1: Guide for life cycle management
 Part 2: Guide to the application of ISO/IEC 15288 (System life cycle processes)
 Part 3: Guide to the application of ISO/IEC 12207 (Software life cycle processes)
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
v
 Part 4: Systems engineering planning
 Part 5: Software development planning
© ISO/IEC 2016  All rights reserved
vi
© IEEE 2016 – All rights reserved

Introduction
ISO/IEC/IEEE 15288, Systems and software engineering – System life cycle processes, provides a common
process framework covering the life cycle of man-made systems. This life cycle spans the conception of ideas
through to the retirement of a system. It provides the processes for acquiring and supplying systems. In
addition, this framework provides for the assessment and improvement of the life cycle processes. This
common framework improves communication and cooperation among the parties that create, utilize, and
manage modern systems in order that they can work in an integrated, coherent fashion.
The acquisition or supply of a system is usually done within a project. A project prepares and implements the
technical plans and schedules necessary to guide the project toward accomplishment of its objectives and
proper conclusion. Given the project’s authorization and objectives, the project should establish a Systems
Engineering Management Plan (SEMP).
This part of ISO/IEC/IEEE 24748 replaces the former ISO/IEC 26702:2007 (IEEE Std 1220-2005), Systems
engineering — Application and management of the systems engineering process. In preparation for
harmonization, ISO/IEC 26702 provided explanations regarding key differences between IEEE Std 1220 and
ISO/IEC/IEEE 15288 in areas such as terminology and structure.
The evolution of the harmonized set of ISO/IEC/IEEE 15288-12207 related standards and technical reports
that are discussed in this part of ISO/IEC/IEEE 24748 provides detailed requirements and guidance on the
application of system life cycle processes. This part of ISO/IEC/IEEE 24748 unifies technical and
management requirements and guidance from several of these sources to specify the requirements for the
content of a SEMP and to provide a common SEMP format. This part of ISO/IEC/IEEE 24748 also identifies
the processes as defined in ISO/IEC/IEEE 15288 to perform the necessary project planning activities to
accomplish the project's technical effort and to develop the project's SEMP. Due to close alignment with the
content of ISO/IEC 24748, ISO/IEC 26702 is now Part 4 of the multi-part International Standard, ISO/IEC
24748 (Systems and software engineering – Life cycle management).
Taken together, the parts of ISO/IEC 24748 are intended to facilitate the joint usage of the process content of
ISO/IEC/IEEE 15288 and ISO/IEC 12207, Systems and software engineering – Software life cycle processes,
which in turn may be used together with related standards such as for service management, and various other
lower-level process standards. In this way, ISO/IEC 24748 provides unified and consolidated guidance on the
life cycle management of systems and software. Its purpose is to help ensure consistency in system concepts
and life cycle concepts, models, stages, processes, process application, key points of view, adaptation, and
use in various domains as the two International Standards (and others) are used in combination. It should help
a project to design a life cycle model for managing progress on a project.
The five parts of ISO/IEC 24748 are:
 ISO/IEC TR 24748-1: Systems and software engineering – Life cycle management – Part 1: Guide for life
cycle management
 ISO/IEC TR 24748-2: Systems and software engineering – Life cycle management – Part 2: Guide for the
application of ISO/IEC 15288 (System life cycle processes)
 ISO/IEC TR 24748-3: Systems and software engineering – Life cycle management – Part 3: Guide for the
application of ISO/IEC 12207 (Software life cycle processes)
 ISO/IEC/IEEE 24748-4: Systems and software engineering – Life cycle management – Part 4: Systems
engineering planning
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
ix
 ISO/IEC/IEEE 24748-5: Systems and software engineering – Life cycle management – Part 5: Software
development planning
Whereas Part 1 addresses in generic terms the purpose stated above of guidance for the life cycle
management of systems and software, Part 2 focuses on and expands the coverage of those aspects for
systems. Part 2 will also, in conjunction with Part 1, aid in identifying and planning the use of the life cycle
processes described in ISO/IEC/IEEE 15288. The proper use of these processes will contribute to a project
being completed successfully, meeting its objectives and requirements for each stage and for the overall
project.
This part of ISO/IEC/IEEE 24748 focuses on the processes required for successful planning and management
of the project’s systems engineering effort. It calls for development of a SEMP as the key vehicle for
representing a project's application of systems life cycle processes. The SEMP is a top level technical
planning document for a project which addresses Technical Management processes established by three
principal sources (the project’s contract or agreement, applicable organizational processes, and the systems
engineering project team) as necessary to successfully accomplish the systems engineering-related tasks of
the project. The terms technical planning and systems engineering planning are used interchangeably in this
part of ISO/IEC/IEEE 24748 to emphasize or differentiate technical contributions in the processes under
discussion. This part of ISO/IEC/IEEE 24748 draws on key aspects of the former ISO/IEC 26702 (IEEE 1220)
to highlight additional practices and provide normative content for a SEMP.
© ISO/IEC 2016  All rights reserved
x
© IEEE 2016 – All rights reserved

INTERNATIONAL STANDARD ISO/IEC/IEEE 24748-4:2016(E)
Systems and software engineering — Life cycle management —
Part 4: Systems engineering planning
1 Scope
This part of ISO/IEC/IEEE 24748
 specifies the Technical Management processes from ISO/IEC/IEEE 15288 that are required to be
implemented for planning a systems engineering project,
 gives guidelines for applying the required processes,
 specifies a required information item, a plan for the technical management and execution of the project
that is to be produced through the implementation of the Project Planning process,
 gives guidelines for the format and content of the required information item, and
 provides normative definition of the content of the information item that results from the application of
these processes to that end. In this part of ISO/IEC/IEEE 24748 that plan for technical project
management is termed the Systems Engineering Management Plan (SEMP).
This part of ISO/IEC/IEEE 24748 is applicable to
 those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including
software-intensive systems, software products, and services related to those systems and products,
 those who are responsible for the technical management of projects concerned with the engineering of
systems,
 those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level,
 organizations and individuals who are subcontracting a project management effort,
 anyone developing engineering management documentation to complete technical planning aspects of
their project’s processes.
In many organizations, the various responsibilities of technical management are assigned to more than one
person. Where the term "technical manager" or "systems engineering manager" is used in this part of
ISO/IEC/IEEE 24748, the guidance, advice or normative requirement applies to the applicable role within the
project or organization.
This part of ISO/IEC/IEEE 24748 is intended to provide guidance for two-party situations and may be equally
applied where the two parties are from the same organization. This part of ISO/IEC/IEEE 24748 can also be
used by a single party as self-imposed tasks.
This part of ISO/IEC/IEEE 24748 can also serve as guidance in multi-party situations, where high risks are
inherent in the supply and integration of complex systems, and procurement can involve several suppliers,
organizations or parties.
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
2 Conformance
2.1 Intended usage
This part of ISO/IEC/IEEE 24748 provides guidance for the execution of the ISO/IEC/IEEE 15288 processes
that are required for planning and managing a project to implement a significant systems engineering effort.
This part of ISO/IEC/IEEE 24748 also provides normative definition of the content and recommendations for
the format of the related information item, the project's SEMP.
Users of this part of ISO/IEC/IEEE 24748 can claim conformance to the process provisions or to the
information item provisions, or both.
The requirements in this part of ISO/IEC/IEEE 24748 are contained in 6.1, Clauses 7 and 9 and in Annex C.
2.2 Conformance to processes
This part of ISO/IEC/IEEE 24748 identifies required processes for planning the technical management and
execution of projects that implement considerable systems engineering efforts regarding the project's system
products.
The requirements for these processes in this part of ISO/IEC/IEEE 24748 are contained in 6.1.
If a user of this part of ISO/IEC/IEEE 24748 claims full conformance to ISO/IEC/IEEE 15288:2015, then by
implication the user may claim conformance to the processes in this part of ISO/IEC/IEEE 24748.
NOTE A claim to tailored conformance to ISO/IEC/IEEE 15288:2015, does not necessarily imply conformance to the
processes in this part of ISO/IEC/IEEE 24748.
2.3 Conformance to information item content
This part of ISO/IEC/IEEE 24748 provides the requirements for an information item – the SEMP.
A claim of conformance to the information item provisions of this part of ISO/IEC/IEEE 24748 means that
 the user produces the required information item stated in this part of ISO/IEC/IEEE 24748, and
 the user demonstrates that the information item produced during the project planning activities conforms
to the content requirements defined in this part of ISO/IEC/IEEE 24748.
The requirements for the information item in this part of ISO/IEC/IEEE 24748 are contained in Clause 7.
The requirements for the content of the information item in this part of ISO/IEC/IEEE 24748 are contained in
Clause 9.
NOTE 1 If a user of this part of ISO/IEC/IEEE 24748 claims full conformance to ISO/IEC/IEEE 15289, it does not imply
that the user may claim conformance to the information items and information item content in this part of
ISO/IEC/IEEE 24748. The reason is that this part of ISO/IEC/IEEE 24748 adds additional information items and additional
detail.
NOTE 2 In this part of ISO/IEC/IEEE 24748, for simplicity of reference, an information item is described as if it were
published as a separate document. However, information items will be considered as conforming if they are unpublished
but available in a repository for reference, or divided into separate documents or volumes.
2.4 Full conformance
A claim of full conformance to this part of ISO/IEC/IEEE 24748 is equivalent to claiming conformance
 to the processes of ISO/IEC/IEEE 15288, cited in subclause 6.1,
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved

 to the information item cited in Clause 7, and
 to content requirements of the information item in Clause 9.
2.5 Tailored conformance
A claim of tailored conformance to this part of ISO/IEC/IEEE 24748 is equivalent to claiming conformance in
accordance with the tailoring direction provided in normative Annex C.
3 Normative references
The following document, in whole or in part, is normatively referenced in this document and is indispensable
for its application. For dated references, only the edition cited applies. For undated references, the latest
edition of the referenced document (including any amendments) applies.
ISO/IEC/IEEE 15288:2015, Systems and software engineering – System life cycle processes
4 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 15288:2015 and the
following apply.
NOTE 1 ISO/IEC TR 24748-1 provides guidance on the application of ISO/IEC/IEEE 15288, including definition or
expansion of important organization, project, process, and life cycle model concepts and their adaptation for successful
project implementation. ISO/IEC TR 24748-1 is a publicly available technical report; please see the ISO - Publicly
Available Standards site: http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
NOTE 2 ISO/IEC TR 24748-1 also references and uses the terms and definitions from ISO/IEC/IEEE 15288.
4.1
document
uniquely identified unit of information for human use
EXAMPLE Report, specification, manual or book, in printed or electronic form.
[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
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
[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.
EXAMPLE A “plan” is the information item type for all plans and “report” is the information item type for all reports.
[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
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved

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.
[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]
5 Concepts
5.1 Introduction
This Clause presents concepts that apply to and are necessary to understand the systems engineering
planning aspects of a project and for the development and content of a project's SEMP.
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
The Agreement processes of ISO/IEC/IEEE 15288 specify the requirements for the establishment of
agreements with organizational entities, both external and internal to the organization, for the acquisition and
supply of products and services. The Organizational Project-Enabling processes of ISO/IEC/IEEE 15288
provide resources and infrastructure necessary to support projects and help ensure the satisfaction of
organizational objectives and established agreements. The Technical Management processes of
ISO/IEC/IEEE 15288 contain the generic activities and tasks, which may be employed by any party that has to
manage a project dealing with systems or products. The Technical processes of ISO/IEC/IEEE 15288
transform the needs of stakeholders first into a product and then, by applying that product, provide a
sustainable service, when and where needed in order to achieve customer satisfaction.
As discussed in this part of ISO/IEC/IEEE 24748, there are several standards that detail requirements and
application guidance for use of ISO/IEC/IEEE 15288. Some of these standards further expand the
requirements of ISO/IEC/IEEE 15288 to support its application and implementation in organizations and on
projects. Their content includes pertinent requirements and guidance to support systems engineering planning
activities and tasks; for the development of a SEMP for implementation on a project; or for a SEMP template
for organizational use.
This part of ISO/IEC/IEEE 24748 unifies and supplements the extensive application information available in
these standards to assist organizations and project management teams in performance of systems
engineering planning activities and developing an engineering management plan to address a project's
technical management needs. It must be noted that these referenced standards and other documents have
been developed over different time spans and originated by different organizations, so the user may
encounter some contradictions when applying these references.
Performance of systems engineering planning activities to manage the technical aspects of a project and for
development of a SEMP presupposes an understanding of several key concepts. These include the concepts
of: system, life cycle, process, organization, project, information item, and SEMP development. Foundational
material that explains these concepts is discussed or identified in 5.2 to 5.7.
5.2 System concepts
System concepts for systems that are any mix of products and services are introduced in ISO/IEC/IEEE 15288,
5.2. Additional discussion is in ISO/IEC TR 24748-1, 3.1, which explains systems, system boundaries,
structure in systems and projects, and enabling systems
5.3 Life cycle concepts
System life cycle concepts are introduced in ISO/IEC/IEEE 15288, 5.4. Additional discussion is in
ISO/IEC TR 24748-1, 3.2.
Project life cycle concepts and application are addressed in ISO/IEC/IEEE 16326.
The INCOSE Systems Engineering Handbook discusses system life cycle concepts in terms of business,
budget and technical aspects, and project cycles in terms of decision gates. Discussion of different methods,
implementation strategies and case studies highlight some of the decisions facing organizations and projects
in determining appropriate system and life cycle models to employ.
5.4 Process concepts
ISO/IEC TR 24774 provides foundational discussion of process concepts to encourage consistency in
development of standard process reference models. It presents guidelines for the elements used most
frequently in describing a process: the title, purpose, outcomes, activities, tasks and information items.
Process concepts are introduced in ISO/IEC/IEEE 15288, 5.5. Additional discussion for application is provided
in ISO/IEC TR 24748-1, 3.3, and in ISO/IEC TR 24748-2, 4.4.
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved

ISO/IEC/IEEE 15288 establishes a top-level architecture of the life cycle of systems from conception through
retirement. The architecture is constructed with a set of processes and interrelationships among these
processes.
Process principles are introduced in ISO/IEC TR 24748-2, 4.4.2.
The process categories of ISO/IEC/IEEE 15288 are discussed in ISO/IEC TR 24748-2, 4.4.3.
The recursive and iterative application of processes is discussed in ISO/IEC TR 24748-2, 4.4.4.
5.5 Organizational concepts
Clause 4 provides a definition of organization as adapted from ISO/IEC/IEEE 15288. 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. In ISO/IEC/IEEE 15288, when an
organization, as a whole or a part, enters into an agreement, it is a party. Organizations are separate bodies,
but the parties may be from the same organization or from separate organizations.
Organizational concepts, such as responsibility, organizational relationships and project organizational
structure, are discussed in ISO/IEC TR 24748-2, 4.5.
5.6 Project concepts
Clause 4 provides a definition of project as adapted from ISO/IEC/IEEE 15288.
A project can be viewed as a single endeavour, unique in its purpose and consisting of various implemented
lifecycle processes.
ISO/IEC TR 24748-1, 3.1.4, discusses system structure and implications in projects.
ISO/IEC TR 24748-1, 3.1.5, explains enabling systems in terms of the system-of-interest and its operational
environment.
ISO/IEC TR 24748-2, 4.6, discusses project concepts, relationships among projects, project relationships with
enabling systems and hierarchy of projects.
IEEE Std. 1490-2011, IEEE Guide: Adoption of PMI Standard: A Guide to the Project Management Body of
Knowledge, provides more information on projects and project management.
ISO/IEC/IEEE 16326, Systems and software engineering – Life cycle processes – Project management,
provides more information on project management and the information item, Project Management Plan (PMP).
5.7 Information items concepts
Clause 4 provides definitions of an information item and related terms as adapted from ISO/IEC/IEEE 15289.
ISO/IEC/IEEE 15289 provides more detail on information items and specifies how life cycle data is managed
in information items.
ISO/IEC/IEEE 15289, 6.1, provides requirements for life cycle data characteristics of information items that are
produced as documents.
ISO/IEC/IEEE 15289 indicates that an information item is required to be consistent with an information item
generic type. The key information item addressed in this part of ISO/IEC/IEEE 24748 is of type plan.
ISO/IEC/IEEE 15289, Clause 7, identifies several generic types of information items and provides generic
content for each information item type.
© ISO/IEC 2016  All rights reserved
© IEEE 2016 – All rights reserved
ISO/IEC/IEEE 15289, 7.3, provides generic content elements for plans.
ISO/IEC/IEEE 15289 makes a distinction between records and documents (which includes plans). Each
information item produced as a document supports certain life cycle data characteristics. Documents are
produced and communicated for human use and contain formal elements (such as purpose, scope, and
summary), intended to make them usable by their intended audience.
ISO/IEC/IEEE 15289, 6.4, provides requirements for the management of information items through the
application of ISO/IEC/IEEE 15288 and ISO/
...