This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Assumptions Lead to Preventable Errors
July/August 2009 (vol. 7 no. 4)
pp. 84-87
Gunnar Peterson, Arctec Group
Undocumented assumptions are often the cause of serious software system failure. Thus, to reduce such failures, developers must become better at discovering and documenting their assumptions. In this article, we focus on common categories of assumptions in software, discuss methods for recognizing when developers are making them, and recommend techniques for documenting them.

1. M. Zhivich and R.K. Cunningham, "The Real Cost of Software Errors," IEEE Security &Privacy, vol. 7, no. 2, 2009, pp. 87–90.
2. G.A. Lewis et al., "Assumptions Management in Software Development," Software Eng. Inst., Carnegie Mellon Univ., 2004; www.sei.cmu.edu/publications/documents/04.reports 04tn021.html.
3. M. Bishop and M. Dilger, "Checking for Race Conditions in File Accesses," Computing Systems, vol. 9, no. 2, 1996, pp. 131–152.

Index Terms:
Building security in, assumptions, software development
Citation:
Andy Steingruebl, Gunnar Peterson, "Software Assumptions Lead to Preventable Errors," IEEE Security & Privacy, vol. 7, no. 4, pp. 84-87, July-Aug. 2009, doi:10.1109/MSP.2009.107
Usage of this product signifies your acceptance of the Terms of Use.