ISO/IEC 20582

Software and systems engineering — Capabilities of build and deployment tools

This document defines the requirements of capabilities of build and deployment tools to support and automate build, package, and deployment work. This document is intended for use in evaluating and selecting build and deployment tools according to the procedures defined in ISO/IEC 20741. By using these two standards together, objective and rational results can be derived for the evaluation and selection of build and deployment tools. This document is independent of development methodologies and approaches (such as Waterfall, Agile, or DevOps).

Ingénierie du logiciel et des systèmes — Capacités des outils de construction et de déploiement

General Information

• Status: Not Published
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Current Stage: 6000 - International Standard under publication
• Start Date: 01-May-2025
• Completion Date: 03-May-2025

Standards Content (Sample)

FINAL DRAFT
International
Standard
ISO/IEC FDIS
ISO/IEC JTC 1/SC 7
Software and systems
Secretariat: BIS
engineering — Capabilities of build
Voting begins on:
and deployment tools
2025-03-05
Voting terminates on:
2025-04-30
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/IEC FDIS 20582:2025(en) © ISO/IEC 2025

FINAL DRAFT
ISO/IEC FDIS 20582:2025(en)
International
Standard
ISO/IEC FDIS
ISO/IEC JTC 1/SC 7
Software and systems
Secretariat: BIS
engineering — Capabilities of build
Voting begins on:
and deployment tools
Voting terminates on:
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO/IEC 2025
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
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 Reference number
ISO/IEC FDIS 20582:2025(en) © ISO/IEC 2025

© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC FDIS 20582:2025(en)
Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Object model for build and deployment tools . 2
4.1 Overview .2
4.2 Use case .3
4.2.1 Build, deployment and CI/CD in system lifecycle . .3
4.2.2 Use cases of the build and deployment tool .4
4.2.3 Use case scenario .4
4.3 Object model for build and deployment entity.8
4.3.1 Overview .8
4.3.2 ResourceEntities.8
4.3.3 ControlEntities .10
5 Entities used in building, deployment, and CI/CD . 14
5.1 Overview .14
5.2 AbstractControlEntities . 15
5.2.1 LinkToExternalLibrary . . 15
5.2.2 LinkToSourceCode . 15
5.2.3 LinkToInternalLibrary . 15
5.2.4 LinkToData . 15
5.2.5 LinkToSupportTool.16
5.2.6 LinkToServer .16
5.2.7 Dependency .16
5.2.8 Procedure .16
5.2.9 Step .16
5.3 BuildEntities .16
5.3.1 BuildDependency .16
5.3.2 BuildStep .18
5.3.3 BuildProcedure . .18
5.3.4 LinkToTranslator .18
5.4 DeploymentEntities .19
5.4.1 DeploymentDependency .19
5.4.2 DeploymentStep . 20
5.4.3 DeploymentProcedure . 20
5.4.4 LinkToInstaller . 20
5.5 CI/CDEntities . 20
5.5.1 CI/CDDependency . 20
5.5.2 CI/CDStep .21
5.5.3 CI/CDProcedure .21
5.5.4 LinkToTestSupportTool .21
6 Capabilities of build and deployment tool .22
6.1 Overview . 22
6.2 Space of dependency in building, deployment, and CI/CD . 22
6.3 Build-related capabilities . 23
6.3.1 Register build procedure . 23
6.3.2 Execute build procedure . 23
6.3.3 Confirm result of build procedure . 25
6.4 Deployment-related capabilities . 25
6.4.1 Register deployment procedure . 25
6.4.2 Execute deployment procedure . 25
6.4.3 Confirm result of deployment procedures .27

© ISO/IEC 2025 – All rights reserved
iii
ISO/IEC FDIS 20582:2025(en)
6.5 CI/CD-related capabilities .27
6.5.1 Register CI/CD procedure .27
6.5.2 Execute CI/CD procedure .27
6.5.3 Confirm result of CI/CD procedure . 28
Annex A (informative) How to use this document with ISO/IEC 20741 .29
Annex B (informative) Overview of the approach for this document .30
Bibliography .32

© ISO/IEC 2025 – All rights reserved
iv
ISO/IEC FDIS 20582:2025(en)
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-governme
...

ISO/IEC FDIS 20582:2024(en)
ISO/IEC JTC 1/SC 7/ N9694
Date: 2025-01-03
Secretariat: BIS
Date: 2025-02-18
Software and systems engineering — Capabilities of build and
deployment tools
FDIS stage
ISO/IEC FDIS 20582:2025(en)
© ISO/IEC 20242025
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'sISO’s member body in the country of the requester.
ISO Copyright Officecopyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: + 41 22 749 01 11
Email: E-mail: [e-mail]
Website: www.iso.org
Published in Switzerland.
© ISO/IEC 2025 – All rights reserved
ii
ISO/IEC FDIS 20582:20242025(en)
Contents
Foreword . vi
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Object model for build and deployment tools . 2
4.1 Overview . 2
4.2 Use case . 3
4.3 Object model for build and deployment entity . 13
5 Entities used in building, deployment, and CI/CD . 25
5.1 Overview . 25
5.2 AbstractControlEntities . 25
5.3 BuildEntities . 27
5.4 DeploymentEntities . 29
5.5 CI/CDEntities . 31
6 Capabilities of build and deployment tool . 33
6.1 Overview . 33
6.2 Space of dependency in building, deployment, and CI/CD . 33
6.3 Build-related capabilities . 35
6.4 Deployment-related capabilities . 37
6.5 CI/CD-related capabilities . 39
Annex A (informative) How to use this document with ISO/IEC 20741 . 42
Annex B (informative) Overview of the approach for this document . 44
Bibliography . 47

3.1
3.1.1
3.1.2
3.1.3
3.1.4
3.1.5
3.1.6
3.2
4.1
4.2
© ISO/IEC 2024 2025 – All rights reserved
iii
ISO/IEC FDIS 20582:2025(en)
4.2.1
4.2.2
4.2.3
4.3
4.3.1
4.3.2
4.3.3
5.1
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
5.3
5.3.1
5.3.2
5.3.3
5.3.4
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.5
5.5.1
5.5.2
5.5.3
5.5.4
6.1
6.2 Space of dependency in Build and Deployment . 22
© ISO/IEC 2025 – All rights reserved
iv
ISO/IEC FDIS 20582:20242025(en)
6.3
6.3.1
6.3.2
6.3.3
6.4
6.4.1
6.4.2
6.4.3
6.5
6.5.1
6.5.2
© ISO/IEC 2024 2025 – All rights reserved
v
ISO/IEC FDIS 20582:2025(en)
6.5.3 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 Joint Technical Committee ISO/IEC JTC 1, 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 2025 – All rights reserved
vi
ISO/IEC FDIS 20582:20242025(en)
Introduction
Build and deployment tools and methods have long been central to software engineering, and the importance
of their role continues to increase. Traditionally, build and deployment tools were simple mechanisms used
to create executable code from the source code written in a programming language, typically comprising a
compiler and a linker bundled with the operating system. Over time, these mechanisms have become much
more complex, where application software is built using the source code and libraries distributed across
multiple servers. Furthermore, the testing and operation of a system often requires deployment to a large
number of servers. Increasing sophistication in software development environments is another factor in the
increasing the importance of advanced build and deployment tools and methods.
Many modern build and deployment tools are now available on the market, independent of the vendor
providing the operating system. These tools can be configured as independent automation on top of compilers
and linkers bundled with individual operating systems, as well as repositories that manage assets. Therefore,
there are multiple options available, and it is essential to choose the appropriate one for each different
software engineering context. This standarddocument provides guidance in the selection of commercially
available tools from different vendors as well as tools provided as open source.
This document treats tasks and tools related to change management and configuration management as out of
scope. Build and deployment processes are typically initiated by modifications to the source code, indicating
they are closely related to change management and configuration management. However, while change
management and configuration management primarily deal with source code, build and deployment involves
the transformation of source code into sophisticated operational representations and structures. Therefore,
change management and configuration management are excluded to enable focus on the single build and
deployment concern.
From a user's perspective, it is important to choose the right tools from the variety of available build and
deployment tools, especially in large organizations. It is imperative that tool evaluation and selection be done
in accordance with fair and public standards. To this end, ISO/IEC 20741 was published in 2017 as a guideline
to evaluate and select software engineering tools. However, ISO/IEC 20741 does not identify the standard
capabilities specific to build and deployment tools since it is generalized without regard to a specific tool
categoriescategory.
This document defines the requirements for capabilities of build and deployment tools and is intended to be
used in conjunction with ISO/IEC 20741 to select the appropriate tool (see Annex AAnnex A).). The document
provides a list of capabilities in build and deployment tools. The capabilities described in this document are
gathered from existing tools (see Annex BAnnex B).).
Build, deploy, and CI/CD tools are separate and independent tools, which couldcan logically be treated in
separate standards. However, in most software engineering environments, they are applied in highly
integrated, interdependent, and continuous workflows. Evaluation and selection are best conducted from this
integrated viewpoint and this document functions as a single standard for this integrated collection tools.
© ISO/IEC 2024 2025 – All rights reserved
vii
DRAFT International Standard ISO/IEC DIS 20582:2024(en)

Software and systems engineering — Capabilities of build and
deployment tools
1 Scope
This document defines the requirements for capabilities of build and deployment tools to support and
automate building, packaging, and deploying work.
This document is intended for use in evaluating and selecting build and deployment tools according to the
procedures defined in ISO/IEC 20741.
This document is applicable to different development methodologies and approaches (e.g. Waterfall, Agile, or
DevOps)).
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions 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/
3.1 3.1
build
process of generating an executable and testable system from source versions or baselines
[SOURCE: ISO/IEC/IEEE 32675:2022]
3.2 3.2
continuous integration
CI
technique that continually merges artifacts, including source code updates from all developers on a team, into
a shared mainline to build and test the developed system
[SOURCE: ISO/IEC/IEEE 32675:2022, modified — The abbreviated term "CI" has been added.]
3.3 3.3
continuous delivery
CD
software engineering practices that allow for frequent releases of new systems (including software) to staging
or various test environments through the use of automated tools
[SOURCE: ISO/IEC/IEEE 32675:2022, modified — The abbreviated term "CD" has been added.]
© ISO/IEC 2024 – All rights reserved

ISO/IEC FDIS 20582:2025(en)
3.4 3.4
continuous deployment
CD
automated process of deploying changes to production by verifying intended features and validations to
reduce risk
[SOURCE: ISO/IEC/IEEE 32675:2022, modified — The abbreviated term "CD" has been added.]
3.5 3.5
deployment
stages of a life cycle in which a system is put into operation and transition issues are resolved
[SOURCE: ISO/IEC/IEEE 32675:2022]
3.6 3.6
package
combine related components into a single, deployable item
Note 1 to entry: A package is used to group elements and provides a namespace for the grouped elements. See
ISO/IEC 19505-2.
[SOURCE: ISO/IEC/IEEE 32675:2022, modified — Note 1 to entry has been added.]
4 Object model for build and deployment tools
4.1 Overview
Generally, tools reduce manual effort by automatically generating entities to be created during the software
development process.
The tools, the entities, and the process are expressed as three views:
— process view;
— entity view;
...