January 6th, 2006


[/.] All software engineers need to read this.

The principles of "specify rigidly," "design intelligently and for verifiably," "test early, test often, and automate your tests to facilitate both operations" are well known principles. It's putting them into actual use that is often the problem. The company Praxis has a model for software development that has averaged less than 0.1 bugs per 1000 lines of code in several medium sized software projects. They call this approach "Correct By Construction", and it's worth at least reading about:


As this article says, there's a widespread belief that it's impossible to deliver near zero-bug software in a timely or profitable manner. This belief is mistaken, and it's about time us CS wonks started laying the smack down on the managers and executives who prop it up. Praxis is proof that IT CAN BE DONE. To do it, we have to become better engineers. Which I think most of us wouldn't mind anyway...