Where do bugs come from?

Authors:
Adrian Schröter;Thomas Zimmermann;Rahul Premraj;Andreas Zeller
Affiliations:
Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany;Saarland University, Saarbrücken, Germany
Venue:
ACM SIGSOFT Software Engineering Notes
Year:
2006

Citing 4
Cited 1

A Metrics Suite for Object Oriented Design

IEEE Transactions on Software Engineering
Mining Version Histories to Guide Software Changes

IEEE Transactions on Software Engineering
Mining metrics to predict component failures

Proceedings of the 28th international conference on Software engineering
Predicting component failures at design time

Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering

Evaluating three approaches to extracting fault data from software change repositories

PROFES'10 Proceedings of the 11th international conference on Product-Focused Software Process Improvement

Quantified Score

Hi-index	0.00

Visualization

Abstract

"Where do bugs in programs come from?"---this is one of the pivotal research questions in software engineering. To answer it, one can find out which parts of a program are more defect-prone than others, and then investigate which properties correlate with defect density. In other words, once we can measure the effect, we can search for its causes. Bug databases of open-source projects are a good place to begin search because they record all the problems that occurred during the projects's lifetime. However, the location of the fix (and thus the defect) is hidden in version archives and has to be extracted separately [5]. As a result one obtains a mapping from defects to code locations.