the power of ten rules for developing safety critical code

#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE VERIFICATION#
#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE SOFTWARE#
#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE CODE#

#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE SOFTWARE#

We want to make sure that this software is as robust as it can be.

#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE CODE#

The next mission to Mars, for instance, - the Mars Science Laboratory (MSL) mission - will fly more code than all earlier missions to Mars combined. If you look at the trends, the amount of software that we use to control spacecraft is increasing very rapidly. We’ve seen our share of anomalies on missions that we’ve flown in the past, some of them caused by software malfunctions. Holzmann: We started LaRS more or less as an experiment, to see if we could help figure out some of the more difficult software related problems that can complicate the execution of ever more complex space missions. What is the Laboratory for Reliable Software, and what types of projects does it typically get involved with? NTB: You currently head-up NASA/JPL’s Laboratory for Reliable Software. I was sort of partially recreating that spark from the early eighties of being part of a research agenda that people really felt passionate about, like the exploration of the solar system and the universe.

#THE POWER OF TEN RULES FOR DEVELOPING SAFETY CRITICAL CODE VERIFICATION#

I’d had a lot of interaction with JPL, working on software verification problems, so that really attracted me to JPL. I was more attracted to the passion that I saw in the scientists and engineers working on space missions at JPL. Many of my friends – about 20 of my colleagues from the Computer Science Research Center – found it in the somewhat unconventional culture at Google, which indeed is very similar to Bell Labs in the early eighties. In some sense, most of us tried to find a research environment as close as possible to the old Bell Labs.

When many of my colleagues started leaving Bell Labs around 20, I also started looking. The company that owned Bell Labs, which was AT&T at that time, was quite powerful and rich, so it was a very special research environment with almost no restrictions and virtually complete freedom for researchers.īut 23 years is a very long time and life is too short to spend it all in one place. Also, at that time – the 1980s and 90s – Bell Labs had a lot of really talented people working there. A lot of really important inventions came out of that lab. I consider myself fortunate to have spent such a long time at Bell Labs during what many people call “the golden days of research at Bell Labs.” NTB: It was arguably one of the most famous think tanks in the world. What made you decide to leave Bell Labs in 2003 and work for NASA?ĭr. NASA Tech Briefs: After completing your education at Delft University of Technology in the Netherlands, you spent the first 20-plus years of your career at Bell Labs working in their Computing Science Research Center. Holzmann is credited with inventing the SPIN model checker for distributed software systems and a Method and Apparatus for Testing Event Driven Software, as well as authoring The Power of 10: Rules for Developing Safety Critical Code, and the groundbreaking book Beyond Photography – The Digital Darkroom. Gerard Holzmann joined NASA’s Jet Propulsion Laboratory in 2003 to help create the Laboratory for Reliable Software (LaRS), which he currently manages.

The power of ten rules for developing safety critical code