ABSTRACT

Overview

Bug: means persistent error in software or hardeare.If the bug is in software it can be corrected
by changing the program. If the bug is in hardware new circuits’ have to be designed

Tracking: Means tracking reported bugs, defects business issues, enhancement requests.

Overview of Project:

Bug tracking system is a software application which is designed to help the quality assurance and
programmers to keep track of reported software bugs in their work. Bug tracking system is an automated
bug tracking system that provides automation of keeping track of product development and bug
processing.

The main task of this project is to keep track of bugs, developers working of bugs and bug life cycle from
submission of bug to bug resolution processes.

Existing System

In this existing system the bug are not properly maintained. In this existing system, the bugs are simply
relied on shared lists and mailed to monitor the bugs. In this type of system, it becomes difficult to track
the bug if the bug is over looked and it may cause tremendous errors in the next phase. The cost of the
project is increased in this type of system and the bug maintenance may not be worthy.

In this type of system there is no efficient search technology. One has to search the entire data base for
the details of the bug, it is time consuming and error prone. In this system, it is very difficult to share the
bug among several users as there is no proper maintenance of bugs.

Drawbacks in existing system:

1. In this system doesn’t maintain the bug details

2. Doesn’t maintain the history and life cycle.

3. We can’t maintain the bulk(log)amount of records

4. It is a time consuming process.

5. It is very difficult to share the bug among several users.

6. In this system there is no efficient technology

In proposed system have many advantages than existing system. In this type of system, we maintain the
bugs and bug tracking. It is having the advantage of maintaining of bug history. It stores all the details
from bug origin for the bug resolution.

In this system it would not be a difficult task to for the users to know how much effort to be spent on the
bug. The main advantage of this system is maintaining a log records which are helpful in knowing any
errors of the system by other users.

Process:

In this bug tracking system supports the concept of the lifecycle for a bug which is tracked through status
assigned to the bug. The tester is found the errors and bug reports send to the developer and project
manager. In this system maintain all the details about bug details and assignment details and this system
maintain the resolution details. The system should also allow administrator to configure the bug statuses.
When new records are added are the status changes, what status a bug in a particular status can be moved
some system will email interested parties, such as submitter and assigned to programmer.

The main benefit of the bug tracking system is to provide a clear centralized overview of development
requests and their state .The prioritized list of pending items provides valuable input when defining the
product roadmap or maybe just “the next release”. Bug tracking system as a part of integrated project
management system.

Advantages

1. Its maintain bulk(log) records

2. In this system maintain bug lifecycle, bug resolution details bug details

3. It is the time saving process

4. It is very easy to search record using some technologies like fossil, fogbugz,
fuzz etc.

5. It is also maintain bug history.

6. It is used to increased productivity and improved customer satisfaction.

• Bug tracking system modules are

1. Database administration

2. Security and administration

3. User interface
 1. Database administration

The major component of a bug tracking system is database records facts about known bugs. Facts may
include the time a bug was reported, its severity. The erroneous program behavior and details on how
reduce the bug as well as the identity of the person who reported if and any programmers who may be
working on fixing.

It is maintain the following details [functionalities]

 Product details

 Product version details

 Bug details

 Bug lifecycle

 Bug resolution details

 Bug assignment details

 User/developer details
2. Security and administration

In this module we can maintain the following details (functionalities)

 User logins

 Products

 Product version

 Task assignments

The administration provide the security for this system using user login that means it’s provide
user name and password for every developer, tester and project manager

Administrator as well as provide the security for product, product version and also maintain
configurations

Administrator is assigned to task for developer & tester and project manager

The bug tracking system should allow administrators to configure permission based on status,
more the bug to another status, and more the bug to another status and also allow administrator to
configure the bug statuses.

3. User Interface module

In this user interface system will be maintain interaction between user and system through the
forms or manual description

. Functionalities in user interface as follows.

 Login/logout

 Record insertion

 Record deletion

 Record editing

 Displaying various type summary

In this system net result tracker is a powerful easy to use web based collaboration tool to
help companies track business issues and automatically manage then through to resolution

In this module user easily interact to the system through forms the user login to the system
and his work will be completed using different forms (insert, delete, edit) logout from the
system
 Role and responsibilities:

Role: The roles are the people who involved in implementing the project following are the persons
involved in “Bug tracking system”.

1. Project manager

2. Tester

3. Developer

Responsibility: The responsibility of are the tasks that are performed by the roles of the project. The

Responsibilities of various roles involved in this system are.

1. project manager:

The responsibility of the project manager is to maintain the product (project) details,
tester/developer information, bug details, bug lifecycle, bug resolution details, bug assignment
details.

2. Tester

The responsibility of the tester is track the bugs and the bug details send to the developer and as
well as project manager.

3. Developer:

The responsibility of the developer is resolve bug and resolving details sends to the project
manager.

Functional requirements:

Functional requirements describe the interaction between the system and its implementation

The environment includes the user and any other external system with which the system interacts.

The function that are being performed and the requirements needed to smooth run the system are

The following.

Authentication:

Tester/developer username, password and designation in the login form and then the system will check
these details with already stored details. If he/she is the authorized person then it gives permission to
access the system. If not if redirects to error login form.

Bug management:

In this, we maintain the bug details, bug lifecycle, bug resolution details and we also maintain the bug
assignment details
 Product(project ) management:

In this, we maintain the products (projects) details and we also maintain the product (project) version
details.

Project manager management:

In this, project manager maintain the all the details about product and bug details and he/she also
maintain the tester/developer information.

Tester management:

In this, we maintain the tester details and we also maintain bug tracking details.

Developer management:

In this, we maintain developer details and we also maintain the bug assignment, bug resolution details.

Nonfictional requirements:

Non functional requirements describe user visible aspects of the system that are not directly to the
functional behavior of the system that are not directly to the functional behavior of the system,
nonfunctional requirements can be elicited by investigating the following issue.

User interface & human factors:

The user interface and is a graphical user interface when the tester/project manager/developer
clicks buttons, select the project, uses the mouse or perform any relate action, and interface event occurs.

A little training for the user to system is needed a preliminary user manual with all user
commands, screen formats. An explanation is giving how to feedback and error messages.

Documentation:

User (tester/developer) level documentation is providing in this system. This will guide
tester/developer/project manager in driving the system in a perfect manner. There is no needing specify
technical documentation for user.

Hardware considerations:

We need following hardware minimum requirements processor

• RAM

• Hard disk

• CD/DVD

Software consideration:

• Front-end
 • Back-end

Quality issues:

The quality issue of the system or project depends on how reliable/available/robust should be the
system. Our system ensures these quality factors by maintaining a lot of validation check and it can be
suited for any platform.

The project manager/administrator can enter product (project) details, bug details ,bug lifecycle,

Bug resolution details etc we disabled master data entry for the logins of the tester/developer.

Resource issue:

The developer should take concern about resource utilization issues. The resource such as hardware
printer, ups etc must be used.

USECASSES

Use case name : Authentication

Participating actors : project manager/tester/developer

Entry condition : when the (system) project manager need to be authenticated

Flow events : 1. Project manager/developer/testers the login name, password and designation

: 2. The system checks the project manager, tester, developer details

: 3. If the system operator details are correct, the system will give permission to

To the operator for further processing.

: 4. If the project manager/tester/developer is wrong, then the system didn’t

Give permission to the operator for further processing and acknowledges

About the invalid data.

Existing system : Getting the permission for further processing.

Quality requirements : The process has to be completed within a minimum time

Use cases name : Tester page (manage)

Participating actors : Tester

Entry condition