Iso 26262-6:2018: Product Development At The Software Level

Plain and simple clause by clause explanation of ISO 26262-6:2018: SW development with exercises (electric vehicle)

What you’ll learn
Functional Safety
ISO 26262
Software Development
Software Safety Requirements
Software Architectural Design
Software Unit Design
Coding
Software Testing
Testing of the Embedded Software

Requirements
Recommended but not mandatory: Basic understanding of ISO 26262 and Functional Safety

Description
This course is about ISO 26262-4: Product development at the system level. All relevant clauses of this part of ISO 26262 are explained in the course. The following clauses are considered:Clause 6: Specification of software safety requirementsClause 7: Software architectural designClause 8: Software unit design and implementationClause 9: Software unit testingClause 10: Software integration and testingClause 11: Testing of the embedded softwareThe following aspects are considered in Clause 6: Specification of software safety requirements:The ISO 26262 V-model for the software development phaseCharacteristics and attributes of the software safety requirementsThe following aspects are considered in Clause 7: Software architectural design:Principles and notations for the software architectural designError detection mechanisms according to ISO 26262Error reaction mechanisms according to ISO 26262Example for the software architectural design The following aspects are considered in Clause 8: Software unit design and implementation:Principles and notations for the software unit designMethods for implementation of the software unit designSoftware tool qualificationExample for the software unit designThe following aspects are considered in Clause 9: Software unit testing:Aims of software unit testingMethods to derive test methods with several examplesTest methodsStructural coverage (statement coverage, branch coverage, modified condition/decision coverage) with examplesThe following aspects are considered in Clause 10: Software integration and testing:Aims of software integration and testingMethods to derive test casesTest methodsStructural coverage (function coverage, call coverage) with exampleThe following aspects are considered in Clause 11: Testing of the embedded software:Aims of testing of the embedded softwareTest methodsIn the exercises you will learn step by step how to develop the software architectural design and software safety requirements for an electric vehicle and the safety goal “Avoid an unintented acceleration”.A possible solution for the exercises is presented in a video.

Overview
Section 1: Introduction

Lecture 1 Introduction

Lecture 2 What is Functional Safety?

Lecture 3 Overview of ISO 26262:2018

Section 2: 6-6 Specification of software safety requirements

Lecture 4 Specification of software safety requirements

Section 3: 6-7 Software architectural design

Lecture 5 Principles and notations

Lecture 6 Basic design with an example

Lecture 7 Error detection and reaction mechanisms

Section 4: 6-8 Software unit design and implementation

Lecture 8 Methods and principles

Lecture 9 Software Unit Design (Example)

Lecture 10 Model-based Development (ASCET-DEVELOPER)

Lecture 11 Software Tool Qualification

Section 5: 6-9 Software unit testing

Lecture 12 Methods to derive test cases

Lecture 13 Test methods

Section 6: 6-10 Software integration and testing

Lecture 14 Software integration and testing

Section 7: 6-11 Testing of the embedded software

Lecture 15 Testing of the embedded software

Lecture 16 Thank you for your attention!

Project Leaders,Safety Managers,System Designers,Software Developers,Hardware Developers,Test Engineers,Quality Responsibles