• Content Type

ISO/IEC/IEEE 15026-4:2021
BS ISO/IEC/IEEE 15026-4:2021

Systems and software engineering. Systems and software assurance. Assurance in the life cycle

Last updated: 18 Jul 2024

Development Stage

Pre-draft

Draft

Published

30 Jun 2021
published

Scope

What is ISO/IEC/IEEE 15026-4 about?

 ISO/IEC/IEEE 15026-4 is the fourth part of a series of documents applicable to system and software assurance. ISO/IEC/IEEE 15026-4 provides guidance and recommendations for the 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.

ISO/IEC 150262, ISO/IEC 150263 and ISO/IEC/IEEE 15026-4 all use the concepts and vocabulary defined in ISO/IEC/IEEE 150261; however, any part may be applied independently of the others and the use of one does not require the use of any others.

The conformance to ISO/IEC/IEEE 15026-4 shall be achieved in either or both of the following ways:

  • Achieving the required outcomes of the system assurance process view, in addition to conforming to ISO/IEC/IEEE 15288
  • Achieving the required outcomes of the software assurance process view, in addition to conforming to ISO/IEC/IEEE 12207

Who is ISO/IEC/IEEE 15026-4 for?

ISO/IEC/IEEE 15026-4 on systems and software assurances is useful for:

  • Software engineers
  • Software project managers
  • Software testers
  • System engineers
  • Authoritative bodies for regulation

Why should you use ISO/IEC/IEEE 15026-4?

 ISO/IEC 150262 provides minimum requirements for the structure and contents of assurance cases that treat claims regarding properties of a system or software product selected for special treatment. The results of performing the life cycle activities and tasks referenced in ISO/IEC 150262 can be recorded in the form of the assurance.

Using ISO/IEC 150262 software engineers can improve the quality of the software. ISO/IEC/IEEE 15026-4 can be used for establishing an agreement between an acquirer and a supplier, for regulatory purposes, or for the assessment of internal development processes. ISO/IEC/IEEE 15026-4 clarifies what it means both to achieve the assurance claim and to demonstrate that the assurance claim is achieved. ISO/IEC/IEEE 15026-4 can be used for establishing an agreement between an acquirer and a supplier concerning achieving the assurance claim and showing the achievement.

© BSI 2022 All rights reserved

Let the community know

Categorisation

Domain: Horizontal

Key Information

Organisation: ISO/IEC/IEEE, BSI
Committee: ISO/IEC JTC 1/SC 7
Relevant UK committee: IST/15/-/3

Referenced standards: ISO/IEC/IEEE 15288, ISO/IEC/IEEE 15026-1, ISO/IEC/IEEE 12207, ISO/IEC/IEEE 90003, ISO/IEC 21827, ISO/IEC 25000:2014, ISO/IEC 25020, ISO/IEC/IEEE 24748-3, ISO/IEC 15026-3, ISO/IEC 25012, ISO/IEC/IEEE 16326, IEC 61508-1, ISO/IEC/TS 33030, ISO/IEC 15026-2, ISO/IEC/IEEE 24748-2, ISO/IEC 27002, ISO/IEC/IEEE 15939, ISO/IEC 25010, ISO/IEC 33001, ISO/IEC/IEEE 16085, ISO/IEC 25040, ISO/IEC 27001, ISO/IEC/IEEE 24765, ISO/IEC 15504-5, ISO/IEC 25051, ISO/IEC 25030, ISO/IEC 33002:2015, ISO/IEC/IEEE 24748-1, ISO/IEC/IEEE 15289, ISO/IEC/IEEE 29148:2018

Discussion Forum

You must be logged in to contribute to the discussion

Login
\\n\\t\\t\\t\\t-->