The coupling between systems is insane, and it's all super rigid, with legal contracts specifying what, when and how often something can communicate. Many milli

The coupling between systems is insane, and it's all super rigid, with legal contracts specifying what, when and how often something can communicate. Many millions of dollars ride on these contracts. Basically it's a big jumbled big of Lego that's covered in Kraggle. With those constraints, lots of bugs are mis-design. IDK bug counts, or if that is even meaningful as it depends on thoroughness of testing, but a huge emphasises was placed on coding standards, static and dynamic analysis. They could well be the biggest single customer of Coverity. Overall I'd say it hasn't been a critical issue, given the larger architectural problems. The use of something like Ada SPARK in particular components might have focused attention on proving rather then testing, i.e. a completely different philosophy.