ISO/IEC TR 33022:2024

Information technology - Process assessment - Application of ISO/IEC/IEEE 12207 processes to the ISO/IEC 33020 process capability measurement scale

This document provides a specification for associating the life cycle processes of ISO/IEC/IEEE 12207 with the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of the process capability measurement scale defined in ISO/IEC 33020.

Technologies de l'information — Évaluation du processus — Application des processus ISO/IEC/IEEE 12207 à l'échelle de la mesure de la capacité de processus de l'ISO/IEC 33020

General Information

• Status: Published
• Publication Date: 30-Sep-2024
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7/WG 10 - Process assessment
• Current Stage: 6060 - International Standard published
• Start Date: 01-Oct-2024
• Due Date: 11-Sep-2026
• Completion Date: 01-Oct-2024

Overview

ISO/IEC TR 33022:2024 (Technical Report) specifies how to apply the lifecycle processes defined in ISO/IEC/IEEE 12207 to the ISO/IEC 33020 process capability measurement scale. Its primary purpose is to provide a validated mapping that demonstrates support for process capability levels 1–3 in ISO/IEC 33020. The report is aimed at developers of process assessment models, lead assessors and other stakeholders who need to show that ISO/IEC 33020 process attribute outcomes are met by ISO/IEC/IEEE 12207 life‑cycle process outcomes.

Key topics

• Process capability mapping: Specifies associations between ISO/IEC 33020 process attribute outcomes (PA 1.1, PA 2.1, PA 2.2, PA 3.1, PA 3.2, PA 3.3) and ISO/IEC/IEEE 12207 life‑cycle processes.
• Lifecycle process partitioning: Shows how some 12207 processes are split into establishment and performance sub‑processes (e.g., life cycle model management, infrastructure, human resources, quality, measurement, knowledge).
• Information items & characteristics: Uses information item characteristics as the linking mechanism between process attributes and lifecycle outcomes.
• Generic practices to tasks: Relates ISO/IEC 33020 generic practices to 12207 activities and tasks for objective validation.
• Traceability considerations: Discusses model mapping and traceability with reference to ISO/IEC/IEEE 24774:2021 (model mapping considerations).
• Scope limitations: Notes processes without discernible relationships to ISO/IEC 33020 (e.g., acquisition and decision management are not mapped).

Applications

• Developing process assessment models that align lifecycle activities to the ISO/IEC 33020 capability framework.
• Conducting process assessments to demonstrate compliance with capability levels 1–3, using mapped evidence and information items.
• Assessor guidance: Practical references for lead assessors and assessment sponsors to validate process attribute outcomes by inspection.
• Process improvement and governance: Helps organizations translate ISO/IEC/IEEE 12207 process outputs into measurable capability attributes for quality management, measurement, and continuous improvement.
• Procurement and supplier oversight: Use mappings to evaluate supplier process capability where lifecycle processes are central.

Related standards

• ISO/IEC 33020:2019 - Process capability measurement scale (reference framework).
• ISO/IEC 33001 - Concepts and terminology for process assessment.
• ISO/IEC/IEEE 12207 - System and software lifecycle processes (source of lifecycle process outcomes).
• ISO/IEC/IEEE 24774:2021 - Model mapping and traceability guidance referenced in Annex D.

ISO/IEC TR 33022:2024 is a practical, evidence‑oriented guide for organizations and assessors who need to connect established lifecycle process practices (12207) with the ISO/IEC 33020 process capability model for reliable, auditable assessments.

Standards Content (Sample)

Technical
Report
ISO/IEC TR 33022
First edition
Information technology — Process
2024-10
assessment — Application of ISO/
IEC/IEEE 12207 processes to the
ISO/IEC 33020 process capability
measurement scale
Technologies de l'information — Évaluation du processus —
Application des processus ISO/IEC/IEEE 12207 à l'échelle de la
mesure de la capacité de procesus de l'ISO/IEC 33020
Reference number
© ISO/IEC 2024
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 at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: [phone]
Email: [e-mail]
Website: www.iso.org
Published in Switzerland
© ISO/IEC 2024 – All rights reserved
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Content of the process capability measurement framework . 1
4.1 General .1
4.2 Relationships between model elements.3
Annex A (informative) Associations between the ISO/IEC 33020 process attribute outcomes,
ISO/IEC/IEEE 12207 life cycle process outcomes and information items . 4
Annex B (informative) Associations between the ISO/IEC 33020 generic practices, ISO/IEC/
IEEE 12207 life cycle process activities, tasks and information item characteristics .16
Annex C (informative) Listing of the information items and their characteristics .44
Annex D (informative) Establishing the traceability between model elements with reference to
ISO/IEC/IEEE 24774:2021, Annex B .106
Bibliography .107

© ISO/IEC 2024 – 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 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 or www.iec.ch/members_experts/refdocs).
ISO and IEC draw attention to the possibility that the implementation of this document may involve the
use of (a) patent(s). ISO and IEC take no position concerning the evidence, validity or applicability of any
claimed patent rights in respect thereof. As of the date of publication of this document, ISO and IEC had not
received notice of (a) patent(s) which may be required to implement this document. However, implementers
are cautioned that this may not represent the latest information, which may be obtained from the patent
database available at www.iso.org/patents and https://patents.iec.ch. ISO and IEC shall not be held
responsible for identifying any or all such patent rights.
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.
In the IEC, see www.iec.ch/understanding-standards.
This document was prepared by Technical Committee ISO/IEC JTC1, Information technology, Subcommittee
SC 7, Software and systems engineering.
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 and
www.iec.ch/national-committees.

© ISO/IEC 2024 – All rights reserved
iv
Introduction
This document provides a specification for mapping the ISO/IEC/IEEE 12207 life cycle processes to the
ISO/IEC 33020 process attributes with the intent of demonstrating support for the levels 1 to 3 of the
ISO/IEC 33020 process capability measurement framework.
This document is primarily addressed to developers of process assessment models for the process quality
characteristic of process capability. It is also addressed to the lead assessor and other stakeholders, such as
the sponsor of the assessment, who need to be assured that the requirements of the ISO/IEC 33020 process
measurement framework have been met.
Within this document:
— Clause 4 provides a summary description of the relationship between the ISO/IEC 33020 process
attribute outcomes and the ISO/IEC/IEEE 12207 life cycle processes.
— Annex A extends the summary mapping in Clause 4 by providing details of the relationship between
the process attribute outcomes and the life cycle process outcomes. Links to the information items
listed in Annex C are identified. These details are provided for validating by inspection the relationships
between the process attribute outcomes of ISO/IEC 33020 and the ISO/IEC/IEEE 12207 life cycle process
outcomes.
— Annex B focuses on the relationships between the generic practices associated with ISO/IEC 33020 and
the task descriptions of ISO/IEC/IEEE 12207. These model elements are linked via the information item
characteristics listed in Annex C.
— Annex C provides a listing of the applicable information items and their characteristics.
— Annex D provides an overview of the key concerns arising from the application of ISO/IEC/IEEE 24774
when attempting to demonstrate objective relationships between process model elements.

© ISO/IEC 2024 – All rights reserved
v
Technical Report ISO/IEC TR 33022:2024(en)
Information technology — Process assessment — Application
of ISO/IEC/IEEE 12207 processes to the ISO/IEC 33020
process capability measurement scale
1 Scope
This document provides a specification for associating the life cycle processes of ISO/IEC/IEEE 12207 with
the process attribute outcomes of ISO/IEC 33020 with the intent of demonstrating support for levels 1 to 3 of
the process capability measurement scale defined in ISO/IEC 33020.
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 33001, Information technology — Process assessment — Concepts and terminology
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 33001 apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
4 Content of the process capability measurement framework
4.1 General
In ISO/IEC 33020:2019, Clause 5, the relationship between process attributes and process capability levels
is described.
Process capability is defined in ISO/IEC 33020:2019, Clause 5 on a six-point ordinal scale that enables process
capability to be assessed from the bottom of the scale, 'incomplete', through to the top end of the scale,
'innovating'. The scale represents increasing capability of an implemented process, from failing to achieve
the process purpose through to continually improving and able to respond to process change.
The relationship between the process capability levels and the process attributes is shown in Table 1. In
addition, a summary view is presented of the relationship of the process attributes to the life cycle processes
associated with ISO/IEC/IEEE 12207.
Two processes from ISO/IEC/IEEE 12207 do not appear in the list in Table 1, namely, the acquisition and
decision management processes. These outcomes of these processes do not have any discernible relationships
to the process attribute outcomes of ISO/IEC 33020.
Certain ISO/IEC/IEEE 12207 processes have been partitioned into sub processes, namely life cycle model
management, infrastructure management, human resource management, knowledge management, quality
management, measurement and quality assurance. This action has been taken to address outcomes in the
basic processes that deal with firstly, establishment concerns, and secondly, performance (or operational)

© ISO/IEC 2024 – All rights reserved
concerns. The 'establishment' outcomes of these sub processes are mapped to ISO/IEC 33020:2019 PA
3.1 concerns. The 'performance' concerns of the sub processes are mapped to either PA 3.2 or PA 3.3, as
appropriate.
As an example, with reference to ISO/IEC/IEEE 12207:2017, 6.2.1, life cycle model management, the basic
and sub process outcomes are presented in Table 1.
Table 1 — ISO/IEC/IEEE 12207:2017, 6.2.1, life cycle model management
Basic process outcomes Sub process: Establish Sub process: Perform
a) Organizational policies and procedures for the a) Organizational policies and procedures for
management and deployment of life cycle models the management and deployment of life cycle
and processes are established. models and processes are established.
b) Responsibility, accountability, and authority b) Responsibility, accountability, and authori-
within life cycle policies, processes, models, and ty within life cycle policies, processes, models,
procedures are defined. and procedures are defined.
c) Life cycle models and processes for use by the c) Life cycle models and processes for use
organization are assessed. by the organization are assessed.
d) Prioritized process, model, and procedure im- d) Prioritized process, model, and proce-
provements are implemented. dure improvements are implemented.
The list of ISO/IEC/IEEE 12207 processes that have been mapped as sub processes is presented in Table 2.
Table 2 — ISO/IEC/IEEE 12207 processes mapped as sub processes
Basic process Basic processes Sub process refer- Sub processes
reference in ence in ISO/IEC/
ISO/IEC/IEEE IEEE 12207:2017
12207:2017
6.2.1 Life cycle model management 6.2.1.1 Life cycle model management: Establish
6.2.1.2 Life cycle model management: Assess and improve
6.2.2 Infrastructure management 6.2.2.1 Infrastructure management: Establish
6.2.2.2 Infrastructure management: Maintain
6.2.4 Human resource management 6.2.4.1 Human resource management: Establish
6.2.4.2 Human resource management: Perform
6.2.5 Quality management 6.2.5.1 Quality management: Establish
6.2.5.2 Quality management: Perform
6.2.6 Knowledge management 6.2.6.1 Knowledge management: Establish
6.2.6.2 Knowledge management: Share and manage
6.3.7 Measurement 6.3.7.1 Measurement: Establish
6.3.7.2 Measurement: Perform
6.3.8 Quality assurance 6.3.8.1 Quality assurance: Establish
6.3.8.2 Quality assurance: Perform
The summary relationship between the ISO/IEC/IEEE 12207 processes and the ISO/IEC 33020 process
capability levels is presented in Table 3.

© ISO/IEC 2024 – All rights reserved
Table 3 — Relationship between the ISO/IEC 33020 process capability levels and process attributes,
and the ISO/IEC/IEEE 12207 life cycle processes
Process ISO/IEC 33020:2019 process Reference in ISO/IEC/IEEE 12207:2017 life cycle processes
Capability attribute outcomes ISO/IEC/IEEE
Level 12207:2017
1 5.2.3.2 PA 1.1 Process perfor- 6.4 The processes in this group are typically identified in the assessment
mance process attribute scope. The processes ISO/IEC/IEEE 12207:2017, 6.4 are likely candi-
dates.
2 5.2.4.2 PA 2.1 Performance man- 6.3.1 Project planning
agement process attribute
6.3.2 Project assessment and control
6.3.4 Risk management
2 5.2.4.3 PA 2.2 Documented in- 6.3.5 Configuration management
formation management process
6.3.6 Information management
attribute
3 5.2.5.2 PA 3.1 Process definition 6.2.1.1 Life cycle model management: Establish
process attribute
6.2.2.1 Infrastructure management: Establish
6.2.4.1 Human resource management: Establish
6.2.5.1 Quality management: Establish
6.2.6.1 Knowledge management: Establish
6.3.7.1 Measurement: Establish
6.3.8.1 Quality assurance: Establish
3 5.2.5.3 PA 3.2 Process deploy- 6.2.1.2 Life cycle model management: Assess and improve
ment process attribute
6.2.2.2 Infrastructure management: Maintain
6.2.3 Portfolio management
6.2.4.2 Human resource management: Perform
6.2.6.2 Knowledge management: Share and manage
3 5.2.5.4 PA 3.3 Process assurance 6.2.5.2 Quality management: Perform
process attribute
6.3.7.2 Measurement: Perform
6.3.8.2 Quality assurance: Perform
4.2 Relationships between model elements
The rationale for the selection of the ISO/IEC/IEEE 12207 life cycle processes and their associations with the
ISO/IEC 33020 process attribute outcomes can be found in Annexes A and B.
Annex A elaborates the summary mapping in Clause 4 by providing extended details of the relationship
between the ISO/IEC 33020 process attribute outcomes and the ISO/IEC/IEEE 12207 life cycle process
outcomes. Links to the information items described in Annex C are provided in a summary format. The level
of detail provides the basis for validation by inspecting the relationships between the ISO/IEC 33020 process
attribute outcomes and the ISO/IEC/IEEE 12207 life cycle process outcomes.
Annex B focuses on the relationships between the ISO/IEC 33020 generic practices and the
ISO/IEC/IEEE 12207 activity/task descriptions. These model elements are linked via the information item
characteristics, as listed in Annex C.

© ISO/IEC 2024 – All rights reserved
Annex A
(informative)
Associations between the ISO/IEC 33020 process attribute outcomes,
ISO/IEC/IEEE 12207 life cycle process outcomes and information items
A.1 General
This annex describes the relationships between the ISO/IEC 33020 process attribute outcomes and the
ISO/IEC/IEEE 12207 life cycle process outcomes. The model outcomes are linked by applicable information
item characteristics, as described in Annex D.
A.2 Associations between the ISO/IEC 33020 process attribute outcomes, ISO/IEC/
IEEE 12207 life cycle processes and information items
Information item characteristics provide the link between the ISO/IEC 33020 process attribute outcomes
and the ISO/IEC/IEEE 12207 life cycle process outcomes. Each linked information item in Table A.1 is
indicated by its reference label and name, and the reference number of the characteristic.
Table A.1 provides the basis for a detailed validation by inspection of the associations between the
ISO/IEC 33020 process attribute outcomes and ISO/IEC/IEEE 12207 life cycle process outcomes in
accordance with ISO/IEC/IEEE 24774:2021, Annex B model mapping considerations.
Table A.1 — Associations between the ISO/IEC 33020 process attribute outcomes,
ISO/IEC/IEEE 12207 life cycle process outcomes and information item characteristics
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
5.2.3.2 PA 1.1 Process performance 6.1.2 Supply 03-23 Request for propos-
process attribute 1) An acquirer for a product or service is al (RFP)
1) the process achieves its de- identified. 3)
fined process outcomes. 04-28 Supply strategy
3)
6.1.2 Supply 03-24 Response to RFP
2) A response to the acquirer's request is 2)
produced. 08-65 RFP acquisition re-
quirements review record
2)
6.1.2 Supply 01-2 Supply agreement
3) An agreement is established between 5), 6)
the acquirer and supplier.
6.1.2 Supply 08-07 Agreement perfor-
4) A product or service is provided. mance review record
6)
08-75 Supply Delivery
Records (for system, soft-
ware, product or service)
3)
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.1.2 Supply 08-52 Product acceptance
5) Supplier obligations defined in the record
agreement are satisfied. 8)
08-73 Supplier payment
receipt record
2)
11-6 Request for Supply
(e.g., Request for Propos-
al, Request for Tender)
1)
6.1.2 Supply 08-52 Product acceptance
6) Responsibility for the acquired product record

or service, as directed by the agreement, 6)
is transferred.
6.4.1 Business or mission analysis 03-08 Identify business
1) The problem or opportunity space is opportunities
defined. 6)
04-02 Business strategy
3)
08-10 Business opportu-
nities review record
3)
6.4.1 Business or mission analysis 03-08 Identify business
2) The solution space is characterized. opportunities
7)
6.4.1 Business or mission analysis 03-07 Business opportu-
3) Preliminary operational concepts and nity space

other concepts in the life cycle stages are 7)
defined.
6.4.1 Business or mission analysis 03-07 Business opportu-
4) Candidate alternative solution classes nity space
are identified and analysed. 8)
6.4.1 Business or mission analysis 08-09 Business opportu-
5) The preferred candidate alternative nities evaluation record
solution class(es) are selected. 6), 7)
6.4.1 Business or mission analysis 08-20 Enabling system
6) Any enabling systems or services records: Business or

needed for business or mission analysis Mission Analysis.
are available. 1), 2)
6.4.2 Stakeholder needs and requirements 02-2 Stakeholders
definition 3)
1) Stakeholders of the system are identi- 04-29 System require-
fied. ments definition strategy
3)
6.4.2 Stakeholder needs and requirements 03-31 Stakeholder Needs
definition 11)
2) Required characteristics and context 03-32 System operational

of use of capabilities and concepts in the concept
life cycle stages, including operational 7), 8)
concepts, are defined.
6.4.2 Stakeholder needs and requirements 12-11 System stakeholder
definition requirements
3) Constraints on a system are identified. 13)
6.4.2 Stakeholder needs and requirements 03-31 Stakeholder Needs
definition 12), 14)
4) Stakeholder needs are defined.
6.4.2 Stakeholder needs and requirements 03-02 Analyse stakehold-
definition er requirements
5) Stakeholder needs are prioritized and 8), 9), 11)
transformed into clearly defined stake- 03-31 Stakeholder Needs
holder requirements. 13)
6.4.2 Stakeholder needs and requirements 12-11 System stakeholder
definition requirements
6) Critical performance measures are 14), 15)
defined.
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.4.2 Stakeholder needs and requirements 03-02 Analyse stakehold-
definition er requirements
7) Stakeholder agreement that their needs 10)

and expectations are reflected adequately 08-44 Manage stakehold-
in the requirements is achieved. er requirements
3)
6.4.2 Stakeholder needs and requirements 08-27 Enabling system
definition records: Stakeholder
8) Any enabling systems or services needs and requirements
needed for stakeholder needs and require- 1), 2)
ments are available.
6.4.3 System/software requirements defi- 03-34 System require-
nition ments definition
1) The system or element description, 5), 6)

including interfaces, functions and bound- 12-10 System require-
aries, for a system solution is defined. ments
16)
6.4.3 System/software requirements defi- 12-10 System require-
nition ments
2) System/software requirements 18), 19), 20)

(functional, performance, process,
non-functional, and interface) and design
constraints are defined.
6.4.3 System/software requirements defi- 12-10 System require-
nition ments
3) Critical performance measures are 17)
defined.
6.4.3 System/software requirements defi- 03-33 System require-
nition ments analysis
4) The system/software requirements are 11), 12), 13), 14)
analysed.
6.4.3 System/software requirements defi- 08-29 Enabling system
nition records: System/software
5) Any enabling systems or services need- requirements
ed for system/software requirements 1), 2)
definition are available.
6.4.3 System/software requirements defi- 08-45 Manage system
nition requirements
6) Traceability of system/software re- 3)
quirements to stakeholder requirements
is developed.
6.4.4 Architecture definition 03-03 Architecture
1) Identified stakeholder concerns are definition
addressed by the architecture. 10), 11), 12), 13)
6.4.4 Architecture definition 03-05 Architecture view-
2) Architecture viewpoints are developed. points
7), 8), 9), 10)
6.4.4 Architecture definition 03-06 Architecture views
3) Context, boundaries, and external 11)
interfaces of the system are defined.
6.4.4 Architecture definition 03-06 Architecture views
4) Architecture views and models of the 12), 13), 14), 15), 16)
system are developed.
6.4.4 Architecture definition 08-66 Requirements
5) Concepts, properties, characteristics, allocation
behaviours, functions, or constraints that 9), 12), 13)

are significant to architecture decisions of
the system are allocated to architectural
entities.
6.4.4 Architecture definition 08-66 Requirements
6) System elements and their interfaces allocation
are identified. 10)
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.4.4 Architecture definition 08-08 Architecture
7) Architecture candidates are assessed. assessment result
8), 9), 10)
6.4.4 Architecture definition 08-08 Architecture
8) An architectural basis for processes assessment result
throughout the life cycle is achieved. 11)
6.4.4 Architecture definition 08-41 Manage architec-
9) Alignment of the architecture with ture
requirements and design characteristics 8), 9), 10), 11), 12)

is achieved. 08-66 Requirements
allocation
11)
6.4.4 Architecture definition 08-19 Enabling system
10) Any enabling systems or services records: Architecture

needed for architecture definition are definition
available. 1), 2)
6.4.5 Design definition 03-28 Software system
1) Design characteristics of each system design definition
element are defined. 5), 6)
03-29 Software system
element design
12)
03-30 Software system
element evaluation
9)
6.4.5 Design definition 03-29 Software system
3) Design enablers necessary for design element design
definition are selected or defined. 13)
6.4.5 Design definition 03-29 Software system
4) Interfaces between system elements element design

composing the system are defined or 15)
refined.
6.4.5 Design definition 03-29 Software system
5) Design alternatives for system ele- element design
ments are assessed. 14)
03-30 Software system
element evaluation
10), 11), 12)
6.4.5 Design definition 03-29 Software system
6) Design artifacts are developed. element design
16)
08-43 Manage software
system element design
6)
6.4.5 Design definition 08-21 Enabling system
7) Any enabling systems or services need- records: Design definition
ed for design definition are available. 1), 2)
6.4.5 Design definition 08-43 Manage software
8) Traceability of the design character- system element design

istics to the architectural entities of the 7)
system architecture is established.
6.4.6 System analysis 04-30 Systems analysis
1) System analyses needed are identified. strategy
9), 10), 11), 12), 13)
6.4.6 System analysis 08-48 Perform systems
2) System analysis assumptions and analysis
results are validated. 8), 9), 10)
6.4.6 System analysis 08-48 Perform systems
3) System analysis results are provided analysis
for decisions. 11), 12)
6.4.6 System analysis 08-28 Enabling system
4) Any enabling systems or services need- records: System analysis
ed for system analysis are available. 1), 2)

© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.4.7 Implementation 04-07 Implementation
1) Implementation constraints that influ- Plan

ence the requirements, architecture, or 6), 7)
design are identified.
6.4.7 Implementation 07-8 Software element
2) A system element is realized. 9), 10), 11)
08-69 Software code &
test evaluation record
5), 6)
6.4.7 Implementation 08-42 Manage software
3) A system element is packaged or stored. elements
5), 6)
6.4.7 Implementation 08-23 Enabling system
4) Any enabling systems or services need- records: Implementation
ed for implementation are available. 1), 2)
6.4.8 Integration 04-26 Software integra-
1) Integration constraints that influence tion plan

system requirements, architecture, or de- 11), 13)
sign, including interfaces, are identified.
6.4.8 Integration 04-26 Software integra-
2) Approach and checkpoints for the cor- tion plan

rect operation of the assembled interfaces 12)
and system functions are defined.
6.4.8 Integration 08-24 Enabling system
3) Any enabling systems or services need- records: Integration
ed for integration are available. 1), 2)
6.4.8 Integration 07-6 Integrated system
4) A system composed of implemented 9), 10)
system elements is integrated.
6.4.8 Integration 08-71 Software integra-
7) Integration results and anomalies are tion test results
identified. 3)
6.4.9 Verification 04-32 Verification
1) Constraints of verification that influ- strategy
ence the requirements, architecture, or 14), 15), 16), 17)

design are identified. 06-3 Verification Proce-
dures
5)
6.4.9 Verification 08-32 Enabling system
2) Any enabling systems or services need- records: Verification
ed for verification are available. 1), 2)
6.4.9 Verification 08-93 Verification prob-
6) Verification results and anomalies are lems and non-conform-

identified. ances
6), 7)
6.4.10 Transition 04-27 Software release
1) Transition constraints that influence plan

system/software requirements, architec- 12), 13), 14), 15), 16)
ture, or design are identified.
6.4.10 Transition 08-30 Enabling system
2) Any enabling systems or services need- records: Transition
ed for transition are available. 1), 2)
6.4.10 Transition 08-76 System/ software
3) The site is prepared. installation record
17), 18)
6.4.10 Transition 08-76 System/ software
4) The system, as installed in its opera- installation record

tional location, is capable of delivering its 19)
specified functions.
6.4.10 Transition 08-76 System/ software
5) Operators, users and other stakehold- installation record

ers necessary to the system utilization 20)
and support are trained.
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.4.10 Transition 08-72 Software operation
6) Transition results and anomalies are release test results
identified. 5), 6)
6.4.10 Transition 08-76 System/ software
7) The installed system is activated and installation record
ready for operation. 21)
6.4.11 Validation 04-31 Validation plan
1) Validation criteria for stakeholder 14), 16), 17)
requirements are defined. 06-2 Validation Proce-
dures
5)
6.4.11 Validation 08-90 Validation Records
2) The availability of services required by 2)
stakeholders is confirmed.
6.4.11 Validation 04-31 Validation plan
3) Constraints of validation that influence 15)

the requirements, architecture, or design
are identified.
6.4.11 Validation 06-2 Validation Proce-
4) The system or system element is vali- dures
dated. 6)
6.4.11 Validation 08-31 Enabling system
5) Any enabling systems or services need- records: Validation
ed for validation are available. 1), 2)
6.4.11 Validation 08-90 Validation Records
6) Validation results and anomalies are 4)
identified. 08-91 Validation prob-

lems and non-conform-
ances
3)
6.4.11 Validation 08-92 Validation test
7) Objective evidence that the realized suite confirmation record

system or system element satisfies stake- 2)
holder needs is provided.
6.4.12 Operation 04-15 Operation plan
1) Operation constraints that influence 8), 9), 10)

system/software requirements, architec-
ture, or design are identified.
6.4.12 Operation 08-26 Enabling system
2) Any enabling systems, services, and records: Operation

material needed for operation are avail- 1), 2)
able.
6.4.12 Operation 04-15 Operation plan
3) Trained, qualified operators are avail- 11)
able.
6.4.12 Operation 08-46 Operation actions
4) System product services that meet 13), 14), 16), 18)
stakeholder requirements are delivered.
6.4.12 Operation 08-46 Operation actions
5) System product performance during 15), 17)

operation is monitored. 11-4 Operation requests
9)
6.4.12 Operation 08-47 Operation records
6) Support to the customer is provided. 7), 8)

11-4 Operation requests
7), 8)
6.4.13 Maintenance 04-14 Maintenance Plan
1) Maintenance constraints that influence 8), 9), 10), 11)

system requirements, architecture, or
design are identified.
6.4.13 Maintenance 08-25 Enabling system
2) Any enabling systems or services need- records: Maintenance
ed for maintenance are available. 1), 2)

© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
6.4.13 Maintenance 09-07 Maintenance
3) Replacement, repaired, or revised sys- (Logistics) Report
tem elements are made available. 10), 11), 12), 13)

11-3 Maintenance Re-
quests
14), 15), 16), 17)
6.4.13 Maintenance 08-40 Maintenance
4) The need for changes to address correc- (Logistics) Records
tive, perfective, or adaptive maintenance 8)

is reported. 11-3 Maintenance Re-
quests
18), 19)
6.4.13 Maintenance 08-40 Maintenance
5) Failure and lifetime data, including (Logistics) Records
associated costs, is determined. 9), 10)
6.4.14 Disposal 04-06 Disposal strategy
1) Disposal constraints are provided as 6), 7), 8), 9)

inputs to requirements, architecture,
design, and implementation.
6.4.14 Disposal 08-22 Enabling system
2) Any enabling systems or services need- records: Disposal
ed for disposal are available. 1), 2)
6.4.14 Disposal 08-17 Disposal Records
3) The system elements or waste products 14), 15), 16), 17), 18), 19)
are destroyed, stored, reclaimed or recy-
cled in accordance with requirements, e.g.
, safety and security requirements.
6.4.14 Disposal 08-17 Disposal Records
4) The environment is returned to its 20)
original or an agreed state.
6.4.14 Disposal 08-17 Disposal Records
5) Records of disposal actions and analy- 21)
sis are available.
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 03-17 Project goals
ment process attribute 1) Objectives and plans are defined. 6), 7)
1) results to be achieved are de-
termined and communicated;
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 04-25 Risk Management
ment process attribute 1) Objectives and plans are defined. Plan
2) risks that can affect perfor- 6), 7)
mance of the process are deter-
6.3.4 Risk management 03-26 Risk identification
mined and addressed;
1) Risks are identified. 3)
03-27 Risk management
profile
5), 6), 7)
6.3.4 Risk management 03-25 Risk analysis
2) Risks are analysed. 6), 7), 8)
6.3.4 Risk management 08-67 Risk treatment
3) Risk treatment options are identified, evaluation
prioritized, and selected. 6), 7), 8)
6.3.4 Risk management 08-67 Risk treatment
4) Appropriate treatment is implemented. evaluation
9)
6.3.4 Risk management 09-16 Risk monitoring
5) Risks are evaluated to assess changes report
in status and progress in treatment. 4), 5), 6)

© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 04-03 Configuration Man-
ment process attribute 1) Objectives and plans are defined. agement Plan
3) performance of the process is 8), 9)
planned, monitored, measured, 04-08 Information man-
evaluated and adjusted (as agement plan
needed); 11), 13)
04-20 Project budget
3)
04-21 Project plan
14)
04-22 Project schedule
3)
04-33 Work breakdown
structure
4)
6.3.2 Project assessment and control 04-19 Project assessment
1) Performance measures or assessment strategy
results are available. 3)
09-13 Project status
report
20), 27), 30)
6.3.2 Project assessment and control 09-13 Project status
3) Adequacy of resources is assessed. report
24)
6.3.2 Project assessment and control 09-13 Project status
4) Technical progress reviews are per- report
formed. 22), 26)
6.3.2 Project assessment and control 09-13 Project status
5) Deviations in project performance from report
plans are investigated and analysed. 21), 25), 28)
6.3.2 Project assessment and control 11-5 Project change
7) Corrective action is defined and request
directed, when project achievement is not 9), 11)
meeting targets.
6.3.2 Project assessment and control 11-5 Project change
8) Project replanning is initiated, as request
necessary. 10)
6.3.2 Project assessment and control 08-55 Project continua-
9) Project action to progress (or not) from tion authorization record
one scheduled milestone or event to the 1)
next is authorized.
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 04-08 Information man-
ment process attribute 1) Objectives and plans are defined. agement plan
4) responsibilities and authori- 12)
ties for performing the process
6.3.1 Project planning 04-21 Project plan
are determined, assigned and
2) Roles, responsibilities, accountabilities, 11)
communicated;
and authorities are defined.
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 04-21 Project plan
ment process attribute 1) Objectives and plans are defined. 12)
5) resources necessary for per-
6.3.1 Project planning 04-21 Project plan
forming the process are deter-
3) Resources and services necessary 13)
mined, provided and maintained
to achieve the objectives are formally 08-59 Project resource
(as needed);
requested and committed. request record
3)
6.3.1 Project planning 08-56 Project initiation
4) Plans for the execution of the project authorization record
are activated. 9), 10)
5.2.4.2 PA 2.1 Performance manage- 6.3.2 Project assessment and control 09-13 Project status
ment process attribute 2) Adequacy of roles, responsibilities, ac- report
6) person(s) performing the countabilities, and authorities is assessed. 23)
process are competent on the
basis of appropriate education,
training, or experience;
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
5.2.4.2 PA 2.1 Performance manage- 6.3.1 Project planning 04-21 Project plan
ment process attribute 1) Objectives and plans are defined. 15)
7) interfaces between the
6.3.2 Project assessment and control 09-13 Project status
involved parties are managed to
6) Affected stakeholders are informed of report
ensure both effective commu-
project status. 29)
nication and the level of control
expected.
5.2.4.3 PA 2.2 Documented informa- 6.3.6 Information management 04-10 Information
tion management process 1) Information to be managed is identi- management plan: item
attribute fied. identification
1) requirements for the doc- 1)
umented information of the
6.3.6 Information management 04-09 Information man-
process are determined;
2) Information representations are agement plan: Presenta-
defined. tion
1)
5.2.4.3 PA 2.2 Documented informa- 6.3.5 Configuration management 08-13 Configuration man-
tion management process 1) Items requiring configuration manage- agement identification
attribute ment are identified and managed. records
3) documented information is 10), 11)
appropriately identified, and
6.3.5 Configuration management 12-03 Configuration
controlled according to require-
2) Configuration baselines are estab- Baseline
ments;
lished. 6), 7)
6.3.5 Configuration management 08-06 Agreement impact
3) Changes to items under configuration evaluation record
management are controlled. 3)
6.3.5 Configuration management 09-02 Configuration
4) Configuration status information is Status Report
available. 5), 6)
6.3.6 Information management 07-1 Information item
1) Information to be managed is identi- 10), 11), 12), 13), 14), 15),
fied. 16), 18), 19), 20), 21), 22)
6.3.6 Information management 07-3 Information item:
5) Information is available to designated Publish
stakeholders. 1)
5.2.4.3 PA 2.2 Documented informa- 6.3.5 Configuration management 08-11 Configuration Man-
tion management process 3) Changes to items under configuration agement Change Requests
attribute management are controlled. 9), 10), 11)
4) documented information is 11-1 Agreement Change
reviewed and approved for suit- Request
ability and adequacy in accord- 5), 6)
ance with planned arrangements
and adjusted as necessary to
meet requirements;
5.2.4.3 PA 2.2 Documented informa- 6.3.6 Information management 07-1 Information item
tion management process 3) Information is obtained, developed, 9), 17)
attribute transformed, stored, validated, presented, 08-04 Agreement amend-
5) documented information is [and disposed of]. ment record
determined, maintained and re- 3), 4)
tained to the extent necessary to 08-61 Quality Assurance
have confidence that the process Records
has been performed as planned 4)
and to demonstrate the conform- 10-1 Information Item
ity of products and/or services to Archive
their requirements. 3)
6.3.6 Information management 07-2 Information item:
4) The status of information is identified. Item status
1)
6.3.6 Information management 08-61 Quality Assurance
5) Information is available to designated Records
stakeholders. 5)
6.3.6 Information management 08-33 Information item
6) Information is archived, or disposed of, disposal record
as required. 3)
© ISO/IEC 2024 – All rights reserved
TTabablele A A.11 ((ccoonnttiinnueuedd))
ISO/IEC Description ISO/IEC/IEEE Description ISO/IEC/IEEE
33020:2019 12207:2017 12207:2017
process
attribute
outcomes
5.2.5.2 PA 3.1 Process definition pro- 6.2.1.1 Life cycle model management: Estab- 03-10 Life cycle model
cess attribute lish 22), 23), 24), 25), 26),
1) a standard process, including 1) Organizational policies and procedures 27), 28)
appropriate tailoring guidelines, for the management and deployment
is established and maintained of life cycle models and processes are
that describes the fundamental established.
elements that must be incorpo-
6.2.5.1 Quality management: Establish 03-22 Quality manage-
rated into a defined process;
1) Organizational quality management ment authorities and
policies, objectives, and procedures are responsibilities
defined and implemented. 3)
04-23 Quality Manage-
ment Plan
4)
6.2.5.1 Quality management: Establish 12-09 Quality evaluation
2) Quality evaluation criteria and meth- criteria and methods
ods are established. 2)
6.3.7.1 Measurement: Establish 03-13 Organizational
1) Information needs are identified. characteristics
2)
03-14 Organizational
information needs
3)
04-11 Information meas-
urement strategy
3), 4)
6.3.7.1 Measurement: Establish 03-09 Information meas-
2) An appropriate set of measures, based ures
on the information needs, is identified or 2)
developed.
6.3.8.1 Quality assurance: Establish 04-24 Quality assurance
1) Project quality assurance procedures strategy
are defined and implemented. 6)
6.3.8.1 Quality assurance: Establish 04-24 Quality assurance
2) Criteria and methods for quality assur- strategy
ance evaluations are defined. 7)
5.2.5.2 PA 3.1 Process definition pro- 6.2.1.1 Life cycle model management: Estab- 03-11 Life cycle model:
cess attribute lish Responsibilities
4) roles, competences, respon- 2) Responsibility, accountability, and au- 1)
sibilities and authorities for thority within life cycle policies, process-
performing the standard process es, models, and procedures are defined.
are determined;
6.2.4.1 Human resource management: Estab- 03-12 Organization skills
lish identification
1) Skills required by projects are identi- 2)
fied. 03-15 Organizational skill
needs
2)
5.2.5.2 PA 3.1
...