“Bug Tracking mechanism” is employe only is some of the large software development houses. Most of the others never bothered with bug tracking at all, and instead. Simply relied on shared lists and email to monitor the status of defects. This procedure is error-prone and tends to cause those bugs judge least significant by developers to be drop or ignored.
The project can dramatically increase the productivity and accountability of individual employees by providing. A documented workflow and positive feedback for good performance. The main objective of this system is to develop flawless systems, which is access real-time information.
Another aim is that manage hundreds of projects in multiple locations or just a few. Another main objective of this system is to track all the defects or bugs in the project and make the project user-friendly. Eventually, this system maintains the products, Bugs and bug Tracking. It has the advantage of maintaining bug history it stores all the details from bug origin to bug resolution.
Firstly, Each product can have versions for easy maintenance of the product and all the user of the product is store in the database. Secondly, this system provides the searching based on status, priority, and operating system. It is provided with a fully authenticated system with password encryption. After that it will the facility for storing attachments for a bug. The most advantage of this system is maintaining log records which are helpful in knowing any errors or misuse of the system by other users.
This Project is an ideal solution to track the bugs of a product, solution or application. However, it Allows individual or groups of developers to keep track of outstanding bugs in their product effectively.
Diagrams Needed for this Project are:
- Data Flow
- ER Diagram
- Schema Diagram
- Use Case Diagram
