Foreword

Introduction

1Scope

2Normative references

3Terms and definitions

4Requirements for compliance

4.1Purpose

4.2General requirements

4.3Interpretations of tables

4.4ASIL-dependent requirements and recommendations

4.5Adaptation for motorcycles

4.6Adaptation for trucks, buses, trailers and semi-trailers

5General topics for the product development at the software level

5.1Objectives

5.2General

5.3Inputs to this clause

5.3.1Prerequisites

5.3.2Further supporting information

5.4Requirements and recommendations

5.5Work products

6Specification of software safety requirements

6.1Objectives

6.2General

6.3Inputs to this clause

6.3.1Prerequisites

6.3.2Further supporting information

6.4Requirements and recommendations

6.5Work products

7Software architectural design

7.1Objectives

7.2General

7.3Inputs to this clause

7.3.1Prerequisites

7.3.2Further supporting information

7.4Requirements and recommendations

7.5Work products

8Software unit design and implementation

8.1Objectives

8.2General

8.3Inputs to this clause

8.3.1Prerequisites

8.3.2Further supporting information

8.4Requirements and recommendations

8.5Work products

9Software unit verification

9.1Objectives

9.2General

9.3Inputs to this clause

9.3.1Prerequisites

9.3.2Further supporting information

9.4Requirements and recommendations

9.5Work products

10Software integration and verification

10.1Objectives

10.2General

10.3Inputs to this clause

10.3.1Prerequisites

10.3.2Further supporting information

10.4Requirements and recommendations

10.5Work products

11Testing of the embedded software

11.1Objective

11.2General

11.3Inputs to this clause

11.3.1Prerequisites

11.3.2Further supporting information

11.4Requirements and recommendations

11.5Work products

Annex AOverview of and workflow of management of product development at the software level (informative)

Annex BModel-based development approaches (informative)

B.1Objectives

B.2General

B.2.1Introduction

B.2.2General suitability aspects

B.2.3Potential impact of MBD on the software lifecycle

B.3Specific considerations for the example software development use cases

B.3.1Specification of software safety requirements (Clause 6 and ISO 26262‑8:2018, Clause 6)

B.3.2Development of the software architectural design (Clause 7)

B.3.3Design and implementation of software units (Clauses 8 and 9)

B.3.4Design, implementation and integration of software components, including automated code generation from software component models (Clauses 8, 9 and 10)

B.3.5Verification (static and/or dynamic) (Clauses 9, 10 and 11)

Annex CSoftware configuration (normative)

C.1Objectives

C.2General

C.3Inputs to this clause

C.3.1Prerequisites

C.3.2Further supporting information

C.4Requirements and recommendations

C.5Work products

Annex DFreedom from interference between software elements (informative)

D.1Objectives

D.2General

D.2.1Achievement of freedom from interference

D.2.2Timing and execution

D.2.3Memory

D.2.4Exchange of information

Annex EApplication of safety analyses and analyses of dependent failures at the software architectural level (informative)

E.1Objectives

E.2General

E.2.1Scope and purpose of the analyses

E.2.2Relationship between safety analyses and dependent failure analyses at the system, hardware and software level

E.2.3Safety analyses in a distributed software development (including SEooC development of software elements)

E.3Topics for performing analyses

E.3.1Determination of the goals for the analyses

E.3.2Determination of the scope and boundaries regarding the specific architectural design to be analysed

E.3.3Determination of the method applied to conduct the analyses

E.3.4Aspects to support the meaningfulness, objectivity and rigour of the analyses

E.3.4.1Coupling factor classes for DFA in accordance with ISO 26262‑9:2018

E.3.4.2Use content of Annex D

E.3.4.3Analyses supported by using guide words

E.4Mitigation strategy for weaknesses identified during safety and dependent failure analyses

Bibliography