- 1 Ahituv, N., Neumann, S., and Riley, H. Principles oflnj~rmation Systemsj~r Management. 4th ed. Brown Communications, Inc., Dubuque, Iowa. 1994.]] Google ScholarDigital Library
- 2 Barki, H., Rivard, S., and Talbot, J. Towards assessment of software development risk. J. Manage. Inf. Syst. 10, 2 (Fall 1993), 203-225.]] Google ScholarDigital Library
- 3 Boehm, B. Software Engineering Economics. Prentice-Hall, Englewood Cliffs, N.J., 1981.]] Google ScholarDigital Library
- 4 Boehm, B. A spiral model of software development and enhancement. Comput. 21, 5 (May 1988), 61-72.]] Google ScholarDigital Library
- 5 DuBrin, A., Ireland, R., and Williams, J. Organization and Management. South-Western Publishing Co., Cincinnati, Ohio, 1989.]]Google Scholar
- 6 Frantz, D. $80-million failure: B of A's plans for computer don't add up. LosAnge/es Times, Feb. 7, 1988, D1-D3.]]Google Scholar
- 7 McCracken, D., and Jackson, M. Life-cycle concepts considered harmful. ACM Software Eng. Notes (Apr. 1982), 29-32.]] Google ScholarDigital Library
- 8 McFarlan, F. Portfolio approach to information systems. Harvard Bus. Rev. 59, (Sept.-Oct. 1981), 17-25.]]Google Scholar
- 9 Ozz, E. When professional standards are lax: The CONFIRM failure and its lessons. Commun. ACM 37, 10 (Oct. 1994), 29-36.]] Google ScholarDigital Library
- 10 Robey, D., and Sales, C. Designing Organizations. 4th ed. Irwin, Chicago, II1., 1994.]]Google Scholar
- 11 Rothfeder, J. It's late, costly, incompetent, but try firing a computer system. Business Week (Nov. 7, 1988), 86-89.]]Google Scholar
- 12 Zwass, V. Management Inj~rmation Systems. Brown Communications, Inc., Dubuque, Iowa, 1992.]] Google ScholarDigital Library
Index Terms
- Top management toolbox for managing corporate IT
Comments