TROUBLE REPORT HANDLING SYSTEM ABSTRACT This project is used to store the trouble report or bugs occurred during

testing activity or actual usage of the project execution at the customer location. Managing trouble reports is the biggest challenge during project execution. Often many projects will be delivered to the customers by ignoring critical troubles identified during testing. CMMI practices mandate the usage of proper trouble report management during project execution. PURPOSE OF THE PROJECT: Trouble report or bugs will be identified during testing activity or actual usage of the project execution at the customer location. All the troubles should be resolved to make the application run in perfect way. To better management of trouble report handling all the identified trouble should be categorized as priority A, priority B, priority C. Development team working on these troubles should be resolved within the timeliness they find for each category of the priority levels. 1 .The criticality of the priority A is high. 2 .The criticality of the priority B is medium. 3 .The criticality of the priority C is low. Modules: This project contains four modules. 1. 2. 3. 4. Administrator Development Manager Developer Tester.

Life cycle of trouble report system: When a user/tester identifies a trouble it should provide a details like title of a trouble, description priority level, software name, software version and any required

log information related to the trouble. When the user submits the trouble report the state of the trouble will be in submitted the development team gets the notification about the trouble, the development team should accept the trouble report status to open. Then the development team should assign this trouble report to a developer and the trouble report status should be changed into assigned. The developer will analyze the trouble and identifies the route cost and proposed solution should be informed to the person who raised this trouble report now the status should be changed to propose. When the user/tester agrees the solution the status should be changed to accepted. Once the developer provides the solution the status should be changed to resolved. Once the user/tester verifies the solution in the next release of the software the status should be changed to accept and development team close the trouble report. This system should also provide some reports like specified priority trouble reports, list of resolved, accepted, proposed trouble reports, trouble reports resolved during month, trouble reports opened during this month. ADVANTAGES: Benefits of trouble reporting handling system is: It stores the troubles/bugs which are identified during testing at SDLC. It also stores troubles/bugs which are occurred at maintenance.

SYSTEM REQUIREMENT SPECIFICATIONS: Hardware Requirements Pentium IV 500 MHz 512 MB RAM 500 MB Free Hard disk space Color Monitor

Software Requirements Java 2 platform (J2SE 1.6) Jsp, Servlets Tomcat 6.0 My SQL 5.0 Windows XP.

Plan for Accomplishment: The system to develop will be dealt across the following stages: 1. Analysis Study of the requirement and collection of raw data. 2. Design Prepare the logical design diagrammatically to propose a solution. 3. Implementation Develop the application using the framework. 4. Testing Test the implementation. The implementation since uses the framework, it involves the OOPS methodology. A bottom up approach is used for the solution. The application revolves in the prototype model.