ISO/IEC/IEEE 24748-6:2023
(Main)Systems and software engineering — Life cycle management — Part 6: System and software integration
Systems and software engineering — Life cycle management — Part 6: System and software integration
This document: — provides supplemental requirements and guidance for the planning and performing of the integration processes given in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; — provides guidance on the relationship between the integration process and other life cycle processes. — specifies requirements for information items to be produced as a result of using the integration process, including the content of the information items. This document is applicable to: — those who use or plan to use ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or both, on projects dealing with human-made systems, software-intensive systems, and products and services related to those systems, regardless of the project scope, methodology, size, or complexity; — anyone planning or performing integration activities to aid in ensuring that the application of the integration process and its relationships to other system life cycle processes conform to ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207.
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 6: Intégration du système et du logiciel
General Information
Relations
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/
STANDARD IEC/IEEE
24748-6
First edition
2023-07
Systems and software engineering —
Life cycle management —
Part 6:
System and software integration
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 6: Intégration du système et du logiciel
Reference number
ISO/IEC/IEEE 24748-6:2023(E)
© ISO/IEC 2023
© IEEE 2023
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2023
© IEEE 2023
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
ii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 3
4 Conformance . 3
4.1 Conformance to processes . 3
4.2 Conformance to information item content . 3
4.3 Full conformance . 3
4.4 Tailored conformance . 4
4.4.1 Processes . 4
4.4.2 Information items . . 4
5 Integration concepts . 4
5.1 General . 4
5.2 Interface concept . 4
5.3 Aggregation and synthesis concepts . 5
5.4 Integration concept . 5
5.5 Relationship of integration to life cycle processes . 6
5.6 Progressive interface definition . 7
5.7 Integration over the life cycle . 7
5.8 Iteration and recursion in integration . 8
5.8.1 General . 8
5.8.2 Iterative application of processes . 8
5.8.3 Recursive application of processes . 8
5.9 Regression testing in integration . 8
5.10 Integration enabling systems . 8
6 Integration process planning and application purposes . 9
6.1 General . 9
6.2 Integration planning and application guidelines . 9
6.2.1 General . 9
6.2.2 Integration strategy . 9
6.2.3 Efficiency considerations in the integration strategy . 10
6.2.4 Integration context. 11
6.2.5 Roles and competencies of integration team . 11
6.2.6 Methods used to perform integration .12
6.3 Integration process application requirements and guidelines . 20
6.3.1 General .20
6.3.2 Purpose . 20
6.3.3 Outcomes . 22
6.3.4 Activities and tasks .23
6.4 Other processes used in relationship to integration process application . 31
6.4.1 General . 31
6.4.2 Agreement processes . 31
6.4.3 Organizational project-enabling processes . 31
6.4.4 Technical management processes. 31
6.4.5 Technical processes . 32
6.5 Integration of systems-of-systems . 37
6.6 Integration throughout a system life cycle .38
7 Information item requirements .38
7.1 General .38
iii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
7.2 Integration plan .38
Annex A (Informative) Coupling matrixes .40
Bibliography .42
IEEE notices and abstract .43
iv
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE 24748-6:2023(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/IEC documents 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).
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.ch).
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.
ISO/IEC/IEEE 24748-6 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.
This first edition cancels and replaces ISO/IEC TS 24748-6:2016, which has been technically revised.
The main changes are as follows:
— changed from a Technical Specification to an International Standard;
— updated to reflect the process requirements of ISO/IEC/IEEE 12207:2017 and
ISO/IEC/IEEE 15288:2023;
— added material specific to software integration and systems-of-systems integration, as well as
system aggregation.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website.
v
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
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.
vi
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
Introduction
Both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 include an integration process that focuses
on aggregating the elements comprising a system. The integration process depends on a clear
understanding of interfaces of all kinds and the use, possibly repeated, of the verification process and
the validation process.
Systems that this document are concerned with are as described in ISO/IEC/IEEE 12207 and
ISO/IEC/IEEE 15288, i.e. systems that are human-made, comprised of any mixture of products and
services and can be configured with one or more of the following: hardware, software, data, humans,
processes (e.g. a review process or processes for providing service to users), procedures (e.g. operator
instructions), facilities, materials and naturally occurring entities (e.g. water, organisms, minerals).
The purpose of this document is to elaborate and facilitate the usage of the integration process given in
ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 by providing requirements and guidance for the planning
and performing of that process, including requirements for the information items to be provided for
systems and software integration, considering:
— the underlying concepts of aggregation, integration, interface, synthesis, verification, and validation;
— the possible composition of that human-made system;
— the life cycle stages of a system at which one or more parts of the integration process can occur;
— the context of the domain in which the system functions.
For life cycle process information items (documentation) described in ISO/IEC/IEEE 15288 and
ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15289 summarises requirements for their content and provides
guidance on their development. Although this document identifies additional required information
items with related content for the integration process, it does not require a specific name, format,
recording media or explicit details for population of the information item's required content.
NOTE This document is intended to be consistent with the other parts of the ISO/IEC/IEEE 24748 series.
vii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO/IEC/IEEE 24748-6:2023(E)
Systems and software engineering — Life cycle
management —
Part 6:
System and software integration
1 Scope
This document:
— provides supplemental requirements and guidance for the planning and performing of the
integration processes given in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207;
— provides guidance on the relationship between the integration process and other life cycle processes.
— specifies requirements for information items to be produced as a result of using the integration
process, including the content of the information items.
This document is applicable to:
— those who use or plan to use ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or both, on projects
dealing with human-made systems, software-intensive systems, and products and services related
to those systems, regardless of the project scope, methodology, size, or complexity;
— anyone planning or performing integration activities to aid in ensuring that the application of
the integration process and its relationships to other system life cycle processes conform to
ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207.
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
ISO/IEC/IEEE 15288:2023, Systems and software engineering — System life cycle processes
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 15288,
ISO/IEC/IEEE 12207 and the following apply.
ISO, IEC and IEEE 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/
— IEEE Standards Dictionary Online: available at: http:// dictionary .ieee .org
1
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
NOTE For additional terms and definitions in the field of systems and software engineering, see
ISO/IEC/IEEE 24765, which is published periodically as a “snapshot” of the Systems and Software Engineering
Vocabulary (SEVOCAB) database and is publicly accessible at www .computer .org/ sevocab.
3.1.1
aggregate, noun
result of combining one or more physical, logical, or both, system elements
3.1.2
driver
launcher
external dynamic component or simulator that activates the performing of functions of an aggregate
(3.1.1) of system elements
3.1.3
interface
point at which two or more logical, physical, or both, system elements or software system elements
meet and act on or communicate with each other
3.1.4
integration
process of planning for and aggregating a progressively more complete set of physical, logical, or both,
system elements and activating their interfaces (3.1.3) to synthesize a system or part of a system whose
properties can be verified and possibly validated
Note 1 to entry: An outcome of integration is a system whose properties can be verified and possibly validated.
3.1.5
logical interface
input-output flow between two or more system elements or software system elements and the function
that determines it
Note 1 to entry: A logical interface can be functional (as in process steps), informational (as in a communications
link), or other.
3.1.6
physical interface
physical link between two or more system elements
Note 1 to entry: A physical interface can be solid, liquid, gas, vacuum, thermal, electromagnetic field, or other.
3.1.7
stub
computer programs and data files built to support software development and testing, but not intended
to be included in the final product
3.1.8
synthesis
result of combining the constituent elements of separate physical or logical, or both, entities into a
single or unified entity
2
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
3.2 Abbreviated terms
API application program interface
ISC integration services components
MBSE model-based systems engineering
NDI non-developmental item
QA quality assurance
SDP software development plan
SEMP systems engineering management plan
SoI system-of-interest
4 Conformance
4.1 Conformance to processes
Conformance requirements for the integration process are specified in ISO/IEC/IEEE 12207:2017 and
ISO/IEC/IEEE 15288 and further elaborated in 6.3. One supplemental integration process outcome
is added in 6.3.3. If using ISO/IEC/IEEE 15288:2023 outcomes, it would become outcome h). If using
ISO/IEC/IEEE 12207:2017 outcomes, it would become outcome i).
4.2 Conformance to information item content
Clause 7 provides requirements for a number of information items to be produced during the life cycle
of a system.
A claim of conformance to the information item provisions of this document means that
— the required information items stated in this document are produced, and
— the information items produced demonstrate conformity to the content requirements defined in
this document.
Clause 7 contains the requirements for the content of the information items in this document.
In this document, each information item is described as if it were published as a separate document.
However, information items are considered to be conforming if the information items are unpublished
but available in a repository for reference, divided into separate documents or volumes, or combined
with other information items into one document. It is not required to treat every topic in this document
in the same order, using the same wording as its title, or with the same level of detail. That depends on
the nature of the system, implementation methods, life cycle model, and scope of the project.
4.3 Full conformance
A claim of full conformance to this document is equivalent to claiming conformance to the integration
process requirements identified in 4.1 and the requirements for the information items cited in 4.2.
3
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
4.4 Tailored conformance
4.4.1 Processes
This document makes the following provision for a claim of tailored conformance to the integration
process: ISO/IEC/IEEE 12207:2017, Annex A and ISO/IEC/IEEE 15288:2023, Annex A provide
requirements regarding the tailoring of system and software life cycle processes. Those provisions
should be used to tailor the integration process requirements identified in 4.1 as the basis for a claim of
tailored conformance to the integration process as elaborated in this document.
4.4.2 Information items
When this document is used as a basis for establishing a set of information items that do not qualify for
full conformance, the requirements in Clause 7 are selected or modified in accordance with this clause.
The tailored text, for which tailored conformance is claimed, shall be declared. Tailored conformance is
achieved by demonstrating that requirements for the information items, as tailored, are satisfied.
5 Integration concepts
5.1 General
This clause presents the concepts that apply to system integration, including software systems. These
concepts embody the definitions in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and set the basis for
explaining the application of those concepts. The central concepts that this clause presents are those of
interface, aggregation, synthesis, and integration.
There are conceptual relationships between the integration process and system and software life cycle
processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, which this clause presents. This clause also
presents the concepts associated with system integration as a process over the life cycle of a system,
including software systems.
Finally, this clause presents concepts on iteration and recursion in integration, and regression testing.
5.2 Interface concept
An interface has a set of logical or physical characteristics required to exist at a common boundary or
connection between system elements, systems, or the environment external to the SoI.
NOTE 1 Throughout this document, statements referring to "system elements" inferentially can include
elements of other systems, or the external environment.
A physical interface is a physical link that binds two or more system elements within the SoI, or one
system element of the SoI with one or more elements external to the SoI. A physical interface can be
considered a system element.
A logical interface consists of an output flow, or an input flow, or a bi-directional, i.e. transactional, flow
between two or more elements of the system so that the elements can exchange some mix of energy or
information items.
NOTE 2 Table 1 provides examples of system element integration involving physical interfaces (e.g. material
and thermal example of Table 1) and logical interfaces (e.g. the software-to-software example of Table 1).
The progressive definition of interfaces is an intrinsic part of applying the technical processes of
ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and is critical to the success of integration. Inadequately
defined interfaces are common failure points in complex systems. Such inadequately defined interfaces
commonly include the points where independent systems or system elements not necessarily made
of the same technology meet and communicate with each other. Consideration for indirectly coupled
elements (e.g. via control mechanisms or shared memory in software systems) often involves complex
4
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC/IEEE 24748-6:2023(E)
analysis. Technical processes' activities and decisions should fully define interfaces so that integration,
and subsequent verification of system elements' properties, can be planned and performed successfully.
ISO/IEC/IEEE 12207:2017, E.5 and ISO/IEC/IEEE 24748-1:2018, D.5 provide a process view for the
management of interfaces and identify the purpose and outcomes with selected life cycle process
activities and tasks to facilitate the identification, definition, design, and management of interfaces of
the SoI.
5.3 Aggregation and synthesis concepts
The integration of a system is based on the notions of aggregation and synthesis. For example, wings,
body, engines, hardware and software controls, air traffic procedures, and information items, are
aggregated along with other elements not listed here to synthesize an aircraft operating in its intended
environment. A synthesis performs functions not possible from the individual elements that are
aggregated. An aggregate has a functional consistency that allows the performance of subsequent
verification actions and possibly validation actions. Each aggregate is characterized by a configuration
that specifies the impleme
...
ISO/IEC/IEEE TC JTC1/SC 7 N xxxx
Date: 2022-12-14
ISO/IEC/IEEE FDIS 24748-6:2023(E)
Date: 2023-02-16
ISO/IEC TC JTC1/SC 7/WG 7 N2928
Secretariat: BIS
Systems and software engineering — Life cycle management — Part 6: System and
software integration
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 6: Ligne directrices pour
l'intégration du système et du logiciel
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
© ISO/IEC 20222023
© IEEE 20222023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no
part of this publication may be reproduced or utilised 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 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
Commented [eXtyles1]: The URL www.ieee.org has been
Website: www.iso.org Website: www.ieee.orgwww.ieee.org
redirected to https://www.ieee.org/. Please verify the URL.
Published in Switzerland
© ISO/IEC 20222023 – All rights reserved
ii
© IEEE 20222023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
Contents Page
Foreword . v
Introduction . vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 2
3.1 Terms and definitions . 2
3.2 Abbreviations . 3
4 Conformance . 3
4.1 Conformance to processes . 3
4.2 Conformance to information item content . 3
4.3 Full conformance . 4
4.4 Tailored conformance . 4
4.4.1 Processes . 4
4.4.2 Information items . 4
5 Integration concepts . 4
5.1 General . 4
5.2 Interface concept . 5
5.3 Aggregation and synthesis concepts . 5
5.4 Integration concept . 5
5.5 Relationship of integration to life cycle processes . 7
5.6 Progressive interface definition . 8
5.7 Integration over the life cycle . 8
5.8 Iteration and recursion in integration . 8
5.8.1 General . 8
5.8.2 Iterative application of processes . 8
5.8.3 Recursive application of processes. 9
5.9 Regression testing in integration . 9
5.10 Integration enabling systems . 9
6 Integration process planning and application purposes . 10
6.1 General . 10
6.2 Integration planning and application guidelines . 10
6.2.1 General . 10
6.2.2 Integration strategy . 10
6.2.3 Efficiency considerations in the integration strategy . 11
6.2.4 Integration context . 11
6.2.5 Roles and competencies of integration team . 12
6.2.6 Methods used to perform integration . 13
6.3 Integration process application requirements and guidelines . 21
6.3.1 General . 21
6.3.2 Purpose . 21
6.3.3 Outcomes . 23
6.3.4 Activities and tasks . 25
6.4 Other processes used in relationship to Integration process application . 33
6.4.1 General . 33
6.4.2 Agreement processes . 33
6.4.3 Organizational project-enabling processes . 34
6.4.4 Technical management processes . 34
© ISO/IEC 2022 – All rights reserved
iii
© IEEE 2022 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
6.4.5 Technical processes . 35
6.5 Integration of systems-of-systems . 40
6.6 Integration throughout a system life cycle . 41
7 Information item requirements . 41
7.1 General . 41
7.2 Integration plan. 42
Annex A (Informative) Coupling Matrixes . 44
A.1 Coupling matrix purpose . 44
A.2 Coupling matrix description and example . 44
Bibliography . 46
© ISO/IEC 20222023 – All rights reserved
iv
© IEEE 20222023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(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/IEC documents 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).
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.ch).
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.
ISO/IEC/IEEE 24748-6 was prepared by Joint Technical Committee ISO/TCIEC JTC 1, Information Commented [eXtyles2]: ISO/IEC/IEEE 24748-6: current stage
is 50.00
Technologytechnology, Subcommittee SC 7, SystemsSoftware and softwaresystems 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.
This first edition cancels and replaces ISO/IEC TS 24748-6:2016, which has been technically revised.
The main changes are as follows:
— changed from a Technical Specification to an International Standard;
— updated to reflect the process requirements of ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:
Commented [eXtyles3]: ISO/IEC/IEEE 15288: —: current
—;:—;
stage is 50.20
© ISO/IEC 2022 – All rights reserved
v
© IEEE 2022 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
— added material specific to software integration and systems-of-systems integration, as well as system
aggregation.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website. Commented [eXtyles4]: Invalid reference:
"ISO/IEC/IEEE 24748 series"
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 20222023 – All rights reserved
vi
© IEEE 20222023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
Introduction
Both ISO/IEC/IEEE 15288: — and ISO/IEC/IEEE 12207:2017 include an integration process that focuses Commented [eXtyles5]: ISO/IEC/IEEE 15288: —: current
stage is 50.20
on aggregating the elements comprising a system. The integration process depends on a clear
understanding of interfaces of all kinds and the use, possibly repeated, of the verification process and the
validation process.
Systems that this document are concerned with are as described in ISO/IEC/IEEE 12207:2017 and
ISO/IEC/IEEE 15288: —,, i.e.,. systems that are human-made, comprised of any mixture of products and
services and can be configured with one or more of the following: hardware, software, data, humans,
processes (e.g.,. a review process or processes for providing service to users), procedures (e.g.,. operator
instructions), facilities, materials and naturally occurring entities (e.g.,. water, organisms, minerals).
The purpose of this document is to elaborate and facilitate the usage of the integration process given in
ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288: — by providing requirements and guidance for the
planning and performing of that process, including requirements for the information items to be provided
for systems and software integration, considering:
— the underlying concepts of aggregation, integration, interface, synthesis, verification, and validation,;
— the possible composition of that human-made system, ;
— the life cycle stages of a system at which one or more parts of the integration process can occur, and;
— the context of the domain in which the system functions.
For life cycle process information items (documentation) described in ISO/IEC/IEEE 15288: — and
ISO/IEC/IEEE 12207:2017, ISO/IEC/IEEE 15289 summarises requirements for their content and
provides guidance on their development. Although this document identifies additional required
information items with related content for the integration process, it does not require a specific name,
format, recording media or explicit details for population of the information item's required content.
NOTE This document is intended to be consistent with the other parts of the ISO/IEC/IEEE 24748 series. Commented [eXtyles6]: Invalid reference:
"ISO/IEC/IEEE 24748 series"
© ISO/IEC 2022 – All rights reserved
vii
© IEEE 2022 – All rights reserved
---------------------- Page: 7 ----------------------
FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC/IEEE FDIS 24748-
6:20232022(E)
Systems and software engineering — Life cycle management —
Part 6: System and software integration
1 Scope
This document:
— provides supplemental requirements and guidance for the planning and performing of the
1
integration processes given in ISO/IEC/IEEE 15288: — and ISO/IEC/IEEE 12207:2017; Commented [eXtyles7]: ISO/IEC/IEEE 15288: —: current
stage is 50.20
— provides guidance on the relationship between the integration process and other life cycle processes.
— specifies requirements for information items to be produced as a result of using the integration
process, including the content of the information items.
This document is applicable to:
— those who use or plan to use ISO/IEC/IEEE 12207:2017 or ISO/IEC/IEEE 15288: —,, or both, on
projects dealing with human-made systems, software-intensive systems, and products and services
related to those systems, regardless of the project scope, methodology, size, or complexity;
— anyone planning or performing integration activities to aid in ensuring that the application of the
integration process and its relationships to other system life cycle processes conform to
ISO/IEC/IEEE 15288: — or ISO/IEC/IEEE 12207:2017.
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
2
Commented [eXtyles8]: ISO/IEC/IEEE 15288:—: current
ISO/IEC/IEEE 15288: —,:— , Systems and software engineering — System life cycle processes
stage is 50.20
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
Commented [eXtyles9]: ISO/IEC/IEEE 15288: —: current
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 15288: —,,
stage is 50.20
ISO/IEC/IEEE 12207:2017 and the following apply.
1
Under preparation
2
Under preparation.
© ISO/IEC 20222023 – All rights reserved
1
© IEEE 20222023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
ISO, IEC and IEEE 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/
— IEEE Standards Dictionary Online: available at: http://dictionary.ieee.org Commented [eXtyles10]: The URL http://dictionary.ieee.org
has been redirected to http://ieeexplore.ieee.org/xpls/dictionary.jsp.
Please verify the URL.
NOTE For additional terms and definitions in the field of systems and software engineering, see
ISO/IEC/IEEE 24765, which is published periodically as a “snapshot” of the Systems and software Engineering
Vocabulary (SEVOCAB) database and is publicly accessible at www.computer.org/sevocab.
Commented [eXtyles11]: The URL
http://www.computer.org/sevocab has been redirected to
http://pascal.computer.org/sev_display/index.action. Please verify
3.1.1
the URL.
aggregate, noun
result of combining one or more physical, logical, or both, system elements
3.1.2
driver
launcher Commented [eXtyles12]: The term "launcher" has not been
used anywhere in this document
external dynamic component or simulator that activates the performing of functions of an aggregate
(3.1.1) of system elements
3.1.3
interface
point at which two or more logical, physical, or both, system elements or software system elements meet
and act on or communicate with each other
3.1.4
integration
process of planning for and aggregating a progressively more complete set of physical, logical, or both,
system elements and activating their interfaces (3.1.3) to synthesize a system or part of a system whose
properties can be verified and possibly validated
Note 1 to entry: An outcome of integration is a system whose properties can be verified and possibly validated.
3.1.5
logical interface
input-output flow between two or more system elements or software system elements and the function
that determines it
Note 1 to entry: A logical interface can be functional (as in process steps), informational (as in a communications
link,) or other.
3.1.6
physical interface
physical link between two or more system elements
Note 1 to entry: A physical interface can be solid, liquid, gas, vacuum, thermal, electromagnetic field, or other.
3.1.7
stub
computer programs and data files built to support software development and testing, but not intended
to be included in the final product
3.1.8
synthesis
© ISO/IEC 20222023 – All rights reserved
2
© IEEE 20222023 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
result of combining the constituent elements of separate physical or logical, or both, entities into a single
or unified entity
3.2 Abbreviated terms
API application program interface
ISC integration services components
API application program interfaceintegration services componentsmodel-
based systems engineering
ISC
MBSE
NDI non-developmental item
QA quality assurance
SDP software development plan
SEMP systems engineering management plan
SoI system-of-interest
4 Conformance
4.1 Conformance to processes
Conformance requirements for the integration process are specified in ISO/IEC/IEEE 12207:2017 and
ISO/IEC/IEEE 15288: — and further elaborated in 6.3. One supplemental integration process outcome is Commented [eXtyles13]: ISO/IEC/IEEE 15288: —: current
stage is 50.20
added in 6.3.3. If using ISO/IEC/IEEE 15288: —:— outcomes, it would become outcome h). If using
Commented [eXtyles14]: ISO/IEC/IEEE 15288: —: current
ISO/IEC/IEEE 12207:2017 outcomes. It would become outcome i).
stage is 50.20
4.2 Conformance to information item content
Clause 7 provides requirements for a number of information items to be produced during the life cycle of
a system.
A claim of conformance to the information item provisions of this document means that
— the required information items stated in this document are produced, and
— the information items produced demonstrate conformity to the content requirements defined in this
document.
Clause 7 contains the requirements for the content of the information items in this document.
In this document, each information item is described as if it were published as a separate document.
However, information items are considered to be conforming if the information items are unpublished
but available in a repository for reference, divided into separate documents or volumes, or combined
with other information items into one document. It is not required to treat every topic in this document
in the same order, using the same wording as its title, or with the same level of detail. That depends on
the nature of the system, implementation methods, life cycle model, and scope of the project.
4.3 Full conformance
A claim of full conformance to this document is equivalent to claiming conformance to the integration
process requirements identified in 4.1 and the requirements for the information items cited in 4.2.
© ISO/IEC 20222023 – All rights reserved
3
© IEEE 20222023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
4.4 Tailored conformance
4.4.1 Processes
This document makes the following provision for a claim of tailored conformance to the integration
process: ISO/IEC/IEEE 12207:2017, Annex A and ISO/IEC/IEEE 15288: —,:—, Annex A provide Commented [eXtyles15]: ISO/IEC/IEEE 15288: —: current
stage is 50.20
requirements regarding the tailoring of system and software life cycle processes. Those provisions should
be used to tailor the integration process requirements identified in 4.1 as the basis for a claim of tailored
conformance to the integration process as elaborated in this document.
4.4.2 Information items
When this document is used as a basis for establishing a set of information items that do not qualify for
full conformance, the requirements in Clause 7 are selected or modified in accordance with this clause.
The tailored text, for which tailored conformance is claimed, shall be declared. Tailored conformance is
achieved by demonstrating that requirements for the information items, as tailored, are satisfied.
5 Integration concepts
5.1 General
This clause presents the concepts that apply to system integration, including software systems. These
concepts embody the definitions in ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288: — and set the
basis for explaining the application of those concepts. The central concepts that this clause presents are
those of interface, aggregation, synthesis, and integration.
There are conceptual relationships between the integration process and system and software life cycle
processes of ISO/IEC/IEEE 15288: — and ISO/IEC/IEEE 12207:2017, which this clause presents. This
clause also presents the concepts associated with system integration as a process over the life cycle of a
system, including software systems.
Finally, this clause presents concepts on iteration and recursion in integration, and regression testing.
5.2 Interface concept
An interface has a set of logical or physical characteristics required to exist at a common boundary or
connection between system elements, systems, or the environment external to the SoI.
NOTE 1 Throughout this document, statements referring to "system elements" inferentially can include elements
of other systems, or the external environment.
A physical interface is a physical link that binds two or more system elements within the SoI, or one
system element of the SoI with one or more elements external to the SoI. A physical interface can be
considered a system element.
A logical interface consists of an output flow, or an input flow, or a bi-directional, i.e. transactional, flow
between two or more elements of the system so that the elements can exchange some mix of energy or
information items.
NOTE 2 Table 1 provides examples of system element integration involving physical interfaces (e.g. material and
thermal example of Table 1) and logical interfaces (e.g. the software-to-software example of Table 1).
The progressive definition of interfaces is an intrinsic part of applying the technical processes of
ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288: — and is critical to the success of integration.
Inadequately defined interfaces are common failure points in complex systems. Such inadequately
defined interfaces commonly include the points where independent systems or system elements not
necessarily made of the same technology meet and communicate with each other. Consideration for
© ISO/IEC 20222023 – All rights reserved
4
© IEEE 20222023 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
indirectly coupled elements (e.g. via control mechanisms or shared memory in software systems) often
involves complex analysis. Technical processes' activities and decisions should fully define interfaces so
that integration, and subsequent verification of system elements' properties, can be planned and
performed successfully.
ISO/IEC/IEEE 12207:2017, E.5 and ISO/IEC/IEEE 24748-1:2018, D.5 provide a process view for the
management of interfaces and identify the purpose and outcomes with selected life cycle process
activities and tasks to facilitate the identification, definition, design, and management of interfaces of the
SoI.
5.3 Aggregation and synthesis concepts
The integration of a system is based on the notions of aggregation and synthesis. For example, wings,
body, engines, hardware and software contr
...
FINAL
INTERNATIONAL ISO/
DRAFT
STANDARD IEC/IEEE
FDIS
24748-6
ISO/IEC JTC 1/SC 7
Systems and software engineering —
Secretariat: BIS
Life cycle management —
Voting begins on:
2023-03-03
Part 6:
Voting terminates on:
System and software integration
2023-04-28
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
Reference number
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO-
ISO/IEC/IEEE FDIS 24748-6:2023(E)
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN-
© ISO/IEC 2023
DARDS TO WHICH REFERENCE MAY BE MADE IN
NATIONAL REGULATIONS. © IEEE 2023
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
FINAL
INTERNATIONAL ISO/
DRAFT
STANDARD IEC/IEEE
FDIS
24748-6
ISO/IEC JTC 1/SC 7
Systems and software engineering —
Secretariat: BIS
Life cycle management —
Voting begins on:
Part 6:
Voting terminates on:
System and software integration
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2023
© IEEE 2023
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
RECIPIENTS OF THIS DRAFT ARE INVITED TO
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
SUBMIT, WITH THEIR COMMENTS, NOTIFICATION
OF ANY RELEVANT PATENT RIGHTS OF WHICH
CH-1214 Vernier, Geneva NY 10016-5997, USA
THEY ARE AWARE AND TO PROVIDE SUPPOR TING
Phone: +41 22 749 01 11
DOCUMENTATION.
Fax: +41 22 749 09 47
IN ADDITION TO THEIR EVALUATION AS
Reference number
Email: copyright@iso.org Email: stds.ipr@ieee.org
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO
ISO/IEC/IEEE FDIS 247486:2023(E)
Website: www.iso.org Website: www.ieee.org
LOGICAL, COMMERCIAL AND USER PURPOSES,
DRAFT INTERNATIONAL STANDARDS MAY ON
Published in Switzerland
OCCASION HAVE TO BE CONSIDERED IN THE
LIGHT OF THEIR POTENTIAL TO BECOME STAN
© ISO/IEC 2023
DARDS TO WHICH REFERENCE MAY BE MADE IN
ii
© ISO/IEC 2023 – All rights reserved
NATIONAL REGULATIONS. © IEEE 2023
© IEEE 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Conformance . 3
4.1 Conformance to processes . 3
4.2 Conformance to information item content . 3
4.3 Full conformance . 3
4.4 Tailored conformance . 3
4.4.1 Processes . 3
4.4.2 Information items . . 3
5 Integration concepts . 4
5.1 General . 4
5.2 Interface concept . 4
5.3 Aggregation and synthesis concepts . 4
5.4 Integration concept . 5
5.5 Relationship of integration to life cycle processes . 6
5.6 Progressive interface definition . 7
5.7 Integration over the life cycle . 7
5.8 Iteration and recursion in integration . 7
5.8.1 General . 7
5.8.2 Iterative application of processes . 8
5.8.3 Recursive application of processes . 8
5.9 Regression testing in integration . 8
5.10 Integration enabling systems . 8
6 Integration process planning and application purposes . 9
6.1 General . 9
6.2 Integration planning and application guidelines . 9
6.2.1 General . 9
6.2.2 Integration strategy . 9
6.2.3 Efficiency considerations in the integration strategy . 10
6.2.4 Integration context. 10
6.2.5 Roles and competencies of integration team . 11
6.2.6 Methods used to perform integration .12
6.3 Integration process application requirements and guidelines . 20
6.3.1 General .20
6.3.2 Purpose . 20
6.3.3 Outcomes . 22
6.3.4 Activities and tasks .23
6.4 Other processes used in relationship to integration process application . 31
6.4.1 General . 31
6.4.2 Agreement processes . 31
6.4.3 Organizational projectenabling processes . 31
6.4.4 Technical management processes. 31
6.4.5 Technical processes . 32
6.5 Integration of systems-of-systems . 37
6.6 Integration throughout a system life cycle .38
7 Information item requirements .38
7.1 General .38
iii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
7.2 Integration plan .38
Annex A (Informative) Coupling matrixes .40
Bibliography .42
IEEE notices and abstract .43
iv
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(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 nongovernmental, 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/IEC documents 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).
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEESA) 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.ch).
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/understandingstandards.
ISO/IEC/IEEE 24748-6 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.
This first edition cancels and replaces ISO/IEC TS 24748-6:2016, which has been technically revised.
The main changes are as follows:
— changed from a Technical Specification to an International Standard;
— updated to reflect the process requirements of ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:—
;
— added material specific to software integration and systems-of-systems integration, as well as
system aggregation.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website.
v
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
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/nationalcommittees.
vi
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
Introduction
Both ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 include an integration process that focuses
on aggregating the elements comprising a system. The integration process depends on a clear
understanding of interfaces of all kinds and the use, possibly repeated, of the verification process and
the validation process.
Systems that this document are concerned with are as described in ISO/IEC/IEEE 12207 and
ISO/IEC/IEEE 15288, i.e. systems that are human-made, comprised of any mixture of products and
services and can be configured with one or more of the following: hardware, software, data, humans,
processes (e.g. a review process or processes for providing service to users), procedures (e.g. operator
instructions), facilities, materials and naturally occurring entities (e.g. water, organisms, minerals).
The purpose of this document is to elaborate and facilitate the usage of the integration process given in
ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 by providing requirements and guidance for the planning
and performing of that process, including requirements for the information items to be provided for
systems and software integration, considering:
— the underlying concepts of aggregation, integration, interface, synthesis, verification, and validation;
— the possible composition of that human-made system;
— the life cycle stages of a system at which one or more parts of the integration process can occur;
— the context of the domain in which the system functions.
For life cycle process information items (documentation) described in ISO/IEC/IEEE 15288 and
ISO/IEC/IEEE 12207, ISO/IEC/IEEE 15289 summarises requirements for their content and provides
guidance on their development. Although this document identifies additional required information
items with related content for the integration process, it does not require a specific name, format,
recording media or explicit details for population of the information item's required content.
NOTE This document is intended to be consistent with the other parts of the ISO/IEC/IEEE 24748 series.
vii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 7 ----------------------
FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC/IEEE FDIS 24748-6:2023(E)
Systems and software engineering — Life cycle
management —
Part 6:
System and software integration
1 Scope
This document:
— provides supplemental requirements and guidance for the planning and performing of the
integration processes given in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207;
— provides guidance on the relationship between the integration process and other life cycle processes.
— specifies requirements for information items to be produced as a result of using the integration
process, including the content of the information items.
This document is applicable to:
— those who use or plan to use ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or both, on projects
dealing with human-made systems, software-intensive systems, and products and services related
to those systems, regardless of the project scope, methodology, size, or complexity;
— anyone planning or performing integration activities to aid in ensuring that the application of
the integration process and its relationships to other system life cycle processes conform to
ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207.
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
1)
ISO/IEC/IEEE 15288:— , Systems and software engineering — System life cycle processes
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC/IEEE 15288,
ISO/IEC/IEEE 12207 and the following apply.
ISO, IEC and IEEE 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/
— IEEE Standards Dictionary Online: available at: http:// dictionary .ieee .org
1) Under preparation.
1
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
NOTE For additional terms and definitions in the field of systems and software engineering, see
ISO/IEC/IEEE 24765, which is published periodically as a “snapshot” of the Systems and software Engineering
Vocabulary (SEVOCAB) database and is publicly accessible at www .computer .org/ sevocab.
3.1.1
aggregate, noun
result of combining one or more physical, logical, or both, system elements
3.1.2
driver
launcher
external dynamic component or simulator that activates the performing of functions of an aggregate
(3.1.1) of system elements
3.1.3
interface
point at which two or more logical, physical, or both, system elements or software system elements
meet and act on or communicate with each other
3.1.4
integration
process of planning for and aggregating a progressively more complete set of physical, logical, or both,
system elements and activating their interfaces (3.1.3) to synthesize a system or part of a system whose
properties can be verified and possibly validated
Note 1 to entry: An outcome of integration is a system whose properties can be verified and possibly validated.
3.1.5
logical interface
input-output flow between two or more system elements or software system elements and the function
that determines it
Note 1 to entry: A logical interface can be functional (as in process steps), informational (as in a communications
link,) or other.
3.1.6
physical interface
physical link between two or more system elements
Note 1 to entry: A physical interface can be solid, liquid, gas, vacuum, thermal, electromagnetic field, or other.
3.1.7
stub
computer programs and data files built to support software development and testing, but not intended
to be included in the final product
3.1.8
synthesis
result of combining the constituent elements of separate physical or logical, or both, entities into a
single or unified entity
3.2 Abbreviated terms
API application program interface
ISC integration services components
MBSE model-based systems engineering
NDI nondevelopmental item
2
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
QA quality assurance
SDP software development plan
SEMP systems engineering management plan
SoI system-of-interest
4 Conformance
4.1 Conformance to processes
Conformance requirements for the integration process are specified in ISO/IEC/IEEE 12207:2017 and
ISO/IEC/IEEE 15288 and further elaborated in 6.3. One supplemental integration process outcome
is added in 6.3.3. If using ISO/IEC/IEEE 15288:— outcomes, it would become outcome h). If using
ISO/IEC/IEEE 12207:2017 outcomes. It would become outcome i).
4.2 Conformance to information item content
Clause 7 provides requirements for a number of information items to be produced during the life cycle
of a system.
A claim of conformance to the information item provisions of this document means that
— the required information items stated in this document are produced, and
— the information items produced demonstrate conformity to the content requirements defined in
this document.
Clause 7 contains the requirements for the content of the information items in this document.
In this document, each information item is described as if it were published as a separate document.
However, information items are considered to be conforming if the information items are unpublished
but available in a repository for reference, divided into separate documents or volumes, or combined
with other information items into one document. It is not required to treat every topic in this document
in the same order, using the same wording as its title, or with the same level of detail. That depends on
the nature of the system, implementation methods, life cycle model, and scope of the project.
4.3 Full conformance
A claim of full conformance to this document is equivalent to claiming conformance to the integration
process requirements identified in 4.1 and the requirements for the information items cited in 4.2.
4.4 Tailored conformance
4.4.1 Processes
This document makes the following provision for a claim of tailored conformance to the integration
process: ISO/IEC/IEEE 12207:2017, Annex A and ISO/IEC/IEEE 15288:—, Annex A provide requirements
regarding the tailoring of system and software life cycle processes. Those provisions should be used
to tailor the integration process requirements identified in 4.1 as the basis for a claim of tailored
conformance to the integration process as elaborated in this document.
4.4.2 Information items
When this document is used as a basis for establishing a set of information items that do not qualify for
full conformance, the requirements in Clause 7 are selected or modified in accordance with this clause.
3
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE FDIS 24748-6:2023(E)
The tailored text, for which tailored conformance is claimed, shall be declared. Tailored conformance is
achieved by demonstrating that requirements for the information items, as tailored, are satisfied.
5 Integration concepts
5.1 General
This clause presents the concepts that apply to system integration, including software systems. These
concepts embody the definitions in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and set the basis for
explaining the application of those concepts. The central concepts that this clause presents are those of
interface, aggregation, synthesis, and integration.
There are conceptual relationships between the integration process and system and software life cycle
processes of ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207, which this clause presents. This clause also
presents the concepts associated with system integration as a process over the life cycle of a system,
including software systems.
Finally, this clause presents concepts on iteration and recursion in integration, and regression testing.
5.2 Interface concept
An interface has a set of logical or physical characteristics required to exist at a common boundary or
connection between system elements, systems, or the environment external to the SoI.
NOTE 1 Throughout this document, statements referring to "system elements" inferentially can include
elements of other systems, or the external environment.
A physical interface is a physical link that binds two or more system elements within the SoI, or one
system element of the SoI with one or more elements external to the SoI. A physical interface can be
considered a system element.
A logical interface consists of an output flow, or an input flow, or a bi-directional, i.e. transactional, flow
between two or more elements of the system so that the elements can exchange some mix of energy or
information items.
NOTE 2 Table 1 provides examples of system element integration involving physical interfaces (e.g. material
and thermal example of Table 1) and logical interfaces (e.g. the software-to-software example of Table 1).
The progressive definition of interfaces is an intrinsic part of applying the technical processes of
ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 and is critical to the success of integration. Inadequately
defined interfaces are common failure points in complex systems. Such inadequately defined interfaces
commonly include the points where independent systems or system elements not necessarily made
of the same technology meet and communicate with each other. Consideration for indirectly coupled
elements (e.g. via control mechanisms or shared memory in software systems) often involves complex
analys
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.