CASE Planning and the Software Process

Abstract

Automating a software process magnifies its strengths and accentuates its weaknesses. Automation can make an effective process more effective, but it can also 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 such tools are obtained as part of a thoughtful software process improvement plan, the purchase could be an expensive mistake. This article discusses software process maturity and its relationship to planning and installing computer-aided software engineering (CASE) systems. Although 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. Because 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.

¹This material is based in part on material from, Watts S. Humphrey, Managing the Software Process, Addison-Wesley, Reading, MA, © 1989. Reprinted with permission.

²This was sponsored by the U.S. Department of Defense. The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange.