Assessing CASE: A Manager’s Perspective

While CASE can mean different things  to different people, we need to decide on a definition that will help to explain how CASE tools are used and how they can be evaluated. For this purpose, we will define Computer Aided Software Engineering (CASE) as: The automation of software engineering principles and methodologies to the development of computer software. This generally (but not always) involves structured diagramming tools, prototyping, data definition and diagram syntax checking. Different CASE tools attempt to address different phases or steps in the SDLC and some CASE tools try to address all the phases. Likewise, some CASE tools work only with a single methodology while others try to support many different methodologies.

This paper will enable you to:
– Understand the technology behind CASE
– Understand your own development environment
– Understand the potential benefits and drawbacks to using CASE
– Determine if CASE might help and where it could be best applied
– Identify potential CASE products/techniques
– Sell the organization on CASE
– Develop and implement a transition plan for CASE

ESC_1991_Vol2_Page452_Topper – Assessing CASE- A Manager’s Perspective.pdf

1 thought on “Assessing CASE: A Manager’s Perspective

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.