3 ms·
Here's the regulations they usually go by: https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178C h
by nickpsecurity 9y ago
Here's the regulations they usually go by:
https://en.wikipedia.org/wiki/DO-178B https://en.wikipedia.org/wiki/DO-178B
https://en.wikipedia.org/wiki/DO-178C https://en.wikipedia.org/wiki/DO-178C
There's an ecosystem of products developed this way, products such as static analyzers to help develop them, and even companies assisting in any part of the lifecycle. Market shifted toward reusable components for things such as RTOS's and middleware. Examples include INTEGRITY-178B, LynxOS-178B, Alt's OpenGL + driver for Radeon, partitioning Ethernet/networking/filesystems, Esterel SCADE, SPARK Ada, and so on. Lots of good stuff came from this.
On a tangent note, it's why I'm for software regulation where the useful subset of assurance methods that make those great become part of the requirements for commercial software. Defects will go down and predictability up across the board. Things will get more expensive with development slowing down a bit. That will probably be a good thing given Worse is Better effect market has been doing.
I went into more detail on regulation prior results and some predicted ones here:
https://www.schneier.com/blog/archives/2016/11/regulation_of_t.html#c6739118 https://www.schneier.com/blog/archives/2016/11/regulation_of...