ISO/IEC/IEEE 24748-3:2020
(Main)Systems and software engineering — Life cycle management — Part 3: Guidelines for the application of ISO/IEC/IEEE 12207 (software life cycle processes)
Systems and software engineering — Life cycle management — Part 3: Guidelines for the application of ISO/IEC/IEEE 12207 (software life cycle processes)
This document is a guideline for the application of ISO/IEC/IEEE 12207:2017. This document establishes guidance to implement a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. This document provides guidance on defining, controlling, and improving software life cycle processes within an organization or a project. This document recommends methods and approaches suitable for a variety of life cycle models. The guidance emphasizes the importance of establishing a strategy, planning, and the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. This document applies to the acquisition, supply, design and development, transition, operation, maintenance, and disposal (whether performed internally or externally to an organization) of software systems, products, and services (including software as a service (SaaS)), and the software portion of any system. Software includes the software portion of firmware. The guidance on processes, activities, and tasks in this document can also be applied during the acquisition of a system that contains software. The guidance in this document can also be used as a basis for selecting, establishing, and improving organizational environments, e.g., methods, procedures, techniques, tools, and trained personnel. In the context of this document, there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system-of-interest (SoI) or as an enabling system or infrastructure. Thus, the choice of whether to apply this document for guidance to the software life cycle processes, or ISO/IEC/IEEE 24748-2, depends on the SoI. At a high level, both documents have the same life cycle process framework, but differ in guidance for activities and tasks to perform software engineering or systems engineering, respectively. The processes and process groups in this document are identical in their purpose and outcomes with those in ISO/IEC/IEEE 12207:2017 and in ISO/IEC/IEEE 15288:2015, with one exception: the System/Software Requirements Definition process of ISO/IEC/IEEE 12207:2017 and this document has a different name from the System Requirements Definition process of ISO/IEC/IEEE 15288:2015. Use of the guidance in this document is appropriate regardless of software system size or complexity or organizational size. The process outcomes from the ISO/IEC/IEEE 12207:2017 life cycle processes are meant to be generic and applicable to the engineering of any software system in any size organization. This document does not prescribe nor detail a specific software life cycle model, development methodology, method, modelling approach, or technique and method. The variety of ways for implementing software (e.g., development of new code, integration of existing open source components and commercial products, or modifications to existing software, including transition to new platforms) make it impossible to detail specific procedures. This document does not establish a management system or provide guidance on the use of any management system standard. However, it is intended to be compatible with the quality management system specified by ISO 9001, the service management system specified by ISO/IEC 20000-1, the IT asset management system specified by ISO/IEC 19770 (all parts), and the information security management system specified by ISO/IEC 27000. Clause 6 provides guidance on aspects of purposes, outcomes, activities, and tasks in ISO/IEC/IEEE 12207:2017. However, this document does not repeat the detailed requirements and recommendations for purposes, outcomes, activities, and tasks for each life cycle process found in ISO/IEC/IEEE 12207:2017. Clause 6 also pr
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 3: Lignes directrices pour l'application de l'ISO/IEC/IEEE 12207 (processus du cycle de vie du logiciel)
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC/
STANDARD IEEE
24748-3
First edition
2020-10
Systems and software engineering —
Life cycle management —
Part 3:
Guidelines for the application of ISO/
IEC/IEEE 12207 (software life cycle
processes)
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 3: Lignes directrices pour l'application de l'ISO/IEC/IEEE
12207 (processus du cycle de vie du logiciel)
Reference number
©
ISO/IEC 2020
©
IEEE 2020
© ISO/IEC 2020
© IEEE 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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 or IEEE at the
respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2020 – All rights reserved
ii © IEEE 2020 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms, definitions, and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 2
4 Concepts for software and software systems . 3
4.1 General . 3
4.2 Software system concepts . 3
4.3 Organizational concepts . 4
4.4 Project concepts . 6
5 Process and life cycle concepts . 8
5.1 Process concepts . 8
5.2 Life cycle concepts .10
5.2.1 Life cycle stages.10
5.2.2 Interrelationships of software processes and stages .11
5.2.3 Life cycle process models for software systems .12
5.3 Process groups .16
6 Software life cycle processes .17
6.1 Agreement processes .17
6.1.1 Acquisition process .17
6.1.2 Supply process .20
6.2 Organizational project-enabling processes .21
6.2.1 Life cycle model management process .21
6.2.2 Infrastructure Management process .22
6.2.3 Portfolio Management process .24
6.2.4 Human Resource Management process .24
6.2.5 Quality Management process .25
6.2.6 Knowledge Management process.26
6.3 Technical Management processes .27
6.3.1 Project Planning process.27
6.3.2 Project assessment and control process .28
6.3.3 Decision Management process .31
6.3.4 Risk Management process .32
6.3.5 Configuration Management process .34
6.3.6 Information Management process .35
6.3.7 Measurement process .36
6.3.8 Quality Assurance process .38
6.4 Technical processes .39
6.4.1 Business or Mission Analysis process .39
6.4.2 Stakeholder Needs and Requirements Definition process .40
6.4.3 System/Software requirements definition process .41
6.4.4 Architecture Definition process .43
6.4.5 Design Definition process .47
6.4.6 System Analysis process .49
6.4.7 Implementation process .50
6.4.8 Integration process .52
6.4.9 Verification process .53
6.4.10 Transition process .55
6.4.11 Validation process . . .57
6.4.12 Operation process .58
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved iii
6.4.13 Maintenance process .59
6.4.14 Disposal process .61
Annex A (informative) Tailoring process .62
Bibliography .64
IEEE notices and abstract .67
© ISO/IEC 2020 – All rights reserved
iv © IEEE 2020 – 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.
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).
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.
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 World Trade Organization (WTO)
principles in the Technical Barriers to Trade (TBT) see www .iso .org/ iso/ foreword .html.
This document was prepared by ISO/IEC JTC 1, Information technology, SC 7, Systems and software
engineering, in cooperation with the Systems and Software Engineering Standards Committee of the
IEEE Computer Society, under the Partner Standards Development
...
INTERNATIONAL ISO/IEC/
STANDARD IEEE
24748-3
First edition
2020-10
Systems and software engineering —
Life cycle management —
Part 3:
Guidelines for the application of ISO/
IEC/IEEE 12207 (software life cycle
processes)
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 3: Lignes directrices pour l'application de l'ISO/IEC/IEEE
12207 (processus du cycle de vie du logiciel)
Reference number
©
ISO/IEC 2020
©
IEEE 2020
© ISO/IEC 2020
© IEEE 2020
All rights reserved. Unless otherwise specified, or required in the context of its implementation, 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 or IEEE at the
respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2020 – All rights reserved
ii © IEEE 2020 – All rights reserved
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 2
3 Terms, definitions, and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviated terms . 2
4 Concepts for software and software systems . 3
4.1 General . 3
4.2 Software system concepts . 3
4.3 Organizational concepts . 4
4.4 Project concepts . 6
5 Process and life cycle concepts . 8
5.1 Process concepts . 8
5.2 Life cycle concepts .10
5.2.1 Life cycle stages.10
5.2.2 Interrelationships of software processes and stages .11
5.2.3 Life cycle process models for software systems .12
5.3 Process groups .16
6 Software life cycle processes .17
6.1 Agreement processes .17
6.1.1 Acquisition process .17
6.1.2 Supply process .20
6.2 Organizational project-enabling processes .21
6.2.1 Life cycle model management process .21
6.2.2 Infrastructure Management process .22
6.2.3 Portfolio Management process .24
6.2.4 Human Resource Management process .24
6.2.5 Quality Management process .25
6.2.6 Knowledge Management process.26
6.3 Technical Management processes .27
6.3.1 Project Planning process.27
6.3.2 Project assessment and control process .28
6.3.3 Decision Management process .31
6.3.4 Risk Management process .32
6.3.5 Configuration Management process .34
6.3.6 Information Management process .35
6.3.7 Measurement process .36
6.3.8 Quality Assurance process .38
6.4 Technical processes .39
6.4.1 Business or Mission Analysis process .39
6.4.2 Stakeholder Needs and Requirements Definition process .40
6.4.3 System/Software requirements definition process .41
6.4.4 Architecture Definition process .43
6.4.5 Design Definition process .47
6.4.6 System Analysis process .49
6.4.7 Implementation process .50
6.4.8 Integration process .52
6.4.9 Verification process .53
6.4.10 Transition process .55
6.4.11 Validation process . . .57
6.4.12 Operation process .58
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved iii
6.4.13 Maintenance process .59
6.4.14 Disposal process .61
Annex A (informative) Tailoring process .62
Bibliography .64
IEEE notices and abstract .67
© ISO/IEC 2020 – All rights reserved
iv © IEEE 2020 – 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.
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).
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.
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 World Trade Organization (WTO)
principles in the Technical Barriers to Trade (TBT) see www .iso .org/ iso/ foreword .html.
This document was prepared by ISO/IEC JTC 1, Information technology, SC 7, Systems and software
engineering, in cooperation with the Systems and Software Engineering Standards Committee of the
IEEE Computer Society, under the Partner Standards Development
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.