ISO/PAS 8926:2024

ISO/PAS 8926:2024

January 2024
Publicly available specification Current

Road vehicles - Functional safety - Use of pre-existing software architectural elements

This document describes a framework for functional safety to enable the use of pre-existing software architectural elements not originally developed in accordance with the ISO 26262:2018 series, but intended to be integrated into safety-related embedded software conformant with the ISO 26262:2018 series by:—     determining relevant criteria when using the pre-existing software architectural element as a safety-related element of safety-related embedded software;—     determining relevant criteria inherent to the pre-existing software architectural element, e.g. needs for external safety mechanisms to detect and control failures caused by the pre-existing software architectural element;—     providing suitable evidence and arguments for use of the pre-existing software architectural element that can include applicable procedures, techniques and safety measures;—     supporting the fulfilment of software safety requirements when using the pre-existing software architectural element as a safety-related element of safety-related embedded software;—     supporting the integration of the pre-existing software architectural element as a safety-related element of safety-related embedded software.

View the extract
Main informations

Collections

International ISO standards

Publication date

January 2024

Number of pages

19 p.

Reference

ISO/PAS 8926:2024

ICS Codes

43.040.15   Car informatics. On board computer systems

Print number

1
Sumary
Road vehicles - Functional safety - Use of pre-existing software architectural elements

This document describes a framework for functional safety to enable the use of pre-existing software architectural elements not originally developed in accordance with the ISO 26262:2018 series, but intended to be integrated into safety-related embedded software conformant with the ISO 26262:2018 series by:

     determining relevant criteria when using the pre-existing software architectural element as a safety-related element of safety-related embedded software;

     determining relevant criteria inherent to the pre-existing software architectural element, e.g. needs for external safety mechanisms to detect and control failures caused by the pre-existing software architectural element;

     providing suitable evidence and arguments for use of the pre-existing software architectural element that can include applicable procedures, techniques and safety measures;

     supporting the fulfilment of software safety requirements when using the pre-existing software architectural element as a safety-related element of safety-related embedded software;

     supporting the integration of the pre-existing software architectural element as a safety-related element of safety-related embedded software.

ZOOM ON ... the Requirements department
To comply with a standard, you need to quickly understand its issues in order to determine its impact on your activity.

The Requirements department helps you quickly locate within the normative text:
- mandatory clauses to satisfy,
- non-essential but useful clauses to know, such as permissions and recommendations.

The identification of these types of clauses is based on the document “ISO / IEC Directives, Part 2 - Principles and rules of structure and drafting of ISO documents ”as well as on a constantly enriched list of verbal forms.

With Requirements, quickly access the main part of the normative text!

With Requirements, quickly access the main part of the normative text!
Need to identify, monitor and decipher standards?

COBAZ is the simple and effective solution to meet the normative needs related to your activity, in France and abroad.

Available by subscription, CObaz is THE modular solution to compose according to your needs today and tomorrow. Quickly discover CObaz!

Request your free, no-obligation live demo

I discover COBAZ