Abstract
By analyzing the classes of errors that people make with systems, it is possible to develop principles of system design that minimize both the occurrence of error and the effects. This paper demonstrates some of these principles through the analysis of one class of errors: slips of action. Slips are defined to be situations in which the user's intention was proper, but the results did not conform to that intention. Many properties of existing systems are conducive to slips; from the classification of these errors, some procedures to minimize the occurrence of slips are developed.
- 1 Card, S., Moran, T., and Newell, A. Applied Information-Processing Psychology: The Human-Computer Interface. Er}baum Associates, Hillsdale, N.J., 1983.Google Scholar
- 2 Gentner, D. The Structure of Analogical Models in Science: Technical Report 4451. Bolt, Beranek and Newman, Cambridge, Mass, 1980.Google Scholar
- 3 Gentner, D. and Stevens, A. (Eds.), Mental Models. Erlbaum Associates, Hillsdale, N.J., 1983.Google Scholar
- 4 Lakoff, G. and Johnson, M. Metaphors We Live By. University of Chicago Press, Chicago, 1980.Google Scholar
- 5 Lockheed Missiles and Space Company. Human factors review of nuclear power plant control room design. EPRI NP-309-SY. Electric Power Research Institute, Palo Alto, California, 1976.Google Scholar
- 6 National Transportation Safety Board (NTSB). Aircraft incident report: Aero Mexico DC-10-30, XA-DUH over Luxembourg, Europe, November 11, 1979. (NTSB-AAR-80-10). National Transportation Safety Board, Washington, D.C., November, 1980. (Report available from National Technical Information Service.)Google Scholar
- 7 National Transportation Safety Board (NTSB). Special investigation report: Design-induced landing gear retraction accidents in Beech Baron, Bonanza, and other light aircraft. (NTSB-SR-80-1). National Transportation Safety Board, Washington, D.C., June, 1980. (Report available from National Technical Information Service.)Google Scholar
- 8 Norman, D. A. Categorization of action slips. Psychological Review, 88, 1981, 1-15.Google ScholarCross Ref
- 9 Norman, D. A. A psychologist views human processing: Human errors and other phenomena suggest processing mechanisms. Invited address, published in Proceedings of the International Joint Conference on Artificial Intelligence. Vancouver, 1981.Google Scholar
- 10 Norman, D. A. How to make computer systems that people will like to use: Steps toward a cognitive engineering. Proceedings of the Western Electronic Show and Convention (Wescon/82). Anaheim, California, Sept. 15, 1982.Google Scholar
- 11 Norman, D. A. Some observations on mental models. In D. Gentner and A. Stevens (Eds.), Mental Models. Erlbaum Associates, Hillsdale, N.J., 1983.Google Scholar
- 12 Norman, D. A. and Bobrow, D. G. Descriptions: An intermediate stage in memory retrieval. Cognitive Psychology, 11, 1979, 107-123.Google ScholarCross Ref
- 13 Schneider, M. L., Wexelblat, R. L., and Jende, M. S. Designing control languages from the user's perspective. In D. Beech (Ed.), Command Language Directions: Proceedings of the IFIP TC 2.7 Working Conference on Command Languages. North-Holland Publishing Co., New York, 1980.Google Scholar
- 14 Smith, D. C., Irby, C., Kimball, R., and Verplank, B. Designing the star user interface. Byte 7, 4 (April 1982), 242-282.Google Scholar
- 15 Teitelman, W. and Masinter, L. The Interlisp programming environment. Computer 14, 4 (April 1981), 25-33.Google ScholarDigital Library
Index Terms
- Design rules based on analyses of human error
Recommendations
Using human error information for error prevention
Developing error-free software requirements is of critical importance to the success of a software project. Problems that occur during requirements collection and specification, if not fixed early, are costly to fix later. Therefore, it is important to ...
Human Errors in Medical Practice: Systematic Classification and Reduction with Automated Information Systems
We review the general nature of human error(s) in complex systems and then focus on issues raised by Institute of Medicine report in 1999. From this background we classify and categorize error(s) in medical practice, including medication, procedures, ...
A Case History Development of a Foolproofing Interface Documentation System
The authors discuss information transmission errors occurring between design engineers involved in software development and describe an interface design documentation system that can prevent them. The equivalence of human errors in software design and ...
Comments