ISO/IEC TS 24748-1:2016

TECHNICAL ISO/IEC TS
SPECIFICATION 24748-1
First edition
Systems and software engineering —
Life cycle management —
Part 1:
Guide for life cycle management
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 1: Guide de gestion du cycle de vie
PROOF/ÉPREUVE
Reference number
ISO/IEC TS 24748-1:2016(E)
©
ISO/IEC 2016

---------------------- Page: 1 ----------------------
ISO/IEC TS 24748-1:2016(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 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.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2016 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC TS 24748-1:2016(E)

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Terms and definitions . 1
3 Life cycle-related concepts .10
3.1 System concepts .10
3.1.1 General.10
3.1.2 Systems .10
3.1.3 System structure .12
3.1.4 Structure in systems and projects.13
3.1.5 Enabling systems .14
3.2 Life cycle concepts .15
3.2.1 System life cycle model.15
3.2.2 System life cycle stages . .16
3.2.3 Stages in a system-of-interest and its enabling systems .17
3.3 Process concepts .18
3.3.1 Life cycle processes .18
3.3.2 Process responsibility .21
3.4 Process application .22
3.5 Processes under key views .24
4 Life cycle stages .26
4.1 General .26
4.2 Concept stage .27
4.2.1 Overview .27
4.2.2 Purpose .28
4.2.3 Outcomes .28
4.3 Development stage .28
4.3.1 Overview .28
4.3.2 Purpose .29
4.3.3 Outcomes .29
4.4 Production stage .30
4.4.1 Overview .30
4.4.2 Purpose .30
4.4.3 Outcomes .30
4.5 Utilization stage .31
4.5.1 Overview .31
4.5.2 Purpose .31
4.5.3 Outcomes .31
4.6 Support stage.31
4.6.1 Overview .31
4.6.2 Purpose .32
4.6.3 Outcomes .32
4.7 Retirement stage .32
4.7.1 Overview .32
4.7.2 Purpose .33
4.7.3 Outcomes .33
5 Life cycle adaptation .33
5.1 General .33
5.2 Adaptation sequence .34
5.2.1 General.34
5.2.2 Identify the project environment and characteristics .35
5.2.3 Solicit inputs .35
© ISO/IEC 2016 – All rights reserved PROOF/ÉPREUVE iii

---------------------- Page: 3 ----------------------
ISO/IEC TS 24748-1:2016(E)

5.2.4 Select the appropriate standards .35
5.2.5 Select life cycle model .36
5.2.6 Select stages and processes .36
5.2.7 Document the adaptation decisions and rationale .36
5.3 Adaptation guidance .37
5.4 Scope adaptation .38
5.5 Stage adaptation .39
5.6 Process adaptation .39
5.7 Life cycle model adaptation for domains, disciplines and specialties .39
5.7.1 Adaptation for domains .39
5.7.2 Adaptation for disciplines .41
5.7.3 Adaptation for specialties .41
5.8 Adapting evaluation-related activities .43
6 Relationship with detailed process standards .44
Annex A (informative) Process views .46
Annex B (informative) Guidance on development strategies and build planning .56
Annex C (informative) Candidate joint management reviews .59
Annex D (informative) Problem reporting capability .62
Bibliography .64
iv PROOF/ÉPREUVE © ISO/IEC 2016 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC TS 24748-1:2016(E)

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.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for
the different types of document should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical
Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 7, Software
and systems engineering.
This first edition of ISO/IEC TS 24748-1 cancels and replaces ISO/IEC TR 24748-1, 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 [Technical Specification]
— Part 2: Guide to the application of ISO/IEC 15288 (System life cycle processes) [Technical Report]
— Part 3: Guide to the application of ISO/IEC 12207 (Software life cycle processes) [Technical Report]
— Part 4: Systems engineering planning [ISO/IEC/IEEE]
— Part 5: Software development planning [ISO/IEC/IEEE]
The following parts are under preparation:
— Part 6: Guide to system integration engineering
© ISO/IEC 2016 – All rights reserved PROOF/ÉPREUVE v

---------------------- Page: 5 ----------------------
ISO/IEC TS 24748-1:2016(E)

Introduction
The purpose of this Technical Specification is to facilitate the joint usage of the process content of the
latest revisions of ISO/IEC/IEEE 15288 and ISO/IEC 12207, by providing unified and consolidated
guidance on life cycle management of systems and software. This 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 are used in combination.
That will in turn help a project team design a life cycle model for managing the progress of their project.
This Technical Specification will also aid in identifying and planning use of life cycle processes described
in ISO/IEC/IEEE 15288 and ISO/IEC 12207 that will enable the project to be completed successfully,
meeting its objectives/requirements for each stage and for the overall project.
Besides the above, there is also increasing recognition of the importance of ensuring that all life cycle
stages and all aspects within each stage are supported with thorough guidance to enable alignment
with any process documents that might subsequently be created that focus on areas besides systems
and software, including hardware, humans, data, processes (e.g. review process), procedures (e.g.
operator instructions), facilities and naturally occurring entities (e.g. water, organisms, minerals).
By addressing these needs specifically in this Technical Specification, the users of the process-
focused ISO/IEC 12207 and ISO/IEC/IEEE 15288 will not only benefit from having one document
complementarily addressing the aspect of product or service life cycle: they will also benefit from a
framework that links life cycle management aspects to more than just the systems or software aspects
of products or services.
ISO/IEC/IEEE 15288 and ISO/IEC 12207 also have published guidelines (ISO/IEC TR 24748-2 and
ISO/IEC TR 24748-3), respectively, to support use of the two revised International Standards
individually.
vi PROOF/ÉPREUVE © ISO/IEC 2016 – All rights reserved

---------------------- Page: 6 ----------------------
TECHNICAL SPECIFICATION ISO/IEC TS 24748-1:2016(E)
Systems and software engineering — Life cycle
management —
Part 1:
Guide for life cycle management
1 Scope
This Technical Specification is a guideline for the life cycle management of systems and software,
complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC 12207. This Technical
Specification
— addresses systems concepts and life cycle concepts, models, stages, processes, process application,
key points of view, adaptation and use in various domains and by various disciplines,
— establishes a common framework for describing life cycles, including their individual stages, for the
management of projects to provide, or acquire either products or services,
— defines the concept and terminology of a life cycle,
— supports the use of the life cycle processes within an organization or a project. Organizations and
projects can use these life cycle concepts when acquiring and supplying either products or services,
— provides guidance on adapting a life cycle model and the content associated with a life cycle or a
part of a life cycle,
— describes the relationship between life cycles and their use in applying the processes in ISO/IEC/
IEEE 15288 (systems aspects) and ISO/IEC 12207 (software aspects),
— shows the relationships of life cycle concepts to the hardware, human, services, process, procedure,
facility and naturally occurring entity aspects of projects, and
— describes how its concepts relate to detailed process standards, for example, in the areas of
measurement, project management and risk management.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.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, purchaser, or
internal/organizational sponsor.
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.2
acquisition
process of obtaining a system, product or service
[SOURCE: ISO/IEC/IEEE 15288:2015]
© ISO/IEC 2016 – All rights reserved PROOF/ÉPREUVE 1

---------------------- Page: 7 ----------------------
ISO/IEC TS 24748-1:2016(E)

2.3
activity
set of cohesive tasks of a process
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.4
agile development
software development approach based on iterative development, frequent inspection and adaptation,
and incremental deliveries, in which requirements and solutions evolve through collaboration in cross-
functional teams and through continual stakeholder feedback
[SOURCE: ISO/IEC/IEEE 26515:2011]
2.5
agreement
mutual acknowledgement of terms and conditions under which a working relationship is conducted
EXAMPLE Contract, memorandum of agreement.
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.6
architecture
fundamental concepts or properties of a system in its environment embodied in its elements,
relationships, and in the principles of its design and evolution
Note 1 to entry: ISO/IEC 12207 and ISO/IEC/IEEE 15288 use the word “elements” instead of “components” and
this Technical Specification follows that usage.
[SOURCE: ISO/IEC/IEEE 42010:2011]
2.7
architecture framework
conventions, principles and practices for the description of architectures established within a specific
domain of application and/or community of stakeholders
EXAMPLE 1 Generalized Enterprise Reference Architecture and Methodologies (GERAM) (ISO 15704) is an
architecture framework.
EXAMPLE 2 Reference Model of Open Distributed Processing (RM-ODP) (ISO/IEC 10746) is an architecture
framework.
[SOURCE: ISO/IEC/IEEE 42010:2011]
2.8
architecture view
work product expressing the architecture of a system from the perspective of specific system concerns
[SOURCE: ISO/IEC/IEEE 42010:2011]
2.9
architecture viewpoint
work product establishing the conventions for the construction, interpretation and use of architecture
views to frame specific system concerns
[SOURCE: ISO/IEC/IEEE 42010:2011]
2 PROOF/ÉPREUVE © ISO/IEC 2016 – All rights reserved

---------------------- Page: 8 ----------------------
ISO/IEC TS 24748-1:2016(E)

2.10
audit
independent examination of a work product or set of work products to assess compliance with
specifications, standards, contractual agreements, or other criteria
[SOURCE: ISO/IEC/IEEE 24765:2010]
2.11
baseline
approved version of a configuration item, regardless of media, formally designated and fixed at a
specific time during the configuration item’s life cycle
[SOURCE: IEEE 828:2012]
2.12
concept of operations
verbal and/or graphic statement, in broad outline, of an organization’s assumptions or intent in regard
to an operation or series of operations
Note 1 to entry: The concept of operations frequently is embodied in long-range strategic plans and annual
operational plans. In the latter case, the concept of operations in the plan covers a series of connected operations
to be carried out simultaneously or in succession. The concept is designed to give an overall picture of the
organization operations. See also operational concept (2.25).
Note 2 to entry: It provides the basis for bounding the operating space, system capabilities, interfaces and
operating environment.
[SOURCE: ANSI/AIAA G-043A-2012e]
2.13
concern
interest in a system relevant to one or more of its stakeholders
Note 1 to entry: A concern pertains to any influence on a system in its environment, including developmental,
technological, business, operational, organizational, political, economic, legal, regulatory, ecological and social
influences.
[SOURCE: ISO/IEC/IEEE 42010:2011]
2.14
configuration item
item or aggregation of hardware, software, or both, that is designated for configuration management
and treated as a single entity in the configuration management process
[SOURCE: ISO/IEC/IEEE 24765:2010, modified — added “item or”.]
2.15
customer
organization or person that receives a product or service
EXAMPLE Consumer, client, user, acquirer, buyer, or purchaser.
Note 1 to entry: A customer can be internal or external to the organization.
[SOURCE: ISO 9000:2015, modified — added “service”.]
2.16
design
to define the architecture, system elements, interfaces, and other characteristics of a system
or system element
[SOURCE: ISO/IEC/IEEE 24765:2010, modified – changed “components” to “system elements”.]
© ISO/IEC 2016 – All rights reserved PROOF/ÉPREUVE 3

---------------------- Page: 9 ----------------------
ISO/IEC TS 24748-1:2016(E)

2.17
design
result of the process in 2.15
Note 1 to entry: Information, including specification of system elements and their relationships, that is sufficiently
complete to support a compliant implementation of the architecture.
Note 2 to entry: Design provides the detailed implementation-level physical structure, behavior, temporal
relationships and other attributes of system elements.
[SOURCE: ISO/IEC/IEEE 24765:2010]
2.18
design characteristic
design attributes or distinguishing features that pertain to a measurable description of a product
or service
[SOURCE: ISO/IEC/IEEE 24765:2010]
2.19
enabling system
system that supports a system-of-interest during its life cycle stages but does not necessarily contribute
directly to its function during operation
EXAMPLE When a system-of-interest enters the production stage, a production-enabling system is required.
Note 1 to entry: Each enabling system has a life cycle of its own. This Technical Specification 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]
2.20
environment
context determining the setting and circumstances of all influences upon a system
[SOURCE: ISO/IEC/IEEE 42010:2011]
2.21
facility
physical means or equipment for facilitating the performance of an action, e.g. buildings,
instruments, tools
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.22
incident
anomalous or unexpected event, set of events, condition, or situation at any time during the life cycle of
a project, product, service, or system
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.23
information item
separately identifiable body of information that is produced, stored, and delivered for human use
[SOURCE: ISO/IEC/IEEE 15289:2015]
2.24
life cycle
evolution of a system, product, service, project or other human-made entity from conception through
retirement
[SOURCE: ISO/IEC/IEEE 15288:2015]
4 PROOF/ÉPREUVE © ISO/IEC 2016 – All rights reserved

---------------------- Page: 10 ----------------------
ISO/IEC TS 24748-1:2016(E)

2.25
life cycle model
framework of processes and activities concerned with the life cycle that may be organized into stages,
which also acts as a common reference for communication and understanding
[SOURCE: ISO/IEC/IEEE 15288:2015]
2.26
operational concept
verbal and graphic statement of an organization’s assumptions or intent in regard to an operation or
series of operations of a system or a related set of systems
Note 1 to entry: The operational concept is designed to give an overall picture of the operations using one or
more specific systems, or set of related systems, in the organization’s operational environment from the users’
and operators’ perspective. See also concept of operations (2.11).
[SOURCE: ANSI/AIAA G-043A-2012e]
2.27
operator
individual or organization 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: 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]
2.28
organization
group of people and facilities with an arrangement of responsibilities, authorities and relationships
EXAMPLE Company, corporation, firm, enterpr
...