Show simple item record

dc.contributor.authorHall, Tracy
dc.contributor.authorBowes, David
dc.contributor.authorLiebchen, Gernot
dc.contributor.authorWernick, Paul
dc.contributor.editorBabar, MA
dc.contributor.editorVierimaa, M
dc.contributor.editorOivo, M
dc.date.accessioned2012-01-03T16:01:14Z
dc.date.available2012-01-03T16:01:14Z
dc.date.issued2010
dc.identifier.citationHall , T , Bowes , D , Liebchen , G & Wernick , P 2010 , Evaluating Three Approaches to Extracting Fault Data from Software Change Repositories . in MA Babar , M Vierimaa & M Oivo (eds) , Product-Focused Software Process Improvement : Procs of 11th Int Conf PROFES 2010 . Lecture Notes in Computer Science , vol. 6156 , Springer , BERLIN , pp. 107-115 , 11th Int Conf, PROFES 2010 , Limerick , Ireland , 21/06/10 . https://doi.org/10.1007/978-3-642-13792-1_10
dc.identifier.citationconference
dc.identifier.isbn978-3-642-13791-4
dc.identifier.otherPURE: 444195
dc.identifier.otherPURE UUID: 69c156d3-1ac1-4462-8a8f-bb1763d3fa56
dc.identifier.otherWOS: 000286415300010
dc.identifier.otherScopus: 77955449055
dc.identifier.urihttp://hdl.handle.net/2299/7576
dc.description.abstractSoftware 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.en
dc.format.extent9
dc.language.isoeng
dc.publisherSpringer
dc.relation.ispartofProduct-Focused Software Process Improvement
dc.relation.ispartofseriesLecture Notes in Computer Science
dc.subjectSoftware
dc.subjectfault
dc.subjectdata
dc.subjectprediction
dc.titleEvaluating Three Approaches to Extracting Fault Data from Software Change Repositoriesen
dc.contributor.institutionCentre for Computer Science and Informatics Research
dc.contributor.institutionSchool of Computer Science
dc.contributor.institutionScience & Technology Research Institute
dc.identifier.urlhttp://www.scopus.com/inward/record.url?scp=77955449055&partnerID=8YFLogxK
dc.relation.schoolSchool of Computer Science
dcterms.dateAccepted2010
rioxxterms.versionVoR
rioxxterms.versionofrecordhttps://doi.org/10.1007/978-3-642-13792-1_10
rioxxterms.typeOther
herts.preservation.rarelyaccessedtrue


Files in this item

FilesSizeFormatView

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record