When Bugs Aren't Allowed
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."
probably helps too :P
You slashdotted stsc.hill.af.mil!
Unpretentious Sydney reviews by unqualified Sydney reviewers
Uh... it's going to be kind of hard for the NSA to do its job without bugs, isn't it?
*rimshot*
Ususually when the software and the phrases "life support" or "nuclear weapons" are together in the same sentence.
"I am the king of the Romans, and am superior to rules of grammar!"
-Sigismund, Holy Roman Emperor (1368-1437)
Could you clarify here. When talking about bad guidance software for planes, "crashing" is an ambigious term ;)
To make laws that man cannot, and will not obey, serves to bring all law into contempt.
--E.C. Stanton
control structures != Turing complete. You can have loops as long as they have constant maximum bounds. Whatever it happens to be that you mean when you say "Nand is Turing complete" it makes no sense when you actually typed it. "turing-complete (for arithmetic)." makes no sense at all. WTF? Someone failed CS 315.
autopr0n is like, down and stuff.
I was at an X windows technical conference many years ago when someone gave a presentation on X with Ada. When the speaker mentioned that it was for an air traffic control application, there was a sharp intake of breath all around the audience, most of whom had flown in for the meeting.
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.
Professional Politicians are not the solution, they ARE the problem.
I think the parent was talking to/about non-deities.
> Gawk all the way, got the project done in half an hour, if I
> 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...
maybe that 0.00 errors is just a result of a more exotic rounding algorithm than was discussed earlier
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?
And where's the description of GNU/Linux Air?
[Fuck Beta]
o0t!
I would have said no payments for the first six months, then 19.7% after that.
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.
Think of someone with average intelligence. Now think 1/2 the world is dumber than that guy.