Software for dependable systems: Sufficient evidence?

Software for Dependable Systems: Sufficient Evidence?

Volumn , Issue , 2007, Pages 1-148

  Jackson, Daniel ^a   Thomas, Martyn ^b   Millett, Lynette I ^c  

^a MASSACHUSETTS INSTITUTE OF TECHNOLOGY   (United States)

^b Martyn Thomas Associates   (United Kingdom)

^c NATIONAL ACADEMIES OF SCIENCES   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SOFTWARE; SOFTWARE ENGINEERING; SOFTWARE TESTING;

AUTOMATED REGRESSION TESTING; CONFIGURATION MANAGEMENT; DEPENDABLE SOFTWARES; DEPENDABLE SYSTEMS; DEVELOPMENT METHOD; FUNDAMENTAL PRINCIPLES; SOUND AND COMPLETE; SYSTEM DEPENDABILITY;

STATIC ANALYSIS;

EID: 84991042142     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.17226/11923     Document Type: Book

References (139)

1. Adams, E. 1984. "Optimizing Preventive Service of Software Products." IBM Journal of Research 28(1):2-14.
2. Akerlof, George A. 1970. "The Market for 'Lemons': Quality Uncertainty and the Market Mechanism." Quarterly Journal of Economics 84(3):488-500.
3. Alves-Foss, Jim, Bob Rinker, and Carol Taylor. 2002. "Merging Safety and Assurance: The Process of Dual Certification for FAA and the Common Criteria." Available online at .
4. Amey, Peter. 2002. "Correctness by Construction: Better Can Also Be Cheaper," Cross- Talk Magazine, The Journal of Defence Software Engineering, March. Available online at .
5. Avizienis, A., J.-C. Laprie, B. Randell, and C. Landwehr. 2004. "Basic Concepts and Taxonomy of Dependable and Secure Computing." IEEE Transactions on Dependable and Secure Computing 1(1):11-33.
6. Barnes, John. 2003. High Integrity Software: The SPARK Approach to Safety and Security. Addison- Wesley, Boston, Mass.
7. BBC News. 2005. "Hospital Struck by Computer Virus." August 22. Available online at .
8. Beck, Kent. 1999. Extreme Programming Explained: Embrace Change. Addison-Wesley, New York.
9. Besnard, D., C. Gacek, and C.B. Jones, eds. 2006. Structure for Dependability, Springer-Verlag, New York.
10. Boyapati, Chandrasekhar, Sarfraz Khurshid, and Darko Marinov. 2002. "Korat: Automated Testing Based on Java Predicates." ACM/SIGSOFT International Symposium on Software Testing and Analysis, Rome, Italy. July.
11. Butler, R., and G. Finelli. 1993. "The Infeasibility of Quantifying the Reliability of Life- Critical Real-Time Software." IEEE Transactions on Software Engineering 19(1):3-12.
12. Chapman, R., and A. Hall. 2002. "Correctness by Construction: Developing a Commercially Secure System." IEEE Software (January/February):18-25.
13. Chillarege, R. 1999. "Software Testing Best Practices," IBM Technical Report RC 21457 Log 96856.
14. Civil Aviation Authority. 2003. "CAP 670: Air Traffic Services Safety Requirements." Available online at .
15. Computer Economics. 2003. "Virus Attack Costs on the Rise-Again." Available online at .
16. Cook, Richard, and Michael O'Connor. Forthcoming. "Thinking About Accidents and Systems," in Improving Medication Safety, K. Thompson and H. Manasse, eds. American Society of Health-System Pharmacists, Washington, D.C.
17. Cook, R., and J. Rasmussen. 2005. "Going Solid: A Model of System Dynamics and Consequences for Patient Safety." Quality and Safety in Health Care 14(2):130-134.
18. Cook, R.I., D.D. Woods, and M.B. Howie. 1992. "Unintentional Delivery of Vasoactive Drugs with an Electromechanical Infusion Device." Journal of Cardiothoracic and Vascular Anesthesia 6:238-244.
19. Cook, R.I., D.D. Woods, and C. Miller. 1998. "A Tale of Two Stories: Contrasting Views on Patient Safety." National Patient Safety Foundation, Chicago, Ill., April. Available online at .
20. Cusumano, Michael A., and David B. Yoffie. 1998. Competing on Internet Time: Lessons from Netscape and Its Battle with Microsoft. Free Press, New York.
21. Dahl, O.J., E.W. Dijkstra, and C.A.R. Hoare. 1972. Structured Programming. Academic Press, New York.
22. Department of Transportation, Office of the Inspector General. 2005. "Status of FAA's major acquisitions: Cost growth and schedule delays continue to stall air traffic modernization." Report Number AV-2005-061, May 26.
23. Dornheim, Michael A. 2005. "Codes gone awry." Aviation Week & Space Technology, February 28, p. 63.
24. FAA (Federal Aviation Administration). 2003. Charter for the Certification Process Study (CPS) Response Aviation Rulemaking Committee. January 16.
25. FAA. 2004. "Reusable Software Components" (AC 20-148). FAA, Washington, D.C. Available online at .
26. FDA (Food and Drug Administration). 2002. "General Principles of Software Validation; Final Guidance for Industry and FDA Staff." Available online at .
27. FDA. 2003. "Why Is Human Factors Engineering Important for Medical Devices?" Available online at .
28. Fenton, N.E., and M. Neil. 1998. "A Strategy for Improving Safety Related Software Engineering Standards." IEEE Transactions on Software Engineering 24(11):1002-1013.
29. Fitzgibbon, Chris. 1998. "Impact of ISO 9001 on Software Quality." Capital Quality News. Available online at .
30. Frankl, Phyllis G., and Elaine J. Weyuker. 1993. "A Formal Analysis of the Fault-Detecting Ability of Testing Methods." IEEE Transactions on Software Engineering 19(3):202-213.
31. Freeman, Sholnn. 2005. "Toyota Attributes Prius Shutdowns to Software Glitch." Wall Street Journal, May 16. Available online at .
32. Gacek, Cristina, and Budi Arief. 2004. "The Many Meanings of Open Source." IEEE Software 21(1):34-40.
33. Gage, Deborah, and John McCormick. 2004. "We Did Nothing Wrong." Baseline, March 4. Available online at .
34. GAO (General Accounting Office). 1986. "Medical Devices: Early Warning of Problems Is Hampered by Severe Underreporting," U.S. Government Printing Office, Washington, D.C. GAO publication PEMD-87-1.
35. GAO. 1992. Patriot Missile Software Problem. Report of the Information Management and Technology Division. Available online at .
36. GAO. 2003. "Tactical Aircraft, Status of the F/A-22 Program: Statement of Allen Li, Director, Acquisition and Sourcing Management." GAO-33-603T. April 2.
37. Gardner, Reed M., and Randolph Miller. 1997. "Recommendations for Responsible Monitoring and Regulation of Clinical Software Systems." Annals of Internal Medicine 127(9): 842-845.
38. Geppert, L. 2004. "Lost Radio Contact Leaves Pilots on Their Own," IEEE Spectrum 41(11):16- 17, November.
39. German, Andy, and Gavin Mooney. 2001. "Air Vehicle Software Static Code Analysis- Lessons Learnt." Proceedings of the Ninth Safety-Critical Systems Symposium. Felix Redmill and Tom Anderson, eds. Springer-Verlag, Bristol, United Kingdom.
40. Glass, Robert L. 2005. "IT Failure Rates-70 Percent or 10-15 Percent?" IEEE Software 22(3):112.
41. Goetz, Brian, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes, and Doug Lea. 2006. Java Concurrency in Practice. Addison-Wesley, Boston, Mass.
42. GPS News. 2004. "Tanker Truck Shutdown via Satellite." Available online at .
43. Greenwell, William S., and John C. Knight. 2005. "What Should Aviation Safety Incidents Teach Us?" Technical Report CS-2003-12. University of Virginia, Charlottesville, Va. Available online at .
44. Grimaldi, James V., and Guy Gugliotta. 2001. "Chemical Plants Feared as Targets." Washington Post, December 16, p. A01.
45. Guth, Robert. 2003. "Make Software More Reliable." The Wall Street Journal. November 17.
46. Guttman, William. 2002. "The Private Sector: Sustainable Computing." Pittsburgh Post-Gazette, December 10. Available online at .
47. Hall, Anthony. 1996. "Using Formal Methods to Develop an ATC Information System." IEEE Software 13(2):66-76.
48. Hammond, J., R. Rawlings, and A. Hall. 2001. "Will It Work?" Proceedings of the 5 th IEEE International Symposium on Requirements Engineering, August.
49. Hilton, Adrian. 2003. "Engineering Software Systems for Customer Acceptance." Available online at .
50. Hinchey, Michael G., and Jonathan P. Bowen, eds. 1999. Industrial-Strength Formal Methods in Practice. Springer, London, United Kingdom.
51. Hoare, C.A.R. 1981. "The Emperor's Old Clothes" (Turing Award Lecture), Communications of the ACM 24(2):75-83. Available online at .
52. Hoare, C.A.R. 1996. "How Did Software Get So Reliable Without Proof?" Lecture Notes in Computer Science 1051:1-17.
53. Hoare, C.A.R.. 2003. "The Verifying Compiler: A Grand Challenge for Computing Research." Journal of the ACM 50(1):63-69.
54. Hollnagel, E., D.D. Woods, and N. Leveson, eds. 2006. Resilience Engineering: Concepts and Precepts. Ashgate, Aldershot, United Kingdom.
55. Holzmann, G.J. 2006. "The Power of Ten: Rules for Developing Safety Critical Code." IEEE Computer 39(6):95-97.
56. IAEA (International Atomic Energy Agency). 2001. "Investigation of an Accidental Exposure of Radiotherapy Patients in Panama: Report of a Team of Experts, 26 May-1 June 2001." IAEA, Vienna, Austria. Available online at .
57. Institute of Medicine. 2000. To Err Is Human: Building a Safer Health System. National Academy Press, Washington, D.C. Available online at .
58. Instrument Society of America. 1996. "Application of Safety Instrumented Systems for the Process Industries." ISA-S-84.01-1996 (S84.01).
59. Jackson, D., and J. Wing. 1996. "Lightweight Formal Methods." IEEE Computer Magazine 29(4)21-22.
60. Jackson, Michael. 1996. Software Requirements & Specifications. Addison-Wesley and ACM Press.
61. Jackson, Michael. 2000. "The Real World." In Millennial Perspectives in Computer Science: Proceedings of the 1999 Oxford-Microsoft Symposium in Honour of C A R Hoare, Jim Davies, Bill Roscoe, and Jim Woodcock, eds. Palgrave Macmillan.
62. Jackson, Michael. 2001. Problem Frames: Analysing and Structuring Software Development Problems. Addison-Wesley, Boston, Mass.
63. Jackson, Michael. 2004. "Seeing More of the World." IEEE Software 21(6):83-85. Available online at .
64. Johnson, C.W. 2003. Failure in Safety-Critical Systems: A Handbook of Accident and Incident Reporting. University of Glasgow Press, Glasgow, Scotland.
65. Keizer, Gregg. 2004. "Unprotected PCs fall to hacker bots in just four minutes." Tech Web, November 30. Available online at .
66. Khurshid, S., and D. Marinov. 2004. "TestEra: Specification-based Testing of Java Programs Using SAT." Automated Software Engineering Journal 11(4):403-434.
67. Kilbridge, Peter. 2003. "Computer Crash: Lessons from a System Failure." New England Journal of Medicine 348(March 6):881-882.
68. King, S., J. Hammond, R. Chapman, and A. Pryor, eds. 2000. "Is Proof More Cost-Effective Than Testing?" IEEE Transactions on Software Engineering 26(8):675-686.
69. Knight, John C. 2002. "Software Challenges in Aviation Systems." Lecture Notes in Computer Science 2434:106-112.
70. Koppel, Ross, Joshua P. Metlay, Abigail Cohen, Brian Abaluck, A. Russell Localio, Stephen E. Kimmel, and Brian L. Strom. 2005. "Role of Computerized Physician Order Entry Systems in Facilitating Medication Errors." Journal of the American Medical Association 293(10):1197-1203.
71. Kommerling, O., and M. Kuhn. 1999. "Design Principles for Tamper-Resistant Smartcard Processors," Proceedings of the USENIX Workshop on Smartcard Technology (Smartcard '99), Chicago, Ill., May 10-11. USENIX Association. Available online at .
72. Ladkin, Peter, translator. 1994. Translation of Report on the Accident to Airbus A32 0-211 Aircraft in Warsaw on 14 September 1993. Main Commission, Aircraft Accident Investigation, Warsaw. Available online at .
73. Lampson, Butler. 1983. "Hints for Computer System Design." ACM Operating Systems Review 17(5):33-48. Reprinted in IEEE Software 1(1):11-28. Available online at .
74. Layton, C., P.J. Smith, and C.E. McCoy. 1994. "Design of a Cooperative Problem-Solving System for En-route Flight Planning: An Empirical Evaluation." Human Factors 36:94-119.
75. Lee, Insup, and George Pappas. 2005. Final Report of High Confidence Medical Device Software and Systems (HCMDSS) Workshop, Philadelphia, Pa., June 2-3. Available online at .
76. Leemore, Dafny, and David Dranove. 2005. "Do Report Cards Tell Consumers Anything They Don't Already Know? The Case of Medicare HMOs," NBER Working Paper No. 11420. National Bureau of Economic Research, Cambridge, Mass.
77. Leveson, Nancy. 1995. Safeware: System Safety and Computers. Addison-Wesley, Boston, Mass.
78. Leveson, Nancy, and Clark S. Turner. 1993. "An Investigation of the Therac-25 Accidents." IEEE Computer 26(7):18-41.
79. Levy, Matthys, and Mario Salvadori. 1992. Why Buildings Fall Down. W.W. Norton & Company, New York.
80. Lin, L., R. Isla, K. Doniz, H. Harkness, K. Vicente, and D. Doyle. 1998. "Applying Human Factors to the Design of Medical Equipment: Patient Controlled Analgesia." Journal of Clinical Monitoring 14:253-263.
81. Lin, L., K. Vicente, and D.J. Doyle. 2001. "Patient Safety, Potential Adverse Drug Events, and Medical Device Design: A Human Factors Engineering Approach." Journal of Biomedical Informatics 34(4):274-284.
82. Lions, J.L. 1996. "ARIANE 5: Flight 501 Failure." Report by the Inquiry Board. Available online at .
83. Litchfield, David. 2006. "Which Database Is More Secure? Oracle vs. Microsoft." NGSSoftware Insight Security Research. Available online at .
84. Littlewood, B., and L. Strigini. 1993. "Validation of Ultra-High Dependability for Software- Based Systems." Communications of the ACM 36(11):69-80.
85. Loeb, Vernon. 2002. "'Friendly Fire' Deaths Traced to Dead Battery: Taliban Targeted, but U.S. Forces Killed." Washington Post, March 24, p. A21.
86. Lohr, Steve. 2003. "2 Companies to Announce U.S. Clearance for Linux Security." New York Times, August 5. Available online at .
87. LynuxWorks. 2002. "LynuxWorks to Offer First DO-178B Certifiable POSIX RTOS." December 10. Available online at .
88. MacKenzie, Donald. 2001. Mechanizing Proof: Computing, Risk, and Trust. MIT Press, Cambridge, Mass.
89. Maisel, William H., Michael O. Sweeney, William G. Stevenson, Kristin E. Ellison, and Laurence M. Epstein. 2001. "Recalls and Safety Alerts Involving Pacemakers and Implantable Cardioverter-defibrillator Generators." Journal of the American Medical Association 286:793-799.
90. Michaels, Daniel, and Andy Pasztor. 2006. "Incidents Prompt New Scrutiny of Airplane Software Glitches." Wall Street Journal, May 30, p. A1.
91. Miller, Randolph, and Reed M. Gardner. 1997. "Recommendations for Responsible Monitoring and Regulation of Clinical Software Systems." Journal of the American Medical Informatics Association (4):442-457.
92. Montgomery, Kathryn. 2006. How Doctors Think, Clinical Judgment and the Practice of Medicine. Oxford University Press, Oxford, United Kingdom.
93. Naur, P., and B. Randell, eds. 1969. Software Engineering: Report on a Conference Sponsored by the NATO Science Committee. Garmisch, Germany, October 7-11. NATO Scientific Affairs Division, Brussels, Belgium. Available online at .
94. Nebeker, Jonathan R., Jennifer M. Hoffman, Charlene R. Weir, Charles L. Bennett, and John F. Hurdle. 2005. "High Rates of Adverse Drug Events in a Highly Computerized Hospital." Archives of Internal Medicine 165:1111-1116.
95. NRC (National Research Council). 1999a. Being Fluent with Information Technology. National Academy Press, Washington, D.C. Available online at .
96. NRC. 1999b. Trust in Cyberspace. National Academy Press, Washington, D.C. Available online at .
97. NRC. 2002. Cybersecurity Today and Tomorrow: Pay Now or Pay Later. The National Academies Press, Washington, D.C. Available online at .
98. NRC. 2003a. Critical Information Infrastructure Protection and the Law: An Overview of Key Issues. The National Academies Press, Washington, D.C. Available online at .
99. NRC. 2003b. The Internet Under Crisis Conditions: Learning from September 11. The National Academies Press, Washington, D.C. Available online at .
100. NRC. 2004. Summary of a Workshop on Software Certification and Dependability. The National Academies Press, Washington, D.C. Available online at .
101. NRC. 2005. Asking the Right Questions About Electronic Voting. The National Academies Press, Washington, D.C. Available online at .
102. NRC. 2006. "Letter Report on Electronic Voting." The National Academies Press, Washington, D.C. Available online at .
103. Nunnally, M., C.P. Nemeth, V. Brunetti, and R.I. Cook. 2004. "Lost in Menuspace: User Interactions with Complex Medical Devices." IEEE Transactions on Systems, Man and Cybernetics-Part A: Systems and Humans 34(6):736-742.
104. Olavsrud, Thor. 2003. "White House E-mail System Slows to a Crawl." Dc.internet.com, July 18. Available online at .
105. Page, D., P. Williams, and D. Boyd. 1993. Report of the Inquiry into the London Ambulance Service, Communications Directorate, South West Thames Regional Health Authority, London, February. Available online at .
106. Parnas, D.L., and J. Madey. 1995. "Functional Documentation for Computer Systems." Science of Computer Programming 25(1):41-61.
107. Perlis, Alan J. 1982. "Epigrams on Programming." SIGPLAN Notices 17(9):7-13.
108. Perrow, Charles. 1999. Normal Accidents. Princeton University Press, Princeton, N.J.
109. Perrow, Charles. 2007. The Next Catastrophe: Reducing Our Vulnerabilities to Natural, Industrial, and Terrorist Disasters. Princeton University Press, Princeton, N.J.
110. Perry, Shawna J., Robert L. Wears, and Richard I. Cook. 2005. "The Role of Automation in Complex System Failures." Journal of Patient Safety 1(1):56-61.
111. Petroski, Henry. 2004. To Engineer Is Human. St Martin's Press, New York.
112. Pfleeger, Shari Lawrence. 1998. "Understanding and Improving Technology Transfer in Software Engineering." Report DACS-SOAR-98-1. DoD Data and Analysis Center for Software.
113. Pfleeger, Shari Lawrence, and Les Hatton. 1997. "Investigating the Influence of Formal Methods." IEEE Computer 30(2):33-43.
114. Research Triangle Institute. 2002. The Economic Impacts of Inadequate Infrastructure for Software Testing (Final Report). Prepared for Gregory Tassey, National Institute of Standards and Technology, Acquisition and Assistance Division. Available online at .
115. Rice, Lynne L., and Andrew Lowery. 1995. "Premarket Notification 510(K): Regulatory Requirements for Medical Devices." Division of Small Manufacturers Assistance. U.S. Department of Health and Human Services, Publication FDA 95-4158. Center for Devices and Radiological Health. Available online at .
116. Rubin, Avi, Tadayoshi Kohno, Adam Stubblefield, and Dan S. Wallach. 2004. "Analysis of an Electronic Voting System." IEEE Symposium on Security and Privacy, Oakland, Calif. Available online at .
117. Sarter, N., and D.D. Woods. 1995. "How in the World Did We Get into That Mode? Mode Error and Awareness in Supervisory Control." Human Factors 37:5-19.
118. Sarter, N., D.D. Woods, and C. Billings. 1997. "Automation Surprises," Handbook of Human Factors/Ergonomics, G. Salvendy, ed., 2nd Ed., Wiley, New York, pp. 1926-1943. (Reprinted in N. Moray, ed., Ergonomics: Major Writings, Taylor & Francis, Boca Raton, Fla., 2004.).
119. Schneider, Fred. 2000. "Enforceable Security Policies." ACM Transactions on Information and System Security (TISSEC) 3(1):30-50.
120. Sha, Lui. 2001. "Using Simplicity to Control Complexity." IEEE Software 18(4):20-28.
121. Shankland, Stephen. 2003. "SuSE Linux gets security credentials." CNET News.com, August 5. Available online at .
122. Shooman, M.L. 1996. "Avionics Software Problem Occurrence Rates." The Seventh International Symposium on Software Reliability Engineering (ISSRE '96), p. 55. Available online at .
123. Shortliffe, Edward H. 2005. "Strategic Action in Health Information Technology: Why the Obvious Has Taken So Long." Health Affairs 24(5):1222-1233.
124. Slabodkin, Gregory. 1998. "Software Glitches Leave Navy Smart Ship Dead in the Water." Government Computer News, July 13. Available online at .
125. Smith, P.J., E. McCoy, and C. Layton. 1997. "Brittleness in the Design of Cooperative Problem- Solving Systems: The Effects on User Performance." IEEE Transactions on Systems, Man and Cybernetics- Part A 27(3):360-371.
126. Starbuck, W.H., and M. Farjoun, eds. 2005. Organization at the Limit: NASA and the Columbia Disaster. Blackwell, Malden, Mass.
127. "Tanker Truck Shutdown via Satellite." 2004. GPS News, November 4. Available online at .
128. Taylor, Andrew. 2001. "IT Projects Sink or Swim," Based on author's M.B.A. dissertation, BCS Review.
129. Thibodeau, Patrick. 2003. "NASA Leads Efforts to Build Better Software." Computerworld, February 7. Available online at .
130. Tiernan, Ray. 2003. "When Computing Was Reliable." osOpinion.com, March 17.
131. Trimble, Stephen. 2005. "Avionics Redesign Aims to Improve F/A-22 Stability." Flight International, August 23.
132. Verton, Dan. 2003. "GAO Reports Focused on NASA IT Workforce Issues." Computerworld, February 4. Available online at .
133. Wall, Robert. 2003. "Code Red Emergency." Aviation Week & Space Technology, June 9, pp. 35-36.
134. Wears, Robert L., and Marc Berg. 2005. "Computer Technology and Clinical Work: Still Waiting for Godot." Journal of the American Medical Association 293:1261-1263.
135. Weaver, Nicholas, and Vern Paxson. 2004. "A Worst-Case Worm." Paper presented at the Third Annual Workshop on Economics and Information Security (WEIS04), March 13- 14. Available online at .
136. Williams, Laurie, Robert R. Kessler, Ward Cunningham, and Ron Jeffries. 2000. "Strengthening the Case for Pair Programming." IEEE Software 17(4):19-25.
137. Woods, D.D., and E. Hollnagel. 2006. Joint Cognitive Systems: Patterns in Cognitive Systems Engineering. Taylor & Francis, Boca Raton, Fla.
138. Yurcik, William, and David Doss. 2001. "Achieving Fault-Tolerant Software with Rejuvenation and Reconfiguration." IEEE Software 18(4):48-52.
139. Yurcik, William, and David Doss. 2002. "Software Technology Issues for a U.S. National Missile Defense System." IEEE Technology and Society Magazine 21(2):36-46.