|
|
|
|
|
by ams6110
2634 days ago
|
|
The software that runs safety-critical flight controls is actually developed nothing like typical ecommerce or social media. It is designed and developed to an engineering standard. You can review DO-178C requirements[1]. Not all software has the same consequences for failure. The highest level is when failure is catastrophic, i.e. "Failure may cause deaths, usually with loss of the airplane." This requires the highest "Level A" assurance level. Presumably MCAS was not originally evaluated as needing to meet the highest level. If it were, the single AoA input would have immediately disqualified the design right off the bat. There's some speculation that the delays on the "fix" are because if they have to redevelop the software at a "Level A" standard that means basically a complete reimplementation with full tracability of requirements from design to source code through compilation to executable, with independent verification. That won't happen in a few weeks. [1] https://en.wikipedia.org/wiki/DO-178C |
|
Hmmmm. Interesting. Is it legally required to use this standard for these critical softwares?
And are developers legally required to be licensed, in the same way that civil engineers are?