Ø In March of 2002 it was reported that
software bugs in Britain 's
national tax system resulted in more than 100,000 erroneous tax overcharges.
The problem was partly attibuted to the difficulty of testing the integration
of multiple systems.
Ø A newspaper columnist reported in July
2001 that a serious flaw was found in off-the-shelf software that had long been
used in systems for tracking certain U.S. nuclear materials. The same
software had been recently donated to another country to be used in tracking
their own nuclear materials, and it was not until scientists in that country
discovered the problem, and shared the information, that U.S. officials
became aware of the problems.
Ø According to newspaper stories in
mid-2001, a major systems development contractor was fired and sued over
problems with a large retirement plan management system. According to the
reports, the client claimed that system deliveries were late, the software had
excessive defects, and it caused other systems to crash.
Ø In January of 2001 newspapers reported
that a major European railroad was hit by the aftereffects of the Y2K bug. The company
found that many of their newer trains would not run due to their inability to
recognize the date '31/12/2000'; the trains were started by altering the
control system's date settings.
Ø News reports in September of 2000 told
of a software vendor settling a lawsuit with a large mortgage lender; the
vendor had reportedly delivered an online mortgage processing system that did
not meet specifications, was delivered late, and didn't work.
Ø In early 2000, major problems were
reported with a new computer system in a large suburban U.S. public school
district with 100,000+ students; problems included 10,000 erroneous report
cards and students left stranded by failed class registration systems; the
district's CIO was fired. The school district decided to reinstate it's
original 25-year old system for at least a year until the bugs were worked out
of the new system by the software vendors.
Ø In October of 1999 the $125 million
NASA Mars Climate Orbiter spacecraft was believed to be lost in space due to a
simple data conversion error. It was determined that spacecraft software used
certain data in English units that should have been in metric units. Among
other tasks, the orbiter was to serve as a communications relay for the Mars
Polar Lander mission, which failed for unknown reasons in December 1999.
Several investigating panels were convened to determine the process failures
that allowed the error to go undetected.
Ø Bugs in software supporting a large
commercial high-speed data network affected 70,000 business customers over a
period of 8 days in August of 1999. Among those affected was the electronic
trading system of the largest U.S.
futures exchange, which was shut down for most of a week as a result of the
outages.
Ø In April of 1999 a software bug caused
the failure of a $1.2 billion military satellite launch, the costliest unmanned
accident in the history of Cape Canaveral
launches. The failure was the latest in a string of launch failures, triggering
a complete military and industry review of U.S. space launch programs,
including software integration and testing processes. Congressional oversight
hearings were requested.
Ø A small town in Illinois received an unusually large monthly
electric bill of $7 million in March of 1999. This was about 700 times larger than
its normal bill. It turned out to be due to bugs in new software that had been
purchased by the local power company to deal with Y2K software issues.
Ø In early 1999 a major computer game
company recalled all copies of a popular new product due to software problems.
The company made a public apology for releasing a product before it was ready.
Ø The computer system of a major online U.S. stock
trading service failed during trading hours several times over a period of days
in February of 1999 according to nationwide news reports. The problem was
reportedly due to bugs in a software upgrade intended to speed online trade
confirmations.
Ø In April of 1998 a major U.S. data
communications network failed for 24 hours, crippling a large part of some U.S. credit card
transaction authorization systems as well as other large U.S. bank, retail, and
government data systems. The cause was eventually traced to a software bug.
Ø January 1998 news reports told of
software problems at a major U.S.
telecommunications company that resulted in no charges for long distance calls
for a month for 400,000 customers. The problem went undetected until customers
called up with questions about their bills.
Ø In November of 1997 the stock of a
major health industry company dropped 60% due to reports of failures in
computer billing systems, problems with a large database conversion, and
inadequate software testing. It was reported that more than $100,000,000 in
receivables had to be written off and that multi-million dollar fines were levied
on the company by government agencies.
Ø A retail store chain filed suit in
August of 1997 against a transaction processing system vendor (not a credit
card company) due to the software's inability to handle credit cards with year
2000 expiration dates.
Ø In August of 1997 one of the leading
consumer credit reporting companies reportedly shut down their new public web
site after less than two days of operation due to software problems. The new
site allowed web site visitors instant access, for a small fee, to their
personal credit reports. However, a number of initial users ended up viewing
each others' reports instead of their own, resulting in irate customers and
nationwide publicity. The problem was attributed to "...unexpectedly high
demand from consumers and faulty software that routed the files to the wrong
computers."
Ø In November of 1996, newspapers
reported that software bugs caused the 411 telephone information system of one
of the U.S. RBOC's to fail for most of a day. Most of the 2000 operators had to
search through phone books instead of using their 13,000,000-listing database.
The bugs were introduced by new software modifications and the problem software
had been installed on both the production and backup systems. A spokesman for
the software vendor reportedly stated that 'It had nothing to do with the
integrity of the software. It was human error.'
Ø On June 4 1996 the first flight of the
European Space Agency's new Ariane 5 rocket failed shortly after launching,
resulting in an estimated uninsured loss of a half billion dollars. It was
reportedly due to the lack of exception handling of a floating-point error in a
conversion from a 64-bit integer to a 16-bit signed integer.
Ø Software bugs caused the bank accounts
of 823 customers of a major U.S. bank to be credited with $924,844,208.32 each
in May of 1996, according to newspaper reports. The American Bankers
Association claimed it was the largest such error in banking history. A bank
spokesman said the programming errors were corrected and all funds were
recovered.
Ø Software bugs in a Soviet
early-warning monitoring system nearly brought on nuclear war in 1983,
according to news reports in early 1999. The software was supposed to filter
out false missile detections caused by Soviet satellites picking up sunlight
reflections off cloud-tops, but failed to do so. Disaster was averted when a
Soviet commander, based on a what he said was a '...funny feeling in my gut',
decided the apparent missile attack was a false alarm. The filtering software
code was rewritten.
No comments:
Post a Comment