Chillarege, R. 1999. “Software Testing Best Practices,” IBM Technical Report RC 21457 Log 96856.
Civil Aviation Authority. 2003. “CAP 670: Air Traffic Services Safety Requirements.” Available online at <http://www.caa.co.uk/docs/33/cap670.pdf>.
Computer Economics. 2003. “Virus Attack Costs on the Rise—Again.” Available online at <http://www.computereconomics.com/article.cfm?id=873>.
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.
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.
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.
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 <http://www.npsf.org/exec/report.html>.
Cusumano, Michael A., and David B. Yoffie. 1998. Competing on Internet Time: Lessons from Netscape and Its Battle with Microsoft. Free Press, New York.
Dahl, O.J., E.W. Dijkstra, and C.A.R. Hoare. 1972. Structured Programming. Academic Press, New York.
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.
Dornheim, Michael A. 2005. “Codes gone awry.” Aviation Week & Space Technology, February 28, p. 63.
FAA (Federal Aviation Administration). 2003. Charter for the Certification Process Study (CPS) Response Aviation Rulemaking Committee. January 16.
FAA. 2004. “Reusable Software Components” (AC 20-148). FAA, Washington, D.C. Available online at <http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgAdvisoryCircular.nsf/0/EBFCCB29C0E78FFF86256F6300617BDD?OpenDocument>.
FDA (Food and Drug Administration). 2002. “General Principles of Software Validation; Final Guidance for Industry and FDA Staff.” Available online at <http://www.fda.gov/cdrh/comp/guidance/938.html>.
FDA. 2003. “Why Is Human Factors Engineering Important for Medical Devices?” Available online at <http://www.fda.gov/cdrh/humanfactors/important.html>.
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.
Fitzgibbon, Chris. 1998. “Impact of ISO 9001 on Software Quality.” Capital Quality News. Available online at <http://www.orioncanada.com/Impact.htm>.
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.
Freeman, Sholnn. 2005. “Toyota Attributes Prius Shutdowns to Software Glitch.” Wall Street Journal, May 16. Available online at <http://online.wsj.com/article_print/SB111619464176634063.html>.
Gacek, Cristina, and Budi Arief. 2004. “The Many Meanings of Open Source.” IEEE Software 21(1):34-40.
Gage, Deborah, and John McCormick. 2004. “We Did Nothing Wrong.” Baseline, March 4. Available online at <http://www.baselinemag.com/article2/0,1540,1543571,00.asp>.
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.