Search engine for discovering works of Art, research articles, and books related to Art and Culture
ShareThis
Javascript must be enabled to continue!

Bug Tracking System to Reduce Duplicate Bug Reports Using Cost-Aware Algorithm

View through CrossRef
Software engineers rely heavily on bug-tracking solutions to help direct their maintenance efforts. In certain projects, as many as quarters of all bug reports are duplicates, reducing the usefulness of these systems. Bugs are prioritized by cost-conscious algorithms according to their effect on consumers, possible business hazards, and resource availability. By doing this, the bug tracking system can concentrate on fixing high-priority problems first, reducing the effect on users and the software system. A cost-aware algorithm in a bug tracking system aims to maximize the problem resolution process via resource allocation, bug fix prioritization, and cost management of software issues. Manually identifying duplicate bug reports is a time-consuming and expensive procedure that adds to developers' workloads. To prevent developers from wasting time, suggest a system that may automatically sort incoming problem reports into distinct categories. This method makes use of graph clustering in addition to textual semantics and surface information to make duplication predictions. Simulate a real-time bug reporting environment and conduct experiments using a dataset of 29,000 bug reports from Mozilla projects. By eliminating 8% of duplicate bug reports while ensuring that developers get at least one report for each genuine fault, the solution can cut down on development costs significantly. A bug-tracking system is a piece of software that acts as a database for recording software defects and user recommendations. The result shows that the false positive rate is reduced to 1% by using the Cost Aware algorithm.
Title: Bug Tracking System to Reduce Duplicate Bug Reports Using Cost-Aware Algorithm
Description:
Software engineers rely heavily on bug-tracking solutions to help direct their maintenance efforts.
In certain projects, as many as quarters of all bug reports are duplicates, reducing the usefulness of these systems.
Bugs are prioritized by cost-conscious algorithms according to their effect on consumers, possible business hazards, and resource availability.
By doing this, the bug tracking system can concentrate on fixing high-priority problems first, reducing the effect on users and the software system.
A cost-aware algorithm in a bug tracking system aims to maximize the problem resolution process via resource allocation, bug fix prioritization, and cost management of software issues.
Manually identifying duplicate bug reports is a time-consuming and expensive procedure that adds to developers' workloads.
To prevent developers from wasting time, suggest a system that may automatically sort incoming problem reports into distinct categories.
This method makes use of graph clustering in addition to textual semantics and surface information to make duplication predictions.
Simulate a real-time bug reporting environment and conduct experiments using a dataset of 29,000 bug reports from Mozilla projects.
By eliminating 8% of duplicate bug reports while ensuring that developers get at least one report for each genuine fault, the solution can cut down on development costs significantly.
A bug-tracking system is a piece of software that acts as a database for recording software defects and user recommendations.
The result shows that the false positive rate is reduced to 1% by using the Cost Aware algorithm.

Related Results

Feature Learning via Correlation Analysis for Effective Duplicate Detection
Feature Learning via Correlation Analysis for Effective Duplicate Detection
With the growing reliance on software, the frequency of software bugs has increased significantly. To address these issues, users or developers typically submit bug reports, which ...
Bug Report Summarization by Using Swarm Intelligence Approaches
Bug Report Summarization by Using Swarm Intelligence Approaches
Background: Bug reports are considered as a reference document, during the maintenance phase of the software development process. The developer's counsel them at whatever point the...
Effective Bug Triage With Software Reliability
Effective Bug Triage With Software Reliability
Programming associations spend in excess of 45 percent of cost in overseeing programming bugs. An inevitable progress of settling bugs is bug triage, which wants to precisely dole ...
Is a Fitbit a Diary? Self-Tracking and Autobiography
Is a Fitbit a Diary? Self-Tracking and Autobiography
Data becomes something of a mirror in which people see themselves reflected. (Sorapure 270)In a 2014 essay for The New Yorker, the humourist David Sedaris recounts an obsession spu...
Evaluating Fine-tuning Approaches for Duplicate Bug Report Detection
Evaluating Fine-tuning Approaches for Duplicate Bug Report Detection
Bug reports are artefacts that document defects encountered by users or developers. Rapid testing and release cycles often lead to the creation of similar or near-duplicate bug rep...
Using CNN to Predict the Resolution Status of Bug Reports
Using CNN to Predict the Resolution Status of Bug Reports
Abstract Bug tracking systems (BTS) are a resource for receiving bug reports that help to improve software applications. They usually contain reports reported by the...
Missing values compensation in duplicates detection using hot deck method
Missing values compensation in duplicates detection using hot deck method
Abstract Duplicate record is a common problem within data sets especially in huge volume databases. The accuracy of duplicate detection determines the efficiency ...
Software Bug Ontology Supporting Bug Search on Peer-to-Peer Networks
Software Bug Ontology Supporting Bug Search on Peer-to-Peer Networks
This paper presents a semantics-based bug search system that allows users to solve bugs by searching similar bug reports on peer-to-peer networks. This system uses a bug schema to ...

Back to Top