Resources about programming practices for writing safety-critical software

The obsession with C&#x2F;C++ here is really weird. Like, take the MCO failure. That&#x27;s a classic, textbook problem that can be structurally guaranteed not to happen with use of even a basic type system. It should be literally impossible to confuse values of different types&#x2F;units&#x2F;dimensions like this in something described as &quot;safety-critical&quot;.<p>It seems like all the resources here are concerned with trying to whittle C&#x2F;C++ into an appropriate choice of tool, rather than choosing a different tool. It seems like a 1980s-1990s mindset.

I don&#x27;t have all my resources on hand right now, but off the top of my head this book should be added:<p><a href="https:&#x2F;&#x2F;mitpress.mit.edu&#x2F;books&#x2F;engineering-safer-world" rel="nofollow">https:&#x2F;&#x2F;mitpress.mit.edu&#x2F;books&#x2F;engineering-safer-world</a><p>This list is barely scratching the surface of safety-critical system engineering, but it&#x27;s a start.

Other than the latest MISRA, I really enjoyed &quot;Better Embedded System Software&quot; by Phil Koopman.<p>Ideally you should read it before starting your project, since it deal with the product specification&#x2F;gathering requirements phase, which is your starting point in safety critical systems.<p>[1] <a href="https:&#x2F;&#x2F;betterembsw.blogspot.com.br&#x2F;2010&#x2F;05&#x2F;test-post.html" rel="nofollow">https:&#x2F;&#x2F;betterembsw.blogspot.com.br&#x2F;2010&#x2F;05&#x2F;test-post.html</a>

Does anyone know how software quality is handled in complex supply chains, e.g. automotive? From my point of view software is a 2nd grade citizen in areas dominated by manufacturing and classical engineering.<p>I guess testing an over-the-update for a car that was build by ann OEM and thousands of suppliers must be quite a task.

hopefully in a future not so far away, most safety-critical code will be formally verified, like <a href="http:&#x2F;&#x2F;sel4.systems&#x2F;" rel="nofollow">http:&#x2F;&#x2F;sel4.systems&#x2F;</a> for example

DO-178B has been replaced by DO-178C.

In addition to MISRA, I&#x27;ve found the safety checklist in Lutz&#x27;s &quot;Targeting Safety-Related Errors During Software Requirements Analysis&quot; at <a href="https:&#x2F;&#x2F;trs.jpl.nasa.gov&#x2F;bitstream&#x2F;handle&#x2F;2014&#x2F;35179&#x2F;93-0749.pdf" rel="nofollow">https:&#x2F;&#x2F;trs.jpl.nasa.gov&#x2F;bitstream&#x2F;handle&#x2F;2014&#x2F;35179&#x2F;93-0749...</a> to be very useful.

Is there anything like this that specifically addresses reliability in a critical (but not &quot;safety-critical&quot;) system?

I have read the JSF standard. I learned a lot from reading it.<p>However, the JSF project has been reported to have lots of software defects.

That is awesome, thank you.

c++ is not considered safe for any RTOS system, in fact you won&#x27;t find it used in Aviation embedded devices (referring to the big 3 ) Tools yes, you can higher level languages to your heart&#x27;s content.