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)

Ratings 3.81 / 5.00
ISO 26262-6:2018: Product development at the software level

What You Will Learn!

  • Functional Safety
  • ISO 26262
  • Software Development
  • Software Safety Requirements
  • Software Architectural Design
  • Software Unit Design
  • Coding
  • Software Testing
  • Testing of the Embedded Software

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 requirements

  • Clause 7: Software architectural design

  • Clause 8: Software unit design and implementation

  • Clause 9: Software unit testing

  • Clause 10: Software integration and testing

  • Clause 11: Testing of the embedded software


The following aspects are considered in Clause 6: Specification of software safety requirements:

  • The ISO 26262 V-model for the software development phase

  • Characteristics and attributes of the software safety requirements

The following aspects are considered in Clause 7: Software architectural design:

  • Principles and notations for the software architectural design

  • Error detection mechanisms according to ISO 26262

  • Error reaction mechanisms according to ISO 26262

  • Example 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 design

  • Methods for implementation of the software unit design

  • Software tool qualification

  • Example for the software unit design

The following aspects are considered in Clause 9: Software unit testing:

  • Aims of software unit testing

  • Methods to derive test methods with several examples

  • Test methods

  • Structural coverage (statement coverage, branch coverage, modified condition/decision coverage) with examples

The following aspects are considered in Clause 10: Software integration and testing:

  • Aims of software integration and testing

  • Methods to derive test cases

  • Test methods

  • Structural coverage (function coverage, call coverage) with example

The following aspects are considered in Clause 11: Testing of the embedded software:

  • Aims of testing of the embedded software

  • Test methods


In 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.

Who Should Attend!

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

TAKE THIS COURSE

Tags

  • Automotive Engineering

Subscribers

171

Lectures

16

TAKE THIS COURSE



Related Courses