ISO/IEC/IEEE 15026-2:2022
(Main)Systems and software engineering — Systems and software assurance — Part 2: Assurance case
Systems and software engineering — Systems and software assurance — Part 2: Assurance case
This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.
Ingénierie du logiciel et des systèmes — Assurance du logiciel et des systèmes — Partie 2: Cas d'assurance
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/
STANDARD IEC/IEEE
15026-2
Second edition
2022-11
Systems and software engineering —
Systems and software assurance —
Part 2:
Assurance case
Ingénierie du logiciel et des systèmes — Assurance du logiciel et des
systèmes —
Partie 2: Cas d'assurance
Reference number
© ISO/IEC 2022
© IEEE 2022
© ISO/IEC 2022
© IEEE 2022
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 2022 – All rights reserved
© IEEE 2022 – All rights reserved
Contents Page
Foreword .iv
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 Use of assurance cases . 2
4.1 Overview . 2
4.2 Application of this document . 4
5 Structure of assurance cases . 4
5.1 General . 4
5.2 Top-level structure . 5
5.3 Description of types . 5
5.3.1 Context type . 5
5.3.2 Evidence type . 5
5.3.3 Claim type . 6
5.3.4 Inference type . 7
5.3.5 Supported claim type and argument type . 7
5.3.6 Narrative introduction type . 8
Annex A (informative) Examples of supported claims and arguments . 9
Annex B (informative) An example of top-level structure of assurance cases .13
Annex C (informative) Comparison of terminology .16
Bibliography .20
IEEE Notices and Abstract.21
iii
© ISO/IEC 2022 – All rights reserved
© IEEE 2022 – 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/IEC 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 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.
This document 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 second edition cancels and replaces the first edition (ISO/IEC 15026-2:2011), which has been
technically revised.
The main changes are as follows:
— Clause 2 of the previous edition was deleted.
— The title of Clause 5 of the previous edition was changed and became Clause 4 of this edition.
— Revised contents of Clause 6 can be found in Clause 5 of this edition.
— Clause 7 was deleted and its revised contents can be found in 4.2 and 5.2 of this edition.
A list of all parts in the ISO/IEC/IEEE 15026 series can be found on the ISO website.
iv
© ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
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 2022 – All rights reserved
© IEEE 2022 – All rights reserved
Introduction
The purpose of this document is to define assurance case structure terminology, thereby improving
consistency and comparability among instances of assurance cases and facilitating stakeholder
communications, engineering decisions, and other uses of assurance cases.
This document does not place requirements on the quality of the contents but describes the structure
and meaning of assurance cases with the necessary level of precision and detail so as to avoid
inconsistent and subjective use of the terms.
Existing standards addressing different application areas and topics related to assurance cases possibly
uses differing terminology and concepts when addressing common themes. This document is based on
experience drawn from these specialized standards and guidelines.
While several notations and slightly varying terminologies are currently used in practice, this document
does not require the use of any particular concrete representation including graphical representation.
Likewise, it places no requirements on physical implementation of the data; in particular, it includes no
requirements for redundancy or co-location.
Assurance cases are generally developed to support claims in areas such as safety, reliability,
maintainability, human factors, operability, and security. They are applicable to any property of a
system. These assurance cases are often called by more specific names, e.g. safety case or dependability
case. ISO/IEC/IEEE 15026-1 provides concepts, terminology, background and a list of standards related
to assurance cases.
[1]
This document uses the terminology and concepts consistent with ISO/IEC/IEEE 12207,
[5] [6]
ISO/IEC/IEEE 15288, and ISO/IEC/IEEE 15289. This document does not presume or require that it
[1] [5]
is applied in conjunction with ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288 .
vi
© ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
INTERNATIONAL STANDARD ISO/IEC/IEEE 15026-2:2022(E)
Systems and software engineering — Systems and software
assurance —
Part 2:
Assurance case
1 Scope
This document specifies requirements for structure terminology of assurance cases.
This document is applicable for developing and maintaining assurance cases.
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 15026-1, Systems and software engineering — Systems and software assurance — Part 1:
Concepts and vocabulary
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 15026-1 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 https:// dictionary .ieee .org
NOTE For additional terms and definitions in the field of systems and software engineering, see
[7]
ISO/IEC/IEEE 24765, which is published periodically as a "snapshot" of the SEVOCAB (Systems and software
Engineering Vocabulary) database and is publicly accessible at computer .org/ sevocab.
3.1.1
assurance case
auditable artefact that provides a convincing and sound argument for a claim on the basis of tangible
evidence under a given context
Note 1 to entry: An argument is valid if and only if it is necessary that if all of the premises are true, then the
conclusion is true. An argument is sound if and only it is valid and contains only true premises.
© ISO/IEC 2022 – All rights reserved
© IEEE 2022 – All rights reserved
3.1.2
assurance case report
auditable artefact that provides the claim of an assurance case (3.1.1) and a complete index of the
argument and evidence of the assurance c
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.