Re:Rules for Writing Safety Critical Code (2006)
by pjmlp on Friday November 04, 2016 @08:40AM
(#12872057)
MISRA only goes thus far.
For writing safe code in C, you should also check Frama-C and CERT Secure Coding Standards.
https://www.securecoding.cert.org/confluence/display/seccode...
Even better, get the algorithms written in a theorem prover which is guaranteed to generate reliable safe C code.
This is approach taken by Microsoft with P Language(Windows USB device driver stack) and F* (new TLS implementation).
Re:Rules for Writing Safety Critical Code (2006)
by mos_basik on Friday November 04, 2016 @11:38AM
(#12873404)
Gerard Holzmann is the main author of the formal software verification tool "spin" as well as the owner of spinroot.com. I took a class on formal verification under him at Caltech.
Re:Rules for Writing Safety Critical Code (2006)
by 4ad on Friday November 04, 2016 @11:44AM
(#12873459)
As an anecdote, spin was used in Plan 9 to validate the kernel scheduler and the IL network protocol. It was also used to validate a very early version of the Go scheduler.
FWIW the initial page just reflects the JPL publication "The Power of Ten – Rules for Developing Safety Critical Code" by Gerard Holzmann [0]
[0]: http://spinroot.com/gerard/pdf/P10.pdf