Home > Research > Publications & Outputs > Evaluating three approaches to extracting fault...

Research

Associated organisational units

Links

Text available via DOI:

View graph of relations

Evaluating three approaches to extracting fault data from software change repositories

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Published

Standard

Evaluating three approaches to extracting fault data from software change repositories. / Hall, T.; Bowes, D.; Liebchen, G. et al.
International Conference on Product Focused Software Process Improvement: PROFES 2010: Product-Focused Software Process Improvement. ed. / M. Ali Babar; M. Viermaa; M. Oivo. Springer, 2010. p. 107-115.

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSN › Conference contribution/Paper › peer-review

Harvard

Hall, T, Bowes, D, Liebchen, G & Wernick, P 2010, Evaluating three approaches to extracting fault data from software change repositories. in M Ali Babar, M Viermaa & M Oivo (eds), International Conference on Product Focused Software Process Improvement: PROFES 2010: Product-Focused Software Process Improvement. Springer, pp. 107-115. https://doi.org/10.1007/978-3-642-13792-1_10

APA

Hall, T., Bowes, D., Liebchen, G., & Wernick, P. (2010). Evaluating three approaches to extracting fault data from software change repositories. In M. Ali Babar, M. Viermaa, & M. Oivo (Eds.), International Conference on Product Focused Software Process Improvement: PROFES 2010: Product-Focused Software Process Improvement (pp. 107-115). Springer. https://doi.org/10.1007/978-3-642-13792-1_10

Vancouver

Hall T, Bowes D, Liebchen G, Wernick P. Evaluating three approaches to extracting fault data from software change repositories. In Ali Babar M, Viermaa M, Oivo M, editors, International Conference on Product Focused Software Process Improvement: PROFES 2010: Product-Focused Software Process Improvement. Springer. 2010. p. 107-115 doi: 10.1007/978-3-642-13792-1_10

Author

Hall, T. ; Bowes, D. ; Liebchen, G. et al. / Evaluating three approaches to extracting fault data from software change repositories. International Conference on Product Focused Software Process Improvement: PROFES 2010: Product-Focused Software Process Improvement. editor / M. Ali Babar ; M. Viermaa ; M. Oivo. Springer, 2010. pp. 107-115

Bibtex

@inproceedings{858999ff403a472ab0799d6b3e100c4d,
title = "Evaluating three approaches to extracting fault data from software change repositories",
abstract = "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.",
author = "T. Hall and D. Bowes and G. Liebchen and P. Wernick",
year = "2010",
doi = "10.1007/978-3-642-13792-1_10",
language = "English",
isbn = "9783642137914",
publisher = "Springer",
pages = "107--115",
editor = "{Ali Babar}, M. and M. Viermaa and M. Oivo",
booktitle = "International Conference on Product Focused Software Process Improvement",

}

RIS

TY - GEN

T1 - Evaluating three approaches to extracting fault data from software change repositories

AU - Hall, T.

AU - Bowes, D.

AU - Liebchen, G.

AU - Wernick, P.

PY - 2010

Y1 - 2010

N2 - 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.

AB - 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.

U2 - 10.1007/978-3-642-13792-1_10

DO - 10.1007/978-3-642-13792-1_10

M3 - Conference contribution/Paper

SN - 9783642137914

SP - 107

EP - 115

BT - International Conference on Product Focused Software Process Improvement

A2 - Ali Babar, M.

A2 - Viermaa, M.

A2 - Oivo, M.

PB - Springer

ER -