Re: Space exploration: Where do we go from here?
I know. 
Software Safety is not magic or new. We have known how to build safe software for a long, long time, based on practices developed for the nuclear power, defense, aviation, and space industries. They all have their own flavors (e.g. commercial aviation is Do-178C, NASA is NASA-STD-8719.13, military is covered under the Mil-Std-882 which allows the use of the Do-178 methods in many cases, etc). So there are no technical hurdles that would prevent "normal people" from developing their code using these methodologies - they are published, publicly available documents that provide a guide for writing safe code AND testing it properly to *prove* that it is safe. The only hurdle is $$$ - rigor does not come for free.
For commercial/military software, the gold standard is that you need to estimate a full day of a person's effort for every 10 "SLOCs" (source lines of code) that you have. The F-35 fighter, for example, had ~30M SLOCs last I knew, so that's 3 million person-days of effort. At 250 working days per year, that's 12,000 person-years worth of effort. If you want to get it done in 4 years, that means that you need a team of 3,000 software engineers writing and testing your code. By comparison, Google is estimated to be 2B (with a B) SLOCs, so if they wanted to apply the same rigor that aviation does - no problem. It's just going to take a team of 100,000 coders 8 years to put out Google 2.0. Not going to happen - nor should it. I don't need my search engine to be as bug-free as my aircraft flight control system.
Originally posted by alfablue
View Post

Software Safety is not magic or new. We have known how to build safe software for a long, long time, based on practices developed for the nuclear power, defense, aviation, and space industries. They all have their own flavors (e.g. commercial aviation is Do-178C, NASA is NASA-STD-8719.13, military is covered under the Mil-Std-882 which allows the use of the Do-178 methods in many cases, etc). So there are no technical hurdles that would prevent "normal people" from developing their code using these methodologies - they are published, publicly available documents that provide a guide for writing safe code AND testing it properly to *prove* that it is safe. The only hurdle is $$$ - rigor does not come for free.
For commercial/military software, the gold standard is that you need to estimate a full day of a person's effort for every 10 "SLOCs" (source lines of code) that you have. The F-35 fighter, for example, had ~30M SLOCs last I knew, so that's 3 million person-days of effort. At 250 working days per year, that's 12,000 person-years worth of effort. If you want to get it done in 4 years, that means that you need a team of 3,000 software engineers writing and testing your code. By comparison, Google is estimated to be 2B (with a B) SLOCs, so if they wanted to apply the same rigor that aviation does - no problem. It's just going to take a team of 100,000 coders 8 years to put out Google 2.0. Not going to happen - nor should it. I don't need my search engine to be as bug-free as my aircraft flight control system.
Comment