Maintenance is crucial to ensure delivered software continues to meet its end users' evolving needs mainly among Web applications' users. Many approaches and tools have been developed for handling modification requests, of which is the first step of the change management process. However, they lack of functionality to facilitate end users to specify their requests. This limitation causes problems not only to the end users, but to the maintainers as well, who need to understand the requests thoroughly before making any changes. We propose a user-centered technique to support the maintenance process by managing and tracking the modification requests effectively. This paper reports the implementation of the proposed technique as a tool and includes its adoption on a Web application. Initial case study shows that the tool is able to support end users to specify their requests easily and quickly, and maintainers to handle the requests effectively.

Nowadays, a lot of development of Web applications use prototyping approach such as throw-away prototyping and evolutionary prototyping. In order to fulfill the users' requirements, developers need to communicate with the users, therefore prototyping is widely used in software development to assist these developers. As we develop Web application and release them as a number of versions or releases of prototype, it constantly requires changes to evolve and meet users' specific requirements. Thus, prototyping approach may cause more maintenance cost to be incurred due to scope creep during software development. In addition, it provides the challenges to a maintenance team who is mostly not the actual development team, to manage and track maintenance process of such Web applications. This paper proposes a user-centered technique for managing and tracking modification requests in a Web application. We anticipate that the proposed technique can assist maintainers to manage and track modification of a Web application in more effective and efficient manner by capturing, classifying and validating the enhancement requests, problem report and modification requests directly from the users during the prototyping process itself. This in turn will avoid unexpected modification requests once we release the Web application and to allow the tracing of both enhancement and problem report during prototyping and modification requests and problem report during maintenance.