Systems and software engineering -- Software life cycle processes

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

General Information

Status
Published
Publication Date
22-Oct-2020
Current Stage
5060 - Close of voting Proof returned by Secretariat
Start Date
05-Sep-2020
Completion Date
04-Sep-2020
Ref Project

Buy Standard

Standard
ISO/IEC/IEEE 12207-2:2020 - Systems and software engineering -- Software life cycle processes
English language
267 pages
sale 15% off
Preview
sale 15% off
Preview
Draft
ISO/IEC/IEEE FDIS 12207-2:Version 24-apr-2020 - Systems and software engineering -- Software life cycle processes
English language
270 pages
sale 15% off
Preview
sale 15% off
Preview

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/IEEE 12207-2:2020(E)
ISO/IEC 2020
IEEE 2020
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
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
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 12207-2:2020(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.

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
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
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
---------------------- Page: 5 ----------------------
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
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
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 conformance requirements. However, process outcome or activity/task

mapping of this document can be used to support conformance to ISO/IEC/IEEE 12207:2017. Such a

case is stated in Clause 1.

NOTE 1 The mappings in this document expand on ISO/IEC/IEEE 12207:2017, Table I.1, "Comparison of

processes in ISO/IEC/IEEE 12207:2017 and the previous edition", and ISO/IEC/IEEE 12207:2017, Table I.2,

"Comparison of process outcomes in ISO/IEC/IEEE 12207:2017 and software-related outcomes in the previous

edition".

NOTE 2 Analysis of the relationships between the tasks and activities of ISO/IEC 12207:2008 and

ISO/IEC/IEEE 12207, as detailed in this document, can assist in process assessment and improvement.

ISO/IEC 33004 can be used to develop a process reference model.

The following are typical use cases when users of this document can apply mappings:

— users can understand which processes, outcomes, activities, or tasks of ISO/IEC/IEEE 12207:2017

cover or subsume the outcomes, activities, or tasks of processes (including software specific

processes) of ISO/IEC 12207:2008;

— users can identify outcomes, activities, or tasks of processes (including software specific processes)

of ISO/IEC 12207:2008 that are to be continuously conducted, enhanced, extended or improved to

meet the requirements of ISO/IEC/IEEE 12207:2017 and/or to demonstrate achievement of required

outcomes, activities and tasks of the software life cycle processes.
5 Overview of the mappings
5.1 General

The process models used in ISO/IEC 12207:2008 and ISO/IEC 15288:2008 were harmonized to the

process model used in both ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.

This document provides bi-directional mappings for outcomes, activities, and tasks between

ISO/IEC 12207:2008 and ISO/IEC/IEEE 12207:2017.
This document contains the following tables:
— Clause 6 Outcome mappings
— Mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008 (Table 1)
© ISO/IEC 2020 – All rights reserved
2 © IEEE 2020 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
— Mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017 (Table 2)
— Clause 7 Activity and Task-level mappings
— Mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008 (Table 3)
— Mapping from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017 (Table 4)

These tables can be used to determine how requirements in ISO/IEC 12207:2008 were treated or

requirements in ISO/IEC/IEEE 12207:2017 have originated. Where a relationship is identified, it does

not necessarily imply that the intent is identical.

This document provides a correspondence between ISO/IEC 12207:2008 and ISO/IEC/IEEE 12207:2017.

It does not provide any explanatory commentary on why a change has been made, or the significance of

the change.

NOTE Couplings of associative multiple outcomes or tasks are often mapped, rather than one-to-one

mapping, from ISO/IEC 12207:2008 to ISO/IEC/IEEE 12207:2017.
5.2 Compound and singular requirements

A compound requirement is a requirement (i.e. 'shall') containing more than one obligation that needs

to be satisfied. There are many instances in ISO/IEC 12207:2008 where the requirement is expressed as

'.. shall do this and do that and do the other'.

Although this may be a single sentence, it represents three separate obligations that will need to be

satisfied.

Singular requirements are created from compound requirements by separating out these distinct

requirements, when such a separated mapping helps to provide more obvious relations.

By way of example, the following sub-clause fragment is taken from ISO/IEC 12207:2008, 6.4.10.3.1.1,

task ‘Software Maintenance Process, Process implementation’, “The maintainer shall develop,

document, and execute plans and procedures for conducting the activities and tasks of the Software

Maintenance Process.”
Three singular requirements can be identified in this compound requirement:

— “6.4.10.3.1.1-1 The maintainer shall develop[, document, and execute] plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

— “6.4.10.3.1.1-2 The maintainer shall [develop,] document[, and execute] plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

— “6.4.10.3.1.1-3 The maintainer shall [develop, document, and] execute plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

Square brackets (i.e. [ ]) are used to identify the particular requirement(s) to be ignored in reading the

numbered compound requirements.

NOTE Additionally, ‘should’ and ‘may’ statements and descriptions in NOTEs are used to make mapping,

when they are helpful for user to understand reasons for correspondences.
6 Outcome mappings
6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008

Table 1 correlates process outcomes required by ISO/IEC/IEEE 12207:2017 to process outcomes

required in ISO/IEC 12207:2008. The mapping indicates related outcomes that may be helpful in meeting

© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)

the requirements of ISO/IEC/IEEE 12207:2017. There is no assumption that all the required outcomes

of ISO/IEC 12207:2008 are required to fulfil the required outcomes of ISO/IEC/IEEE 12207:2017.

When the subclause is indicated by ‘l.m.n.2 x)’, it indicates the process outcome x) that is described in the

subclause for outcome ‘l.m.n.2’ of process ‘l.m.n’ in ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008

respectively.

NOTE An only process outcome with asterisk marking, i.e. ‘ (*) ’, has a discrepancy mapping between the

one in ISO/IEC/IEEE 12207:2017, Table I.2 to provide the more obvious relation, though this is extension of

ISO/IEC/IEEE 12207:2017, Table I.2.
Table 1 — Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC 12207:2008
Outcomes Sub Sub Outcomes
(ISO/IEC/IEEE 12207:2017) clause clause (ISO/IEC 12207:2008)
6.1.1 Acquisition process

Acquisition 2. a) A request for supply 6.1.1.2a) 6.1.1.2a) Acquisition 2. a) acquisition needs, goals,

is prepared. product and/or service acceptance criteria and
acquisition strategies are defined;

Acquisition 2. b) One or more suppli- 6.1.1.2b) 6.1.1.2c) Acquisition 2. c) one or more suppliers is

ers are selected. selected;

Acquisition 2. c) An agreement is 6.1.1.2c) 6.1.1.2b) Acquisition 2. b) an agreement is developed

established between the acquirer and that clearly expresses the expectation, respon-

supplier. sibilities and liabilities of both the acquirer and
the supplier;

Acquisition 2. d) A product or service 6.1.1.2d) 6.1.1.2d) Acquisition 2. d) a product and/or service is ac-

complying with the agreement is quired that satisfies the acquirer’s stated need;

accepted.
6.1.1.2d) 6.1.1.2e) Acquisition 2. e) the acquisition is monitored
so that specified constraints such as cost,
schedule and quality are met;
6.1.1.2d) 6.1.1.2f) Acquisition 2. f) supplier deliverables are
accepted;

Acquisition 2. e) Acquirer obligations 6.1.1.2e) 6.1.1.2g) Acquisition 2. g) any identified open items

defined in the agreement are satisfied. have a satisfactory conclusion as agreed to by

the acquirer and the supplier.
6.1.2 Supply process

Supply 2. a) An acquirer for a product 6.1.2.2a) 6.1.2.2a) Supply 2. a) an acquirer for a product or service

or service is identified. is identified;

Supply 2. b) A response to the acquir- 6.1.2.2b) 6.1.2.2b) Supply 2. b) a response to an acquirer's request

er’s request is produced. is produced;

Supply 2. c) An agreement is estab- 6.1.2.2c) 6.1.2.2c) Supply 2. c) an agreement is established

lished between the acquirer and between the acquirer and the supplier for
supplier. developing, maintaining, operating, packaging,
delivering, and installing the product and/or
service;

Supply 2. d) A product or service is 6.1.2.2d) 6.1.2.2d) Supply 2. d) a product and/or service that

provided. meets the agreed requirements are developed
by the supplier;

Supply 2. e) Supplier obligations de- 6.1.2.2e) 6.1.2.2e) Supply 2. e) the product and/or service is de-

fined in the agreement are satisfied. livered to the acquirer in accordance with the

agreed requirements;

Supply 2. f) Responsibility for the ac- 6.1.2.2f) 6.1.2.2f) Supply 2. f) the product is installed in accord-

quired product or service, as directed ance with the agreed requirements.
by the agreement, is transferred.
© ISO/IEC 2020 – All rights reserved
4 © IEEE 2020 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
Table 1 (continued)
Outcomes Sub Sub Outcomes
(ISO/IEC/IEEE 12207:2017) clause clause (ISO/IEC 12207:2008)
6.2.1 Life cycle model Management
process

Life cycle model management 2. a) 6.2.1.2a) 6.2.1.2a) Life Cycle Model Management 2. a) policies

Organizational policies and proce- and procedures for the management and de-

dures for the management and deploy- ployment of life cycle models and processes are

ment of life cycle models and processes provided;
are established.

Life cycle model management 2. b) 6.2.1.2b) 6.2.1.2b) Life Cycle Model Management 2. b) responsi-

Responsibility, accountability, and bility, accountability and authority for life cycle

authority within life cycle policies, management are defined;
processes, models, and procedures are
defined.

Life cycle model management 2. c) 6.2.1.2c) 6.2.1.2c) Life Cycle Model Management 2. c) life cycle

Life cycle models and processes for use processes, models and procedures for use by

by the organization are assessed. the organization are defined, maintained and
improved;

Life cycle model management 2. d) 6.2.1.2d) 6.2.1.2d) Life Cycle Model Management 2. d) prior-

Prioritized process, model, and proce- itized process improvements are implemented.

dure improvements are implemented.
6.2.2 Infrastructure Management
process

Infrastructure Management 2. a) 6.2.2.2a) 6.2.2.2a) Infrastructure Management 2. a) the require-

The requirements for infrastructure ments for infrastructure to support processes

are defined. are defined;
Infrastructure Management 2. b)
Infrastructure Management 2. b) the infra-
The infrastructure elements are iden- 6.2.2.2b) 6.2.2.2b)
structure elements are identified and specified;
tified and specified.

Infrastructure Management 2. c) 6.2.2.2c) 6.2.2.2c) Infrastructure Management 2. c) the infra-

Infrastructure elements are developed structure elements are acquired;
or acquired.
6.2.2.2c) 6.2.2.2d) Infrastructure Management 2. d) the infra-
structure elements are implemented;

Infrastructure Management 2. d) 6.2.2.2d) 6.2.2.2e) Infrastructure Management 2. e) a stable

The infrastructure is available. and reliable infrastructure is maintained and
improved.
6.2.3 Portfolio Management process

Portfolio Management 2.a) Business 6.2.3.2a) 6.2.3.2a) Project Portfolio Management 2. a) business

venture opportunities, investments or venture opportunities, investments or necessi-

necessities are qualified and prior- ties are qualified, prioritized and selected;

itized.

Portfolio Management 2. b) Projects 6.2.3.2b) 6.3.1.2a) Project Planning 2. a) the scope of the work for

are identified. the project is defined;

Portfolio Management 2. c) Resourc- 6.2.3.2c) 6.2.3.2b) Project Portfolio Management 2. b) resources

es and budgets for each project are and budgets for each project are identified and

allocated. allocated;

Portfolio Management 2. d) Project 6.2.3.2d) 6.2.3.2c) Project Portfolio Management 2. c) project

management responsibilities, account- management accountability and authorities are

ability, and authorities are defined. defined;

Portfolio Management 2. e) Projects 6.2.3.2e) 6.2.3.2d) Project Portfolio Management 2. d) projects

meeting agreement and stakeholder meeting agreement and stakeholder require-
requirements are sustained. ments are sustained;
© ISO/IEC 2020 – All rights reserved
© IEEE 2020 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE 12207-2:2020(E)
Table 1 (continued)
Outcomes Sub Sub Outcomes
(ISO/IEC/IEEE 12207:2017) clause clause (ISO/IEC 12207:2008)

Portfolio Management 2. f) Projects 6.2.3.2f) 6.2.3.2e) Project Portfolio Management 2. e) projects

not meeting agreement or satisfying not meeting agreement or stakeholder require-

stakeholder requirements are redi- ments are redirected or terminated;
rected or terminated.
Portfolio Management 2. g) Projects 6.2.3.2g) None None of outcomes is mapped.
that have completed agreements and
satisfied stakeholder requirements
are closed.
6.2.4 Human Resource
Management process

Human Resource Management 2. 6.2.4.2a) 6.2.4.2a) Human Resource Management 2. a) skills

a) Skills required by projects are required by projects are identified;
identified.

Human Resource Management 2. b) 6.2.4.2b) 6.2.4.2b) Human Resource Management 2. b) neces-

Necessary human resources are pro- sary human resources are provided to projects;

vided to projects.

Human Resource Management 2. 6.2.4.2c) 6.2.4.2c) Human Resource Management 2. c) skills

c) Skills of personnel are developed, of personnel are developed, maintained or
maintained or enhanced. enhanced;
6.2.4.2c) 6.2.4.2e) Human Resource Management 2. e) individ-
ual knowledge, information and skills are col-
lected, shared, reused and improved through-
out the organization.

Human Resource Management 2. 6.2.4.2d) 6.2.4.2d) Human Resource Management 2. d) con-

d) Conflicts in multi-project resource flicts in multi-project resource demands are

demands are resolved. resolved;
6.2.5 Quality Management process

Quality Management 2. a) Organiza- 6.2.5.2a) 6.2.5.2a) Quality Management 2. a) organization qual-

tional quality management policies, ity management policies and procedures are
objectives, and procedures are defined defined;
and implemented.
Quality Management 2. b) organization quali-
6.2.5.2a) 6.2.5.2b)
ty objectives are defined;
Quality Management 2. c) accountability and
6.2.5.2a) 6.2.5.2c)
authority for quality management are defined;

Quality Management 2. b) Quality 6.2.5.2b) 6.2.5.2a) Quality Management 2. a) organization qual-

evaluation criteria and methods are ity management policies and procedures are
established. defined;

Quality Management 2. c) Resourc- 6.2.5.2c) 6.2.4.2b) Human Resource Management 2. b) neces-

es and information are provided to sary human resources are provided to projects;

projects to support the operation and
monitoring of project quality assur-
ance activities.

Quality Management 2. d) Quality 6.2.5.2d) 6.2.5.2d) Quality Management 2. d) the status of cus-

assurance evaluation results are gath- tomer satisfaction is monitored;
ered and analyzed.

Quality Management 2. e) Quality 6.2.5.2e) 6.2.5.2e) Quality Management 2. e) appropriate ac-

management policies and procedures tion is take
...

DRAFT INTERNATIONAL STANDARD
ISO/IEC/IEEE/DIS 12207-2
ISO/IEC JTC 1/SC 7 Secretariat: BIS
Voting begins on: Voting terminates on:
2019-10-23 2020-01-15
Systems and software engineering — Software life cycle
processes —
Part 2:
Relation and mapping between ISO/IEC/IEEE 12207-
1:2017 and ISO/IEC/IEEE 12207:2008
ICS: 35.080
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
This document is circulated as received from the committee secretariat.
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC/IEEE/DIS 12207-2:2019(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
ISO/IEC 2019
RIGHTS OF WHICH THEY ARE AWARE AND TO
PROVIDE SUPPORTING DOCUMENTATION. IEEE 2019
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
ISO/IEC/IEEE/DIS 12207-2:2019(E)
Contents

Foreword ......................................................................................................................................................................... iv

Introduction..................................................................................................................................................................... v

1 Scope .................................................................................................................................................................... 1

2 Normative references .................................................................................................................................... 1

3 Terms and definitions.................................................................................................................................... 1

4 Purpose ............................................................................................................................................................... 1

5 Overview of the mappings ............................................................................................................................ 2

5.1 General ................................................................................................................................................................ 2

5.2 Compound and singular requirements ................................................................................................... 3

6 Outcome mappings ......................................................................................................................................... 4

6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008

edition ................................................................................................................................................................. 4

6.2 Outcome mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE 12207:2017

edition .............................................................................................................................................................. 23

7 Activity and Task-level mappings .......................................................................................................... 42

7.1 Activity and Task-level mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE

12207:2008 edition ..................................................................................................................................... 42

7.2 Activity and Task-level mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE

12207:2017 edition ................................................................................................................................... 119

Bibliography ............................................................................................................................................................... 185

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2019
© IEEE 2019

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
Fax: +41 22 749 09 47
Email: copyright@iso.org Email: stds.ipr@ieee.org
̹ Ȁ ʹͲͳͻ–ŽŽ”‹‰Š–•”‡•‡”˜‡†
Website: www.iso.org Website: www.ieee.org
̹ ʹͲͳͻ–ŽŽ”‹‰Š–•”‡•‡”˜‡† ‹‹‹
Published in Switzerland
© ISO/IEC 2019 – All rights reserved
ii © IEEE 2019 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
Contents

Foreword ......................................................................................................................................................................... iv

Introduction..................................................................................................................................................................... v

1 Scope .................................................................................................................................................................... 1

2 Normative references .................................................................................................................................... 1

3 Terms and definitions.................................................................................................................................... 1

4 Purpose ............................................................................................................................................................... 1

5 Overview of the mappings ............................................................................................................................ 2

5.1 General ................................................................................................................................................................ 2

5.2 Compound and singular requirements ................................................................................................... 3

6 Outcome mappings ......................................................................................................................................... 4

6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008

edition ................................................................................................................................................................. 4

6.2 Outcome mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE 12207:2017

edition .............................................................................................................................................................. 23

7 Activity and Task-level mappings .......................................................................................................... 42

7.1 Activity and Task-level mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE

12207:2008 edition ..................................................................................................................................... 42

7.2 Activity and Task-level mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE

12207:2017 edition ................................................................................................................................... 119

Bibliography ............................................................................................................................................................... 185

© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies

(ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical

committees. Each member body interested in a subject for which a technical committee has been established has

the right to be represented on that committee. International organizations, governmental and non-governmental,

in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical

Commission (IEC) on all matters of electrotechnical standardization.

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 technical committees is to prepare International Standards. Draft International Standards adopted

by the technical committees are circulated to the member bodies for voting. Publication as an International Standard

requires approval by at least 75 % of the member bodies casting a vote.

In exceptional circumstances, when a 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), it may decide by a simple majority

vote of its participating members to publish a Technical Report. A Technical Report is entirely informative in nature

and does not have to be reviewed until the data it provides 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 shall not be held responsible for identifying any or all such patent rights.

The committee responsible for this document is ISO/IEC JTC1, Information Technology, Subcommittee SC7,

Software and Systems 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 first edition of ISO/IEC/IEEE 12207-2 is intended to complement ISO/IEC/IEEE 12207:2017 by providing a

crosswalk of required outcomes, activities and tasks between ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE

12207:2008.

ISO/IEC/IEEE 12207 consists of the following parts, under the general title Systems and Software Engineering —

Software life cycle processes:
— Part 1: Concepts and requirements

— Part 2: Relation and mapping between ISO/IEC/IEEE 12207-1:2017 and ISO/IEC/IEEE 12207:2008

ISO/IEC/IEEE 12207 Part 1 is the current version of ISO/IEC/IEEE 12207:2017, although without expression of a

Part 1. ISO/IEC/IEEE 12207 Part 2 is additionally provided as extension part of ISO/IEC/IEEE 12207. Future

revisions of ISO/IEC/IEEE 12207:2017 will be renumbered and titled as a Part 1 document of the ISO/IEC/IEEE

12207 series.
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved iv
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
Introduction

The processes in ISO/IEC/IEEE 12207-1:2017, which is only a renumbered version 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 Clause 7 of ISO/IEC/IEEE 12207:2008. Those processes are

subdivided into lower level detailed processes and partially described as tasks and Notes in processes

defined by introducing system views in the new edition of ISO/IEC/IEEE 12207:2017. This document

supports software engineering users of ISO/IEC/IEEE 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 the new edition of 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/IEEE 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/IEEE 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/IEEE 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/IEEE 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/IEEE 12207:2008 to the process reference model in Annex C of ISO/IEC/IEEE 12207:2017-

1 for process assessments that may be used to support organizational process improvement.

© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
Systems and software engineering — Software life cycle processes
— Part 2: Relation and mapping between ISO/IEC/IEEE 12207-
1:2017 and ISO/IEC/IEEE 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 the previous edition ISO/IEC/IEEE 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 the 2008 edition to transition to using the 2017 edition.

This document will help users understand the differences between the reference processes and requirements of the

two editions of ISO/IEC/IEEE12207, and help the user to understand any potential gaps or process enhancements

might be needed in seeking conformance to, and/or use of ISO/IEC/IEEE 12207:2017. Also, this document provides

to such users the mapping which helps to identify corresponding and compatible process outcomes, activities and

tasks of processes for software systems in the ISO/IEC/IEEE 12207:2017.

The mapping between ISO/IEC/IEEE12207:2017 and 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/IEEE12207:2008 for effective implementation of the new edition of ISO/IEC/IEEE 12207:2017. These

process activities and tasks can be applied iteratively.
2 Normative references
There are no normative references in this document.
3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO/IEC 12207:2018 and ISO/IEC/IEEE

24765: 2017 apply.

ISO and IEC and IEEE maintain terminological databases for use in standardization at the following addresses:

— ISO Online browsing platform: available at http://www.iso.org/obp
— IEC Electropedia: available at http://www.electropedia.org/

— IEEE Standards Dictionary Online: available at

NOTE Definitions for software engineering terms typically can be found in ISO/IEC/IEEE 24765, available at

www.computer.org/sevocab
4 Purpose

Users should apply this document to map between their current software life cycle processes consistent with

ISO/IEC/IEEE 12207:2008 and the processes, activities, and tasks required by the current version, ISO/IEC/IEEE

12207:2017.
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)

The user may define and document user implemented processes differently from either ISO/IEC/IEEE 12207:2008

or ISO/IEC/IEEE 12207:2017. Then, the mapping tables of this ISO/IEC/IEEE 12207-2 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/IEEE 12207:2008 as well) to understand the

similarities and differences between the reference process definitions and requirements contained in ISO/IEC/IEEE

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/IEEE 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 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 of this

document.

This ISO/IEC/IEEE 12207-2 document has none of conformance requirements. However, process outcome or

activity/task mapping of this ISO/IEC/IEEE 12207-2 can be used to support conformance to ISO/IEC/IEEE

12207:2017 (i.e. 12207-1). So, such case will be stated in 1. Scope.

NOTE 1 The mappings in this document expand on ISO/IEC/IEEE 12207:2017, Table I.1, Comparison of processes in

ISO/IEC/IEEE 12207:2017 and the previous edition, and Table I.2, Comparison of process outcomes in ISO/IEC/IEEE

12207:2017 and software-related outcomes in the previous edition.

NOTE 2 Analysis of the relationships between the tasks and activities of the previous edition and the current edition of

ISO/IEC/IEEE 12207, as detailed in this document, can assist in process assessment and improvement. ISO/IEC 33004 may be

used to develop a process reference model.

The following are typical use cases when users of this document can apply mappings:

— Users can understand which processes, outcomes, activities, or tasks of ISO/IEC/IEEE 12207:2017 cover or

subsume the outcomes, activities, or tasks of processes (including software specific processes) of ISO/IEC/IEEE

12207:2008;

— Users can identify outcomes, activities, or tasks of processes (including software specific processes) of

ISO/IEC/IEEE 12207:2008 that are to be continuously conducted, enhanced, extended or improved to meet the

requirements of ISO/IEC/IEEE 12207:2017 and/or to demonstrate achievement of required outcomes,

activities and tasks of the software life cycle processes.
5 Overview of the mappings
5.1 General

The process models used in the 2008 versions of ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 were harmonized

to the process model used in both ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015.

This document provides bi-directional mappings for outcomes, activities, and tasks between ISO/IEC/IEEE

12207:2008 and ISO/IEC/IEEE 12207:2017.
This document contains the following tables:
— Clause 6 Outcome mappings
 Mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008 (Table1)
 Mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE 12207:2017 (Table2)
— Clause 7 Activity and Task-level mappings
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved 2
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
 Mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008 (Table3)
 Mapping from ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE 12207:2017 (Table4)

These tables can be used to determine how requirements in the previous edition were treated or requirements in

the current edition have originated. Where a relationship is identified, it does not necessarily imply that the intent

is identical.

This document provides a correspondence between the previous and current editions of ISO/IEC/IEEE 12207. It

does not provide any explanatory commentary on why a change has been made, or the significance of the change.

NOTE Couplings of associative multiple outcomes or tasks are often mapped, rather than one-to-one mapping, from

ISO/IEC/IEEE 12207:2008 to ISO/IEC/IEEE 12207:2017.
5.2 Compound and singular requirements

A compound requirement is a requirement (i.e. 'shall') containing more than one obligation that needs to

be satisfied. There are many instances in ISO/IEC/IEEE 12207:2008 where the requirement is expressed

'.. shall do this and do that and do the other'.

Although this may be a single sentence, it represents three separate obligations that will need to be

satisfied.

Singular requirements are created from compound requirements by separating out these distinct

requirements, when such a separated mapping helps to provide more obvious relations.

By way of example, the following sub-clause fragment is taken from ISO/IEC/IEEE 12207:2008 task

‘6.4.10 Software Maintenance Process, 3.1 Process implementation 1’, 1 sentence, “The maintainer shall

develop, document, and execute plans and procedures for conducting the activities and tasks of the

Software Maintenance Process.”
Three singular requirements can be identified in this compound requirement:

“6.4.10.3.1.1.1-1 The maintainer shall develop, [document, and execute] plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

“6.4.10.3.1.1.1-2 The maintainer shall [develop], document, [and execute] plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

“6.4.10.3.1.1.1-3 The maintainer shall [develop, document, and] execute plans and procedures for

conducting the activities and tasks of the Software Maintenance Process.”

Square brackets (i.e. [ ]) are used to identify the particular requirement(s) to be ignored in reading the

numbered compound requirements.

NOTE Additionally, ‘should’ and ‘may’ statements and descriptions in NOTEs are used to make mapping, when they are

helpful for user to understand reasons for correspondences.
© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)
6 Outcome mappings

6.1 Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008 edition

Table 1 correlates process outcomes required by ISO/IEC/IEEE 12207:2017 to process outcomes

required in ISO/IEC/IEEE 12207:2008. The mapping indicates related outcomes that may be helpful in

meeting the requirements of the ISO/IEC/IEEE 12207:2017. There is no assumption that all the required

outcomes of the ISO/IEC/IEEE 12207:2008 are required to fulfil the required outcomes of ISO/IEC/IEEE

12207:2017.

When the sub clause column expresses ‘l.m.n.2 x)’, it indicates the process outcome x) that is described in sub clause

for outcome ‘l.m.n.2’ of process ‘l.m.n’ in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 12207:2008 respectively.

NOTE An only process outcome with aster marking, i.e. ‘ (*) ’, has a discrepancy mapping between one on Table I.2 in Annex

I.2 of ISO/IEC/IEEE 12207:2017 to provide the more obvious relation, though this is extension of Table I.2.

Table 1 — Outcome mapping from ISO/IEC/IEEE 12207:2017 to ISO/IEC/IEEE 12207:2008

Process Outcomes (ISO/IEC/IEEE 12207:2017) Process Outcomes (ISO/IEC/IEEE 12207:2008)

6.1.1 Acquisition process

Acquisition 2. a) A request for supply is 6.1.1 6.1.1 Acquisition 2. a) acquisition needs, goals, product and/or

prepared. .2a) .2a) service acceptance criteria and acquisition strategies are
defined;

Acquisition 2. b) One or more suppliers are 6.1.1 6.1.1 Acquisition 2. c) one or more suppliers is selected;

selected. .2b) .2c)

Acquisition 2. c) An agreement is established 6.1.1 6.1.1 Acquisition 2. b) an agreement is developed that clearly

between the acquirer and supplier. .2c) .2b) expresses the expectation, responsibilities and liabilities of both

the acquirer and the supplier;
6.1.1 6.1.2 Supply 2. c) an agreement is established between the acquirer
.2c) .2c) and the supplier for developing, maintaining, operating,
packaging, delivering, and installing the product and/or service;

Acquisition 2. d) A product or service complying 6.1.1 6.1.1 Acquisition 2. d) a product and/or service is acquired that

with the agreement is accepted. .2d) .2d) satisfies the acquirer’s stated need;
6.1.1 6.1.1 Acquisition 2. e) the acquisition is monitored so that specified
.2d) .2e) constraints such as cost, schedule and quality are met;
6.1.1 6.1.1 Acquisition 2. f) supplier deliverables are accepted;
.2d) .2f)

Acquisition 2. e) Acquirer obligations defined in 6.1.1 6.1.1 Acquisition 2. g) any identified open items have a satisfactory

the agreement are satisfied. .2e) .2g) conclusion as agreed to by the acquirer and the supplier.

6.1.2 Supply process

Supply 2. a) An acquirer for a product or service 6.1.2 6.1.2 Supply 2. a) an acquirer for a product or service is identified;

is identified. .2a) .2a)

Supply 2. b) A response to the acquirer’s request 6.1.2 6.1.2 Supply 2. b) a response to an acquirer's request is produced;

is produced. .2b) .2b)

Supply 2. c) An agreement is established 6.1.2 6.1.2 Supply 2. c) an agreement is established between the acquirer

between the acquirer and supplier. .2c) .2c) and the supplier for developing, maintaining, operating,

packaging, delivering, and installing the product and/or service;

Supply 2. d) A product or service is provided. 6.1.2 6.1.2 Supply 2. d) a product and/or service that meets the agreed

.2d) .2d) requirements are developed by the supplier;

Supply 2. e) Supplier obligations defined in the 6.1.2 6.1.2 Supply 2. e) the product and/or service is delivered to the

agreement are satisfied. .2e) .2e) acquirer in accordance with the agreed requirements;

© ISO/IEC 2019 – All rights reserved
© IEEE 2019 – All rights reserved 4
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE DIS 12207-2: 2019(E)

Process Outcomes (ISO/IEC/IEEE 12207:2017) Process Outcomes (ISO/IEC/IEEE 12207:2008)

Supply 2. f) Responsibility for the acquired 6.1.2 6.1.2 Supply 2. f) the product is installed in accordance with the

product or service, as directed by the agreement, .2f) .2f) agreed requirements.
is transferred.
6.2.1 Life cycle model Management process

Life cycle model management 2. a) 6.2.1 6.2.1 Life Cycle Model Management 2. a) policies and procedures

Organizational policies and procedures for the .2a) .2a) for the management and deployment of life cycle models and

management and deployment of life cycle models processes are provided;
and processes are established.

Life cycle model management 2. b) 6.2.1 6.2.1 Life Cycle Model Management 2. b) responsibility,

Responsibility, accountability, and authority .2b) .2b) accountability and authority for life cycle management are

within life cycle policies, processes, models, and defined;
procedures are defined.

Life cycle model management 2. c) Life cycle 6.2.1 6.2.1 Life Cycle Model Management 2. c) life cycle processes,

models and processes for use by the organization .2c) .2c) models and procedures for use by the organization are defined,

are assessed. maintained and improved;

Life cycle model management 2. d) Prioritized 6.2.1 6.2.1 Life Cycle Model Management 2. d) prioritized process

process, model, and procedure improvements are .2d) .2d) improvements are implemented.

implemented.
6.2.2 Infrastructure Management process

Infrastructure Management 2. a) The 6.2.2 6.2.2 Infrastructure Management 2. a) the requirements for

requirements for infrastructure are defined. .2a) .2a) infrastructure to support processes are defined;

Infrastructure Management 2. b) The
6.2.2 6.2.2 Infrastructure Management 2. b) the infrastructure elements
infrastructure elements are identified and
.2b) .2b) are identified and specified;
specified.

Infrastructure Management 2. c) Infrastructure 6.2.2 6.2.2 Infrastructure Management 2. c) the infrastructure elements

elements are developed or acquired. .2c) .2c) are acquired;
6.2.2 6.2.2 Infrastructure Management 2. d) the infrastructure elements
.2c) .2d) are implemented;

Infrastructure Management 2. d) The 6.2.2 6.2.2 Infrastructure Management 2. e) a stable and reliable

infrastructure is available. .2d)
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.