ISO/IEC/IEEE 15026-4:2021

Systems and software engineering — Systems and software assurance — Part 4: Assurance in the life cycle

This document provides guidance and recommendations for assurance of a selected claim about the system-of-interest by achieving the claim and showing the achievement. The guidance and recommendations are given in a system assurance process view on top of ISO/IEC/IEEE 15288 and a software assurance process view on top of ISO/IEC/IEEE 12207.

Ingénierie du logiciel et des systèmes — Assurance du logiciel et des systèmes — Partie 4: Assurance du cycle de vie

General Information

• Status: Published
• Publication Date: 27-May-2021
• ICS: 35.080 - Software
• Technical Committee: ISO/IEC JTC 1/SC 7 - Software and systems engineering
• Drafting Committee: ISO/IEC JTC 1/SC 7/WG 7 - Life cycle management
• Current Stage: 9092 - International Standard to be revised
• Start Date: 21-Aug-2025
• Completion Date: 23-Aug-2025

Relations

• Revises: ISO/IEC 15026-4:2012 - Systems and software engineering — Systems and software assurance — Part 4: Assurance in the life cycle
• Effective Date: 26-Aug-2017

Standards Content (Sample)

INTERNATIONAL ISO/IEC/
STANDARD IEEE
15026-4
First edition
2021-05
Systems and software engineering —
Systems and software assurance —
Part 4:
Assurance in the life cycle
Ingénierie du logiciel et des systèmes — Assurance du logiciel et des
systèmes —
Partie 4: Assurance du cycle de vie
Reference number
©
ISO/IEC 2021
©
IEEE 2021
© ISO/IEC 2021
© IEEE 2021
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: [phone]
Email: [e-mail] Email: [e-mail]
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2021 – All rights reserved
ii © IEEE 2021 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Conformance . 2
5 Key concepts . 2
5.1 Process view . 2
5.2 Assurance claim and assurance information . 3
5.3 Using this document . 3
5.3.1 General. 3
5.3.2 Use for an agreement . 3
5.3.3 Use for regulation . 4
5.3.4 Use for development . . 4
6 System assurance process view . 4
6.1 General . 4
6.2 Purpose . 4
6.3 Outcomes . 4
6.4 Processes, activities and tasks that implement the system assurance process view . 4
6.5 Guidance and recommendations .11
6.5.1 General.11
6.5.2 Acquisition process .12
6.5.3 Supply process .13
6.5.4 Life cycle model management process .13
6.5.5 Quality management process.13
6.5.6 Project planning process .14
6.5.7 Project assessment and control process .15
6.5.8 Decision management process .15
6.5.9 Risk management process .15
6.5.10 Configuration management process .16
6.5.11 Information management process .17
6.5.12 Quality assurance process .18
6.5.13 Business or mission analysis process .18
6.5.14 Stakeholder needs and requirements definition process .19
6.5.15 System requirements definition process .21
6.5.16 Architecture definition process .22
6.5.17 Design definition process .22
6.5.18 System analysis process.22
6.5.19 Implementation process .23
6.5.20 Integration process .23
6.5.21 Verification process .23
6.5.22 Transition process .23
6.5.23 Validation process . . .24
6.5.24 Operation process .24
6.5.25 Maintenance process .25
6.5.26 Disposal process .25
7 Software assurance process view .26
7.1 General .26
7.2 Purpose .26
7.3 Outcomes .26
7.4 Processes, activities and tasks that implement the software assurance process view .27
7.5 Guidance and recommendations .32
© ISO/IEC 2021 – All rights reserved
© IEEE 2021 – All rights reserved iii

7.5.1 General.32
7.5.2 Configuration management process .33
7.5.3 System/software requirements definition process .34
7.5.4 Design definition process .35
7.5.5 Verification process .35
7.5.6 Maintenance process .35
Bibliography .37
IEEE Notices and Abstract .39
© ISO/IEC 2021 – All rights reserved
iv © IEEE 2021 – All rights reserved

Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical
activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the
work.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
rules given in the ISO/IEC Directives, Part 2 (see www .iso .org/ directives).
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its
standards through a consensus development process, approved by the American National Standards
Institute, which brings together volunteers representing varied viewpoints and interests to achieve the
final product. Volunteers are not necessarily members of the Institute and serve without compensation.
While the IEEE administers the process and establishes rules to promote fairness in the consensus
development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of
the information contained in its standards.
Attention is drawn to the possibility that some of the elements of this document may be the subject
of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent
rights. Details of any patent rights identified during the development of the document will be in the
Introduction and/or on the ISO list of patent declarations received (see www .iso .org/ patents) or the IEC
list of patent declarations received (see https:// patents .iec .ch).
Any trade name used in this document is information given for the convenience of users and do
...