Abstract

Using a case study, an attempt is made to compare traditional and maintenance-oriented processes. It is emphasized that accepting the importance of maintenance, and focusing the development process toward it, produces software projects that are successful, on time, and on budget.