ISO/IEC/IEEE 24748-9:2023
(Main)Systems and software engineering — Life cycle management — Part 9: Application of system and software life cycle processes in epidemic prevention and control systems
Systems and software engineering — Life cycle management — Part 9: Application of system and software life cycle processes in epidemic prevention and control systems
This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie — Partie 9: Application des processus du cycle de vie des systèmes et du logiciel dans les systèmes de prévention et de lutte contre les épidémies
General Information
Buy Standard
Standards Content (Sample)
INTERNATIONAL ISO/
STANDARD IEC/IEEE
24748-9
First edition
2023-05
Systems and software engineering —
Life cycle management —
Part 9:
Application of system and software
life cycle processes in epidemic
prevention and control systems
Ingénierie des systèmes et du logiciel — Gestion du cycle de vie —
Partie 9: Application des processus du cycle de vie des systèmes et
du logiciel dans les systèmes de prévention et de lutte contre les
épidémies
Reference number
ISO/IEC/IEEE 24748-9:2023(E)
© ISO/IEC 2023
© IEEE 2023
---------------------- Page: 1 ----------------------
ISO/IEC/IEEE 24748-9: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-9:2023(E)
Contents Page
Foreword .v
Introduction . vi
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 Intended usage . 3
4.2 Full conformance . 3
4.2.1 Full conformance to outcomes . 3
4.2.2 Full conformance to tasks . 3
4.3 Tailored conformance . 3
5 Key concepts and application . 3
5.1 General . 3
5.2 System concepts . 4
5.2.1 System . 4
5.2.2 Characteristics of systems for epidemic emergency . 4
5.2.3 System structure . 6
5.2.4 Interfacing, enabling, and interoperating systems . 7
5.2.5 Concepts related to the system solution context. 7
5.2.6 Product line engineering (PLE). 7
5.3 Organization and project concepts . 7
5.3.1 Organizations . 7
5.3.2 Organization and project-level adoption . 7
5.3.3 Organization and collaborative activities . . 7
5.4 Life cycle concepts . 7
5.4.1 System life cycle model . 7
5.4.2 System life cycle stages . 7
5.5 Process concepts . 9
5.5.1 Criteria for processes . 9
5.5.2 Description of processes . 9
5.5.3 General characteristics of processes . 9
5.5.4 Characteristics of life cycle processes for epidemic emergency systems. 9
5.6 Processes in this document . 10
5.6.1 General . 10
5.6.2 Agreement processes . 10
5.6.3 Organizational project-enabling processes . 10
5.6.4 Technical management processes. 10
5.6.5 Technical processes . 10
5.7 System-of-interest concepts . 10
5.7.1 General . 10
5.7.2 Relationships between software and system . 10
5.8 System of systems concepts . 11
5.8.1 General . 11
5.8.2 Differences between systems and SoS . 11
5.8.3 Managerial and operational independence . 11
5.8.4 Taxonomy of SoS . 11
5.8.5 SoS considerations in life cycle stages of a system . 11
5.8.6 Epidemic prevention and control system as an SoS . 11
5.9 Process application .12
5.9.1 Overview . 12
iii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE 24748-9:2023(E)
5.9.2 Process iteration, recursion, and concurrency .13
5.9.3 Process views . 13
5.10 Concept and system definition . 13
5.11 Assurance and quality characteristics. 13
5.12 Process reference model .13
6 System life cycle processes .14
6.1 Agreement processes . 14
6.1.1 Acquisition process . 14
6.1.2 Supply process . 14
6.2 Organizational project-enabling processes . 15
6.2.1 Life cycle model management process . 15
6.2.2 Infrastructure management process . 15
6.2.3 Portfolio management process . 16
6.2.4 Human resource management process . 17
6.2.5 Quality management process . 17
6.2.6 Knowledge management process . 18
6.3 Technical management processes . 18
6.3.1 Project planning process . . 18
6.3.2 Project assessment and control process . 19
6.3.3 Decision management process. 19
6.3.4 Risk management process . 20
6.3.5 Configuration management process . 21
6.3.6 Information management process . 21
6.3.7 Measurement process .22
6.3.8 Quality assurance process . 22
6.4 Technical processes . .23
6.4.1 Business or mission analysis process . 23
6.4.2 Stakeholder needs and requirements definition process . 24
6.4.3 System requirements definition process. 25
6.4.4 Architecture definition process. 26
6.4.5 Design definition process . 27
6.4.6 System analysis process .28
6.4.7 Implementation process .28
6.4.8 Integration process .29
6.4.9 Verification process .30
6.4.10 Transition process . 31
6.4.11 Validation process . 32
6.4.12 Operation process . 32
6.4.13 Maintenance process . 33
6.4.14 Disposal process .34
Annex A (informative) Issues and concerns of stakeholders in the application of lifecycle
processes to epidemic prevention and control systems .35
Bibliography .41
IEEE notices and abstract .42
iv
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE 24748-9: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-9 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and
Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/national-committees.
v
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE 24748-9:2023(E)
Introduction
Many areas have adopted information-based prevention and control measures during an epidemic
and have developed numerous epidemic prevention and control systems and software. Most of
the processes in the entire life cycle of the epidemic prevention and control systems are likely to be
completed in the event of an epidemic. Compared with the normal state, there can be special situations
such as poor communication, caused by the need for personnel to maintain a safe distance, and limited
transportation and logistics services. The result can be insufficient infrastructure protection, short
delivery cycles, frequent iterative upgrades, and special requirements such as accuracy, disaster
tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture.
In the development process of epidemic prevention and control systems, the application of the life cycle
processes specified in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 can effectively help guide the
process management and application of epidemic prevention and control systems.
However, for effective and efficient application of system and software life cycle processes on epidemic
prevention and control systems, additional application requirements are needed. Requirements specific
to the use of the epidemic prevention and control systems that facilitate effective implementation
depend on the nature and severity of the epidemic and are not detailed in this document.
This document is consistent with life cycle processes of ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207
for application on epidemic prevention and control systems, to help ensure the correct application of
stakeholders’ requirements for epidemic prevention and control systems. This document includes the
required outputs and associated attributes.
vi
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO/IEC/IEEE 24748-9:2023(E)
Systems and software engineering — Life cycle
management —
Part 9:
Application of system and software life cycle processes in
epidemic prevention and control systems
1 Scope
This document provides requirements and guidance on the application of system and software
engineering processes to systems for epidemic prevention and control.
This document provides guidance that can be employed for adopting and applying system and software
life cycle processes within an organization or a project in an epidemic emergency. It includes system of
systems considerations in the context of epidemic emergency.
This document applies to acquisition, supply, development, operation, maintenance, and disposal
(whether performed internally or externally to an organization) of system or system of systems in an
epidemic emergency.
Many of the requirements and recommendations in this document are also applicable to other systems
developed rapidly to respond to emergency conditions affecting the public.
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
ISO/IEC/IEEE 15289, Systems and software engineering — Content of life-cycle information items
(documentation)
3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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: https:// dictionary .ieee .org
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 SEVOCAB (Systems and software
Engineering Vocabulary) database, and which is publicly accessible at www .computer .org/ sevocab.
1
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE 24748-9:2023(E)
3.1.1
constituent system
CS
independent system (3.1.3) that forms part of a system of systems (SoS) (3.1.5)
Note 1 to entry: Constituent systems can be part of one or more SoS. Each constituent system is a useful system
by itself, having its own development, management, utilization, goals, and resources, but interacts within the SoS
to provide the unique capability of the SoS.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.1, modified — The abbreviated term "CS" has been added.]
3.1.2
emergency
serious, unexpected, and often dangerous situation requiring immediate action
3.1.3
system
arrangement of parts or elements that together exhibit a stated behaviour or meaning that the
individual constituents do not
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.47]
3.1.4
system-of-interest
SoI
system (3.1.3) whose life cycle is under consideration
[SOURCE: ISO/IEC/IEEE 15288:2023, 3.49]
3.1.5
system of systems
SoS
set of systems (3.1.3) and system elements that interact to provide a unique capability that none of the
constituent systems (3.1.1) can accomplish on its own
Note 1 to entry: System elements can be necessary to facilitate interaction of the constituent systems in the
system of systems.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.4]
3.2 Abbreviated terms
API application program interface
CWBS contract work breakdown structure
DT&E developmental test and evaluation
ESOH environment, safety, and occupational health
EVM earned value management
FMECA failure mode, effects, and criticality analysis
IMP integrated main plan
IMS integrated main schedule
IVS intelligent vision systems
OpsCon operational concept
2
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE 24748-9:2023(E)
PSA product support analysis
QA quality assurance
QPS queries per second
RT response time
SEMP systems engineering management plan
SEP systems engineering plan
SIP system integration plan
TPS transactions per second
4 Conformance
4.1 Intended usage
ISO/IEC/IEEE 15288:2023, 4.1 or ISO/IEC/IEEE 12207:2017, 4.1 shall apply.
4.2 Full conformance
4.2.1 Full conformance to outcomes
ISO/IEC/IEEE 15288:2023, 4.2.1 or ISO/IEC/IEEE 12207:2017, 4.2.1 shall apply with additional
outcomes specified in Clause 6.
4.2.2 Full conformance to tasks
ISO/IEC/IEEE 15288:2023, 4.2.2 or ISO/IEC/IEEE 12207:2017, 4.2.2 shall apply with additional tasks
specified in Clause 6.
4.3 Tailored conformance
ISO/IEC/IEEE 15288:2023, 4.3 or ISO/IEC/IEEE 12207:2017, 4.3 shall apply.
In the case of an epidemic, due to the rapid and serious development of the epidemic, the epidemic
prevention and control system project should adopt a tailoring process.
5 Key concepts and application
5.1 General
ISO/IEC/IEEE 15288:2023, 5.1 or ISO/IEC/IEEE 12207:2017, 5.1 shall apply with the following addition:
For epidemic prevention and control systems, more attention should be paid to the system and process
characteristics in the context of an epidemic.
If the epide
...
ISO/IEC/IEEE TC JTC1/SC 7 N9043
Date: 2022-12-14
ISO/IEC/IEEE FDIS 24748-9:2022(E)
ISO/IEC JTC 1/SC 7/WG 7 N2925
Secretariat: BIS
Date: 2023-02-03
Systems and software engineering – — Life cycle management --
—
Part 9:
Application of system and software life cycle processes in
epidemic prevention and control systems
Ingénierie des systèmes et du logiciel — Partie 9: Application des systèmes et du logiciel processus du
cycle de vie dans les systèmes de prévention et de contrôle des épidémies
---------------------- Page: 1 ----------------------
FDIS stage
---------------------- Page: 2 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(E)
© ISO/IEC/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 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
CH-1214 Vernier, Geneva New York, NY 10016-5997, USA
Phone: + 41 22 749 01 11
Fax: +41 22 749 09 47
Email: E-mail: copyright@iso.org
Website: www.iso.org
Published in Switzerland
© ISO/IEC/IEEE 2023 – All rights reserved iii
© ISO /IEC 2022 – All rights reserved iii
© IEEE 2022 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(E)
Contents
Foreword .v ii
Introduction . viii
Part 9: Application of system and software life cycle processes in epidemic prevention and control
systems . 1
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 Intended usage . 3
4.2 Full conformance . 3
4.2.1 Full conformance to outcomes . 3
4.2.2 Full conformance to tasks . 3
4.3 Tailored conformance . 3
5 Key concepts and application . 3
5.1 General . 3
5.2 System concepts . 3
5.2.1 System . 3
5.2.2 Characteristics of systems for epidemic emergency . 4
5.2.3 System structure . 6
5.2.4 Interfacing, enabling, and interoperating systems . 7
5.2.5 Concepts related to the system solution context . 7
5.2.6 Product line engineering (PLE) . 7
5.3 Organization and project concepts . 7
5.3.1 Organizations . 7
5.3.2 Organization and project-level adoption. 7
5.3.3 Organization and collaborative activities . 7
5.4 Life cycle concepts . 7
5.4.1 System life cycle model . 7
5.4.2 System life cycle stages . 7
5.5 Process concepts . 9
5.5.1 Criteria for processes . 9
5.5.2 Description of processes . 10
5.5.3 General characteristics of processes . 10
5.5.4 Characteristics of life cycle processes for epidemic emergency systems . 10
5.6 Processes in this document . 10
5.6.1 General . 10
5.6.2 Agreement processes . 10
5.6.3 Organizational project-enabling processes . 11
iviv © ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
© ISO/IEC/IEEE 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(E)
5.6.4 Technical management processes. 11
5.6.5 Technical processes . 11
5.7 System-of-interest concepts . 11
5.7.1 General . 11
5.7.2 Relationships between software and system . 11
5.8 System of systems concepts . 12
5.8.1 General . 12
5.8.2 Differences between systems and SoS . 12
5.8.3 Managerial and operational independence . 12
5.8.4 Taxonomy of SoS . 12
5.8.5 SoS considerations in life cycle stages of a system . 12
5.8.6 Epidemic prevention and control system as an SoS . 12
5.9 Process application . 13
5.9.1 Overview . 13
5.9.2 Process iteration, recursion, and concurrency . 14
5.9.3 Process views . 14
5.10 Concept and system definition . 14
5.11 Assurance and quality characteristics . 14
5.12 Process reference model . 14
6 System life cycle processes . 14
6.1 Agreement processes . 14
6.1.1 Acquisition process . 14
6.1.2 Supply process . 15
6.2 Organizational project-enabling processes . 15
6.2.1 Life cycle model management process . 15
6.2.2 Infrastructure management process . 16
6.2.3 Portfolio management process . 17
6.2.4 Human resource management process. 17
6.2.5 Quality management process . 18
6.2.6 Knowledge management process . 18
6.3 Technical management processes . 19
6.3.1 Project planning process . 19
6.3.2 Project assessment and control process . 19
6.3.3 Decision management process . 20
6.3.4 Risk management process . 20
6.3.5 Configuration management process . 21
6.3.6 Information management process . 22
6.3.7 Measurement process . 22
6.3.8 Quality assurance process . 23
6.4 Technical processes . 23
6.4.1 Business or mission analysis process . 23
© ISO/IEC/IEEE 2023 – All rights reserved v
© ISO /IEC 2022 – All rights reserved v
© IEEE 2022 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(E)
6.4.2 Stakeholder needs and requirements definition process. 24
6.4.3 System requirements definition process . 25
6.4.4 Architecture definition process . 26
6.4.5 Design definition process . 27
6.4.6 System analysis process . 28
6.4.7 Implementation process . 29
6.4.8 Integration process . 29
6.4.9 Verification process . 30
6.4.10 Transition process . 31
6.4.11 Validation process . 32
6.4.12 Operation process . 32
6.4.13 Maintenance process . 33
6.4.14 Disposal process . 34
Annex A (informative) Issues and concerns of stakeholders in the application of lifecycle processes to
epidemic prevention and control systems . 35
Bibliography . 41
IEEE notices and abstract . 42
vivi © ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
© ISO/IEC/IEEE 2023 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(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.
Field Code Changed
ISO/IEC/IEEE 24748-9 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and
Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html and www.iec.ch/national-
committees.
© ISO/IEC/IEEE 2023 – All rights reserved vii
© ISO /IEC 2022 – All rights reserved vii
© IEEE 2022 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE FDIS 24748-9:20222023(E)
Introduction
Many areas have adopted information-based prevention and control measures during an epidemic and
have developed numerous epidemic prevention and control systems and software. Most of the processes
in the entire life cycle of the epidemic prevention and control systems are likely to be completed in the
event of an epidemic. Compared with the normal state, there can be special situations such as poor
communication, caused by the need for personnel to maintain a safe distance, and limited transportation
and logistics services. The result can be insufficient infrastructure protection, short delivery cycles,
frequent iterative upgrades, and special requirements such as accuracy, disaster tolerance, degradation
capability, safety, user capacity and stress testing, and rapid demand capture. In the development process
of epidemic prevention and control systems, the application of the life cycle processes specified in
ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 can effectively help guide the process management and
application of epidemic prevention and control systems.
However, for effective and efficient application of system and software life cycle processes on epidemic
prevention and control systems, additional application requirements are needed. Requirements specific
to the use of the epidemic prevention and control systems that facilitate effective implementation depend
on the nature and severity of the epidemic and are not detailed in this document.
This document is consistent with life cycle processes of ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207 for
application on epidemic prevention and control systems, to help ensure the correct application of
stakeholders’ requirements for epidemic prevention and control systems. This document includes the
required outputs and associated attributes.
viiiviii © ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
© ISO/IEC/IEEE 2023 – All rights reserved
---------------------- Page: 8 ----------------------
FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC/IEEE FDIS 24748-9:2022(E)
Systems and software engineering – — Life cycle management --
—
Part 9:
Application of system and software life cycle processes in epidemic
prevention and control systems
1 Scope
This document provides requirements and guidance on the application of system and software
engineering processes to systems for epidemic prevention and control.
This document provides guidance that can be employed for adopting and applying system and software
life cycle processes within an organization or a project in an epidemic emergency. It includes system of
systems considerations in the context of epidemic emergency.
This document applies to acquisition, supply, development, operation, maintenance, and disposal
(whether performed internally or externally to an organization) of system or system of systems in an
epidemic emergency.
Many of the requirements and recommendations in this document are also applicable to other systems
developed rapidly to respond to emergency conditions affecting the public.
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
ISO/IEC/IEEE 15289, Systems and software engineering — Content of life-cycle information items
(documentation)
3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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: https://dictionary.ieee.org
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 SEVOCAB (Systems and software
Engineering Vocabulary) database, and which is publicly accessible at www.computer.org/sevocab.
Field Code Changed
1
Under preparation.
© ISO/IEC 2022– All rights reserved 1
© IEEE 2022 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC/IEEE FDIS 24748-9:2023(E)
3.1.1
constituent system
CS
independent system (3.1.3(3.1.3)) that forms part of a system of systems (SoS) (3.1.5(3.1.5))
Note 1 to entry: Constituent systems can be part of one or more SoS. Each constituent system is a useful system by
itself, having its own development, management, utilization, goals, and resources, but interacts within the SoS to
provide the unique capability of the SoS.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.1, modified — The abbreviated term "CS" has been added.]
3.1.2
emergency
serious, unexpected, and often dangerous situation requiring immediate action
3.1.3
system
arrangement of parts or elements that together exhibit a stated behaviour or meaning that the individual
constituents do not
[SOURCE: ISO/IEC/IEEE 15288:—, 3.47]
3.1.4
system-of-interest
SoI
system (3.1.3(3.1.3)) whose life cycle is under consideration
[SOURCE: ISO/IEC/IEEE 15288:—, 3.49]
3.1.5
system of systems
SoS
set of systems (3.1.3) and system elements that interact to provide a unique capability that none of the
constituent systems (3.1.1(3.1.2)) can accomplish on its own
Note 1 to entry: System elements can be necessary to facilitate interaction of the constituent systems in the system
of systems.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.4]
3.2 Abbreviated terms
API application program interface
CWBS contract work breakdown structure
DT&E developmental test and evaluation
ESOH environment, safety, and occupational health
EVM earned value management
FMECA failure mode, effects, and criticality analysis
IMP integrated main plan
IMS integrated main schedule
IVS intelligent vision systems
OpsCon operational concept
2
2
© ISO/IEC 2022– All rights reserved
© IEEE 2022 – All rights reserved
© ISO/IEC/IEEE 2023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/IEC/IEEE FDIS 24748-9:2023(E)
PSA product support analysis
QA quality assurance
QPS queries per second
RT response time
SEMP systems engineering management plan
SEP systems engineering plan
SIP system integration plan
TPS transactions per second
4 Conformance
4.1 Intended usage
ISO/IEC/IEEE 15288:—, 4.1 or ISO/IEC/IEEE 12207:2017, 4.1 shall apply.
4.2 Full conformance
4.2.1 Full conformance to outcomes
ISO/IEC/IEEE 15288:—, 4.2.1 or ISO/IEC/IEEE 12207:2017, 4.2.1 shall apply with additional outcomes
specified in Clause 6clause 6. .
4.2.2 Full conformance to tasks
ISO/IEC/IEEE 15288:—, 4.2.2 or
...
FINAL
INTERNATIONAL ISO/
DRAFT
STANDARD IEC/IEEE
FDIS
24748-9
ISO/IEC JTC 1/SC 7
Systems and software engineering —
Secretariat: BIS
Life cycle management —
Voting begins on:
2023-02-17
Part 9:
Voting terminates on:
Application of system and software
2023-04-14
life cycle processes in epidemic
prevention and control systems
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-9: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-9:2023(E)
FINAL
INTERNATIONAL ISO/
DRAFT
STANDARD IEC/IEEE
FDIS
24748-9
ISO/IEC JTC 1/SC 7
Systems and software engineering —
Secretariat: BIS
Life cycle management —
Voting begins on:
Part 9:
Voting terminates on:
Application of system and software
life cycle processes in epidemic
prevention and control systems
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 247489: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-9:2023(E)
Contents Page
Foreword .v
Introduction . vi
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 Intended usage . 3
4.2 Full conformance . 3
4.2.1 Full conformance to outcomes . 3
4.2.2 Full conformance to tasks . 3
4.3 Tailored conformance . 3
5 Key concepts and application . 3
5.1 General . 3
5.2 System concepts . 4
5.2.1 System . 4
5.2.2 Characteristics of systems for epidemic emergency . 4
5.2.3 System structure . 6
5.2.4 Interfacing, enabling, and interoperating systems . 7
5.2.5 Concepts related to the system solution context. 7
5.2.6 Product line engineering (PLE). 7
5.3 Organization and project concepts . 7
5.3.1 Organizations . 7
5.3.2 Organization and projectlevel adoption . 7
5.3.3 Organization and collaborative activities . . 7
5.4 Life cycle concepts . 7
5.4.1 System life cycle model . 7
5.4.2 System life cycle stages . 7
5.5 Process concepts . 9
5.5.1 Criteria for processes . 9
5.5.2 Description of processes . 9
5.5.3 General characteristics of processes . 9
5.5.4 Characteristics of life cycle processes for epidemic emergency systems. 9
5.6 Processes in this document . 10
5.6.1 General . 10
5.6.2 Agreement processes . 10
5.6.3 Organizational projectenabling processes . 10
5.6.4 Technical management processes. 10
5.6.5 Technical processes . 10
5.7 System-of-interest concepts . 10
5.7.1 General . 10
5.7.2 Relationships between software and system . 10
5.8 System of systems concepts . 11
5.8.1 General . 11
5.8.2 Differences between systems and SoS . 11
5.8.3 Managerial and operational independence . 11
5.8.4 Taxonomy of SoS . 11
5.8.5 SoS considerations in life cycle stages of a system . 11
5.8.6 Epidemic prevention and control system as an SoS . 11
5.9 Process application .12
5.9.1 Overview . 12
iii
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/IEC/IEEE FDIS 24748-9:2023(E)
5.9.2 Process iteration, recursion, and concurrency .13
5.9.3 Process views . 13
5.10 Concept and system definition . 13
5.11 Assurance and quality characteristics. 13
5.12 Process reference model .13
6 System life cycle processes .14
6.1 Agreement processes . 14
6.1.1 Acquisition process . 14
6.1.2 Supply process . 14
6.2 Organizational projectenabling processes . 15
6.2.1 Life cycle model management process . 15
6.2.2 Infrastructure management process . 15
6.2.3 Portfolio management process . 16
6.2.4 Human resource management process . 17
6.2.5 Quality management process . 17
6.2.6 Knowledge management process . 18
6.3 Technical management processes . 18
6.3.1 Project planning process . . 18
6.3.2 Project assessment and control process . 19
6.3.3 Decision management process. 19
6.3.4 Risk management process . 20
6.3.5 Configuration management process . 21
6.3.6 Information management process . 21
6.3.7 Measurement process .22
6.3.8 Quality assurance process . 22
6.4 Technical processes . .23
6.4.1 Business or mission analysis process . 23
6.4.2 Stakeholder needs and requirements definition process . 24
6.4.3 System requirements definition process. 25
6.4.4 Architecture definition process. 26
6.4.5 Design definition process . 27
6.4.6 System analysis process .28
6.4.7 Implementation process .28
6.4.8 Integration process .29
6.4.9 Verification process .30
6.4.10 Transition process . 31
6.4.11 Validation process . 32
6.4.12 Operation process . 32
6.4.13 Maintenance process . 33
6.4.14 Disposal process .34
Annex A (informative) Issues and concerns of stakeholders in the application of lifecycle
processes to epidemic prevention and control systems .35
Bibliography .41
IEEE notices and abstract .42
iv
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC/IEEE FDIS 24748-9: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-9 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Systems and
Software Engineering Standards Committee of the IEEE Computer Society, under the Partner Standards
Development Organization cooperation agreement between ISO and IEEE.
A list of all parts in the ISO/IEC/IEEE 24748 series can be found on the ISO and IEC website.
Any feedback or questions on this document should be directed to the user’s national standards
body. A complete listing of these bodies can be found at www.iso.org/members.html and
www.iec.ch/nationalcommittees.
v
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC/IEEE FDIS 24748-9:2023(E)
Introduction
Many areas have adopted information-based prevention and control measures during an epidemic
and have developed numerous epidemic prevention and control systems and software. Most of
the processes in the entire life cycle of the epidemic prevention and control systems are likely to be
completed in the event of an epidemic. Compared with the normal state, there can be special situations
such as poor communication, caused by the need for personnel to maintain a safe distance, and limited
transportation and logistics services. The result can be insufficient infrastructure protection, short
delivery cycles, frequent iterative upgrades, and special requirements such as accuracy, disaster
tolerance, degradation capability, safety, user capacity and stress testing, and rapid demand capture.
In the development process of epidemic prevention and control systems, the application of the life cycle
processes specified in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207 can effectively help guide the
process management and application of epidemic prevention and control systems.
However, for effective and efficient application of system and software life cycle processes on epidemic
prevention and control systems, additional application requirements are needed. Requirements specific
to the use of the epidemic prevention and control systems that facilitate effective implementation
depend on the nature and severity of the epidemic and are not detailed in this document.
This document is consistent with life cycle processes of ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207
for application on epidemic prevention and control systems, to help ensure the correct application of
stakeholders’ requirements for epidemic prevention and control systems. This document includes the
required outputs and associated attributes.
vi
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 6 ----------------------
FINAL DRAFT INTERNATIONAL STANDARD ISO/IEC/IEEE FDIS 24748-9:2023(E)
Systems and software engineering — Life cycle
management —
Part 9:
Application of system and software life cycle processes in
epidemic prevention and control systems
1 Scope
This document provides requirements and guidance on the application of system and software
engineering processes to systems for epidemic prevention and control.
This document provides guidance that can be employed for adopting and applying system and software
life cycle processes within an organization or a project in an epidemic emergency. It includes system of
systems considerations in the context of epidemic emergency.
This document applies to acquisition, supply, development, operation, maintenance, and disposal
(whether performed internally or externally to an organization) of system or system of systems in an
epidemic emergency.
Many of the requirements and recommendations in this document are also applicable to other systems
developed rapidly to respond to emergency conditions affecting the public.
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
ISO/IEC/IEEE 15289, Systems and software engineering — Content of life-cycle information items
(documentation)
3 Terms, definitions, and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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: https:// dictionary .ieee .org
1) Under preparation.
1
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC/IEEE FDIS 24748-9: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 SEVOCAB (Systems and software
Engineering Vocabulary) database, and which is publicly accessible at www .computer .org/ sevocab.
3.1.1
constituent system
CS
independent system (3.1.3) that forms part of a system of systems (SoS) (3.1.5)
Note 1 to entry: Constituent systems can be part of one or more SoS. Each constituent system is a useful system
by itself, having its own development, management, utilization, goals, and resources, but interacts within the SoS
to provide the unique capability of the SoS.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.1, modified — The abbreviated term "CS" has been added.]
3.1.2
emergency
serious, unexpected, and often dangerous situation requiring immediate action
3.1.3
system
arrangement of parts or elements that together exhibit a stated behaviour or meaning that the
individual constituents do not
[SOURCE: ISO/IEC/IEEE 15288:—, 3.47]
3.1.4
system-of-interest
SoI
system (3.1.3) whose life cycle is under consideration
[SOURCE: ISO/IEC/IEEE 15288:—, 3.49]
3.1.5
system of systems
SoS
set of systems (3.1.3) and system elements that interact to provide a unique capability that none of the
constituent systems (3.1.1) can accomplish on its own
Note 1 to entry: System elements can be necessary to facilitate interaction of the constituent systems in the
system of systems.
[SOURCE: ISO/IEC/IEEE 21839:2019, 3.1.4]
3.2 Abbreviated terms
API application program interface
CWBS contract work breakdown structure
DT&E developmental test and evaluation
ESOH environment, safety, and occupational health
EVM earned value management
FMECA failure mode, effects, and criticality analysis
IMP integrated main plan
IMS integrated main schedule
2
© ISO/IEC 2023 – All rights reserved
© IEEE 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/IEC/IEEE
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.