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.

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.)

Schneider, Fred. 2000. “Enforceable Security Policies.” ACM Transactions on Information and System Security (TISSEC) 3(1):30-50.

Sha, Lui. 2001. “Using Simplicity to Control Complexity.” IEEE Software 18(4):20-28.

Shankland, Stephen. 2003. “SuSE Linux gets security credentials.” CNET News.com, August 5. Available online at <http://news.com.com/2100-1016_3-5059846.html?tag=fd_top>.

Shooman, M.L. 1996. “Avionics Software Problem Occurrence Rates.” The Seventh International Symposium on Software Reliability Engineering (ISSRE ’96), p. 55. Available online at <http://doi.ieeecomputersociety.org/10.1109/ISSRE.1996.558695>.

Shortliffe, Edward H. 2005. “Strategic Action in Health Information Technology: Why the Obvious Has Taken So Long.” Health Affairs 24(5):1222-1233.

Slabodkin, Gregory. 1998. “Software Glitches Leave Navy Smart Ship Dead in the Water.” Government Computer News, July 13. Available online at <http://www.gcn.com/print/17_17/33727-1.html>.

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.

Starbuck, W.H., and M. Farjoun, eds. 2005. Organization at the Limit: NASA and the Columbia Disaster. Blackwell, Malden, Mass.

“Tanker Truck Shutdown via Satellite.” 2004. GPS News, November 4. Available online at <http://www.spacedaily.com/news/gps-03zn.html>.

Taylor, Andrew. 2001. “IT Projects Sink or Swim,” Based on author’s M.B.A. dissertation, BCS Review.

Thibodeau, Patrick. 2003. “NASA Leads Efforts to Build Better Software.” Computerworld, February 7. Available online at <http://www.computerworld.com/softwaretopics/software/story/0,10801,78362,00.html>.

Tiernan, Ray. 2003. “When Computing Was Reliable.” osOpinion.com, March 17.

Trimble, Stephen. 2005. “Avionics Redesign Aims to Improve F/A-22 Stability.” Flight International, August 23.

Verton, Dan. 2003. “GAO Reports Focused on NASA IT Workforce Issues.” Computerworld, February 4. Available online at <http://www.computerworld.com/careertopics/careers/labor/story/0,10801,78172,00.html>.

Wall, Robert. 2003. “Code Red Emergency.” Aviation Week & Space Technology, June 9, pp. 35-36.

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.

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 <http://www.dtc.umn.edu/weis2004/weaver.pdf>.

Williams, Laurie, Robert R. Kessler, Ward Cunningham, and Ron Jeffries. 2000. “Strengthening the Case for Pair Programming.” IEEE Software 17(4):19-25.

Woods, D.D., and E. Hollnagel. 2006. Joint Cognitive Systems: Patterns in Cognitive Systems Engineering. Taylor & Francis, Boca Raton, Fla.

Yurcik, William, and David Doss. 2001. “Achieving Fault-Tolerant Software with Rejuvenation and Reconfiguration.” IEEE Software 18(4):48-52.

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.



The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement