Delivering high level of software quality has become a major problem area for software development companies. The tough market competition poses an imposing task of delivering on time, high quality software with sound functionality. Bugs infiltrate into software due to software complexities, programming errors, changing requirements and time pressures. To solve the critical issue of maintaining quality, you have to carry out the task of finding and fixing the bugs in your software. The programmer's awareness of the software leads to disastrous oversights; as a result programmers cannot spot the bug in their own code. The cost of fixing the bug after the software is frozen, is huge. Testing is also carried out by pushing the software beyond its

threshold and finding out how the software reacts to such stress. The need for standardized means of nabbing and fixing the bug is a primary requirement. The ZSL bug tracker is an easy to use product with an effective web browser interface. Its clarity reduces the time and money involved in training your staffs on the product. It provides a helpful hand in your pursuit of delivering high quality- productive software. The bug is tracked right from the minute it is posted till error correction is done.

The salient features of Bug Tracker are

1. Bug entry
2. Assigns a bug to a developer
3. Revokes bugs
4. Shows history of the bugs
5. Categorizes bugs according to complexities and types
6. Maintains Developer/Tester details, Test cases, modules and project details
7. Generates robust reports with minimum details
8. Sets screen rights and Project links to developers/Testers

Process of a bug tracker
A project will have modules and screens. Testers enter a set of test cases with expected output criteria. These test cases can be assigned to any project’s module or screen. Checking is carried out to find whether the expected results match the actual results. If there is a failure in match then bugs are found. The identified bugs are posted on the bug tracker system along with the following details

1. Description
2. Type
3. Complexity
4. Suggestions for rectification

The bugs posted are assigned to the developers. The process of checking for the bug again after correction is done by the testing team and if the actual and the expected match, the status of the bug is changed to “completed”. A bug once assigned can be revoked and assigned to another developer. A developer can be assigned any number of bugs. A test case can be assigned to any project’s module or screen.

Benefits

1. Bugs of multiple projects can be maintained.
2. Security based on users screen rights and project links.
3. Extensive reports with minimum details.
4. Provides the summary and history of a bug with just a click.
5. Quick and easy understanding and maintenance.
6. Guarantees accountability, for a bug as the details of the users are also maintained.
7. Enables you in specifying the bug types, complexities, modules, screen and test case at project levels.
8. Multiple language support is available.
9. Flexibility in assigning bugs – All bugs except the ones suspended can be revoked and assigned to another developer at any point of time.
10. Test cases are consolidated.