“Keeping you up to date with everything software engineering!”

Software Failures in the News

In the News | October 06, 2004 | 1 comments

Mathew Fordahl of the Associated Press wrote an article titled “When Computers Run the World” that was published today in the Montreal Gazette that covers some of the recently publicized major software failures. Some of the software failures that are covered in the article include a system to manage orders at HP, a communication system for Southern California’s air traffic controllers and a budget system for Tacoma, Washington.

The author does not blame bad programming for the errors but blames the human limit because technology has gotten ahead of organization and command capabilities.

Interesting tidbits of information from the article:

• software bugs cost the US economy $59.5 billion US annually
• approx. 1/3 of the cost of bugs, or $22.2 billion US, can be eliminated by just improving testing
• a merchandise tracking system for Ross Stores Inc. failed and caused profits to decrease by 40%
• management of the project requirements and user needs seems to be biggest reason for failure

Related Links:

• Article: “When Computers Run the World” - Montreal Gazette

Help Support Us By Visiting Our Sponsor

10% of our revenue from these ads go towards scholarships!

Comments

October 7, 2004 05:55 PM | Mark Pavlidis commented:

My biggest complaint about the way software problems are reported in the media. Because software is the “most complex human artifact” (P. Picasso) many software developers don’t fully understand it, let alone the layperson. This means that a critical problem the shuts down an airport or causes the delay of financial transactions, as has recently occured, are reported as software “glitches”. To me a glitch something like when your parking brake light comes on in your car when it is not supposed to, not major engine failure. This method of reporting desensitises the public to the severity of the problems, and prevents the required critical mass outrage that is the catalyst for change that the industry deeply needs.

The referrenced article does a disservice to this cause by passing the buck to poor management. Don’t get me wrong, that was obviously the problem in the cited cases, and bad management often causes the failure of projects. But more structured methods of design anq development would have exposed the flaws at a much earlier stage, and not in production. Unfortunately, the author seems to have generalised from this that most software failures are due to poor management, when this is only a small piece of the giant jigsaw puzzle.

Post Your Comments

Comments:

Name:

Email Address:
(note: not displayed)

URL:
(note: displayed with comment)