BRTS - Online Help

Help

BRTS is a support tool for any application development and testing department. Using this tool you can efficiently report, update and track bugs. The system also maintains a history of all the bugs reported. Each registered user can maintain his/her specific information related to bugs and their history. If an organization or group of people want to use this tool for bug reporting, updation and tracking they can create a company/group specific login and make it available to all its members who want to report and track bugs. The following is a brief text on the terminology used in the BRTS system. You can also select one of the following links for quick access.

User Authentication
Terminology Reference
1. Project
2. Module
3. Bug Tools
4. Phases (Customize)
5. Priorities (Customize)
6. Status (Customize)

User Authentication

BRTS services are available for registered users only. Most of the options, require user authentication, i.e, you have to enter user-id and password before you can access any of the system tools. Once you have logged in, you can access any page without the need to login again.

How do you login?
There are two ways in which you can login to the system.

Using explicit Login at the top of the page brings you the login page.
Whenever you select any of the menu options and if you are not already logged-in system brings you "Access Denied" page where you have links for Logging-in.

Project

Is an application you want to trace for bugs. To do any of the operations in BRTS you need to have atleast one project for working. With every project you can store its title and the URL for the project. URL information is optional.

Module

To report and handle the bugs more easily, every project is divided into modules. You need to have atleast one module for a project to report a bug. A single project can have any number of modules in it. A module contains no other information except its description.

Bug Tools

Bug tools are the heart of BRTS system. It allows you to define a new bugs, view all bugs, update bugs and view history of bugs.

Phases

A Phase defines the stage of an application development. When you a report a bug for a project under a particular module, you can specify at what stage of the project did you find the bug. Typically the entries would be like - Design phase, Coding phase, Testing phase etc.

IMPORTANT Usually most of the projects/applications, undergo FIVE phases. They are Analysis, Design, Implementation, Maintainance and Testing. For this reason, every user gets these phases into his database by default. You need not create them again. However, you can create new phases of your own.

Priorities

Priority defines the effectness of the bug reported. All the bugs reported need not be of the same priority. Based on the impact/seriouness of the bug on the application, you can select the priority of the bug. This segregation helps the programmers to focus more on the "Critical" bugs. Also, the history of bugs on the priority basis helps to analyse the skills of programmers by checking relative scores of types of bugs found.

IMPORTANT For any kind of project/application, there are 4 priorities which are very much obvious for any bugs. They are Critical, High, Normal and Low. For this reason, every user gets these priorities into his database by default. You need not create them again. However, you can create new priorities of your own.

Status

A bug reported goes through a life cycle. Status defines the state of the bug after which it is fixed. Typically the entries would be like - Open, Fixed, Closed, Reopen, Wrong Usage, Work around available etc. It is one of the main analysing tools of the system. You can keep track of the bug for the states' it went through. Note that, a bug can be reopened even after it is closed.

IMPORTANT Usually a bug reported will be in one of the following eight states - Open, Fixed, Closed, Works as designed, Work around available, Wrong usage, New functionality and Reopen. It is for this reason, every user gets these status values, into his database by default. You need not create them again. However, you can create new status values of your own.