This paper provides a conceptual and discussion framework for answering what the obstacles to diffusion of CASE-technology may be. CASE is viewed in a tool-external context and with focus on the negative aspects of CASEtechnology, as the goal is to discuss the obstacles to diffusion of CASE. The paper is mainly based on literature reviews and serves as a point of departure for further empirical research.
Application of CASE-tools has consequences for the individual work process of the systems developers and for the roles of the development team members. These consequences may cause resistance against the use of CASE-tools. Successful use of CASE-tools is also determined by the basic approach to development of software. Moreover CASE-tools influence the communication between developers and end-users. Increased quality of design and productivity of the development process depend on correctly understanding of the requirements, which reflects the quality of this communication.
An important condition of diffusion is solving of the so-called software crisis: lack of productivity and quality increases of software development. Productivity and quality increases necessitate efforts in the initial development phases and better support of the user-developer communication. These are areas, which are not seriously improved by the application of CASE-tools
