Content area
Abstract
Since the late 1980's CASE ("Computer-Aided Software Engineering") is a common concept in the world of information technology. Nevertheless, many people in the information technology environment do not know what CASE is, or have different concepts about CASE. The author also found a variety of definitions for CASE in literature. This variety of concepts and definitions was the first problem the author investigated.
Although many people know about CASE, companies are slow in adopting CASE and the tools are not used to their full potential. This was the second problem the author investigated.
To address these problems, the research is divided in two logical parts.
The author initiated this study with literature research regarding CASE in which the above mentioned problems were identified. The author found the solution to the first problem in literature and by attending CASE conferences.
Guidelines to help with the second problem was derived from bits and pieces of information found in literature regarding the installation and use of CASE tools. It was also derived from practical experience during the last six months of study at a company busy with the installation of a CASE tool.
To address the first problem, the different aspects surrounding CASE was investigated. The author tried to provide answers to the following questions: What is CASE? What is the logical components and functions of CASE? How can CASE be classified? CASE and integration - what is the difference between CASE, I-CASE and IPSE? Where does CASE fit in the software environment? In the last chapter of this first part, AD/Cycle from IBM (ISM in South Africa) is discussed as an industry standard for the CASE environment.
To address the second problem, the author proposed a methodology covering the initiation phase to the maintenance phase of the implementation of CASE tools in a company.
The methodology consists of four phases, namely, initiation, evaluation and selection, installation and training, and maintenance. In the initiation phase, the use of CASE tools to solve system development problems like the system backlog, bad productivity and poor system quality, are initiated. In the evaluation and selection phase, the different vendors and products on the market are evaluated against the needs of the company. The product which was the best suited for those needs was selected and acquired. In the installation and training phase, that product was installed in the information technology environment and the people were trained in using the product to implement their system development tasks. In the maintenance phase, the information technology environment is regularly investigated to see if the CASE tool is the solution to the problem and to satisfy the system development needs.
This research, especially the second part, is directed to the industry and the author hopes that it will be of great help to everyone struggling with the above mentioned problems.
