Defect tracking system is a web application which is used by most Software Companies to track Defects or Bugs or issues in their developing software applications. Defect Tracking System is also called as Bug Reporting System. This application dramatically increases the productivity of the team and improves the quality of the software application, product or solution developed. Software developers/Programmers and quality assurance team uses this application to effectively track any bug/defect or issues in their work.
Defect tracking systems are used by Software companies to generate project reports which also help to check the productivity of software developers at working and fixing defects. This application basically has 2 modules: front end and administrator module. Detailed descriptions of both the modules are mentioned below.
Front End (User Module): Software development team and quality assurance team has permissions to access this application. Their login authorization and registration is done by the administrator. Software development team has a different UI, permissions and quality assurance team has different UI and permissions. QA team or the testing team reports defects from the front end. An email notification is sent to the developer who worked on that build. Once the developer resolves the defect, logs into the application and enters his remarks and updates the defect status. An email notification is again sent to the tester to do a regression testing.
Administrator Module: Admin has all the privileges to add project, application content, add new user, authorized a new user, set permissions and export project reports. Administrator can also create a user as project manager and set permissions to generate project reports to him. In administrator module there can be many projects. And users will be linked to their respective projects only.
Defect Classification used in this project is:
- New: A new defect has been identified. (This status is given by testing team).
- Non-Reproducible: Defect exists but is identifiable some times. (This status is given by testing team).
- Open: The defect still exists. (This status is given by testing team).
- In Progress: Development team is working on the defect. Work is in progress.
- To be tested: This defect has to be tested. (This status is given by testing team).
- Closed: The defect does not exist now. Defect is closed. (This status is given by testing team & development team both).
- Rejected: This defect is not accepted by the developing team. As the developer tem believes that the build is developed as per the specification documents (SRS, FRS). (This status is given by developer team).
- Re-Open: The defect still exists, and development team has to work on it. (This status is given by testing team).
- Deferred: This defect can be worked later. (This status is given by development team).
- Show Stopper: This is a major defect in the build, needs to be resolved right away. A software build cannot be released with this defect.
- Critical: This defect affects the main functionality of the software and the QA team cannot test further or other functionalities of the software.
- Major: In this type of defects the major functionality of the application is not working but QA team is able to test the other functionalities.
- Minor: This type of defects affects the non critical data or minor requirement of the software. This defect does not damage the usability of the software.
- Highest: This type of defects will cause a big loss to clients business. This type of defects should be resolved as soon as possible.
- High: This type of defects needs attention.
- Medium: This type of defects affects only one functionality of the build and can be deferred to the next release.
- Low: This type of defects are deferred as they affect very little requirement of the software. And mostly resolved in later releases.
For more details you can comment or leave a reply below.