Bug XTracker Report

24

BugX Tracker 2012

CHAPTER 1INTRODUCTION

1.1 Overview:

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 identifies the bugs in the application.

When the tester encounters ‘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.

Computer Science & Engineering Ideal Institute of Technology, Ghaziabad

24

BugX Tracker 2012

The users of BugX Tracker:

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.


24

BugX Tracker 2012

CHAPTER 2

DESIGN PRINCIPLES & EXPLANATION

2.1 Modules

Project has following modules:

Administrator

Project Manager

Developer

Tester

2.2 Module Description

1. Administrator

Has option to access User info, Project info, Assign info, Report, Self details.

User Information :

Add User details into the database.

Delete User from the database.

Modify User details.

Project Information :

Add Project into database by gathering the information like Project name, project ID,

Status, Description.

Delete Project from the database by specifying the Project id.

Modify the project details by specifying the project id.


24

BugX Tracker 2012

Assign Information :

To assign Project to other users- like Project Manager, Developer, and Tester.

View all projects.

Assign Project to Project Manager, Developer, and Tester by gathering information

like user name, project id, and assigned date.

Search a particular project details by specifying Corresponding project id.

Report :

Used to shown the bug report after specifying the project id.

Self :

This option used to view self details.

Option is used to change password.

2. Project Manager

View Project, Users assigned to him & self details.

View Project :

Option to view all his assigned projects.

View User :

Option to view information of employees under him.

Report :

Used to view the bug report after specifying the project id.

Self :


Option to change password.


24

BugX Tracker 2012

3. Developer

View Project, Bugs & Self Details.

View Project :


View Bug :

Option to view all bugs corresponding to his assigned project.

Self :



4. Tester

View Project, Track Bugs & Self Details.

View Project :


Track Bug :

Tracks bug in his assigned project.

Add bug information along with bug id & project id.

Self :




24

BugX Tracker 2012

Chapter 3

SOFTWARE & HARDWARE REQUIREMENT

Hardware Requirement

Ram: 128 MB or higher

Processor: Pentium III or higher

Hard disk: 560 MB or higher

Software Requirement

Language: ASP.Net

Database: Oracle

PLATFORM: .NET FRAMEWORK

Application Server: Apache Tomcat

Web Browser: Google Chrome or Mozilla Firefox


24

BugX Tracker 2012

Chapter 4DEVELOPMENT ENVIRONMENT

Hardware Environment

The hardware environment that is employed in this project is a machine with

Intel Core i3 processor with processing speed of 2.30 GHz of processing speed, L2

cache and 3.00 GB of extended Memory.

Software Environment

.NET Framework 3.5

Apache Tomcat

Microsoft ASP.Net

Oracle tools

The machine that is employed to develop this project has a Windows7 Ultimate

Operating system with Google Chrome and Firefox. The user interface is created

with Hyper Text Markup Language (HTML) and the server side coding component

is JSP. The pages that are created are validated with the help of JavaScript.

Chapter 5


24

BugX Tracker 2012

REQUIREMENT SPECIFICATION

The Bug X Tracker System is not so complex but it requires a well defined

database system to manage & provide the retrieval of data like projects, users, bug

details, work in progress & so on.

The system has to manage the project bug life cycle i.e. submission of a bug,

assignment of bugs, resolution of bugs & so on.

In order to keep track of all these data & activities, the system has the following

requirements:

5.1. Database Requirement

Following are the required details that should be managed by the system:

User Details

Project Details

Bug Details

Bug Assignment Details

5.2. Security & Administration

The Bug Tracker should have a security system to restrict the user access & role

based security for administration the system resources like:

User Logins

Projects

Task Assignments


24

BugX Tracker 2012

5.3. User Interface

The System also requires an interactive User Interface to manage the data. The

interface must have the following features :

Login/Logout

Record Insertion

Record Modification

Record Deleting


User Login Process

Administrator

Project Manager

Developer

Tester

Pass

Login RejectFailsUserid,Password

Login_info1st Level DFD

24

BugX Tracker 2012

5.4. Design Documents

Based on the requirements discussed above, following are the initial design

documents:

5.4.1 Data Flow Diagram


Bug XTracker D

atab

ase

Context Level DFD

Admin

Project Manager

Developer

Tester

24

BugX Tracker 2012


Administrator

Bug id

User Info

Project Info

Assign Info

Change Password

Display Bug Report

Login_info

Bug_info

New Password

2nd Level DFD for Administrator

Project Manager

Bug id

View User Info

View Project Info

View Assign Info

Change Password

Display Bug Report

Login_info

Bug_info

New Password

Assign_info

Project

Login_info

2nd Level DFD for Project Manager

Developer

Display Assigned Display Bug Info Change Password

Assign_info Bug_info Login_info

DetailsBug id New password

2nd Level DFD for Developer

24

BugX Tracker 2012


Tester

View Assigned projects Track Bug & View Bug Change Password

Assign_info Bug_info Login_info

DetailsBug id New Password

2nd Level DFD for Tester

24

BugX Tracker 2012

5.4.2 APPLICATION USE CASES

User Login


24

BugX Tracker 2012

View Users


24

BugX Tracker 2012

Edit User

Delete User


24

BugX Tracker 2012

View Project

Edit Project


24

BugX Tracker 2012

Delete Project

View Project Assign Information

Edit Project Assign


24

BugX Tracker 2012

Delete Project Assigned Information

View Bug Information


24

BugX Tracker 2012

Create BUG

Delete Bug


24

BugX Tracker 2012

Change Password


24

BugX Tracker 2012

Chapter 6ADVANTAGES

In software test management, bug reporting is a complex and complicated

process that requires precision, detailing and a whole lot of information. Reporting

and tracking bugs manually works fine in case of small projects, whereas for mission-

critical or large projects, a paper-based approach can result in chaos and confusion.

QA test management teams need an effective defect tracking management system to

log the identified bugs and to monitor them. A bug-tracking system helps the project

team to successfully measure the project’s status. The measurements, also known as

metrics help the QA test management team to assess the quality of the software and in

taking business decisions. The software metrics like project metrics, progress metrics,

defect metrics and testing metrics also help in evaluating the success ratio of a tester

or programmer. A defect tracking system not only tracks defects but also tracks

metrics to make sure everything is going according to the software development plan.


24

BugX Tracker 2012

Chapter 7FEATURES

1. Product and Component based

2. Creating & Changing Bugs at ease

3. Reporting in more comprehensive way

4. User Accounts to control the access and maintain security

5. Simple Status & Resolutions

6. Robust database back-end


24

BugX Tracker 2012

CONCLUSIONS & FUTURE ENHANCEMENT

BugX Tracker is a web-based application that allows user to access the

application from anywhere over the internet.

The project was carried out and completed to a greater extend of success. I had

done more than what I initially planned. Anyhow this is not the end of the road, this

project can be enhanced further with additional features and latest tools in future.

This project is considered to be an initial version and additional features can be made

and an updated version may be done in future.

1. Uploadable file attachments.

2. Record locking during Edit/Task/Delete operations added to prevent

simultaneous edit of Problem Tracker records.

3. Display bug in the Home Page when the visibility restriction was set

too high.


24

BugX Tracker 2012

REFERENCES

• ASP.NET TUTORIAL [ONLINE]

AVAILABLE: http://www.w3schools.com/aspnet/default.asp

• VISUAL BASIC .NET PROGRAMMING, ADO.NET

AVAILABLE: http://www.csharp-stationTutorial/AdoDotNet

• .NET FRAMEWORK 3.5 [ONLINE]

AVAILABLE: http://www.microsoft.com/details.aspx

• ORACLE DATABASE 10G EXPRESS EDITION TUTORIAL [ONLINE]

AVAILABLE:

http://st-curriculum.oracle.com/tutorial/DBXETutorial/index.htm


http://st-curriculum.oracle.com/tutorial/DBXETutorial/index.htm

Date post:	13-Jun-2015
Category:	Education
Upload:	abhimanyu-sood
View:	1,379 times
Download:	6 times

Bug XTracker Report

Education