When Bugs Aren't Allowed 489
Coryoth writes "When you're writing software for an air traffic control system, military avionics software, or an authentication system for the NSA, the delivered code can't afford to have bugs. Praxis High Integrity Systems, who were the feature of a recent IEEE article, write exactly that kind of software. In "Correctness by Construction: A Manifesto for High-Integrity Software" developers from Praxis discuss their development method, explaining how they manage such a low defect rate, and how they can still maintain very high developer productivity rates using a more agile development method than the rigid processes usually associated with high-integrity software development."
nearly unlimited funding (Score:5, Funny)
Speaking of bugs... (Score:2, Funny)
No Bugs for NSA? (Score:5, Funny)
*rimshot*
When bugs aren't allowed? (Score:5, Funny)
Re:Here, here... (Score:5, Funny)
Uh (Score:4, Funny)
X windows in Ada for ATC (Score:5, Funny)
Re:Microsoft error rates (Score:5, Funny)
If operating systems ran airlines:
UNIX Airways: Everyone brings one piece of the plane along when they
come to the airport. They all go out on the runway and put the plane
together piece by piece, arguing non-stop about what kind of plane they
are suposed to be building.
Mac Airlines: All the airline personnel look and act exactly the same.
Every time you ask questions about details you are gently but firmly told
that you don't need to know, don't want to know, and everything will be
done for you without your ever having to know, so just shut up.
Windows Air: The terminal is pretty and colorful, with friendly stewards,
easy baggage check and boarding and a smooth take off. After about 10
minutes in the air the plane explodes with no warning whatsoever.
Windows NT Air: Just like Windows Air, but costs more, and uses much
bigger planes, and takes out all other planes in a 40 mile radius when it
explodes.
Linux Air: Disgruntled employees of all other OS Airlines, (with UNIX
geeks who finally figured out what kind of plane they were suposed to be
building) decide to start their own airline. They build the planes,
ticket counters, and pave the runways themselves. They charge a small fee
to cover the cost of printing the ticket, but you can also download the
ticket and print it yourself. When you board the plane you are given a
seat, four bolts, a wrench, and a copy of the Seat-HOWTO.html. Once
settled, the fully adjusable seat is very comfotable, the plane leaves
and arrives on time without problems, and the in-flight meal is
wonderful. You try to tell the customers of the other airlines about the
great trip, but all they can say is, "You had to what with the seat?"
with apologies to Doc Searls and Linux Journal.
Re:Not unlimited funding (Score:1, Funny)
Re:The right programming language helps hugely (Score:3, Funny)
> had used C or Java I'd probably have spent triple the time for
> the same results.
Heh, that was probably a 1-liner in APL.
Of course APL programs longer than 1 line are usually unmaintainable, but no language is perfect...
Re:Bugs and Beta testing. (Score:3, Funny)
Wow (Score:3, Funny)
But seriously, that's cool. Any 'net resources on this for us software types who'd like to think we can solder two wires together without burning down the house?
Re:Microsoft error rates (Score:3, Funny)
Re:nearly unlimited funding (Score:5, Funny)
10 PRINK "HELLO WORLD"
Damn.
Re:productivity around 30 LOC per day (Score:3, Funny)
I would have said no payments for the first six months, then 19.7% after that.
Re:Here, here... (Score:2, Funny)
That's the best description of the registry I've ever heard. "The sacrament of reinstall" part reminded me of the little girl in The Exorcist.