Short description:

Standards like ISO 26262 provide not so much of technical solutions how to architect/design a good safety-related software, or in other words, it does not provide a guidance how to do a good software safety concept. Yet it is a crucial topic as a selection of a safety concept can impact the project cost by factor of 10 or more.
Programming languages change, new systems arrive, yet much of safety knowledge stays the same or is updated to new technologies.
So this training will provide a guidance that is applicable regardless if you use e.g. C and classic AUTOSAR, or Rust or C++ on a safe Linux working on top of a hypervisor, or if you are developing a safe server.

General approach:

The exida approach is to describe all ingredients of safety concepts, including partitioning, communication, program flow monitoring, virtualization, containers, access to hardware, access to peripherals, design patterns for monitoring and redundancy, concepts for safety-related availability, concepts for tools like generators or ML frameworks.

Who should attend?

• Software Safety Engineers
• Software Safety Architects
• Product Owners
• Software Developers
• System Architects