A Developer Centered Bug Prediction Model

Abstract

For many years, bug-tracking mechanism is employed only in some of the large
software development houses. Most of the others never bothered with bug tracking at all,
and instead simply relied on shared lists and email to monitor the status of defects. This
procedure is error-prone and tends to cause those bugs judged least significant by
developers to be dropped or ignored. Bug Tracking System is an ideal solution to track
the bugs of a product, solution or an application. Bug Tracking System allows individual
or groups of developers to keep track of outstanding bugs in their product effectively.
This can also be called as Defect Tracking System.
The Bug Tracking System can dramatically increase the productivity and accountability
of individual employees by providing a documented workflow and positive feedback for
good performance.
Some salient features are …
1. Product and Component based
2. Creating & Changing Bugs at ease
3. Query Bug List to any depth
4. Reporting & Charting in more comprehensive way
5. User Accounts to control the access and maintain security
6. Simple Status & Resolutions
7. Multi-level Priorities & Severities.
8. Targets & Milestones for guiding the programmers
9. Attachments & Additional Comments for more information
10. Robust database back-end

Software:

Front End: PHP

Back End: MY SQL
Existing System
In any software development bugs are inevitable. Let it be in any kind of product
bugs arise at any phase of development. one has to take a great care in the proper
maintenance and resolution of the bugs. In the Existing system the bugs are not properly
maintained and they are simply relied on shared lists and email to monitor the bugs. In
this type of system it becomes difficult to track a bug if a bug is over looked then it may
cause tremendous errors in the next phase and can improve the cost of project what ever
necessary effort spent on the bug maintenance may not be worthy. So bug history has to
be maintained properly. And there is no efficient search technique. One has to search the
whole database for the details of particular bug which might have occurred some time
earlier. It is both time consuming and error prone. And it is very difficult to share the bug
among several users as there is no proper maintenance of the bugs. In order to have an
efficient product bugs must be maintained properly and should be resolved in time both
to reduce time and money spent on the development.

Proposed System
The proposed system has many advantages over the existing system. This system
maintains the products, Bugs and bug Tracking. It has advantage of maintaining bug
history it stores all the details from bug origin to bug resolution. So that it would not be
difficult for the user to know how much effort spent on the bug. Each product can have
versions for easy maintenance of the product and all the user of the product is stored in
the database. It provides the advantage of maintaining users to the bugs and resolutions
provided by them. This product provides efficient search technique. As the number of
bugs for a product increases tremendously it would be difficult to search for a single
record. Our system provides the searching based on status, priority, and operating system.
It provides with user and bug hierarchy, which would be helpful in knowing the relation
between bugs and users allotted to the bug. It is provided with a fully authenticated
system with password encryption. And has the facility for storing attachments for a bug.
One can keep a track of the bug in a product with much lower cost and effort. The most
advantage of this system is maintaining log records which are helpful in knowing any
errors or misuse of the system by other users.
Modules Description:

1) Project Details:

This module has contained the master information about projects. Each one has

unique project ID for identifying project Name, Contract Date, Contract years, platform

details and so on. Project is organized into several categories. This can be maintained by

QA who is the controller of all projects. He maintains the project status up to date.

2) Admin:

QA is the Admin of this application. The Roles of the QA is

1)Add new projects to the system.

2)Post new bugs to the system

3)Delete existing bugs from the system.

4)Upload snapshots of errors in the system.

5)Sends bug list to developers those who are involved in this project.

6)Receives the solutions for bugs which are sent by the developer.

7)Verifies the solutions corresponding to that problems.

8)QA can share the comments on the bugs with developers.

9)They generates separate authentication to every Developers.

10)QA can re-open the closed Bug if QA feels that the Bug needs to be rectified more

afterwards.
3) Developer:

Developer can only view the Bug List and can update the status of Bug as Pending,

Completed .in progress or Bot and Bug etc as provided by the QA. Developers can share

the information about Bugs with other Developers. They have the provision of sending

mails and receiving mails about the Bugs.

4) Keyword Search Bugs:

A keyword is a word that is reserved by a program because the word has a special
meaning. Keywords can be commands or parameters. Every programming language has a
set of keywords that cannot be used as variable names. Keywords are sometimes called
reserved names.
5) Paths:

This module used to display the URL. URL stands for Uniform Resource Locator, which
means it is a uniform (same throughout the world) way to locate a resource (file or
document) on the Internet. The URL specifies the address of a file and every file on the
Internet has a unique address. Web software, such as your browser, uses the URL to
retrieve a file from the computer on which it resides.
6) Bugs:

In this Module, the bugs are generated for projects with the details of project name,

description, modules in which bugs are raised and description about the bugs.

7) Reports:

Reports are generated as per the requirements. QA generates Bug list those

which are solved or not yet solved. QA can watch how many developers visited the bug

list.