Fit for Change: Steps towards Effective Software Maintenance

This report describes experiences the authors made over a period of approximately 15 months in a software development and maintenance project in the banking area. It analyzes how the project team managed the transition from the development to the maintenance phase under rather difficult circumstances. The report starts with a description of the project analyzed and a diagnosis of the challenges the project team was facing during that transition period. Then, the measures taken by the project team are described and evaluated. The report concludes with a best practices section summarizing the experiences made.

[1]  Rudolf K. Keller,et al.  Program comprehension by visualization in contexts , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[2]  Carolyn Seaman,et al.  Practical Software Maintenance , 2000, J. Softw. Maintenance Res. Pract..

[3]  Ned Chapin,et al.  Types of software evolution and software maintenance , 2001, J. Softw. Maintenance Res. Pract..

[4]  Carolyn B. Seaman,et al.  Practical Software Maintenance , 2000, J. Softw. Maintenance Res. Pract..

[5]  S. Berner,et al.  Observations and lessons learned from automated testing , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

[6]  Keith H. Bennett,et al.  Software maintenance and evolution: a roadmap , 2000, ICSE '00.