23-12-2009, 10:14 AM
1. ABSTRACT
Bug Tracking System is the system which enable to detect the bugs. It not merely detects the bugs but provides the complete information regarding bugs detected.
Bug Tracking System ensures the user of it who needs to know about a provide information regarding the identified bug. Using this no bug will be unfixed in the developed application.
The developer develops the project as per customer requirements. In the testing phase the tester will identify the bugs. Whenever the tester encounter Ëœnâ„¢ number of bugs he adds the bug id and information in the database.
The tester reports to both project manager and developer. The bug details in the database table are accessible to both project manager and developer.
When a customer puts request or orders for a product to be developed. The project manager is responsible for adding users to Bus Tracking System and assigning projects to the users.
The project manager assigns projects to the developers. The developer develops the projects as per customer requirements. The project manager itself assigns the developed applications to the Testers for testing. The tester tests the application and identify the bugs in the application.
When the tester encounter Ëœnâ„¢ no. of bugs, he generates a unique id number for each individual bug. The bug information along with its id are mailed to the project manager and developer. This is Bug Report. These are stored in the database. This is useful for further reference.
Bug information includes the bug id, bug name, bug priority, project name, bug location, bug type.
This whole process continues until all the bugs are got fixed in the application.
The bug report is mailed to the project manager and the developer as soon as the bug is identified. This makes that no error will go unfixed because of poor communication. It makes ensure that anyone who needs to know about a bug can learn of it soon after it is reported.
Bug Tracking System plays an vital role in the testing phase. But it supports assigning projects for the developer, tester by the project manager. The Bug Tracking System maintains the different users separately i.e., it provides separate environments for project manager, developer and tester.
Existing System:
In the existing system, the project manager assigns the projects to the developers. The developers develops the projects as per customer requirements. The project manager itself assign the developed applications to the tester for testing. In the testing phase, when the tester encounters no. of bugs then he reports to the project manager and developer about the bug information.
Bottlenecks of the Existing System:
The tester report which is called Bug Report is in the form of physical document. If the document is damaged then the total information about the bug will be lost.
The bug information is not stored in the database for future reference.
Proposed System:
The purpose of the Bug Tracking System is to test the application for the bugs and report it to the project manager and developer. The main intention behind the Bug Tracking System is that to track bugs and report them. Store the bug information with a unique id in the database for future reference. So, this makes the job of handling the bugs easy.
Objectives of the Bug Tracking System:
The main objectives of the Bug Tracking System are:
Identifying the bugs in the developed application.
No bug will be unfixed in the developed application.
Not merely identifying the bugs but also providing the bug information.
As soon as the bugs are identified. They are reported to the project manager and developer.
To ensure that who needs to know about the bug can learn soon after it is reported.
Bug Tracking System is the system which enable to detect the bugs. It not merely detects the bugs but provides the complete information regarding bugs detected.
Bug Tracking System ensures the user of it who needs to know about a provide information regarding the identified bug. Using this no bug will be unfixed in the developed application.
The developer develops the project as per customer requirements. In the testing phase the tester will identify the bugs. Whenever the tester encounter Ëœnâ„¢ number of bugs he adds the bug id and information in the database.
The tester reports to both project manager and developer. The bug details in the database table are accessible to both project manager and developer.
When a customer puts request or orders for a product to be developed. The project manager is responsible for adding users to Bus Tracking System and assigning projects to the users.
The project manager assigns projects to the developers. The developer develops the projects as per customer requirements. The project manager itself assigns the developed applications to the Testers for testing. The tester tests the application and identify the bugs in the application.
When the tester encounter Ëœnâ„¢ no. of bugs, he generates a unique id number for each individual bug. The bug information along with its id are mailed to the project manager and developer. This is Bug Report. These are stored in the database. This is useful for further reference.
Bug information includes the bug id, bug name, bug priority, project name, bug location, bug type.
This whole process continues until all the bugs are got fixed in the application.
The bug report is mailed to the project manager and the developer as soon as the bug is identified. This makes that no error will go unfixed because of poor communication. It makes ensure that anyone who needs to know about a bug can learn of it soon after it is reported.
Bug Tracking System plays an vital role in the testing phase. But it supports assigning projects for the developer, tester by the project manager. The Bug Tracking System maintains the different users separately i.e., it provides separate environments for project manager, developer and tester.
Existing System:
In the existing system, the project manager assigns the projects to the developers. The developers develops the projects as per customer requirements. The project manager itself assign the developed applications to the tester for testing. In the testing phase, when the tester encounters no. of bugs then he reports to the project manager and developer about the bug information.
Bottlenecks of the Existing System:
The tester report which is called Bug Report is in the form of physical document. If the document is damaged then the total information about the bug will be lost.
The bug information is not stored in the database for future reference.
Proposed System:
The purpose of the Bug Tracking System is to test the application for the bugs and report it to the project manager and developer. The main intention behind the Bug Tracking System is that to track bugs and report them. Store the bug information with a unique id in the database for future reference. So, this makes the job of handling the bugs easy.
Objectives of the Bug Tracking System:
The main objectives of the Bug Tracking System are:
Identifying the bugs in the developed application.
No bug will be unfixed in the developed application.
Not merely identifying the bugs but also providing the bug information.
As soon as the bugs are identified. They are reported to the project manager and developer.
To ensure that who needs to know about the bug can learn soon after it is reported.