Bug Tracking System
-
Upload
harish-pawar -
Category
Documents
-
view
14 -
download
3
Transcript of Bug Tracking System
Bug tracking System
CONTENTS
1. ABSTRACT
2. INTRODUCTION
3. DESIGN PRINCIPLES & EXPLANATION
3.1. MODULES
3.2. MODULE DESCRIPTIOIN
4. PROJECT DICTIONARY
4.1. DATAFLOW DIAGRAMS
4.2. E-R DIAGRAMS
4.3. DATA DICTIONARY
5. FORMS & REPORTS
5.1. I/O SAMPLES
6. BIBILIOGRAPHY
1. ABSTRACT
Bug Tracking System is the system which enable to detect the
bugs. It not merely detects the bugs but provides the complete
information regarding bugs detected.
Bug Tracking System ensures the user of it who needs to know
about a provide information regarding the identified bug. Using this no
bug will be unfixed in the developed application.
The developer develops the project as per customer
requirements. In the testing phase the tester will identify the bugs.
Whenever the tester encounter ‘n’ number of bugs he adds the bug id
and information in the database.
The tester reports to both project manager and developer. The
bug details in the database table are accessible to both project
manager and developer.
2. INTRODUCTION
When a customer puts request or orders for a product to be
developed. The project manager is responsible for adding users to Bus
Tracking System and assigning projects to the users.
The project manager assigns projects to the developers. The
developer develops the projects as per customer requirements. The
project manager itself assigns the developed applications to the
“Testers” for testing. The tester tests the application and identify the
bugs in the application.
When the tester encounter ‘n’ no. of bugs, he generates a unique
id number for each individual bug. The bug information along with its
id are mailed to the project manager and developer. This is “Bug
Report”. These are stored in the database. This is useful for further
reference.
Bug information includes the bug id, bug name, bug priority,
project name, bug location, bug type.
This whole process continues until all the bugs are got fixed in
the application.
The bug report is mailed to the project manager and the
developer as soon as the bug is identified. This makes that no error
will go unfixed because of poor communication. It makes ensure that
anyone who needs to know about a bug can learn of it soon after it is
reported.
Bug Tracking System plays an vital role in the testing phase. But
it supports assigning projects for the developer, tester by the project
manager. The Bug Tracking System maintains the different users
separately i.e., it provides separate environments for project manager,
developer and tester.
The users of Bug Tracking System:
Project Manager
Developer
Tester
Existing System:
In the existing system, the project manager assigns the projects
to the developers. The developers develop the projects as per
customer requirements. The project manager itself assign the
developed applications to the tester for testing. In the testing phase,
when the tester encounters no. of bugs then he reports to the project
manager and developer about the bug information.
Bottlenecks of the Existing System:
The tester report which is called “Bug Report” is in the form of
physical document. If the document is damaged then the total
information about the bug will be lost.
The bug information is not stored in the database for future
reference.
Proposed System:
The purpose of the Bug Tracking System is to test the application
for the bugs and report it to the project manager and developer. The
main intention behind the Bug Tracking System is that to track bugs
and report them. Store the bug information with a unique id in the
database for future reference. So, this makes the job of handling the
bugs easy.
Objectives of the Bug Tracking System:
The main objectives of the Bug Tracking System are:
Identifying the bugs in the developed application.
No bug will be unfixed in the developed application.
Not merely identifying the bugs but also providing the bug
information.
As soon as the bugs are identified. They are reported to the
project manager and developer.
To ensure that who needs to know about the bug can learn
soon after it is reported.
3. DESIGN PRINCIPLES & EXPLANATION
3.1. MODULES
The main goal of this project is to store bug information by giving
unique id for each bug in the database. This will be used for future
reference while the same bug arises. The project has the following
modules:
Project Manager
Developer
Tester
3.2. MODULE DESCRIPTIOIN
Project Manager:
The project manager has the options to access user information,
project information, assign information, report, self details.
User Information:
The project manager will access the user information. In this
the, the project manager can
Add user details into the database.
Delete user from the database.
Modifying the existing user.
Project Information:
The project manager will access the project information. In this,
the project manager can
Add the project into the database by gathering the
information like project name, status, project id, description.
Delete project from the database by specifying the project
name.
Modify the project details by specifying the project name.
Assign Information:
This can be accessed by the project manager to assign the
projects to the other users like developer, tester. Assign information
has the following options like view, assign and project. The project
manager can
View all the projects.
Assign the projects to the developer and tester by gathering
the information like user name, project id, assigned date,
date of completion.
Search a particular project details by specifying
corresponding project id.
Report:
This is used to view the bug report after specifying the project id.
Self:
This option is used to view the self details. It has option to
change password. This gathers the information like old password, new
password. This makes to store the changed password to the database.
Developer:
The developer has an option to view projects and self details.
View Project:
This option will make the developer to view all his assigned
projects. It displays the project name, project id, assigned date,
expected date of completion.
Self:
This option is used to view the self details. It has option to
change password. This gathers the information like old password, new
password. This makes to store the changed password to the database.
Tester:
The tester has to track bugs in the assigned projects and to view
his projects, self details.
Assigned Projects:
This makes the tester to view the assigned projects and track
bugs in the assigned projects. In this option, the tester can
View the assigned projects to him by specifying the user id and
password.
Track the bugs. It pop ups a window which takes the details of
project id. When the track is clicked the bugs are tracked.
Different test cases are also selected for better test.
Add the bug information along with bug id, project id, bug type,
location
Mail the bug id and some other details regarding the bug to the
project manager and developer.
Self:
This option is used to view the self details. It has option to
change password. This gathers the information like old password, new
password. This makes to store the changed password to the database.
4. PROJECT DICTIONARY
4.1. DATAFLOW DIAGRAMS
A Data Flow Diagram (DFD) is a graphical technique that depicts
information flow and the transforms that are applied as data move
from input to output.
Data flow diagram is a logical model of a system. The model
does not depend on hardware, software, and data structure or file
organization. It only shows the data flow between modules to module
of the entire system. Data flow diagrams can be completed using only
four notations as follows,
Data Flow: Data move in a specific direction from an origin to
destination. The data flow is a “packet” of data.
Process: People, procedures or devices that produce data. The
physical component is not identified.
Source or Destination of Data: External sources or destinations of data,
which may be people or organizations or other entities.
Data Source: Here a process references the data in the system
CONTEXT LEVEL DIAGRAM
Fig.5.1 Context Level DFD for BTS
BTS
Tester
Project manager
Developer
User LoginProcess
Login reject
D1 User info infoinfoinfo
Project manager
Developer
Tester
A1
Pass
Fail
A1: User id, Password, Designation
Fig.5.2 First Level DFD for BTS
User info
Fig 5.3 2nd Level DFD for Project Manager
Project manager
Project info
Assign info
Changepassword D1 User info
New Password
DisplayBug report
D4 Bug info
Bug id
Fig 5.4 2nd Level DFD for Developer
Developer
DisplayAssigned
DisplayBug info
D4 Bug info D1 User info
Details Bug id
ChangePassword
D2 Assign info
A2: Bug id, Details
Fig 5.5 2nd Level DFD for Tester
Tester
Track Bugs
D4 Bug infoD1 User info
View Assign projects
D2 Assign info
ChangePassword
A2 New Password
Fig 5.6 3rd Level DFD for Project Manager
User info
Add user Delete User
D 1 User infoUser details
User id User Details
Modify User
Fig 5.7 3rd Level DFD for Project Manager
AddProject
DeleteProject
Modify Project
Project Details
Projectid Project
Details Project info
Project info
Fig 5.8 3rd Level for Project Manager
5. FORMS & REPORTS
5.1. I/O SAMPLES
Assign info
Assigning Projects
Display Projects
D3 Assign info
D2 Project info
6. BIBILIOGRAPHY
J2EE Complete Reference.
Java Server Pages -------Subrahmanyam
Alamaraju.