Tools and Methodologies to Test Compliance with IEC61508 Standard
summary
Zephyr codebase analysis uses Parasoft C/C++test with the Edison Design Group parser to build a dependency structure matrix that highlights surprises (drivers are ~4% of files, unexpected cross-layer couplings). Architecture checks use Lattix DSM and Tracy to prove freedom from interference and map requirements-to-code. Coverage strategy merges unit, integration and system runs to achieve MCDC coverage where required. Results flow into a CI pipeline on GitHub/GitLab that produces TÜV-ready reports and can block pull requests automatically.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:10Functional Safety standard: IEC61508
- 9:38Architecture design principles in IEC 61508
- 11:05Static Code Analysis to help comply with C.2.6.2
- 17:05Unit Testing - FAQ
- 20:04Code Coverage
- 21:50Requirements Traceability
- 27:50The best path to automating compliance testing
- 28:49What do you need to do for IEC 61508?
related talks
53mBridging Safety and Architecture: Zephyr’s Path To IEC 61508 Complian...
42mZephyr Functional Safety BOF
20mSafety Processes
32mCommSec D2 - ProdSec: A Technical Approach
40mHow I Fell in Love with Zephyr – a System Architect’s Tale
41mA Human-Centric Quality Assurance Process for Open Source Softwa...
43mCode quality as an engine of your IT business
58mCoverage, quality, and Goodhart's Law