Tailoring the process model for maintenance and reengineering

Emerging technology, aging software, and an influx of new software requirements cause many organizations to be inundated with maintenance projects. New software engineered using a mature process model, theoretically, is maintainable with the same process model. Legacy software, not engineered using a process model, is maintained using various approaches. The article introduces a practical maintenance approach, called configuration impact analysis, for rapidly planning and performing maintenance of both legacy and engineered software. This plausible maintenance approach produces a plan consistent with a mature development process model. The intended use of this approach is to maintain software without degrading its quality