Downloads provided by UsageCounts
In large-scale software development environments, defect reports are maintained through Bug Tracking Systems (BTS) and analyzed by domain experts. Since different users may create bug reports in a non-standard manner, each user can report a particular problem with a unique set of words. Therefore, different reports may describe the same problem, generating duplication. In order to avoid redundant tasks for the development team, an expert needs to look at all new reports while trying to label duplicates. This scenario is not trivial neither scalable and has a direct impact on bug fix correction time. Recent efforts to find the best latent space to describe duplicates tend to focus on deep neural approaches that consider hybrid information from bug reports as textual and categorical features. Unfortunately, these approaches ignores that a single bug can have multiple previously identified duplicates and, therefore, multiple textual descriptions, titles and categorical information. In this work, we propose DeepQL, a duplicate bug report detection method that considers not only information on individual bugs, but also collective information from bug clusters. DeepQL combines attention mechanisms, which were not previously used in this task, with a novel loss function called Quintet Loss, that considers the centroid of duplicate bug report representation clusters and their contextual information. We validated our approach on the well-known open-source software repositories Eclipse, NetBeans, Firefox, and Open Office, that comprises more than 500 thousand bug reports. We evaluated both retrieval and classification of duplicates, reporting a mean accuracy of 68% on Recall@25 for retrieval and 90% AUROC for classification tasks.
deep neural networks, duplicate bug report, loss function
deep neural networks, duplicate bug report, loss function
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 0 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
| views | 5 | |
| downloads | 2 |

Views provided by UsageCounts
Downloads provided by UsageCounts