Computer Aided Software Engineering (CASE) is the technology for automating software development and maintenance. This book, by one of the acknowledged experts on the subject, offers a very practical answer to the 25-year-old software crisis. Case technology is not at all that new, as it builds upon the structured techniques developed by Ed Yourdon, James Martin, Tom DeMarco and others in the 1970s. Many of the structured methodologies they fostered are enabled by CASE.

Computer Aided Software Engineering (CASE) tools typically support individual users in the automation of a set of tasks within a software development process. Such tools have helped organizations in their efforts to develop better software within budget and time constraints. However, many organizations are failing to take full advantage of CASE technology as they struggle to make coordinated use of collections of tools, often obtained at different times from different vendors. This book provides an in-depth analysis of the CASE tool integration problem, and describes practical approaches that can be used with current CASE technology to help your organization take greater advantage of integrated CASE.

Automating a software process both magnifies its strengths and accentuates its weaknesses. Automation can make an effective process more effective, but it can make a chaotic process even worse and at considerable expense. Anyone who buys expensive tools to solve an ill-defined problem is likely to be disappointed. Unless procurring such tools is part of a thoughtful software process improvement plan, the purchase could be an expensive mistake. This report discusses software process maturity and its relationship to planning and installing computer-aided software engineering (CASE) systems. While process is not a magic answer (there isn't one), the key issues are discussed from a process perspective, and guidelines are given for avoiding the most common pitfalls. Since CASE systems can involve significant investment, an economic justification may be necessary. The relevant financial considerations are therefore discussed, and some basic steps for producing such justifications are outlined. Finally, some key considerations for introducing and using CASE systems are discussed. (kt).

This paper makes the business case for automating the collection ofsoftware metrics for gauging development performance in integratedcomputer aided software engineering (CASE) environments that arecharacterized by an object-oriented development methodology and acentralized repository. The automation of function point analysisis discussed in the context of such an integrated CASE environment(ICE). We also discuss new metrics that describe three differentdimensions of code reuse -- leverage, value and classification --and examine the p,ossibility of utilizing objects as means toestimate software development labor and measure productivity. Weargue that the automated collection of these software metrics opensup new avenues for refining the management of software developmentprojects and controlling stra-egic costs.