Abstract:
Difficulties that may be encountered, and how they can be avoided, by organizations intending to adopt CASE tools are addressed. An overview of the adoption process, incl...Show MoreScope:This recommended practice views the CASE adoption process as more than the selection of CASE tools. The CASE adoption process consists of the activities by which an organ...Show More
Purpose:The purpose of this recommended practice is to provide guidance that will enhance the probability of the successful adoption of CASE technology. The use of this recommend...Show More
Metadata
Abstract:
Difficulties that may be encountered, and how they can be avoided, by organizations intending to adopt CASE tools are addressed. An overview of the adoption process, including analysis of the organization's needs and readiness for automation, use of a pilot project, and definition of activities necessary to integrate the new technology into the organization's standard software engineering practice, is provided.
Scope:
This recommended practice views the CASE adoption process as more than the selection of CASE tools. The CASE adoption process consists of the activities by which an organization identifies appropriate CASE tools and related technologies and introduces them into general use. The steps of a successful CASE adoption process include the following: a) Defining CASE needs b) Evaluating and selecting CASE tools c) Conducting a pilot d) Fostering routine use of the tool A successful CASE adoption process is not limited solely to tool use. Rather, it embraces the planning and implementation of an entire set of technical, organizational, cultural, and management proce...
Purpose:
The purpose of this recommended practice is to provide guidance that will enhance the probability of the successful adoption of CASE technology. The use of this recommended practice will help maximize the return and minimize the risk of investing in CASE technology. Regardless of the reason for CASE adoption, it is important to recognize that CASE adoption is not amenable to a cookbook approach, which guarantees dramatic improvement in an organization’s software development and maintenance activities. Rather, the adoption process implemented should reflect the particular needs of the organization. In return, incremental improvements in the organization’s sof...
Date of Publication: 10 April 1996
Electronic ISBN:978-0-7381-0423-2
