Content uploaded by Hashani Hemali
Author content
All content in this area was uploaded by Hashani Hemali on Dec 17, 2020
Content may be subject to copyright.
Challengers of Manual Bug Management in Software Development
Industry: A Comprehensive Survey
SMKH Hemali1
1 General Sir John Kotelawala Defence University 1, Sri Lanka
# SMKH Hemali; <35-it-0046@kdu.ac.lk>
Abstract— Software systems are always released with
bugs. In software development life cycle bug resolving
process plays a vital role in development and evaluation
steps. Because developers can encounter a considerable
amount of user and tester errors daily. Bug management
process is important part of software maintenances. In
particular, incorrect action or activity done by developer or
development team. It should be Huge financial loss of
software development project. So, this survey-based
research main objective is to identify challenges of Manual
bug management in Software Development Industry. With
Investigation of researches Duplicate bugs Assign are an
anomaly in every organization in the world that manage
bugs manually, this research observes the result Using
questionnaire for developers and also research analysis
using qualitative data collection. This paper is based on
research work carried out with the objective of Challengers
of manual Bugs management found with time
consumption, budgeting, Duplicate bugs assign and
customer satisfaction.
Keywords— Bugs, Relative similarity, Duplicate bug
Assign
I. INTRODUCTION
After releasing software system, it can be pop up even
errors due to system complexity and inadequate testing.
Troubleshooting plays an important role in software
development and evaluation steps. “Software bug means
human errors”. When always bug management, process
have to handle sensitive data. Bug management process
has several steps, in first step toward correcting a bug the
corresponding bug report must be assigned to a
development team or individual developer, then this task
referred to as bug assignment. And has software bug
management process also. It has six steps discovery bugs,
categorized, resolution, verification, closure and reporting.
Sometimes bug management process like a discussion
between end user and developer. All the liabilities are
loading on software developers because they develop a
software system during the testing also. Developers could
collect number of bugs from users and testers daily. Most
of times in one project works multiple developers. then
they must manage bugs in manually. As well as SQA also
difficult to manage. so which developer assigned the
responsibility of resolving the bug and which developer
make the bug so on. then developers were fixed or identify
bugs during the software testing period. Such period they
should maintain the bug report also. Developers make
complain such huge workload occur disabilities for them.
Sometimes it may be extra expenditure of an organization
and software development project. When bug management
process doing manually have to spent large time period.
One of the objectives of this research is to find out how
time affects as a challenge. Software development industry
is constantly changing. From movement to movement new
technologies are introduce.so then it happens to developers
switch and get used to it. In developer side they maintain
bug report log. Sometimes developers face relative
similarity bug report in different project. It can be a
duplicate report. Then one of the research objectives is to
find how duplicate bug report affects as challenge. When
developers work several different projects with same time,
they have to handle different type of bugs on such projects
in manually. Sometimes one bug has huge number of test
cases. Then SQA takes higher time-period to refer code. As
a result, it may take longer to complete and release the
software. In this project objective is to find out how
budgeting affect as a challenge.
The Software development industry depends Solely on
customer satisfaction. If software development gets less
time-period, customer will satisfy. Because every customer
wants to get a high-quality product quickly at a low cost.
Quality means having a low bug rate.one of the research
objective is find out how customer satisfaction affect as a
challenge.
II. RELATED WORK
Several researchers may have proposed related things. The
Emotional side of Software Developers in JIRA
(Ortu et al., 2016)was discussed about emotional side of
develop project and it may have tested using software call
JIRA, they could achieve some information after doing
their work. They were mention detection in software
objects is still in its infancy due to a lack of manually
validated data and tools. Improved Duplicate bug report
identification(Tian, Sun and Lo, 2012)this was mention
major challenge.it was when many users could submit bug
reports reporting the same problem. these call duplicate
bug reports. Then they were present the inconvenience.
And what are the latest studies for investigate duplicate
bug report problems. After they could find existence of
many bug reports may cause much unnecessary manual
effort as often triage would need to manually tag bug
reports as being duplicate. Difficulties in Managing
Software Problems and Defects(Jäntti, 2008) in this
research domain they were tested about software quality
assurance method can be used to detect defect and identify
the difficulties of manual defect managing. Then they have
tested how successful the services-oriented problem
management method is in manual defect management. A
Dataset of High Impact Bugs : Manually-Classified Issue
Reports(‘A Dataset of High Impact Bugs : Manually-
Classified Issue Reports’, 2014)in this research discussed
bug classification and one of the challenge organization
management face detected after the defect in their newly
released software, it was the which bug should be fixed
first. Then they proposed method first it classified and
identify what is the high impact bug and then fixed it first.
All the function checked by manually. Expectations,
outcomes, and challenges of modern code
review(Bacchelli and Bird, 2013)in this research they have
mention cord reviewing challenge. It is a step-in bug
managing life cycle. Reviewing is something that is done
in the first stage of the bug management process. Then
researchers found the effectiveness of cord review in a
project. So according to their data it was take much time.
And it was spent much cost. An exploration of challenges
limiting pragmatic software defect prediction(Shihab,
2012)this thesis focused about software defect prediction
research can be tailored to consider the impact of defect
when making their predictions. They found that one of the
bugs in the software was one of the reasons for the delay in
its release.
III. METHODOLOGY
This section has to define over roll blueprint of the
research or flow of research functions. Then while
conducting research we want to collect data to analysis.
Methodology as the conduct as the research questions,
describe the research settings, and outline the research
method.
A. Research Questions
Challenges of manual bug management is review using
following research questions, which it iteratively refined
during in-filed observations and interviews.
1.If you face bugs while developing software, do you noted
it immediately?
2.If the answer for fourth question is" yes", do you maintain
a bug reporting log?
3.Do you maintain manual bug reporting log or software?
4.how many time spent for managing bugs per day?
5.As you are a developer, do you think manual bug
management can improve data accuracy?
B. Research setting
Study took place with senior software engineers,
professional developers, testers, and managers. And both
foreign and local project workers. Sample also handle
different types of projects software in driver’s domains,
server enterprise data management solution like SQL
server, mobile phone applications and smartphone
application that each involve section has its own testing,
development and bug handling policies.
C. Research Method
According to this research method conduct a mixed
approach and use primary data set. Basic common method
is to collecting data from different sources for analysis of
previous study researchers, refer and analysis past research
papers and sort some important information as well as it
may help to investigate how manual bug management
process impact to software development industry. And that
information will validate using survey data. When referring
past works could identify some factors related to these
researches also. Those are time consumption, data
accuracy, final outcome, total product cost. Each of these
factors affect when managing a bug as challenge. Past
researchers already mention how this factors effect to the
software development industry also. The other way of
collecting data to do this research is observations and
interviews with developers who works on different
organizations. When sample was selected from different
organizations because error of the sample should be less.
Then the interview data has less error percentage.
Researcher was conducting the one –to- one meeting with
junior software developers and senior developers
separately and each taking 30-40 minutes. There were
about thirty candidates in the studied sample. Each
meeting was made up of two parts. The first part observed
them and about interruptions while manual bug
management. Second part discussed how manual bug
management effect software development industry.so with
consent I record some speech as audio. Other method is
survey to developers, it means our primary data set. Create
questionnaire using google and send it through internet and
collect the information. Google forms make it easy for us
to summarize the data we collect. The survey consisted of
13 questions. the majority closed with multiple-choice
answers. Using this data researcher were going to validate
the identified factors that have studied in past.
Figure 1. Mixed Approach research method applied
IV. HOW AFFECT BUDGETING AS A CHALLENGES
Budget is the most important aspect in software
development industry. Usually in software bugs pop up at
implementation and testing time periods in SDLC. After
observing pervious works, cost of quality and bug
management is varying from one stage to another stage.
pervious stages of SDLC bug fixing and managing
budgeting is lower, but later stage budget is higher. This is
the past researchers result, how to impact of budgets for
bugs management in each stages of software development
life cycle. The conclusion that can be drawn after looking
at this diagram is budgeting is one of the challenge face in
software development industry and if it does manually, it
will take more time, so the budget can be even higher.
(Tian, 2017)
To manage problems at the Requirement gathering Stage
assume Budget 5 present.
To manage problems at the Analysis Stage, assume Budget
10 present.
To manage problems at the Analysis Stage, assume Budget
25 present.
To manage problems at the Analysis Stage, assume Budget
40 present.
To manage problems at the Analysis Stage, assume Budget
70 present.
To manage problems at the Analysis Stage, assume Budget
50 present.
Figure 2. Budget of Managing Bugs in Different Stage of SDLC
V. HOW AFFECT TIME AS A CHALLENGE
In real world scenarios customers does not give extra time
to develop software. Both software developers and
customer’s expectation is finished the software
development within on time. Then they do not provide
extra duration for Bug management. It takes a lot of time
complete the Bug management process in manually.
Previous research papers had mention When Peoples do
some process it will take lots time rather than Machine.
After the evaluation of previous studies have search in
Testing Stage in software development life cycle gets more
time period to fixing or managing bugs. The Following
diagram shows how time affect the SDLC. Acceding to the
diagram it trying to show Time is a one of the Challenge
faces in manual bug management in software development
Industry. The other important thing is time and Budgeting
has proportionately proportional relationship. It means
Budgeting depends on time. Bug managing Time is
increase then the Budget also increase.
But Bug managing Time is reducing then the Budget also
deduce.(Mujtaba, Mahmood and Nasir, 2011)
Figure 3. Relationship Between Budget and Time in Manual Bug
management
Shown by figure 2 impact of time and Budget in Manual
bug managing process in software development industry.
VI. HOW AFFECT CUSTOMER SATISFACTION AS A
CHALLENGE
Customers always expect the 100% bug free software
system. According to the past result of data sets Customer
satisfaction relate those Budgeting and Time. Time and
Customer satisfaction may have an inverse proportional
relationship. And the Budgeting and customer satisfaction
may have an inverse proportional relationship too. In
software development industry face huge challengers to
satisfy the customers. Because the customer requirements
are change rapidly. But in manually Software bug
management process also has this challenge. Observe the
previous research, researchers point out the customer
satisfaction in different viewpoints.in software bug
management process has several stages related to SDLC.
Bug identification, bug analysis, bug assigning and
reporting, and finally bug fixing. In bug identification and
Fixing stage get more Wight than other stages, so when it
done manually it takes lots of time. Then that may be one
reason why the software is time consuming to release. That
is how customer satisfaction and time are affected. This
research one objective is to find customer satisfaction
affect the manual bug management as a challenge.
(Hossain, 2018)
Figure 4. Interrelationship between budget and
customer satisfaction
This Figure 4 shown Variation of budget and customer
satisfaction. In previous research also mention the
relationship with these two factors. customer satisfaction is
one of the challenge face in manual software bug
management process. Because it has inverse relationship.
The following Figure 4 shown as the relationship between
customer Satisfaction and Time.
Figure 4 -Interrelationship between Time and
customer satisfaction
Figure 5. Interrelationship between Time and customer
satisfaction
VII. HOW AFFECT DUPLICATE BUG REPORT AS A
CHALLENGE
Manual bug management process has several stages. One
of the major stages is bug reporting stage.in such stage
notes down the bugs that have occurred in various parts of
the software. Sometimes the same bug or failure affect
many users. Then suddenly developers may note and put it
in to the software bug assigning report. Because all the
process doing by manually. Then in same bugs report twice
the same bug managing report in same developer.
Otherwise these reports are submitting the next stage it
means bug fixing stage, it takes more time to solve the
duplication bug reporting cases. Therefore, the time taken
to complete that stage increases.so it makes kind of
relationship between time and the duplicate bug reports
factors. So according to the data set it was a challenge
managing bugs in manually. And it was a waste of effort
and potential of causing conflicting changes being made to
a system.(Cavalcanti et al., 2010)
VIII.CONCLUSION
Software Development industry are constantly looking for
new ways to implement services and always decrease time
consumption and cost of managing problems, while at the
same time they are struggling with a number of incidents.
There is a clear need for Automation bug management
process that combine previous separate activities. Number
of bugs or defects can cause significant financial losses for
both Software Developers and customers. As shown by the
summarized data in this research manual duplicate bug
report is the huge challenge.so when manually managing
bugs with a software as its quality may decreases, then
customer satisfaction also decrees.
IX. FACTURE WORKS
Bug reporting steps is an uncoordinated distributed
process. Therefore, many duplicate reports being
generated.to address this issue, there is a need for an
automated duplicate report detection approach. In the
facture, researchers will plan to create software to track
this problem and to extend this study by investigating more
bug reports from different software systems. Researchers
also would like to continue improving the accuracy of
duplicate.
Bug tracking is the one of process in the bug management
lifecycle, it could improve software quality by supporting
developers in the bug fixing process. So, do some research
would like to make solution to this using service-oriented
approach.
In facture enhancement this approach could explore make
knowledgebase platform to share the information while
fixing bugs in manually. And researchers will have planned
to improve it and it will host to the network.
ACKNOWLEDGEMENT
It is highly required to express our deep and sincere
gratitude to our Senior Lecturer, Mrs.Nirosha Wedasinghe
of Information Technology Department, General Sir John
Kotelawala Defense University for giving us the
opportunity to make this research and providing invaluable
guidance throughout this. Her dynamism, vision, sincerity
and motivation have deeply inspired us. It was a great
privilege and honor to do a research with her under her
guidance.
LIMITATIONS
In this research there are so many limitations have faced.
The main thing is the data collecting Level. Because the
data gathering sample is lower. Due to the covid situation
difficult to get analysis information properly.
While Observing the developers they hide some
information due to the organizational polices.
Don’t having any secondary information related to our
topic.
Failed to verify some information validity.
Had more challenges but there was enough evidence to
make them identify.
AUTHOR BIOGRAPHIES
SMKH Hemali currently a 3rd year student of
information Technology department at
General Sir John Kotelawala Defence
University.
REFERENCE
‘A Dataset of High Impact Bugs : Manually-Classified Issue
Reports’ (2014), p. 2013.
Bacchelli, A. and Bird, C. (2013) ‘Expectations, outcomes, and
challenges of modern code review’, Proceedings - International
Conference on Software Engineering, pp. 712–721. doi:
10.1109/ICSE.2013.6606617.
Cavalcanti, Y. C. et al. (2010) ‘One step more to understand the
bug report duplication problem’, Proceedings - 24th Brazilian
Symposium on Software Engineering, SBES 2010, (September
2014), pp. 148–157. doi: 10.1109/SBES.2010.12.
Hossain, M. S. (2018) ‘Challenges of Software Quality Assurance
and Testing’, International Journal of Software Engineering and
Computer Systems, 4(1), pp. 133–144. doi:
10.15282/ijsecs.4.1.2018.11.0044.
Jäntti, M. (2008) Difficulties in Managing Software Problems and
Defects, Technology.
Mujtaba, G., Mahmood, T. and Nasir, Z. (2011) ‘A holistic
approach to software defect analysis and management’,
Australian Journal of Basic and Applied Sciences, 5(6), pp.
1632–1640.
Ortu, M. et al. (2016) ‘The emotional side of software developers
in JIRA’, Proceedings - 13th Working Conference on Mining
Software Repositories, MSR 2016, pp. 480–483. doi:
10.1145/2901739.2903505.
Shihab, E. (2012) ‘An exploration of challenges limiting
pragmatic software defect prediction’, (August).
Tian, Y. (2017) ‘Institutional Knowledge at Singapore
Management University Mining software repositories for
automatic software bug management from bug triaging to patch
backporting’.
Tian, Y., Sun, C. and Lo, D. (2012) ‘Improved duplicate bug
report identification’, Proceedings of the European Conference
on Software Maintenance and Reengineering, CSMR, pp. 385–
390. doi: 10.1109/CSMR.2012.48.