It's not a bug, it's a feature: how misclassification impacts bug prediction
dc.contributor.author | Herzig, Kim | |
dc.contributor.author | Just, Sascha | |
dc.contributor.author | Zeller, Andreas | |
dc.contributor.editor | Aßmann, Uwe | |
dc.contributor.editor | Demuth, Birgit | |
dc.contributor.editor | Spitta, Thorsten | |
dc.contributor.editor | Püschel, Georg | |
dc.contributor.editor | Kaiser, Ronny | |
dc.date.accessioned | 2017-06-30T20:56:09Z | |
dc.date.available | 2017-06-30T20:56:09Z | |
dc.date.issued | 2015 | |
dc.description.abstract | This submission presents work submitted and accepted at the International onference on Software Engineering in 2013 [Hj2013]. In empirical software engineering, it has become common to mine historic data to detect where bugs have occurred in the past, or to predict where they will occur in the future. The accuracy of such models depends on the quality of the data. For example, defect prediction models rely on the accuracy of historic data, such as bug reports. | en |
dc.identifier.isbn | 978-3-88579-633-6 | |
dc.identifier.pissn | 1617-5468 | |
dc.language.iso | en | |
dc.publisher | Gesellschaft für Informatik e.V. | |
dc.relation.ispartof | Software-engineering and management 2015 | |
dc.relation.ispartofseries | Lecture Notes in Informatics (LNI) - Proceedings, Volume P-239 | |
dc.title | It's not a bug, it's a feature: how misclassification impacts bug prediction | en |
dc.type | Text/Conference Paper | |
gi.citation.endPage | 104 | |
gi.citation.publisherPlace | Bonn | |
gi.citation.startPage | 103 | |
gi.conference.date | 17.-20. März 2015 | |
gi.conference.location | Dresden |
Dateien
Originalbündel
1 - 1 von 1