| dc.contributor.author | Zimmermann, Thomas | |
| dc.contributor.editor | Cremers, Armin B. | |
| dc.contributor.editor | Manthey, Rainer | |
| dc.contributor.editor | Martini, Peter | |
| dc.contributor.editor | Steinhage, Volker | |
| dc.date.accessioned | 2019-10-11T07:41:25Z | |
| dc.date.available | 2019-10-11T07:41:25Z | |
| dc.date.issued | 2005 | |
| dc.identifier.isbn | 3-88579-396-2 | |
| dc.identifier.issn | 1617-5468 | |
| dc.identifier.uri | http://dl.gi.de/handle/20.500.12116/28065 | |
| dc.description.abstract | Nowadays, any larger software project collects lots of data. Changes to source code are stored in version control archives, and problems in bug databases. In this paper we present two tools that mine both sources to help developers writing better programs. The eROSE tool guides programmers along related changes in a similar way Amazon.com supports its customers: You changed fKeys[] and eROSE suggests initDefaults(), because in the past both items always have been changed together. The HATARI tool warns programmers against risky locations: “Programmers failed at changing resolveClasspath(). Be careful.” To measure risk, HATARI locates changes that lead to problems, as indicated by later fixes. | en |
| dc.language.iso | en | |
| dc.publisher | Gesellschaft für Informatik e.V. | |
| dc.relation.ispartof | Informatk 2005. Informatik Live! Band 1 | |
| dc.relation.ispartofseries | Lecture Notes in Informatics (LNI) - Proceedings, Volume P-67 | |
| dc.title | Learning from project history to support programmers | en |
| dc.type | Text/Conference Paper | |
| dc.pubPlace | Bonn | |
| mci.reference.pages | 387-390 | |
| mci.conference.sessiontitle | Regular Research Papers | |
| mci.conference.location | Bonn | |
| mci.conference.date | 19.-22. September 2005 | |
