ISO/IEC TR 24748-1:2010

TECHNICAL ISO/IEC
REPORT TR
24748-1
First edition
2010-10-01


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




Reference number
ISO/IEC TR 24748-1:2010(E)
©
ISO/IEC 2010

---------------------- Page: 1 ----------------------
ISO/IEC TR 24748-1:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.


COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2010
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2010 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC TR 24748-1:2010(E)
Contents Page
Foreword .vi
Introduction.vii
1 Scope.1
2 Terms and definitions .1
3 Life cycle-related concepts .7
3.1 System concepts .7
3.1.1 Introduction.7
3.1.2 Systems.7
3.1.3 System structure.9
3.1.4 Structure in systems and projects .10
3.1.5 Enabling systems.11
3.2 Life cycle concepts .12
3.2.1 System life cycle model.12
3.2.2 System life cycle stages .14
3.2.3 Stages in a system-of-interest and its enabling systems .15
3.3 Process concepts.16
3.3.1 Life cycle processes .16
3.3.2 Process responsibility.19
3.4 Process application.20
3.5 Processes under key views.22
4 Life cycle stages.24
4.1 Introduction.24
4.2 Concept stage.25
4.2.1 Overview.25
4.2.2 Purpose.25
4.2.3 Outcomes.26
4.3 Development stage.26
4.3.1 Overview.26
4.3.2 Purpose.26
4.3.3 Outcomes.27
4.4 Production stage .27
4.4.1 Overview.27
4.4.2 Purpose.28
4.4.3 Outcomes.28
4.5 Utilization stage .28
4.5.1 Overview.28
4.5.2 Purpose.29
4.5.3 Outcomes.29
4.6 Support stage .29
4.6.1 Overview.29
4.6.2 Purpose.30
4.6.3 Outcomes.30
4.7 Retirement stage.30
4.7.1 Overview.30
4.7.2 Purpose.30
4.7.3 Outcomes.31
5 Life cycle model illustrations using ISO/IEC 15288 and ISO/IEC 12207 .31
5.1 System life cycle model using ISO/IEC 15288.31
5.1.1 Example of ISO/IEC 15288 in a generic system life cycle model .31
© ISO/IEC 2010 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC TR 24748-1:2010(E)
5.2 Software life cycle model using ISO/IEC 12207.33
5.2.1 Example of ISO/IEC 12207 in a generic software life cycle model .33
5.3 Adapting ISO/IEC 15288 and ISO/IEC 12207 life cycle models .36
6 Life cycle adaptation .36
6.1 Introduction.36
6.2 Adaptation sequence .37
6.2.1 Identify the project environment and characteristics.38
6.2.2 Solicit inputs .38
6.2.3 Select the appropriate standards.39
6.2.4 Select life cycle model .39
6.2.5 Select stages and processes.39
6.2.6 Document the adaptation decisions and rationale .40
6.3 Adaptation guidance .40
6.4 Scope adaptation.42
6.5 Stage adaptation.42
6.6 Process adaptation.42
6.7 Adapting evaluation-related activities.42
7 Life cycle model use by domains, disciplines and specialties.43
7.1 Life cycle models for domains and disciplines .43
7.2 Adaptation for domains and disciplines .44
7.3 Adaptation for specialties.44
7.3.1 Human.45
7.3.2 Health.45
7.3.3 Safety.45
7.3.4 Security.45
7.3.5 Interoperability.45
7.3.6 Usability.46
7.3.7 Dependability.46
7.3.8 Environmental impacts.46
8 Relationship with detailed process standards .46
9 Guidance on transitioning from the previous versions.48
9.1 Comparisons between the versions .48
9.2 Relationship description for ISO/IEC 12207:2008 and ISO/IEC 15288:2008 .61
9.3 General notes on transition.65
9.3.1 Joint usage of both ISO/IEC 15288 and ISO/IEC 12207 .65
9.3.2 Independent usage .65
9.4 Notes for new versus existing users .66
9.4.1 Considerations for transition decisions.66
9.4.2 Timing and phasing of transition.66
9.4.3 Adaptation considerations .66
9.5 Notes on using application guides ISO/IEC TR 15271 and ISO/IEC TR 19760 .66
9.6 Adjustments in relationships with other ISO and ISO/IEC documents.66
9.7 Developing a forward strategy .67
Annex A (informative) Guidance on development strategies and build planning.68
A.1 Scope.68
A.2 Candidate development strategies .68
A.3 Selecting an appropriate development strategy .68
A.4 Relationship of systems and software to development strategies .70
A.5 Planning software builds .70
A.5.1 Identifying builds and their objectives .70
A.5.2 Identifying the activities to be performed in each build .70
A.5.3 Recording build planning decisions.70
A.5.4 Scheduling the selected activities in each build .70
Annex B (informative) Candidate joint management reviews .71
B.1 Scope.71
B.2 Assumptions .71
B.3 Candidate reviews.71
iv © ISO/IEC 2010 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC TR 24748-1:2010(E)
B.3.1 Plan reviews.71
B.3.2 Operational concept reviews.71
B.3.3 System requirements reviews.71
B.3.4 System design reviews.72
B.3.5 Software requirements reviews.72
B.3.6 Software design reviews.72
B.3.7 Test readiness reviews .72
B.3.8 Test results reviews .72
B.3.9 Usability reviews.72
B.3.10 Maintenance reviews.72
B.3.11 Critical requirement reviews .73
B.4 Other resources.73
Annex C (informative) Problem reporting capability.74
C.1 Unified problem reporting .74
C.2 Problem classification.74
Bibliography.76

© ISO/IEC 2010 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO/IEC TR 24748-1:2010(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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee 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.
In exceptional circumstances, the joint technical committee may propose the publication of a Technical Report
of one of the following types:
⎯ type 1, when the required support cannot be obtained for the publication of an International Standard,
despite repeated efforts;
⎯ type 2, when the subject is still under technical development or where for any other reason there is the
future but not immediate possibility of an agreement on an International Standard;
⎯ type 3, when the joint technical committee has collected data of a different kind from that which is
normally published as an International Standard (“state of the art”, for example).
Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether
they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to
be reviewed until the data they provide are considered to be no longer valid or useful.
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.
ISO/IEC TR 24748-1, which is a Technical Report of type 3, was prepared by Joint Technical Committee
ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering.
ISO/IEC TR 24748 consists of the following parts, under the general title Systems and software
engineering — Life cycle management:
Part 1: Guide for life cycle management
Guides for the application of ISO/IEC 15288 (systems life cycle processes) and ISO/IEC 12207 (software life
cycle processes) will form the subjects of future parts 2 and 3, respectively.
vi © ISO/IEC 2010 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC TR 24748-1:2010(E)
Introduction
ISO/IEC 15288, Systems and software engineering — System life cycle processes, and ISO/IEC 12207,
Systems and software engineering — Software life cycle processes, each have published guides
(ISO/IEC TR 19760 and ISO/IEC TR 15271, respectively) for the use of each International Standard
individually. The purpose of this Technical Report is to facilitate the joint usage of the process content of the
latest revisions of ISO/IEC 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 Report will also aid in identifying and planning use of life cycle processes described in
ISO/IEC 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. ISO/IEC TR 19760 and ISO/IEC TR 15271
will be replaced by ISO/IEC TR 24748-2 and ISO/IEC TR 24748-3, respectively, to support use of the two
revised International Standards individually.
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, 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 Report, the users of the process-focused
ISO/IEC 12207 and ISO/IEC 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 2010 – All rights reserved vii

---------------------- Page: 7 ----------------------
TECHNICAL REPORT ISO/IEC TR 24748-1:2010(E)

Systems and software engineering — Life cycle management —
Part 1:
Guide for life cycle management
1 Scope
This Technical Report is a guide for the life cycle management of systems and software based on
ISO/IEC 15288 and ISO/IEC 12207. This Technical Report:
• addresses systems concepts and life cycle concepts, models, stages, processes, process application, key
points of view, adaptation and use in various domains;
• 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 ISO/IEC 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;
• describes how its concepts relate to detailed process standards, for example, in the areas of
measurement, project management and risk management;
• complements domain-specific application guidance in ISO/IEC TR 19760 and ISO/IEC TR 15271.
NOTE When published, ISO/IEC TR 24748-2 and ISO/IEC 24748-3 will cancel and replace ISO/IEC TR 19760
and ISO/IEC TR 15271, respectively.
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
[ISO/IEC 12207:2008 and ISO/IEC 15288:2008]
NOTE The acquirer could be one of the following: buyer, customer, owner, or purchaser.
2.2
acquisition
process of obtaining a product or service
[ISO/IEC 15288:2008]
© ISO/IEC 2010 – All rights reserved 1

---------------------- Page: 8 ----------------------
ISO/IEC TR 24748-1:2010(E)
2.3
activity
set of cohesive tasks of a process
[ISO/IEC 12207:2008 and ISO/IEC 15288:2008]
2.4
agreement
mutual acknowledgement of terms and conditions under which a working relationship is conducted
[ISO/IEC 12207:2008 and ISO/IEC 15288:2008]
2.5
architecture
fundamental organization of a system embodied in its components, their relationships to each other, and to
the environment, and the principles guiding its design and evolution
[ISO/IEC 42010:2007]
NOTE ISO/IEC 12207 and ISO/IEC 15288 use the word “elements” instead of “components” and this Technical
Report follows that usage.
2.6
audit
systematic, independent and documented process for obtaining audit evidence and evaluating it objectively to
determine the extent to which audit criteria are fulfilled
[ISO 9000:2005]
2.7
baseline
specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis
for further development, and that can be changed only through formal change control procedures
[ISO/IEC 15288:2008]
2.8
contract
binding agreement between two parties, especially enforceable by law, or a similar internal agreement wholly
within an organization
[ISO/IEC 12207:2008]
2.9
customer
organization or person that receives a product or service
NOTE 1 A customer can be internal or external to the organization.
NOTE 2 Adapted from ISO 9000:2005.
NOTE 3 Other terms commonly used for customer are acquirer, buyer, or purchaser.
[ISO/IEC 12207:2008 and ISO/IEC 15288:2008]
2.10
developer
organization that performs development activities (including requirements analysis, design, testing through
acceptance) during the life cycle process
NOTE Adapted from ISO/IEC 12207:2008.
2 © ISO/IEC 2010 –
...