Miren Begoña Albizuri-Romero
Abstract
This paper provides a retrospective view of the adoption of CASE tools in organizations using some empirical data from various research studies in this field. First, relevant factors that influence the decision to adopt such a tool are discussed. Such factors include elements related to the organization adopting such a technology, as well as other characteristics associated with the application environment and the alternative development methods being used. Then, the advantages and disadvantages of using CASE tools are discussed and some critical success factors are identified. Finally, a taxonomy of CASE tools in the 90's is presented. The paper provides some explanations of why some organizations are successful in adopting CASE tools and gives recommendations for making a better use of such a technology.
- [1] Abi R. (1987): Systems Development Productivity: CAS Approach. Systems Development, vol.7, num. 11, November 1987, pp.4-17. Google Scholar
Digital Library
- [2] Bouldin B. (1987): Implementing CASE: From Strategy to Reality, Computer-world , November 9, 1987, p.518.Google Scholar
- [3] Burgehnan R. A. (1983): Corporate Entrepreneurship and Strategic Management Insights from a Process Study, Management Science, vol. 28, December 1983, pp. 1349-1364.Google ScholarDigital Library
- [4] Chifosky E. J. (1987): Reliability Engineering for Information Systems: The Emerging CASE Technology, Index Technology Corporation, Cambridge, Massachusetts, 1987.Google Scholar
- [5] Dart S. A., Ellison R. J., Feiller P. H. and Habermann A. N. (1987): Sollware Development Environments, Computer, vol. 20, num. 11, November 1987, pp. 18-28. Google ScholarDigital Library
- [6] Davis R. K. (1990): What the Real World is Saying About CASE, Chief Information Officer Journal, vol.2, num.3, Winter 1990.Google Scholar
- [7] Fuggetta A. (1993): A Classification of CASE Technology, IEEE Computer, December 1993, pp. 25-38. Google ScholarDigital Library
- [8] Hayley K. and Lyman H. T. (1990): The Realities of CASE, Journal of Information Systems Management, Summer 1990.Google ScholarCross Ref
- [9] Highsmith J. (1987): Software Design Methodologies in a Case World, Business Software Reviews, September 1987, pp.36-39.Google Scholar
- [10] Hughes C. T. and Clark J. D. (1990): The Stages of CASE Usage, Datamation, vol.36, num.3, February 1990.Google Scholar
- [11] Kull D. (1987): The Rough Road to Productivity, Computer Decisions, February 1987, pp. 30-41.Google Scholar
- [12] Martin C. F. (1988): Second-Generation CASE Tools: A Challenge to Vendors, IEEE Software, March 1988, pp. 46-49. Google ScholarDigital Library
- [13] McClure C. (1987): Software Automation, Business Software Review, September 1987, pp. 28-34.Google Scholar
- [14] McClure C. (1989): The CASE Experience, Byte Magazine, April 1989. Google ScholarDigital Library
- [15] Messenheimer S. and Weiszmann C. (1988): Quality Software Quest, Software Magazine, February 1988, pp.29-36.Google Scholar
- [16] Necco C. R., Gordon C. L. and Tsai N. W. (1987): Systems Analysis and Design: Current Practices, MIS Quaterly, December 1987, pp. 461-475. Google ScholarDigital Library
- [17] Orlikowski W. J. (1988): CASE Tools and the IS Workplace, Proceedings for the 1988 ACMSIGCPR Conference on the Management of Information Systems Personnel, College Park, Md, April 7-8 1988, pp. 88-97. Google ScholarDigital Library
- [18] Perrone G. (1988): Primary Product in the Development Life Cycle, Software Magazine, August 1988, pp.35-41.Google Scholar
- [19] Quinn J. B. (1985): Managing Innovation: Controlled Chaos, Harvard Business Review, July-August 1985, pp. 149-160.Google Scholar
- [20] Rinaldi D. (1987): Software Developers Mired in Maintenance, Software News, October 1987, pp. 75-76.Google Scholar
- [21] Rogers E. M. (1983): Diffusion of Innovations, New York: Free Press, 1983.Google Scholar
- [22] Russel F. (1989): The Case for CASE, ICL Technical Journal, vol. 6, issue 3, May 1989, pp. 479-495.Google Scholar
- [23] Snyders J. (1987): A CASE of Unknown Identity, Infosystems, October 1987, pp.55-59.Google Scholar
- [24] Summer M. and Sitek J. (1986): Structured Methodologies: Are They Being Used?, Journal of Systems Management, vol. 4, num.2, spring 1986.Google Scholar
- [25] Summer M. (1992): The Impact of computer-Assisted Software Engineering on Systems Development, IFIP Transactions, K. E. Kendall el. at. (Editors), 1992, pp. 43-60. Google ScholarDigital Library
- [26] Suydam W. (1987): CASE Makes Strides toward Automated Software Development, Computer Design, January 1987.Google Scholar
- [27] Yourdon E. (1989): Serious Case in the 90's: What Do We Do When the Novelty Wears Off?, Show CASE Conference IV, October 10 1989.Google Scholar
- [28] Zagorsky C. (1990): CASE Study: Managing the Change to CASE, Journal of Information Systems Management, summer 1990.Google ScholarCross Ref
Index Terms
- A retrospective view of CASE tools adoption
Recommendations
Adoption of Case Tools & UML: A Local Study
ICSIE '20: Proceedings of the 9th International Conference on Software and Information EngineeringThis research investigates the role of CASE tools in the software development process by considering importance of CASE in adopting a number of standards. A survey was conducted in six selected companies in Ankara in which semi-structured interviews are ...
CASE tools: understanding the reasons for non-use
Computer-Aided Software Engineering (CASE) technologies are tools that provide automated assistance for software development [3]. The goal of introducing CASE tools is the reduction of the time and cost of software development and the enhancement of the ...
Adoption of computer aided software engineering (CASE) technology: an innovation adoption perspective
Special double issue: diffusion of technological innovationThis study examines the impact of various organizational and technology characteristics on the adoption of computer aided software engineering (CASE) technology. Based on research in innovation adoption and IS implementation, the study develops a ...
Comments