This Article 
 Bibliographic References 
 Add to: 
The Real Cost of Software Errors
March/April 2009 (vol. 7 no. 2)
pp. 87-90
Michael Zhivich, MIT Lincoln Laboratory
Robert K. Cunningham, MIT Lincoln Laboratory
Modern society's reliance on software even in critical infrastructure systems makes software failures difficult to ignore. The cost of such failures manifests itself not only in dollars but also in lives. We present several examples from diverse critical systems that show the dire consequences of software failures and discuss recent research efforts aimed at finding and eliminating such errors.

1. US–Canada Power System Outage Task Force, Final Report on the August 14, 2003 Blackout in the United States and Canada: Causes and Recommendations, tech. report, US Dept. of Energy, Apr. 2004.
2. G. Williamson, "Software Safety and Reliability," IEEE Potentials, vol. 16, no. 4, 1997, pp. 32–36.
3. R. Lippmann, M. Zitser, and T. Leek, "Testing Static Analysis Tools using Exploitable Buffer Overflows from Open Source Code," ACM SIGSOFT Software Eng. Notes, vol. 29, no. 6, 2004, pp. 97–106.
4. T. Leek, M. Zhivich, and R. Lippmann, "Dynamic Buffer Overflow Detection," Proc. Workshop Evaluation of Software Defect Detection Tools, 2005; 61-zhivich.pdf.
5. M. Zhivich, Detecting Buffer Overflows using Testcase Synthesis and Code Instrumentation, master's thesis, Dept. of Electrical Eng. and Computer Science, Massachusetts Inst. of Tech., May 2005.
6. G. McGraw, "Software [In]Security: Software Security Demand Rising," InformIT,11 Aug. 2008; .

Index Terms:
software errors, software failures, cost, risks, secure systems
Michael Zhivich, Robert K. Cunningham, "The Real Cost of Software Errors," IEEE Security & Privacy, vol. 7, no. 2, pp. 87-90, March-April 2009, doi:10.1109/MSP.2009.56
Usage of this product signifies your acceptance of the Terms of Use.