Evaluating three approaches to extracting fault data from software change repositories

This source preferred by Gernot Liebchen

Authors: Hall, T., Bowes, D., Liebchen, G. and Wernick, P.

Editors: Ali Babar, M., Vierimaa, M. and Oivo, M.

http://dx.doi.org/10.1007/978-3-642-13792-1_10

Volume: 6156

Pages: 107-115

Publisher: Springer Berlin Heidelberg

ISBN: 978-3-642-13791-4

DOI: 10.1007/978-3-642-13792-1_10

This data was imported from Scopus:

Authors: Hall, T., Bowes, D., Liebchen, G. and Wernick, P.

Volume: 6156 LNCS

Pages: 107-115

DOI: 10.1007/978-3-642-13792-1_10

Software products can only be improved if we have a good understanding of the faults they typically contain. Code faults are a significant source of software product problems which we currently do not understand sufficiently. Open source change repositories are potentially a rich and valuable source of fault data for both researchers and practitioners. Such fault data can be used to better understand current product problems so that we can predict and address future product problems. However extracting fault data from change repositories is difficult. In this paper we compare the performance of three approaches to extracting fault data from the change repository of the Barcode Open Source System. Our main findings are that we have most confidence in our manual evaluation of diffs to identify fault fixing changes. We had less confidence in the ability of the two automatic approaches to separate fault fixing from non-fault fixing changes. We conclude that it is very difficult to reliably extract fault fixing data from change repositories, especially using automatic tools and that we need to be cautious when reporting or using such data. © 2010 Springer-Verlag.

The data on this page was last updated at 04:50 on October 18, 2018.