Software maintenance is the continuous process of enhancing the operational life of software. The existing approaches to software maintenance, derived from the traditional approaches to development, are unable to resolve the problems of unstructured code, team morale, poor visibility of the project, lack of communication, and lack of proper test suites. Alternatively, extreme programming practices such as test driven development, refactoring, pair programming, continuous integration, small releases, and collective ownership help to resolve the aforesaid problems. In this paper, a process model is proposed for software maintenance using extreme programming practices to resolve maintenance issues in an improved manner. The proposed approach speeds up the maintenance process and produces more maintainable code with less effort for future maintenance and evolution. The proposed model is validated by applying it on several maintenance projects in an academic environment. It has been observed that the approach provides higher quality code. The proposed model based on extreme programming enhances both learning and productivity of the team by improving the morale, courage, and confidence of the team, which supports higher motivation during maintenance.

No abstract

Software maintenance is a complex and life long process due to unstructured code, team morale, poor visibility of the project, lack of communication techniques and lack of proper test suite. On the other hand extreme programming is an existing process of software development with its challenges practices. In this paper, we propose an iterative maintenance life cycle using extreme programming practices. It would be able to resolve software maintenance issues in the smooth manner. The proposed approach speedsup maintenance process with less effort and produces a more maintainable code for future maintenance and evolution.

No abstract

Most of the software maintenance processes are
mainly based on traditional software development process,
which uses traditional Software Change Request (SCR)
form as a requirement artifact. In this paper, we have
designed a requirement artifact Request for Change (RC)
story for software maintenance, which is based on extreme
programming and proposed RC story format validating
using case study of college portal. In order to find the
impact of RC story on software maintenance, we have
applied RC story on iterative maintenance life cycle using
extreme programming. RC story in software maintenance
process can help to resolve the problems of poor visibility of
the project and lack of communication in maintenance
process