Strategies for Developing Safety-Critical Software in C++
summary
Practical takeaways: developing for Medtronic-style medical devices requires concrete processes not platitudes — adherence to IEC 14971 and 62304, limiting external dependencies, and treating prototypes as clinical trials. Expect months to years of testing and audits, require logs and graceful failure modes, and keep unit coverage high. Merge requests include a merge-request checklist of direct questions: is logic infallible, are key assumptions documented, will this package need long-term maintenance, and can failures be diagnosed from available traces?
AI-written summary · about
related talks
55mStrong software for a safer future
21mSafety-Critical Development
55mComprehensive Testing of Embedded Software
53mFrom Chaos to Control: Overcoming C and C++’s Inherent Unsafety
25mContinuous compliance with Rust in automotive software
01h 00mBuilding Effective Embedded Systems in C++: Architectural Best Practices
01h 29mDelivering Safe C++
51m0xBADC0DE