This Article 
 Bibliographic References 
 Add to: 
Maintenance-Oriented Design and Development: A Case Study
July/August 2002 (vol. 19 no. 4)
pp. 100-106

It is a general consensus that maintenance efforts are the most time and resource consuming of the entire software development process. Maintenance is regarded as the last, and least rewarding, step of software development. We propose a different point of view wherein we shift from the traditional perspective and think of the implementation stage as maintenance as well. This means viewing software development as design followed by maintenance; don't design what will be implemented, but what will be maintained.We present this perspective through an experience in the development of educational video games for children. We use this example to compare both traditional and maintenance-oriented processes, determining the proposed method's benefits and drawbacks in the video game domain. We present and analyze two tools in which the concept of a specific computer-aided software engineering tool (SCASE) is present. These are tools that were designed with maintenance specifically in mind.We conclude that taking into consideration the importance of maintenance, as well as focusing the development process toward it, is a great boon toward the development of software projects that are successful, on time, and on budget.

Index Terms:
Software maintenance, software development, CASE, video game development.
José Pablo Zagal, Raúl Santelices Ahués, Miguel Nussbaum Voehl, "Maintenance-Oriented Design and Development: A Case Study," IEEE Software, vol. 19, no. 4, pp. 100-106, July-Aug. 2002, doi:10.1109/MS.2002.1020296
Usage of this product signifies your acceptance of the Terms of Use.