skip to main content
article
Free Access

Exceptions and exception handling in computerized information processes

Published:01 April 1995Publication History
Skip Abstract Section

Abstract

Exceptions, situations that cannot be correctly processed by computer systems, occur frequently in computer-based information processes. Five perspectives on exceptions provide insights into why exceptions occur and how they might be eliminated or more efficiently handled. We investigate these perspectives using an in-depth study of an operating information process that has frequent exceptions. Our results support the use of a total quality management (TQM) approach of eliminating exceptions for some exceptions, in particular, those caused by computer systems that are poor matches to organizational processes. However, some exceptions are explained better by a political system perspective of conflicting goals between subunits. For these exceptions and several other types, designing an integrated human-computer process will provide better performance than will eliminating exceptions and moving toward an entirely automated process.

References

  1. ANDERSON, J.R. 1980. Cognitive Psychology and Its Implications. W. H. Freeman, San Francisco, Calif.Google ScholarGoogle Scholar
  2. BArnEY, J. E. mUD PERSON, S.W. 1983. Development of a tool for measuring and analyzing computer user satisfaction. Manage. Sci. 29, 5 (May), 530-545.Google ScholarGoogle Scholar
  3. BAINBRIDGE, L. 1987. Ironies of automation. In New Technology and Human Error, J. Rasmussen, K. Duncan, and J. Leplat, Eds. John Wiley and Sons, New York, 271-283.Google ScholarGoogle Scholar
  4. BENBASAT, I., GOLDSTEIN, D. K., AND MEAD, M. 1987. The case research strategy in studies of information systems. MIS Q. 11, 3 (Sept.), 369-386. Google ScholarGoogle Scholar
  5. BENDIFALLAH, S. AND SCACCHI, W. 1987. Understanding software maintenance work. IEEE Trans. Softw. Eng. SE~13, 3 (Mar.), 311-323. Google ScholarGoogle Scholar
  6. CASE, K.E. 1987. Quality control and assurance. In Production Handbook, J. A. White. Ed., 4th ed. John Wiley and Sons, New York.Google ScholarGoogle Scholar
  7. COHEN, M.D. 1991. Individual learning and organizational routine: Emerging connections. Org. Sci. 2, i (Feb.), 135-139.Google ScholarGoogle Scholar
  8. COHEN, M. n. AND BACDAYAN, P. 1994. Organizational routines are stored as procedural memory: Evidence from a laboratory study. Org. Sci. 5, 4 (Nov.), 554-568.Google ScholarGoogle Scholar
  9. COHEN, R. M. AND MAY, J.H. 1992. An application-based agenda for encorporating OR into an AI design environment for facility design. Eur. J. Oper. Res. 63, 254-270.Google ScholarGoogle Scholar
  10. COHEN, R. M. AND STRONG, D.M. 1991. A model for supporting database design. In Proceedrags of the 1st Workshop on Information Technologies and Systems. Cambridge, Mass., 243-273.Google ScholarGoogle Scholar
  11. DAVENPORT, T.H. 1993. Process Innovation: Reengineering Work through Information Technology. Harvard Business School Press, Boston, Mass. Google ScholarGoogle Scholar
  12. DAVENPORT, T. H. AND SHORT, J.E. 1990. The new industrial engineering: Information technology and business process redesign. Sloan Manag. Rev. 31, 4 (Summer), 11-27.Google ScholarGoogle Scholar
  13. DEMING, W. 1986. Out of Crisis. Center for Advanced Engineering Study, Massachusetts Inst. of Technolog3r, Cambridge, Mass.Google ScholarGoogle Scholar
  14. ERICSSON, K. A. AND SIMON, H.A. 1984. Protocol Analysts. MIT Press, Cambridge, Mass.Google ScholarGoogle Scholar
  15. FIEGENBAUM, A.V. 1991. Total Quality Control, 4th ed., Revised. McGraw-Hill, New York.Google ScholarGoogle Scholar
  16. FRANZ, C. R. AND ROBEY, D. 1984. An investigation of user-led system design: Rational and political perspectives. Commun. ACM 27, 12 (Dec.), 1202-1217. Google ScholarGoogle Scholar
  17. GALBaAITH, J.R. 1977. Orgamzation Design. Addison-Wesley, Reading, Mass.Google ScholarGoogle Scholar
  18. GALBRAITH, J.R. 1973. The Design of Complex Organizations. Addison-Wesley, Reading, Mass. Google ScholarGoogle Scholar
  19. GASSER, L. 1986. The integration of computing and routine work. ACM Trans. Office Inf. Syst. 4, 3 (July), 205-225. Google ScholarGoogle Scholar
  20. GOLDSTEIN, R. C. AND STOREY, V. C. 1991. The role of commonsense in database design. In Proceedings of the 1st Workshop on Information Technologies and Systems. Cambridge, Mass., 141-150.Google ScholarGoogle Scholar
  21. HAMMER, M. 1990. Reengineering work: Don't automate, obliterate. Harvard Bus. Rev. 68, 4 (July-Aug.), 104-112.Google ScholarGoogle Scholar
  22. ISmKAWA, K. 1985. What is Total Qualzty Control? The Japanese Way. Prentice-Hall, Englewood Cliffs, N.J.Google ScholarGoogle Scholar
  23. JURAN, J.M. 1989. Juran on Leadershzp for Quality: An Executive Handbook. The Free Press, New York.Google ScholarGoogle Scholar
  24. KLING, R. 1980. Social analyses of computing: Theoretical perspectives in recent empirical research. ACM Comput. Surv. 12, i (Mar.), 61-110. Google ScholarGoogle Scholar
  25. KLING, R. AND IACONO, S. 1984a. The control of information systems developments after implementation. Commun. ACM 27, 12 (Dec.), 1218-1226. Google ScholarGoogle Scholar
  26. KLING, R. AND IACONO, S. 1984b. Computing as an occasion for social control. J. Soc. Iss. 40, 3, 77 96.Google ScholarGoogle Scholar
  27. LENAT, D. B., GUHA, R. V., PITTMAN, K., PRATT, D., AND SHEPHERD, M. 1990. CYC: Toward programs with common sense. Commun. ACM 33, 8 (Aug.), 30-49. Google ScholarGoogle Scholar
  28. MARCH, J. G. AND SIMON, H.A. 1958. Organ,zattons. John Wiley and Sons, New York.Google ScholarGoogle Scholar
  29. MARKUS, M.L. 1984. Systems in Organizations: Bugs + Features. Pitman Publishing, Marshfield, Mass.Google ScholarGoogle Scholar
  30. MARKUS, M.L. 1983. Power, politics, and MIS implementation. Comrnun. ACM 26, 6 (June), 430-444. Google ScholarGoogle Scholar
  31. MARKUS, M. L. AND ROBEY, D. 1988. Information technology and organizational change: Causal structure in theory and research. Manag. Sci. 34, 5 (May), 583-598. Google ScholarGoogle Scholar
  32. NELSON, R. R. AND WINTER, S.G. 1982. An Evolutionary Theory of Economlc Change. Harvard University Press, Cambridge, Mass.Google ScholarGoogle Scholar
  33. NISBETT, R. E. AND WILSON, T.D. 1977. Telling more than we know: Verbal reports on mental processes. Psychol. Rev. 84, 3, 231-259.Google ScholarGoogle Scholar
  34. PRIETULA, M. J. AND SIMON, H.A. 1989. The experts in your midst. Harvard Bus. Rev. 67, 1 (Jan.-Feb.), 120-124.Google ScholarGoogle Scholar
  35. RASMUSSEN, J., DUNCAN, K., AND LEPLAT, J. (Eds.). 1987. New Technology and Human Error. John Wiley and Sons, New York.Google ScholarGoogle Scholar
  36. SASSO, W. C., OLSON, J. R., AND MERTEN, A.G. 1987. The practice of office analysis: Objectives, obstacles, and opportunities. IEEE Office Know. Eng. 1, 1, 11-24.Google ScholarGoogle Scholar
  37. SCHNEIDEWIND, N. F. 1987. The state of software maintenance. IEEE Trans. Softw. Eng. SE-13, 3 (Mar.), 303-310. Google ScholarGoogle Scholar
  38. SIMON, H.A. 1981. The Sciences of the Artificial, 2nd ed. MIT Press. Cambridge. Mass. Google ScholarGoogle Scholar
  39. SIMON, H.A. 1977. The New Science of Management Decision. Prentice-Hall, Englewood Cliffs, NJ. Google ScholarGoogle Scholar
  40. SIMON, H.A. 1973. Applying information technology to organization design. Pub. Admm. Rev. (May/June), 268-278.Google ScholarGoogle Scholar
  41. SIRBU, M., SCHOICHET, S., KUNIN, J. S., HAMMER, M., AND SUTHERLAND, J. 1984. OAM: An office analysis methodology. Behav. Inf. Tech. 3, 1, 25-39.Google ScholarGoogle Scholar
  42. STERLING, T.D. 1974. Guidelines for humanizing computerized information systems: A report from Stanley House. Commun. ACM 17, 11 (Nov.), 609-613. Google ScholarGoogle Scholar
  43. STINCHCOMBE, A. L. 1990. Information and Organizations. University of California Press, Berkeley, Calif. Google ScholarGoogle Scholar
  44. STOREY, V. C. AND GOLDSTEIN, R.C. 1993. Knowledge-based approaches to database design. MIS Q. 17, 1 (Mar.), 25-46.Google ScholarGoogle Scholar
  45. STRONG, D. M~ 1992. Decision support for exception handling and quality control in office operations. Dec. Supp. Syst. $, 3 (July), 217-227. Google ScholarGoogle Scholar
  46. STRONG, D.M. 1989. Integration of expert systems, traditional systems, and people: A manufacturing example. In Proceedings of the 3rd International Conference on Expert Systems and the Leading Edge in Production and Operations Management. Univ. of South Carolina, Columbia, S.C., 57-69.Google ScholarGoogle Scholar
  47. SUCH~N, L.A. 1983. Office procedure as practical action: Models of work and system design. ACM Trans. Office Inf. Syst. 1, 4 (Oct.), 320-328. Google ScholarGoogle Scholar
  48. SVIOKLA, J.J. 1990. An examination of the impact of expert systems on the firm: The case of XCON. MIS Q. 14, 2 (June), 126-140. Google ScholarGoogle Scholar
  49. SWANSON, E. B. AND BEAT~{, C.M. 1989. Maintaining Information Sysems ~n Organizations. John Wiley and Sons, Chichester, England. Google ScholarGoogle Scholar
  50. TODD, P. AND BENBASAT, I. 1987. Process tracing methods in decision support systems research: Exploring the black box. MIS Q. 11, 4 (Dec.), 492-512. Google ScholarGoogle Scholar
  51. WHITTEN, J., BENTLEY, L. D., ANn BARLOW, V.M. 1989. Systems Analysis and Design Methods, 2nd ed. Irwin, Homewood, Ill. Google ScholarGoogle Scholar

Index Terms

  1. Exceptions and exception handling in computerized information processes

              Recommendations

              Comments

              Login options

              Check if you have access through your login credentials or your institution to get full access on this article.

              Sign in

              Full Access

              PDF Format

              View or Download as a PDF file.

              PDF

              eReader

              View online with eReader.

              eReader