The document provides an overview and analysis of notable software failures that occurred in 2016. It discusses the total number of people and assets affected by software failures, breaks down failures by industry and software type, and highlights some of the largest and most impactful failures. The goal is to emphasize the pervasiveness of software failures and the need for improved testing to prevent failures and their consequences.
2. How It Works
The Big Picture
Software Fails by Industry
One Year Rewind
Software Type
Type of Software Fail
Software Fails in the Stock Market
Government Software Fails
Retail Software Fails
Entertainment Software Fails
Transportation Software Fails
Service Software Fails
Finance Software Fails
The Software Fail Awards
Biggest Hacks of 2016
Biggest Fails of 2016 That Went
Un-noticed (Almost)
Most Shocking Fails of 2016
Conclusion
Resources
The Software Fail Watch: 2016 in Review is a sobering reminder
of how even a single software bug can cripple an enterprise.
With 4.4 billion people and 1.1 trillion in assets impacted by
software failures in 2016, it’s hard to argue that “more of the
same” is the best path forward for software development
professionals.
As the demand for the latest and greatest in technology and
convenience grows, so does the need for software testers to
protect their users and their brand from the potential influx of
software failures. Our goal at Tricentis is to help testers succeed
in this role—enabling fast, efficient, comprehensive testing that’s
designed to support Continuous Testing, Agile, and DevOps.
Ultimately, we want to ensure that the inevitable software bugs
are found by your testers, not your customers.
Preface
3. The Software Fail Watch is a
collection of software bugs found in
a year’s worth of English language
news articles. To find the stories, we
set up a Google account with an
alert for phrases such as “software
glitch” and “software bug”.
Then we manually sorted through
each of the alerts, picking out
promising headlines, reading the
articles for relevance, and noting
down any specific details of interest.
If the article reported a software
bug, we logged it into an Excel
sheet (which you can download
here), and extracted as much
information as possible.
What industry does this fall into?
Does the article say how much the
affected software cost to
implement?
Does it mention how many cars
were recalled? How long was the
system down? Is the associated
company public, private, or a
government contractor? You get the
idea.
No exact numbers were recorded
unless they were explicitly stated in
the article itself.
Stories that appeared in multiple
news alerts and were covered by
multiple reputable sources were
marked as having a “high level” of
brand damage.
In the end we categorized all the
stories into 6 broad industry
categories: Entertainment, Finance,
Government, Retail, Services, and
Transportation.
How It Works
1159
363
Stories
548 Software Fails
Companies
4. Statistically, there is a very good chance
that you have been personally impacted by
a software failure this year – perhaps even
in the last quarter, or week.
14. "Every company is a software company.
You’re building software that is going to
deliver business outcomes and software is
the differentiator for your business.”
https://www.skytap.com/blog/theresa-lanowitz-on-solving-age-old-problems-in-the-enterprise/
Theresa Lanowitz, voke
25. Most Shocking Fails of 2016
UK’s National Health Service admitted to mis-
prescribing medication to over 300,000 heart
patients due to a software error. SystmOne,
the software used to calculate the risk of a
heart attack, has reportedly produced
incorrect results since 2009. As a result,
some patients suffered from otherwise
preventable heart attacks or strokes. Others
needlessly dealt with the serious side-effects
of taking unnecessary medication.
Fiat Chrysler recalled over 1 million vehicles
after a government investigation revealed
that a gear-shift flaw resulted in 266
accidents, 68 injuries, and at least 1 death (of
a celebrity, no less). A software update was
issued to address the flaw, but the update
reportedly failed to fix at least 29,000 of the
recalled vehicles.
A security researcher disclosed a firmware
bug found in CCTV point-of-sale security
cameras sold by over 70 different vendors.
The bug, nicknamed ”Backoff”, is suspected
to be a contributing factor to the spate of
credit card breaches that occurred in major
retailers in the past years. The U.S.
Department of Homeland Security has
warned that up to 1,000 US businesses may
be infected with the bug.
Thanks to
system,
a faulty automated software
the
Unemployment
state of Michigan’s
Insurance Agency (UIA)
mistakenly accused over 20,000 innocent
people of fraud. Midas, the data analysis
system used, was wrongly accusing claimants
of fraud in a whopping 93% of cases,
resulting in unemployed persons losing their
benefits and facing fines of up to $100,000
USD. The system, implemented in 2013, had
been operating unchecked until 2015, when
Michigan’s auditor general issued a scathing
report on the system’s shortcomings.An Australian hospital suffered a string of
software outages, the longest lasting for 10
hours in early November. The software fail
reportedly
cutting off
medication,
admit and
threw the hospital in chaos,
access to patient records and
and forcing staff to manually
track patients by hand. The
hospital administration had reportedly
complained several times in the previous
months that the new software (implemented
in June) would eventually have “fatal
consequences” for patients if not fixed soon.
26. At one time (long, long ago), software was just a way of getting things
done. It was nothing more than the convenience of using a calculator
instead of doing your sums by hand. Those days are gone, however. The
average enterprise software landscape contains 52 interconnected
systems.* The average person’s software landscape is far vaster – as the
saying goes, “no man is an island”, and the bridges between ourselves
and the world are increasingly built with software.
Logically, this means that we could only expect the numbers we collect for
the annual Software Fail Watch to increase year-by-year. That is not,
however, the future Tricentis sees for software. Software testing methods
will not simply plateau while software development and innovation
climbs. The mainstreaming of DevOps and Agile has already done much
to fulfill today’s demands for modern software. The future of software
testing, however, belongs to Continuous Testing.
Conclusion
Love details?
Download the full list of software bugs collected in 2016.