In automatic software bug localization, source code analysis is usually used to localize the buggy code without manual intervention. However, due to considering irrelevant source code, localization accuracy may get biased. In this paper, a Method level Bug localization using Minimized search space (MBuM) is proposed for improving the accuracy, which considers only the liable source code for gen...

There is a gap between the information available at the time of a software failure and the information actually shipped to developers in the corresponding bug report. As a result, identifying the cause of the bug based on this bug report is often difficult. To close this gap, we propose bug fingerprints—an augmentation of classic automated bug reports with runtime information about how the repo...

Most of the software companies need to deal with vast number of software bugs day to day. This paper can be viewed as an application of instance selection and feature selection in bug repositories. The aim is to address the problem of data reduction for bug triage, and to reduce the scale and improve the quality of bug data. This can be achieved by combining instance selection with feature sele...

Some bugs, among the millions that exist, are similar to each other. When fixing a bug, a programmer tends to search for similar bugs that have been reported and resolved in the past. A fix for a similar bug can help him understand his bug, or even directly fix his bug. Studying bugs with similar symptoms, programmers may determine how to detect or resolve them. Existing work has focused on ana...

We present and categorize a taxonomy of concurrent bug patterns. We then use the taxonomy to create new timing heuristics for ConTest. Initial industrial experience indicates that these heuristics improve the bug finding ability of ConTest. We also show how concurrent bug patterns can be derived from concurrent design patterns. Further research is required to complete the concurrent bug taxonom...

Not all bugs in software would be experienced and reported by end users right away: Some bugs manifest themselves quickly and may be reported by users a few days after they get into the code base; others manifest many months or even years later, and may only be experienced and reported by a small number of users. We refer to the period of time between the time when a bug is introduced into code...

Bug prediction is a technique used to estimate the most bug-prone entities in software systems. Bug prediction approaches vary in many design options, such as dependent variables, independent variables, and machine learning models. Choosing the right combination of design options to build an effective bug predictor is hard. Previous studies do not consider this complexity and draw conclusions b...

Programming associations spend over 45% of cost in overseeing programming bugs. An unavoidable walk of modifying bugs is bug triage, which arrangements to precisely apportion a specialist to another bug. To reduce the time cost in manual work, content request techniques are associated with lead customized bug triage. In this paper, we address the issue of data extenuation for bug triage, i.e., ...

A software Bug report contains information about the bug in the form of problem description and comments using natural language texts. Managing reported bugs is a significant challenge for a project manager when the number of bugs for a software project is large. Prior to the assignment of a newly reported bug to an appropriate developer, the triager (e.g., manager) attempts to categorize it in...

We propose an approach called Bug report assignment with topic modeling and heterogeneous network analysis (BAHA) to automatically assign bug reports to developers. Existing studies adopt social network analysis to characterize the collaboration of developers. The networks used in these studies are all homogenous. In real practice of bug resolution, different developers collaborate on different...