Determining the provenance of software artifacts

dc.contributor.authorGodfrey, M.
dc.contributor.authorDavis, J.
dc.contributor.authorGerman, D.
dc.contributor.authorHindle, Abram
dc.date.accessioned2025-05-01T02:06:28Z
dc.date.available2025-05-01T02:06:28Z
dc.date.issued2011
dc.descriptionSoftware clone detection has made substantial progress in the last 15 years, and software clone analysis is starting to provide real insight into how and why code clones are born, evolve, and sometimes die. In this position paper, we make the case that there is a more general problem lurking in the background: software artifact provenance analysis. We argue that determining the origin of software artifacts is an increasingly important problem with many dimensions. We call for simple and lightweight techniques that can be used to help narrow the search space, so that more expensive techniques - including manual examination can be used effectively on a smaller candidate set. We predict the problem of software provenance will lead towards new avenues of research for the software clones community.
dc.identifier.doihttps://doi.org/10.7939/r3-4rez-7475
dc.language.isoen
dc.rights.urihttp://creativecommons.org/licenses/by/4.0/
dc.subjectBertillonage
dc.subjectprovenance
dc.subjectcode evolution
dc.subjectcode fingerprints
dc.titleDetermining the provenance of software artifacts
dc.typehttp://purl.org/coar/resource_type/R60J-J5BD
ual.jupiterAccesshttp://terms.library.ualberta.ca/public

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
godfrey2011IWSC-provenance.pdf
Size:
208.7 KB
Format:
Adobe Portable Document Format