Mastering Functional Safety – Translating ISO 26262 into system

architecture. Learn from an OEM’s Perspective:

THE ROLE OF ISO 26262 IN TESTING

AUTOMOTIVE SOFTWARE

Presentation by Dr.-Ing Manfred Schölzke, Team Leader “GME Vehicle System Safety”

THE ROLE OF ISO 26262 IN TESTING AUTOMOTIVE SOFTWARE

Dr.-Ing. Manfred Schölzke

GME Vehicle System Safety

25 March 2015

2

MOTIVATION

• GM has implemented a System Safety Engineering Process (SSEP) that

is a managed process compliant to ISO-26262

is based on the Systems Engineering V-cycle

comprehends different types of safety analyses, e.g. Hazard & Risk Analysis, Fault-tree Analysis (FTA) and Design-FMEA

ensures requirements and test case traceability

• Compatible Software Development processes (in-house or out-sourced) should

apply a minimum set of V&V methods, dependent on ASIL

demonstrate sufficient test coverage and structural coverage

enable efficient regression test strategies

support development of SW as part of a “Safety Element out of Context (SEooC)”

provide development vehicles with pre-series SW releases supporting safe operation