ISO/IEC/IEEE 12207-2:2020
(Main)Systems and software engineering — Software life cycle processes — Part 2: Relation and mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008
Systems and software engineering — Software life cycle processes — Part 2: Relation and mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008
This document provides the mapping expressing corresponding relations between software life cycle processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008. These relations are demonstrated by means of mapping tables that show relationships between activities and tasks, and process outcomes. This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017. This document will help users understand the differences between the reference processes and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017. Also, this document provides to such users the mapping which helps to identify corresponding process outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017. The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can be used as a basis to continuously conduct, improve and extend current process assets including software specific process assets based on ISO/IEC 12207:2008 for effective implementation of ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.
Ingénierie des systèmes et du logiciel — Processus du cycle de vie du logiciel — Partie 2: Relation et correspondance entre l'ISO/IEC/IEEE 12207:2017 et l'ISO/IEC 12207:2008
General Information
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/IEC/
STANDARD IEEE
12207-2
First edition
2020-10
Systems and software engineering —
Software life cycle processes —
Part 2:
Relation and mapping between ISO/
IEC/IEEE 12207:2017 and ISO/IEC
12207:2008
Ingénierie des systèmes et du logiciel — Processus du cycle de vie du
logiciel —
Partie 2: Relation et correspondance entre l'ISO/IEC/IEEE
12207:2017 et l'ISO/IEC 12207:2008
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 .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Purpose . 2
5 Overview of the mappings . 2
5.1 General . 2
5.2 Compound and singular requirements . 3
6 Outcome mappings . 3
6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008 . 3
6.2 Outcome mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017 .28
7 Activity and task-level mappings .53
7.1 Activity and task-level mapping from ISO/IEC/IEEE 12207:2017 to ISO/
IEC 12207:2008 edition .53
7.2 Activity and task-level mapping from ISO/IEC 12207:2008 to ISO/IEC/
IEEE 12207:2017 .164
Bibliography .267
IEEE notices and abstract .268
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved iii
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.
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 ISO documents should be noted. This document was drafted in accordance with the
rules given in 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) or the IEC
list of patent declarations received (see https:// patents .iec .c).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, 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 Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
A list of all parts in the ISO/IEC/IEEE 12207 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO/IEC 2020 – All rights reserved
iv © IEEE 2020 – All rights reserved
Introduction
The processes in ISO/IEC/IEEE 12207:2017 form a comprehensive set from which an organization can
construct software system life cycle models appropriate to its products and services. An organization,
depending on its purpose, can select and apply an appropriate subset to fulfil that purpose.
However, ISO/IEC/IEEE 12207:2017 does not include "software-specific processes" as a specialization
of system processes, as identified in ISO/IEC 12207:2008, Clause 7. Those processes are partially
represented as activities, tasks and NOTEs in processes defined in ISO/IEC/IEEE 12207:2017. This
document supports software engineering users of ISO/IEC 12207:2008 in applying their current
processes, activities and tasks based on the previous edition to perform effectively and efficiently
processes, activities and tasks in ISO/IEC/IEEE 12207:2017. This document also intends to help system
engineers using ISO/IEC/IEEE 12207:2017 (or ISO/IEC/IEEE 15288:2015) collaborate with software
engineers who have used ISO/IEC 12207:2008.
This document can be used in one or more of the following modes in conjunction with
ISO/IEC/IEEE 12207:
— By an organization — to help use the current organizational software processes and assets
derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of
ISO/IEC/IEEE 12207:2017.
— By a project — to help use the current project’s software processes and assets derived from
ISO/IEC 12207:2008 and extend these to processes of ISO/IEC/IEEE 12207:2017 to provide software
systems as products and services.
— By an acquirer and a supplier — to help use the current agreement concerning processes and
activities derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of
ISO/IEC/IEEE 12207:2017.
— By process assessors — to serve as an aid to mapping tasks and activities of the previous edition
of ISO/IEC 12207:2008 to the process reference model in ISO/IEC/IEEE 12207:2017, Annex C for
process assessments that may be used to support organizational process improvement.
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved v
INTERNATIONAL STANDARD ISO/IEC/IEEE 12207-2:2020(E)
Systems and software engineering — Software life cycle
processes —
Part 2:
Relation and mapping between ISO/IEC/IEEE 12207:2017
and ISO/IEC 12207:2008
1 Scope
This document provides the mapping expressing corresponding relations between software life cycle
processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008.
These relations are demonstrated by means of mapping tables that show relationships between
activities and tasks, and process outcomes.
This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017.
This document will help users understand the differences between the reference processes
and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process
enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017.
Also, this document provides to such users the mapping which helps to identify corresponding process
outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017.
The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can
be used as a basis to continuously conduct, improve and extend current process assets including
software specific process assets based on ISO/IEC 12207:2008 for effective implementation of
ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. 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 12207:2017, Systems and software engineering — Software life cycle processes
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 12207:2017 apply.
ISO, IEC and IEEE maintain terminological databases for use in standardization at the following
addresses:
— ISO Online browsing platform: available at https:// www .iso .org/
— IEC Electropedia: available at http:// www .electropedia .org/
— IEEE Standards Dictionary Online: available at: http:// dictionary .ieee .org
NOTE Definitions for software engineering terms typically can be found in ISO/IEC/IEEE 24765, available at
www .computer .org/ sevocab.
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved 1
4 Purpose
Users should apply this document to map between their current software life cycle processes consistent
with ISO/IEC 12207:2008 and the processes, activities, and tasks required by ISO/IEC/IEEE 12207:2017.
The user may define and document user implemented processes differently from either
ISO/IEC 12207:2008 or ISO/IEC/IEEE 12207:2017. Then, the mapping tables of this document may
be modified with additional user process information, when the user’s processes are mapped to the
reference processes of ISO/IEC/IEEE 12207:2017 in order to claim conformance with that standard.
This document will help users (who are presumably users of ISO/IEC 12207:2008 as well) to understand
the similarities and differences between the reference process definitions and requirements contained
in ISO/IEC 12207:2008 and ISO/IEC/IEEE 12207:2017 and then to help map their own implemented
lifecycle processes to ISO/IEC/IEEE 12207:2017. Where ISO/IEC/IEEE 12207:2017 requirements (at the
level of processes, outcomes, activities or tasks) differ from those in ISO/IEC 12207:2008, the user will
be able to identify elements (again at the level of processes, activities or tasks) which have gaps or will
not meet the requirements for conformance with ISO/IEC/IEEE 12207:2017.
Users can identify corresponding process outcomes, activities or tasks from the mapping tables in
Clause 6.
This document has none of
...
INTERNATIONAL ISO/IEC/
STANDARD IEEE
12207-2
First edition
2020-10
Systems and software engineering —
Software life cycle processes —
Part 2:
Relation and mapping between ISO/
IEC/IEEE 12207:2017 and ISO/IEC
12207:2008
Ingénierie des systèmes et du logiciel — Processus du cycle de vie du
logiciel —
Partie 2: Relation et correspondance entre l'ISO/IEC/IEEE
12207:2017 et l'ISO/IEC 12207:2008
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 .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Purpose . 2
5 Overview of the mappings . 2
5.1 General . 2
5.2 Compound and singular requirements . 3
6 Outcome mappings . 3
6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008 . 3
6.2 Outcome mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017 .28
7 Activity and task-level mappings .53
7.1 Activity and task-level mapping from ISO/IEC/IEEE 12207:2017 to ISO/
IEC 12207:2008 edition .53
7.2 Activity and task-level mapping from ISO/IEC 12207:2008 to ISO/IEC/
IEEE 12207:2017 .164
Bibliography .267
IEEE notices and abstract .268
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved iii
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.
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 ISO documents should be noted. This document was drafted in accordance with the
rules given in 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) or the IEC
list of patent declarations received (see https:// patents .iec .c).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, 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 Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and Software
Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
A list of all parts in the ISO/IEC/IEEE 12207 series can be found on the ISO website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www .iso .org/ members .html.
© ISO/IEC 2020 – All rights reserved
iv © IEEE 2020 – All rights reserved
Introduction
The processes in ISO/IEC/IEEE 12207:2017 form a comprehensive set from which an organization can
construct software system life cycle models appropriate to its products and services. An organization,
depending on its purpose, can select and apply an appropriate subset to fulfil that purpose.
However, ISO/IEC/IEEE 12207:2017 does not include "software-specific processes" as a specialization
of system processes, as identified in ISO/IEC 12207:2008, Clause 7. Those processes are partially
represented as activities, tasks and NOTEs in processes defined in ISO/IEC/IEEE 12207:2017. This
document supports software engineering users of ISO/IEC 12207:2008 in applying their current
processes, activities and tasks based on the previous edition to perform effectively and efficiently
processes, activities and tasks in ISO/IEC/IEEE 12207:2017. This document also intends to help system
engineers using ISO/IEC/IEEE 12207:2017 (or ISO/IEC/IEEE 15288:2015) collaborate with software
engineers who have used ISO/IEC 12207:2008.
This document can be used in one or more of the following modes in conjunction with
ISO/IEC/IEEE 12207:
— By an organization — to help use the current organizational software processes and assets
derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of
ISO/IEC/IEEE 12207:2017.
— By a project — to help use the current project’s software processes and assets derived from
ISO/IEC 12207:2008 and extend these to processes of ISO/IEC/IEEE 12207:2017 to provide software
systems as products and services.
— By an acquirer and a supplier — to help use the current agreement concerning processes and
activities derived from ISO/IEC 12207:2008 in establishing an environment of desired processes of
ISO/IEC/IEEE 12207:2017.
— By process assessors — to serve as an aid to mapping tasks and activities of the previous edition
of ISO/IEC 12207:2008 to the process reference model in ISO/IEC/IEEE 12207:2017, Annex C for
process assessments that may be used to support organizational process improvement.
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved v
INTERNATIONAL STANDARD ISO/IEC/IEEE 12207-2:2020(E)
Systems and software engineering — Software life cycle
processes —
Part 2:
Relation and mapping between ISO/IEC/IEEE 12207:2017
and ISO/IEC 12207:2008
1 Scope
This document provides the mapping expressing corresponding relations between software life cycle
processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008.
These relations are demonstrated by means of mapping tables that show relationships between
activities and tasks, and process outcomes.
This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017.
This document will help users understand the differences between the reference processes
and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process
enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017.
Also, this document provides to such users the mapping which helps to identify corresponding process
outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017.
The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can
be used as a basis to continuously conduct, improve and extend current process assets including
software specific process assets based on ISO/IEC 12207:2008 for effective implementation of
ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. 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 12207:2017, Systems and software engineering — Software life cycle processes
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 12207:2017 apply.
ISO, IEC and IEEE maintain terminological databases for use in standardization at the following
addresses:
— ISO Online browsing platform: available at https:// www .iso .org/
— IEC Electropedia: available at http:// www .electropedia .org/
— IEEE Standards Dictionary Online: available at: http:// dictionary .ieee .org
NOTE Definitions for software engineering terms typically can be found in ISO/IEC/IEEE 24765, available at
www .computer .org/ sevocab.
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved 1
4 Purpose
Users should apply this document to map between their current software life cycle processes consistent
with ISO/IEC 12207:2008 and the processes, activities, and tasks required by ISO/IEC/IEEE 12207:2017.
The user may define and document user implemented processes differently from either
ISO/IEC 12207:2008 or ISO/IEC/IEEE 12207:2017. Then, the mapping tables of this document may
be modified with additional user process information, when the user’s processes are mapped to the
reference processes of ISO/IEC/IEEE 12207:2017 in order to claim conformance with that standard.
This document will help users (who are presumably users of ISO/IEC 12207:2008 as well) to understand
the similarities and differences between the reference process definitions and requirements contained
in ISO/IEC 12207:2008 and ISO/IEC/IEEE 12207:2017 and then to help map their own implemented
lifecycle processes to ISO/IEC/IEEE 12207:2017. Where ISO/IEC/IEEE 12207:2017 requirements (at the
level of processes, outcomes, activities or tasks) differ from those in ISO/IEC 12207:2008, the user will
be able to identify elements (again at the level of processes, activities or tasks) which have gaps or will
not meet the requirements for conformance with ISO/IEC/IEEE 12207:2017.
Users can identify corresponding process outcomes, activities or tasks from the mapping tables in
Clause 6.
This document has none of
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.