Zur Kurzanzeige

dc.contributor.authorRath, Michael
dc.contributor.authorGoman, Maksim
dc.contributor.authorMäder, Patrick
dc.date.accessioned2023-03-02T10:35:49Z
dc.date.available2023-03-02T10:35:49Z
dc.date.issued2018
dc.identifier.issn0720-8928
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/40533
dc.description.abstractSoftware and systems traceability is widely accepted as an essential element for supporting many software development tasks. Todays version control systems provide inbuilt features that allow developers to tag each commit with one or more issue IDs, thereby providing the building blocks from which project-wide traceability can be established between feature requests, bug fixes, commits, source code, and tests. We analyzed seven large open source projects to investigate to what extent developers explicitly established traces between issues and commits. Therefore, we categorized resolved issues and commits and studied the traces between the resulting artifact clusters. Among other metrics, our research shows, that 70% of all resolved issues are linked to commits. However, in the opposite direction, only 48% of the commits are linked to issues. Thus, open-source developers actively establish traceability. Nevertheless, automated traceability techniques might increase the amount of interlinking.en
dc.language.isoen
dc.publisherGeselllschaft für Informatik e.V.
dc.relation.ispartofSoftwaretechnik-Trends Band 38, Heft 1
dc.titleState of the Art of Traceability in Open-Source Projectsen
dc.typeJournal Articles
dc.pubPlaceBonn
mci.reference.pages8-11
mci.conference.sessiontitleFG ARC: Workshop des Arbeitskreises "Traceability/Evolution", 27.10.2017, Technische Universität Ilmenau


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige