Computer-Aided Software Engineering (CASE) is a revolutionary technology that seeks to automate the software development process. Current literature reports on many successes of CASE adoption Despite of such successes, many organisations are experiencing difficulties in implementing CASE technology . Even many powerful CASE tools have become 'shelfware'. It is argued that the benefits of CASE are unlikely to be realised, unless it is introduced based on a sound implementation plan This article presents a conceptual model to introduce CASE technology within a MIS department Such a plan faciliiaus change in software culture and management practice and enables management to deal with confusion and skepticism prior to its occurrence. Furthermore, a case study is described that focuses on a CASE implementation that failed to achieve its purpose The reasons for the failure are critically examined and explained in the light of the model
