Writing a Base Level Library for Safety Critical Code in C++
summary
A reusable base-level C++ library for in-vehicle safety code enforces C++17 restriction because industry coding standards lag, requires qualified compilers per ASIL level, and uses a static analysis gate in CI that blocks merges; testing produces about four to five lines of test per production line and aims for 100% MCDC targets and requirement traceability, avoids dynamic allocation via preallocated/inline containers, and uses watchdog-driven assertions to reboot controllers when logic errors occur.
AI-written summary · about
chapters (10)
- 0:00Introduction to safety
- 2:30Safety requirements and analysis
- 6:42Industry standards and processes
- 12:18Safety integrity levels
- 19:33Coding standards and constraints
- 25:12Tooling and static analysis
- 34:46Testing methodologies
- 58:00Error handling and design
- 1:15:18Design for safety
- 1:32:53Summary and conclusions
related talks
19mQualification of the C and C++ Standard Libraries for Safety-critical Applications
01h 29mWhat Does It Take to Implement the C++ Standard Library?
45mThe existential threat against C++ and where to go from here
57mHow To Implement the C++ Standard Library - (Part 1 of 2)
54mKeynote: Safety in C++: All the Safeties!
01h 11mC++ in the World of Embedded Systems
01h 41mWriting Good C++14
22mWriting safe and secure code