Analytical Survey on Bug Tracking System

ISSN: 2312-7694
Shivani et al. / International Journal of Computer and Communication System Engineering (IJCCSE)
37 | P a g e
© 2014, IJCCSE All Rights Reserved Vol. 1 No.02 August 2014 www.ijccse.com
Analytical Survey on Bug Tracking System
Shivani Dr. Sanjay Kumar Dubey
Department of Computer Science and Engineering Department of Computer Science and Engineering
Amity School of Engineering and Technology Amity School of Engineering and Technology
Amity University, Noida, India Amity University, Noida, India
shivi0052@gmail.com skdubey1@amity.edu
Abstract— Bug tracking system plays major role in identifying
bug in various software system. Present paper underlined the
importance of bug tracking system in the field of software
development and had also identified the various drawbacks of the
current bug tracking system by exploring the various literatures
and research papers published up to year 2014. Various
recommendations and suggestions have also been provided after
analyzing the obstacles faced by developers and users due to
functioning of current bug tracking system. An extensive survey is
presented in this regards and the provided analysis is truly based on
what have been analyzed s in context with bug tracking system.
I. INTRODUCTION
The term „Bug‟ in context to software development project
refers to any defect, fault, flaw that has been encountered in the
working of a specific software application or in any product.
The mechanism which is used in order to handle these bugs
refers to as “Bug Tracking System”.
It permits the user to interact with the developer and make
him aware of the shortcomings, problem encountered while
working with that particular software application or the
product. It manages to keeps bug record databases that consist
of all the bugs that have been filed by the reporters or user
along with the complete set of information that describes the
error which in turn allows the developer to fix the bug and
prevents its future occurrence. The information provided by the
reporter in the bug report include the time when bug was filed
,its severity, steps to reproduce the error etc.
For any software development company, the
implementation of this tool is vital as it ensures the proper and
smooth functioning of any software application by conquering
all the flaws and then fixing them in an orderly way. Not only
this it enhances the relationship between the manufacturer and
the customers of the product by providing an easy way in
which customers can communicate with the developer and give
their views about the product and find solution of the problems
faced by them.
Bug Tracking System is a very important research subject
that will lead to enhancement in the field of software
development companies, product manufacturing, information
technology etc. But to achieve this, an ideal Bug Tracking
System need to be designed which can only be established only
when we discovers all the shortcomings that exists in the
current BTS and then works to overcome them.
II. LITERATURE REVIEW
The present section provides the detail survey about various
developments in the field of bug tracking system. The survey is
organized according to the year wise systematic enhancement
in this field.
Davor ˇCubrani´, Gail C. Murphy [18] presented their
experimental report by proposing a methodology in which they
evaluated 15,859 bug reports from a large open source projects.
They met their aim using the “Naïve Bayes Classifier”. In their
research they introduced a technique that automatically
performs the task of assigning the bug to appropriate developer
by using text categorization technique which saves a lot of
developer‟s time and resources used in bug triage process.
Robert J. Sandusky, Les Gasser, Gabriel Ripoche [19]
presented their research work by proposing the methodology in
which they have examined a sample of 385 bug report and
then identifying the relationship between them. In their
research work, they have listed out various management
strategies to handle software problems and also explained
when and how communities use BRN (Bug Report Network).
A. Gunes Koro and Jelf Tian [13] presented their survey
report by using a methodology which included conducting a
survey in order to predict defect handling process. A. Gunes
Koro and Jelf Tian meet their objective by using the tool
Bugzilla, survey tool. In their research they found out different
defect handling process adopted by various open source
projects.
John Anvik, Lyndon Hiew Gail C.Murphy [11] have
presented their research work by examining the two open bug
receptacle from eclipse and Firefox projects. They met their
aim by using tool Bugzilla. In their research they come out
with various challenges that the developers face due to
duplicate that the developer face due to duplicate bugs and bug
triage problem.

ISSN: 2312-7694
38 | P a g e
Gabriela Avram, Anne Sheehan and Daniel K. Sullivan [2]
presented their research by using a methodology that included
conducting interviews, going through document analysis and
various workshops. They met the required objective by using
the tool like CDTS and BTS. In their research they presented
the various advantages of CDTS and BTS in the enhancement
of developmental projects of the product.
Pieter Hooimeijer and Westley Weimer [5] presented an
experimental report by adopting a methodology that includes
conducting different experiments using cumulative and non-
cumulative models. They meet their aim using the tool like
Bugzilla. In their research they proposed a model of Bug
Tracking System that aims at reducing the overall software
maintenance cost and also provides better precision and recall
results and has also proved to be helpful in filtering out the
unwanted bugs.
Sascha Just, Rahul Premraj, Thomas Zimmermann [7]
presented their research work by using a methodology using
the card sorting technique that involved the developer and user
of Ecllipse, Apache, Mozilla. They met their aim using the card
sorting technique. After the completion of their research they
presented few suggestions on how one can improve the
working of current bug tracking system by recognizing the bug
duplicates etc.
Nicolas Bettenburg, Rahul Premraj, Thomas Zimmermann,
Sunghun Kim [9] presented an experimental report on by
proposing a methodology by conducting an experiment that
took into account 16,511 master report and 27,838 report
submitted by the reporters. They met their aim by using the
tool called infozilla. In their research they proved that
duplicated bug report cannot always be considered as harmful,
they in fact provide the developer with some useful
information about the bug that were not even present in the
master report[8]. Their research work throws light on various
applications of infozilla in extracting structural information.
Andrea Arcuri [16] presented their research work in which
they proposed a methodology in which they monitored a
specific software as it passes through a set of units. He throws
light on the application of “Automatic Bug Fixing” in the
process of resolving the bug automatically by making changes
in the source code there itself.
Nicolas Bettenburg et al. [4] presented a survey report in
which they proposed a methodology by conducting a survey
that focuses in providing better quality bug report. Authors met
their aim by using tool like cuezilla. In their research the found
the mismatch of information needed by the developer to the
information submitted by reporter and throws light on how one
can improve the quality of bug report.
Jorge Aranda, Gina Vendia [6] presented an experimental
report in which they adopted a methodology that included a
survey conducted between the software professionals and
studied various research around bug fixing. In their research
they presented various ways by which one can get the complete
set of information regarding bug‟s history and has also
explained the use of automated analysis of bug record data in
acquiring information about the bug.
Silvia Breu, Rahul Premaraj, Jonathan Sillito [10] have
presented their research work by using a methodology in which
they conducted a survey considering the questions asked in a
sample of600 bug reports from Mozilla and Ecllipse. They met
their aim by using card sorting technique. In their research they
listed out various implications that can be made to BTS, which
works to improve the interaction between the developer and
user.
Julius Davies et al. [14] presented their experimental report
by proposing a methodology in which they collected UDD and
raw BTS data combined it and used it for comparing the
158058 bug report. Authors fulfilled their aim by using the tool
Linux and Firefox. In their research they presented the three
differences between a conventional BTS and Debian BTS.
Thomas Zimmermann et al. [1] presented an experimental
report by proposing a methodology in which they conducted an
experiment and considered the views of various researchers.
Authors met their objective by using tool like cuezilla,
macrorecorder, Whyline tool. In their research they presented
the list of items that must be acquired from the reporters in
order to complete the bug report.
Kristi Morton, Nicolas Bruno have presented their
experimental report by proposing a methodology in which they
examine a repro which then goes through a test case and if it
found to have an error minimization of repro is done. Kristi
Morton, Nicolas Bruno meet their aim by using the tool
FlexMin. In their research they had listed out the various
application of Flexmin in a commercial DBMS for minimizing
repro [17].
Akhilesh Babu et al. [3] presented an experimental report
by using a methodology that included an self-conducted
experiment, not only this information is also acquired using
various research papers. They met their aim by using the tools
like bugzilla, Bug Genie, Cuezilla, RSS (Really Simple
Syndication).In their research they presented how the
notification process in Bug Tracking System can be improved
using RSS scheme and also conveyed some features that can be
added to current BTS to improve its functioning.
Torky Sultan, Ayman E.Khedr and Mostafa Sayed [12]
have presented their research work in which they used a
methodology which is truly based on theoretical approach.
They met their aim by using the tool Bugzilla. In their research
work they have given a detailed explanation on working of

ISSN: 2312-7694
39 | P a g e
Defect Tracking Model or Bug Tracking Model and also on the
four phases of BTS.
Swati Sen and Anita Ganpati [15] presented the report in
which they used a methodology which was truly based in
collecting data from various survey, research paper etc.
Authors met their aim by using the tools like Bugzilla, Bug
Genie, I tracker, Web Issues, Mantis. In their research they
provided the pros and cons of various Bug Tracking tool by
comparing each one of them in various characteristics.
Nicolas A. Kraft et al. [20] have presented their
experimental report in which they conducted their research by
considering the data set of 137,627 Bug reports from an
android project. They fulfilled their aim by using the tool
Weka. In their research they listed out various attributes which
when added into the current duplicate bug detection system
proposed by the researcher Alipour has improved its accuracy
in detecting duplicates.
III. ANALYSIS
The goal is to study the importance of “Bug Tracking
System” including its various drawbacks and Applications in
the field of software development, product manufacturing,
information technology etc. The work is carried out in two
steps: first gathering knowledge on various aspects of bug
tracking system second analyzing the challenges faced by the
current bug tracking system based on which suggesting what
all can be implemented in order to overcome those
shortcomings . The data has been acquired from various social
sites, blogs and journal. The Table 1 presents detail analysis of
various bug tracking system in the terms of methodologies,
application area and various pros and cons in this field.
IV. CONCLUSION
Bug tracking system forms an essential part in the working
and enhancement of various software developments, product
manufacturing companies etc. But the current bug tracking
system lacks certain features due to which its functioning is not
that accurate and helpful in tracking bugs and fixing them
with the help of developer. A detail extensive survey is
provided. Various methodologies and their applications along
with their pros and cons are presented. The tools presented to
track the system are also reviewed. In order to make it more
efficient various recommendations have provided that would
undoubtedly improve the working of current BTS. In future the
research will be present in more comprehensive form with
experimental results by taking the consideration of some real
time bug tracking system.
REFERENCES
[1] T. Zimmermann, R. Premraj, J. Sillito, S. Breu, “Improving Bug
Tracking System”, 31st
International Conference On Software
Engineering, 2009.
[2] G. Avram, A. Sheehan and D. K. Sullivan “Defect Tracking
System in Global Software Development”, 2007.
[3] A. Babu Kolluri, K. Tameezuddin, K. Gudikandula, “Effective
Bug Tracking System”, IOSR Journal of Computer Engineering,
Vol. 4, 2012.
[4] N. Bettenburg et al., “What Makes A Good Bug Report”, In
FSE‟08 Proceedings of 16th
International Symposium on
Foundation of Software Engineering”, 2008.
[5] P. Hooimeijer, W. Weimer, “Modelling Bug report Quality, In
Automated Software Engineering”, 2007.
[6] J. Aranda, G. Vendia, “The Secret Life Of Bugs”, In ICSE‟09
Proceedings Of The 31st
International Conference On Software
Engineering, 2009.
[7] S. Just, R. Premraj, T. Zimmermann, “Towards the Next
Generation of Bug Tracking System”, in proceedings Of the
IEEE Symposium on Visual languages And Human Centric
Computing, 2008.
[8] N. Bettenburg, R. Premraj, T. Zimmermann, S. Kim, “Duplicate
Bug Report Considered Harmful…Really? In ICSM‟08
Proceedings of 24th
IEEE International Conference On Software
Maintenance,2008.
[9] N. Bettenburg, R. Premraj, “Extracting Structural Information
from Bug Report”, Proceedings of 5th
Working Conference on
Mining Software Repositories, 2008.
[10] S. Breu, R. Premaraj, J. Sillito, “Information Needs in Bug
Reports”, CSCW‟10 Proceedings of 2010 ACM Conference on
Computer Supported Cooperative Work Table of Contents,
2010.
[11] J. Anvik, L. Hiew G. C. Murphy, “Coping with an Open Bug
Repository”, OOPSLA Workshop on Ecllipse Technology
Exchange, 2005.
[12] T. Sultan , A. E.Khedr and M. Sayed, “A proposed Defect
Tracking Model For Classifying The Inserted Defect Report To
Enhance Software Quality Control”, International Journal Of
Computer Applications, 2013.
[13] A. Gunes Koro and J. Tian, “Defect Handling In Medium And
Large Open Source Projects”, IEEE Software, Vol. 21, 2004.
[14] J. Davies Hanyu Zhang, L. Nusshaum, D. M. German
“Perspective on Bugs in Debian Bug Tracking System”, Mining
Software Repositories 7th
IEEE Working Conference‟10, 2010.
[15] S. Sen, A. Ganpati, “Proposed Framework for Bug Tracking
System in OSS Domain”, International Journal of Advance
Research in Computer Science and Engineering, Vol. 3, 2013.
[16] Andrea Arcuri, “On The Automation Of Fixing Software Bugs”,
Proceedings of 30th
International Conference on Software
Engineering (ICSE), 2008.
[17] W Abbas, N Abbas, U Majeed, “Performance enhancement of
End to End Quality of Service in WCDMA wireless networks,
Science International Journal Vol. 26 issue 02, Pp 613-620,
2014.
[18] K. Morton, N. Bruno, “A Flexible tool For Automatic Bug
isolation In DBMS Software”, Proceedings of 4th
International
Workshop On Testing Database system , 2011.
[19] D. ˇCubrani´, G. C.Murphy, “Automatic Bug Triage Using Text
Categorization”, Proceedings of 16th
International Conference
On Software Engineering And Knowledge Engineering , 2004.
[20] R. J. Sandusky, Les Gasser, Gabriel Ripoche, “Bug Report
Network: Varieties, strategies, impact in F/OS development

ISSN: 2312-7694
40 | P a g e
community”, International Conference on Mining Software
Repositories and 26th
International Conference on Software
Engineering, 2004.
[21] N. A. Kraft, Nathan Kleen, Christopher S. Corley, “New
Features For Duplicate bug detection” , Proceedings of 11th
working Conference On Mining Software Repositories”, 2014.
TABLE I. ANALYSIS OF VARIOUS BUG TRACKING SYSTEM
S.N. Title Year Methodology Tools
Application
Area
Pros Cons Analysis
1.
Automatic
Bug Triage
Using Text
Categorization
2004
Have
investigated
the bug triage
or bug
assigning
process by
evaluating
15,859 bug
reports from a
large open
source project
i.e. Eclipse
Naïve Bayes
Classifier
Large open
source projects
like eclipse.
It has provided
text
categorization
technique by
which bugs can
be
automatically
assigned to the
well suited
developer by
evaluating all
the bug report
carefully which
saves resources
used in bug
triage or bug
assigning task.
Have explained
Naïve Bayes
Classifier can
be used as bug
triage.
The two
problems with
this approach is
sometime the
developer who
fix the bug is not
the one to whom
it was officially
assigned ,second
the algorithm
does not proved
to be as efficient
as it was thought
to be.
In order to improve the
approach for handling
bug triage is that on
should involve the
project‟s developer
too.
We should add on
factors that would even
deal with unlabeled
document in corpus.
2.
Bug Report
Network:
Varieties ,
strategies and
Impacts In a
F/OS
Development
2004
Qualitative
approach has
been used in
order to collect
information,
understand
various
concepts and
relationship
between the
between the
data obtained
by examining a
sample of 385
bug reports
drawn and then
identifying the
relationship
between them.
-
Software
development
community
It aimed to
develop a
model that
provides
enhanced
software
management
strategies to
handle various
It has just
considered bug
reports from
single
community.
More research should
be done that identifies
the consequences in
which BRN is proved
to be helpful in
resolving software
bugs and also a tool
that measures
complexity of BRN‟s.
4.
Coping With
An Open Bug
Repository
2005
In order to
describe the
duplicate bug
and bug triage
problem the
paper have
analysed two
open bug
receptacle
from Eclipse
and Firefox
Bugzilla
Development of
eclipse and
Firefox projects
It has listed the
various
challenges that
software
developmental
projects faces
due to duplicate
bug report and
bug assigning
problem and
has also
It does not
provided any
specific tool on
how these
feature can be
implemented
into the BTS.
After analyzing the
whole scenario it could
be suggested that there
must be a tool that
keeps record of what
kind of bugs have been
resolved by a particular
developer, and when a
bug has been filed it
should examine the
whole bug and

ISSN: 2312-7694
41 | P a g e
projects suggested to
add on a feature
that
automatically
detects
duplicate bug
report and
performs the
bug assigning
task.
accordingly assign it to
the well suited
developer.
5.
Defect
Tracking
System
2007
Research is
based on
observation,
document
analysis and
various
workshops.
CDTS and BTS
MNC‟s company
for development
project of a
product.
A.CDTS keeps
track of all the
error, defect,
flaw that may
arise in the
product and
also keeps track
of all
proceedings that
takes place in
order to resolve
the bug.
B.BTS in turn
supports “view”
that provide
team member
with a list of
defect that they
need to handle.
A.CDTS does
not support view
due to which it is
said to have less
functionality.
B. The usage of
CDTS along
with BTS made
the working
more time
consuming.
The two application
CDTS and BTS when
used together were
found to be
unsynchronized so
there must be a system
that immediately
updates the
information while it is
changed in both of the
application.
6.
Modeling Bug
Report
Quality
2007
The studies
were based on
various
experiments
done using
cumulative and
non-
cumulative
model.
Bugzilla
Used as filter in
Mozilla and
Firefox project to
resolve the bug
A. Aims at
reducing overall
software
maintenance
cost.
B. Usage of this
model leads to
better
Precision and
recall results.
The only
drawback is that
it has considered
only a two
project i.e.,
Mozilla and
Firefox
The reporter should be
provided with
complete guidelines on
what all information,
attachment they should
provide along with the
bug report.
7.
Towards the
next
generation of
bug tracking
system
2008
Recommendati
ons were truly
based on the
result of card
sort that
involves the
developer and
user of eclipse,
Mozilla,
Apache
Card sort
technique
Software
development
project ,product
manufacturing
information
technology
A. Has come
out with useful
recommendatio
n that would
improve the
working of
BTS, e.g. by
introducing
search facility
to search for
duplicate bug
report.
B. Asked to
categorise the
user into two
Novice user and
Expert user as
expert user get
more attention.
Though it
provides many
recommendation
s but it does not
provide any tool
or prototype on
how one can
achieve it.
The feature that can be
implemented to
ensures good quality of
bug report is that BTS
should provide its user
with a sample of the
perfect bug report that
has complete
information into it so
that the reporter gets
an idea on how to file a
bug report is that BTS
has complete
bug report.is that BTS
has complete
bug report.

ISSN: 2312-7694
42 | P a g e
8.
Duplicate Bug
Report
Considered
harmful…
Really?
2008
An experiment
was conducted
by taking
16511master
report and
27838
duplicate
report
submitted by
the reporters.
Infozilla
Software
maintenance of
large projects.
It has proved
that duplicate
bug report are
not always
considered to be
harmful as
sometimes it
provides the
developer with
additional
information
that are not
even present in
the master
report.
The study was
based truly on
the survey result
of bug report
from eclipse
project only; it
may not be true
for other
projects.
The research has
only considered
the positive
impact of
duplicate bug
report though it
has many
negative impacts
too.
BTS should consist a
tool that scan all the
duplicate bug reports
and extracts all the
additional information
that might be useful in
fixing the bug and
should automatically
add on those
information into the
master bug report.
9.
Extracting
Structural
Information
2008
Conclusions
have been
made by taking
into account all
the
applications
and drawback
of infozilla
tool.
Infozilla
Software
development
projects Software
development
projects
Throws light on
the application
of infozilla tool
in extracting
structural
element from
bug report
which not only
helps the
developer in
understanding
the cause of bug
but also
facilitates
efficient
training of
machine
learners.
Out of 161500
bug report, the
research has
been conducted
over only 200
bug report which
has been
randomly
selected so they
might not be
considered the
true
representative of
all failures that
can arise while
detecting
elements.
One should conduct a
proper research on
what element could be
qualified as structural
element and on that
basis more elements
should be added on to
the list.
10.
On The
Automation
Of Fixing
Software Bug
2008
Have analyzed
specific
software as it
passes through
a set of unit
test.
-
Software
Development
A technique has
been proposed
for
Automatically
fixing the bug
and also make
specific changes
in the source
code to remove
the bug.
Throws light on
the importance
of “Automatic
Bug Fixing”
As a tool.
Have proved
that ABF is
easier than AP
in terms of
working and
efficiency.
Has not
presented any
ideas or
suggestion on
how we can
implement ABF
testing in real
world oriented
software.
We must design a
framework that saves
developer time in
resolving those bugs
which have already
been fixed earlier, and
resolve such bugs
automatically there
itself.

ISSN: 2312-7694
43 | P a g e
11.
What Makes
A Good Bug
Report
2008
A survey was
conducted that
questioned on
the quality of
bug report
required by the
developer to
the bug report
submitted by
the reporter.
Cuezilla
Software
development
project,
information
technology,
product
manufacturing.
A. Had
mentioned the
factors that
plays crucial
role in resolving
the bug.
B. Identifies the
Reason that
why developer
takes more time
in fixing the
bug.
C. Throws light
on how one can
improve the
quality of bug
report.
A. This survey
only took into
account
responses of
experienced
developers.
B. Survey
followed self-
selection
principle
One way to improve
the quality of bug
report is that it should
be made mandatory for
all reporters to provide
all the relevant
information that will
be required in order to
resolve the bug,
without providing all
such details they
should not be allowed
to file the bug.
12
The Secret
Life Of Bugs
2009
All the
conclusion and
discoveries on
the
coordination
patterns around
bug fixing
were outcomes
of research and
survey
conducted
between the
software
professional
-
Tool designers
and researchers
in software
development
project.
A. Provided the
sources which
must be
considered in
order to get
complete
information
about the bug‟s
history.
B. throws light
on the
importance of
automated
analysis of bug
record data to
acquire initial
information
about the bug.
.
Usage of
concepts that do
not have
compatible
definition in
literature.
Data has been
acquired from
Microsoft and
there is no
assurity whether
it will be
applicable to
other companies
or not.
One should try and
explore all the sources
including conducting
interviews, going
through electronic
conversation, bug
database record and
also observe the
coordination pattern in
order to achieve bug‟s
history.
13.
Information
Needed In
Bug Report
2010
All the
conclusions
have been
made
considering the
questions
asked in a
sample of
600bug reports
from Mozilla
and Ecllipse
projects.
Card sorting
technique
Software
development
project, product
manufacturing
company
This paper
works for
enhancing the
interaction
between the
developer and
reporters which
are very
essential for
fixing the bug
well in time.
Presented the
eight categories
of questions
that are being
asked in the
Bug‟s entire life
cycle by the
developer, and
also the
question that
must be
answered by the
reporter in order
to get the bug
fixed by the
developer.
The result is
based
considering only
the two large
projects Eclipse
and Mozilla it
might not be
applicable to
other projects.
BTS should be
provided with a feature
that shows the
information status of
bug report i.e. if any
information is left
unfilled by the reporter
it will show a “pending
status” and will keep
on notifying the
reporter about it.

ISSN: 2312-7694
44 | P a g e
14.
Perspective on
Bugs In The
Debian Bug
Tracking
System
2010
Downloading
UDD and raw
BTS data and
then
processing it
by combining
the raw bug
files and
sorting them
by bug
number,
grouping them
in term of
month and
package and
forming table,
the resulted
158058 bugs
were compared
against this
table and result
was recorded.
Linux , Firefox
Debian Software
Development
Throws light on
the three
difference
between
conventional
BTS and
Debian BTS in
terms of bug
association, bug
fixing process ,
reporting of bug
, bug frequency
etc.
The research
have not
included the
packages without
bugs, time period
chosen for the
study was
arbitrary.
The study is not
sufficient in
understanding the
whole working of
Debian BTS and its
features.
15.
Improving
Bug Tracking
System
2010
The study is
conducted
based on the
experiments
and taking into
account
various
investigations
put forwarded
by researchers.
Macro recorder,
cuezilla,
Why line tool
Software
development
Company
Helpful in
collecting
relevant
information
from the
reporter which
is needed in
order to
complete the
content on bug
report
A. Does not
provide any way
in which one can
correct the error
in steps to
reproduce.
B. Does not
provide any way
that helps to
reduce the
mismatch of
information
needed by
developer in
order to fix the
bug.
A reporting tool must
be develop that
provides the cause of
bug and prevents its
future occurrence
16.
A Flexible
Tool For
Automatic
Bug Isolation
In DBMS
Software
2011
Have
considered a
repro(sequence
of steps that
reproduce
error)that
consist of
number of
complex query
which then
passes through
a test if it fails
in doing so it is
said to have
error otherwise
not and then
minimization
of repro is
done using
FlexMin
FlexMin
Commercial
Database
Management
System
Have
underlined the
advantage of
Flexmin in
minimising the
sequence of
steps that
reproduce error
in DBMS.
It had put
forwarded a
better round
robin approach
which not only
helps in
computing but
also apply
simplification
across all the
nodes of the
tree.
Had explained
how flexMin
accepts
guidance from
user using “user
directed search
using language
hints”
This tool can
only be used in a
commercial
DBMS.
A tool like FlexMin
should be developed
for resolving the bugs
in software
applications too.

ISSN: 2312-7694
45 | P a g e
17.
Effective Bug
Tracking
System
2012
All the
conclusions
were made
based on the
information
acquired from
research paper
and from a
self-conducted
experiment.
Bugzilla,
Cuezilla, Bug
Genie, RSS
(really simple
syndication).
Software
Development
project and
product
manufacturing
A. Throws light
on RSS scheme
which can be
used for making
notification and
also ensures
that even the
spam filter does
not block them.
B. Have
provided the
tool named
Cuezila that
helps in
checking the
quality of
information
provided in the
bug report.
It does not
provide any way
that overcomes
the drawback of
Bugzilla where
in the set up
process is very
complicated and
Bug Genie
where the bug
reporting process
lacks simplicity
In order to make the
current BTS more
information oriented
we can add on a
feature that displays all
the information that
will be required in
order to fix the bug and
also its occurrence
cause.
18.
A Proposed
Defect
Tracking
Model For
Classifying
The Defect
Report To
Enhance
software
Quality
Control
2013
Theoretical
approach has
been used
using the data
acquired from
previous
research work
Bugzilla
Software
Development
Helped in
understanding
the impact of
defect tracking
system in the
enhancement of
software
quality.
Helped in
understanding
the four phases
of in bug
tracking system
And their role
in the process of
tracking of bug.
It had only
provided the
theoretical
structure for the
defect tracking
model there is no
practical
implementation
for it.
We should add on a
feature into the defect
tracking model that
keeps track of all the
information about the
bug that have been
fixed like the cause of
it ,how one can fix it,
its future prevention
method.
19.
International
Journal Of
Advance
Research In
Computer
Science And
Software
Engineering
2013
Theoretical
approach has
been used,
including
secondary data
acquired from
survey,
research paper.
Bugzilla, bug
Genie, Mantis, I
tracker, Web
issues
Bug Genie
customer service,
developers,
information
technology,
system
administrator
It has listed out
the various
advantages and
disadvantages
of many bug
tracking tools.
Compared them
in the aspect of
size, platform
used, usage,
functionality
etc.
Does not provide
complete
information from
bug tracker‟s
repository to
anonymous user.
It lacks in
providing
filtration of bug
due to which
even the fake
bug can be
submitted by the
reporters.
There should be a
facility of
automatically fixing a
bug and correcting it
there itself, if the
encountered bug has
been fixed earlier.
20.
New Features
For Duplicate
Bug Detection
2014
They have
used the data
set collected by
the researcher
Alipour in
which out of
137,627 bug
reports 1,452
bug report
Weka
Large open
source projects ,
android
development
project
Underlined the
use of
automatically
grouping the
duplicate bug
report that
addresses the
same
error/fault.
Study shows that
in the dataset
36% of bugs
were duplicates
but in our
experiment only
1452 were
marked as
duplicates
The attributes and
metrics proposed in the
research paper should
be further explored so
that better Duplicate
Bug Detection system
could be developed
that gives 100%
accuracy

ISSN: 2312-7694
46 | P a g e
were found to
be duplicate
BRs , after that
all duplicate
BRs were
grouped in
different
bucket in
which they got
2102 unique
reports and
then they
examined topic
document
distribution of
each report
using LDA
Listed out work
of various
researchers in
the field of
Duplicate Bug
Report
Detection.
They have
added on
various
attributes in the
metrics
proposed by
Alipour which
has improved
the bug
detection
process further.
Selection of pair
might not be
appropriate.

Analytical Survey on Bug Tracking System

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Analytical Survey on Bug Tracking System

Similar to Analytical Survey on Bug Tracking System (20)

More from International Journal of Computer and Communication System Engineering

More from International Journal of Computer and Communication System Engineering (20)

Recently uploaded

Recently uploaded (20)

Analytical Survey on Bug Tracking System