Supporting software nearing the end of its life-cycle

Addresses the question of how it is possible to plan to provide support for a system which will have little or no new development, but is used frequently by the end customer. The areas addressed are: maintaining system expertise after the original design and development staff have rotated to new job positions; developing usable documentation for both the product and the process used to produce it; and standardizing the development process. The successful methods developed by the authors as well as the benefits achieved by following the plan are discussed.<
>