Continuous Compliance: Agile Practices for Software Compliance
summary
An accelerator that turns ISO 26262 / Automotive SPICE evidence into code-near artifacts by extracting rst docstrings and PlantUML, running Sphinx + rst docstrings pipelines on every push, and producing a live traceability matrix, HTML dashboard and auto PDF/HTML output for auditors. It runs MISRA linting and architecture checks on C/C++ (proof-of-concept shows two requirements and one unit test), links tests to requirements, and targets OTA-updated projects so compliance moves from a 3–5 year audit to incremental, pipeline-driven assessment.
AI-written summary · about
chapters (11)
- 0:00Software in modern vehicles
- 4:44ISO 26262 and traceability
- 6:06Current compliance process
- 8:58Why continuous compliance
- 11:04Continuous compliance principles
- 13:13Compliance accelerator features
- 16:28Agile mindset for compliance
- 17:54Live demo: compliance docs
- 22:30Industry adoption and future
- 25:19Beyond automotive
- 26:26Q&A
related talks
25mContinuous compliance with Rust in automotive software
05mHow To Automate Compliance If You Aren't Chuck Norris
45mAgile Alchemy: Balancing Flexibility and Compliance in Software Development
15mShifting Open Source Compliance Activities Left
26mOperational Compliance: From Requirements to Reality
33mCompliance Without the Chaos: Building It Right Into Your DevOps...
37mPath To Production: Sustainable Compliance In Strict Environments
29mAutomating Continuous Compliance for Scalable SaaS Delivery