Introduction to ISO 26262 Functional safety

Purpose

Provide an overview of ISO 26262, with a particular emphasis on the early phases, including concept and system development.

Goals

The participants shall get an overall understanding of:

• ISO 26262 structure and content

• terminology and definitions

• development of a ”safety case”

• definition of and compliance with safety goals

• analysis of safety related functions and incidents

• classification of automotive safety integrity levels (ASIL)

• functional and technical safety requirements

• process and work requirements

Day 1

09:00     Introduction

09:30     Safety management

• – An overview of safety process management

• – Overall safety management

• – Safety management during item development

• – Safety management after release for production

10:30     Concept development

• – Overview of the concept phase

• – Item definition

• – Initiation of safety lifecycle

• – Hazard analysis and risk assessment

• – Definition of Safety Goals

• – ASIL classification

• – Functional safety concept

12:00     Lunch

13:00     Exercise

14:00     System development

• – Initiation of product development at the system level

• – Specification of the technical safety requirements

• – System design

15:30     Wrap up

16:00     End

Day 2

09:00     System development continue

• – Item integration and testing

• – Safety validation

• – Functional safety assessment

• – Release for production

09:45     Exercise

10:45     Hardware development

• – Process overview

• – Initiation of product development at hardware level

• – Specification of hardware safety requirements

• – Hardware architectural metrics

• – Evaluation of violation of safety goal due to random HW failures

• – Hardware integration and testing

12:00     Lunch

13:00     Software development

• – Process overview

• – Initiation of product development at software level

• – Specification of software safety requirements

• – Software architectural design

• – Software unit design and implementation

• – Software unit testing

• – Software integration and testing

• – Verification of software safety requirements

14:00     Exercise

15:00     Supporting processes

• – Distributed development

• – Specification and management of safety requirements

• – Configuration Management

• – Change Management

• – Verification

• – Documentation

• – Qualification of software tools

• – Qualification of software components

• – Qualification of hardware components

• – Proven in use argument

15:30     Wrap-up

16:00     End