I wonder how similar this methodology is to that used by like boeing or a major car manufacturer for their automated systems. You don’t hear about a lot of 777s crashing due to software bugs, but I doubt that they go through this same insane process. The software I write is unlikely to kill anyone but it could certainly lose a lot of money if it did the wrong thing. It has bugs all the time and I am always changing it so it will never be anywhere near bug free. What I do to avoid getting destroyed is put in safety features to keep bugs from causing major problems, and test stuff out to try to eliminate serious bugs before production. That works pretty well for me.
Overall, the space shuttle had a lot of bugs if we include mechanical systems and it killed a bunch of people. Given that I don’t know how impressed we should be that they had a really cumbersome software development process.
I wonder how similar this methodology is to that used by like boeing or a major car manufacturer for their automated systems. You don’t hear about a lot of 777s crashing due to software bugs, but I doubt that they go through this same insane process. The software I write is unlikely to kill anyone but it could certainly lose a lot of money if it did the wrong thing. It has bugs all the time and I am always changing it so it will never be anywhere near bug free. What I do to avoid getting destroyed is put in safety features to keep bugs from causing major problems, and test stuff out to try to eliminate serious bugs before production. That works pretty well for me.
Overall, the space shuttle had a lot of bugs if we include mechanical systems and it killed a bunch of people. Given that I don’t know how impressed we should be that they had a really cumbersome software development process.
They use similar methodologies:
http://en.wikipedia.org/wiki/MISRA_C http://www.ldra.com/jsf.asp