A direct path to dependable software

ABSTRACT

Who could fault an approach that offers greater credibility at reduced cost?

REFERENCES

• 1: Yichen Xie , Alex Aiken, Context- and path-sensitive memory leak detection, Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering, September 05-09, 2005, Lisbon, Portugal
• 2: Arney, P. Correctness by construction: Better can also be cheaper. CrossTalk: The Journal of Defense Software Engineering (Mar. 2002); www.praxis-his.com/pdfs/c_by_c_better_cheaper.pdf.
• 3: Thomas Ball , Sriram K. Rajamani, The SLAM project: debugging system software via static analysis, Proceedings of the 29th ACM SIGPLAN-SIGACT symposium on Principles of programming languages, p.1-3, January 16-18, 2002, Portland, Oregon
• 4: Bloch, J. Extra, extra---read all about it: Nearly all binary searches and mergesorts are broken; googleresearch.blogspot.com/2006/06/extra-extra-read-all-about-it-nearly.html.
• 5: Cone, E. The ugly history of tool development at the FAA. Baseline Magazine 4, 9 (Apr. 8, 2002).
• 6: Cook, R. and O'Connor, M. Thinking about accidents and systems. In Medication Safety: A Guide to Health Care Facilities, H.R. Manasse and K.K. Thompson, Eds. American Society of Health-System Pharmacists, Washington, DC, 2005; www.ctlab.org/documents/ASHP_chapter.pdf.
• 7: Patrick Cousot, Proving the absence of run-time errors in safety-critical avionics code, Proceedings of the 7th ACM & IEEE international conference on Embedded software, September 30-October 03, 2007, Salzburg, Austria [doi>10.1145/1289927.1289932]
• 8: Edsger W Dijkstra, The tide, not the waves, Beyond calculation: the next fifty years, Copernicus, New York, NY, 1997
• 9: FDA. Ensuring the safety of marketed medical devices: CDRH's medical device post-market safety program, 2006.
• 10: Feynman, R.P. Appendix F: Personal observations on the reliability of the shuttle. In Report of the Presidential Commission on the Space Shuttle Challenger Accident, 1986; science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt.
• 11: Gallaher, M. and Kropp, B. Economic Impacts of Inadequate Infrastructure for Software Testing, National Institute of Standards and Technology, 2002.
• 12: GAO. Medical Devices: Early Warning of Problems Is Hampered by Severe Under-reporting, Publication PEMD-87--1, U.S. Government Printing Office, 1986.
• 13: Linda Geppert, News: lost radio contact leaves pilots on their own, IEEE Spectrum, v.41 n.11, p.16-17, November 2004 [doi>10.1109/MSPEC.2004.1353787]
• 14: German, A. and Mooney, G. Air vehicle software static code analysis---Lessons learnt. In Proceedings of the Ninth Safety-Critical Systems Symposium, F. Redmill and T. Anderson, Eds. Springer-Verlag, Bristol, U.K., 2001.
• 15: William G. Griswold, Coping with Crosscutting Software Changes Using Information Transparency, Proceedings of the Third International Conference on Metalevel Architectures and Separation of Crosscutting Concerns, p.250-265, September 25-28, 2001
• 16: Anthony Hall, Using Formal Methods to Develop an ATC Information System, IEEE Software, v.13 n.2, p.66-76, March 1996 [doi>10.1109/52.506463]
• 17: Hammond, J., Rawlings, R., and Hall, A. Will it work? In Proceedings of the 5th International Symposium on Requirements Engineering (Toronto, Aug. 27--31, 2001).
• 18: Les Hatton, Safer C: Developing Software for in High-Integrity and Safety-Critical Systems, McGraw-Hill, Inc., New York, NY, 1995
• 19: Gerard J. NASA/JPL Laboratory for Reliable Software, The Power of 10: Rules for Developing Safety-Critical Code, Computer, v.39 n.6, p.95-97, June 2006 [doi>10.1109/MC.2006.212]
• 20: IAEA. Investigation of an Accidental Exposure of Radiotherapy Patients in Panama: Report of a Team of Experts, (Vienna, Austria, May 26--June 1, 2001); www-pub.iaea.org/MTCD/publications/PDF/Publll4_scr.pdf.
• 21: Jackson, D. Dependable software by design. Scientific American (June 2006); www.sciam.com/article.cfm?id=dependable-software-by-de&collD=l.
• 22: Jackson, D., Thomas, M., and Millett, L., Eds. Software For Dependable Systems: Sufficient Evidence? National Research Council. National Academies Press, 2007; books.nap.edu/openbook.php?isbn=0309103940.
• 23: Michael Jackson, Problem frames: analyzing and structuring software development problems, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
• 24: Gross, G. E-voting vendor: Programming errors caused dropped votes. Network World (Aug. 22, 2008); www.networkworld.com/news/2008/082208-e-voting-vendor-programming-errors-caused.html.
• 25: Krebs, B. Cyber incident blamed for nuclear power plant shutdown. Washington Post (June 5, 2008); www.washingtonpost.com/wp-dyn/content/article/2008/06/05/AR2008060501958_pf.html.
• 26: Ladkin, P., Transcriber. Transcription of Report on the Accident of Airbus A320-211 Aircraft in Warsaw on Sept, 14,1993, Main Commission Aircraft Accident Investigation Warsaw; www.rvs.uni-bielefeld.de/publications/Incidents/DOCS/ComAndRep/Warsaw/warsaw-report.html.
• 27: Barbara Liskov, A history of CLU, ACM SIGPLAN Notices, v.28 n.3, p.133-147, March 1993
• 28: Bev Littlewood , David Wright, Some Conservative Stopping Rules for the Operational Testing of Safety-Critical Software, IEEE Transactions on Software Engineering, v.23 n.11, p.673-683, November 1997 [doi>10.1109/32.637384]
• 29: Donald MacKenzie, Mechanizing proof: computing, risk, and trust, MIT Press, Cambridge, MA, 2001
• 30: Maisel, W., Sweeney, M., Stevenson, W., Ellison, K., and Epstein, L. Recalls and safety alerts involving pacemakers and implantable cardioverter-defibrillator generators. Journal of the American Medical Association 286, 7 (Aug. 15, 2001).
• 31: Ministry of Defence. Defence Standard 00-42: Reliability And Maintainability Assurance Guides, Part 2: Software, 1997.
• 32: David Lorge Parnas , Jan Madey, Functional documents for computer systems, Science of Computer Programming, v.25 n.1, p.41-61, Oct. 1995 [doi>10.1016/0167-6423(95)96871-J]
• 33: Perrow, C. Normal Accidents, Princeton University Press, 1999.
• 34: Perrow, C. The Next Catastrophe: Reducing our Vulnerabilities to Natural, Industrial, and Terrorist Disasters, Princeton University Press, 2004.
• 35: Shari Lawrence Pfleeger , Les Hatton, Investigating the Influence of Formal Methods, Computer, v.30 n.2, p.33-43, February 1997 [doi>10.1109/2.566148]
• 36: Rockoff, J. Flaws in medical coding can kill: Spread of computers creates new dangers, FDA officials warn. Baltimore Sun (June 30, 2008); http://pqasb.pqarchiver.com/baltsun/access/1502776681.html?dids=1502776681:1502776681&FMT=ABS&FMTS=A BS:FT&type=current&date=Jun+30%2C+2008&aut hor=Jonathan+D.+Rockoff&pub=The+Sun&desc=FL AWS+IN+MEDICAL+CODING+CAN+KILL.
• 37: Salvadori, M. Why Buildings Stand Up: The Strength of Architecture, Norton, 1980. See also Levy, M. and Salvadori, M. Why Buildings Fall Down: How Structures Fail, Norton, 1992.
• 38: Slabodkin, G. Navy: Calibration flaw crashed Yorktown LAN. Government Computing News (Nov. 9, 1998); www.gcn.com/print/17_30/33914-l.html.
• 39: Zetter, K. E-voting undermined by sloppiness. Wired (December 17, 2003); www.wired.com/politics/security/news/2003/12/61637.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures

Additional Classification:
  D. Software
  D.4 OPERATING SYSTEMS
      D.4.5 Reliability

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management