Software bertillonage: Finding the provenance of an entity

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2011, Pages 183-192

  Davies, Julius ^a   German, Daniel M ^a   Godfrey, Michael W ^b   Hindle, Abram ^c  

^a UNIVERSITY OF VICTORIA   (Canada)

^b UNIVERSITY OF WATERLOO   (Canada)

^c University of California   (United States)

Author keywords

bertillonage; code evolution; code fingerprints; provenance

Indexed keywords

19TH CENTURY; BERTILLONAGE; CODE EVOLUTION; CODE FINGERPRINTS; DEPLOYED SOFTWARE; DEVELOPMENT TEAMS; ETHICAL CONCERNS; FACT EXTRACTION; FLOW GRAPH; FORENSIC ANALYSIS; HISTORICAL ANALYSIS; JAVA APPLICATIONS; JAVA LIBRARY; OPEN SOURCES; PROVENANCE; SIGNATURE-MATCHING; SOFTWARE ASSETS; SOFTWARE CLONE DETECTION; SOFTWARE ENTITIES; SOURCE CODES; STRING MATCHING; VERSION INFORMATION;

CLONING; LIBRARIES;

JAVA PROGRAMMING LANGUAGE;

EID: 79959275002     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1985441.1985468     Document Type: Conference Paper

References (16)

1. PCI Security Standards Council, "Payment Card Industry Data Security Standard (PCI DSS), Version 1.2.1," https://www.pcisecuritystandards.org/ security standards, July 2009.
2. J. Siegel, P. Saukko, and G. Knupfer, Encyclopedia of Forensic Sciences. Academic Press, 2000.
3. M. M. Houck and J. A. Siegel, Fundamentals of Forensic Science. Academic Press, 2006.
4. M. Godfrey and L. Zou, "Using origin analysis to detect merging and splitting of source code entities," IEEE Transactions on Software Engineering, vol. 31, no. 2, pp. 166-181, Feb. 2005.
5. J. Krinke, "Is cloned code more stable than non-cloned code?" in SCAM'08, 2008, pp. 57-66.
6. A. Lozano, "A methodology to assess the impact of source code flaws in changeability and its application to clones," in ICSM 08: Proc. of the Int. Conf. of Software Maintenance, 2008, pp. 424-427.
7. A. Lozano, M. Wermelinger, and B. Nuseibeh, "Evaluating the harmfulness of cloning: A change based experiment," in MSR '07: Proc. of the 4th Int. Workshop on Mining Soft. Repositories, 2007, p. 18.
8. S. Thummalapenta, L. Cerulo, L. Aversano, and M. Di Penta, "An empirical study on the maintenance of source code clones," Emp. Soft. Engineering, vol. 15, no. 1, pp. 1-34, 2009.
9. C. Kapser and M. W. Godfrey, "'Cloning considered harmful' considered harmful: Patterns of cloning in software," Empirical Software Engineering, vol. 13, no. 6, pp. 645-692, 2008.
10. M. Kim, V. Sazawal, D. Notkin, and G. Murphy, "An empirical study of code clone genealogies," ESEC/FSE, vol. 30, no. 5, pp. 187-196, 2005.
11. T. Kamiya, S. Kusumoto, and K. Inoue, "Ccfinder: A multilinguistic token-based code clone detection system for large scale source code," IEEE Trans. Software Eng., vol. 28, no. 7, pp. 654-670, 2002.
12. S. Livieri, Y. Higo, M. Matsushita, and K. Inoue, "Very-large scale code clone analysis and visualization of open source programs using distributed ccfinder: D-ccfinder," in ICSE, 2007, pp. 106-115.
13. D. M. Germán, M. Di Penta, Y.-G. Guéhéneuc, and G. Antoniol, "Code siblings: Technical and legal implications of copying code between applications," in MSR '09: Proc. of the Working Conf. on Mining Software Repositories, 2009, pp. 81-90.
14. R. Holmes, R. J. Walker, and G. C. Murphy, "Approximate structural context matching: An approach to recommend relevant examples," IEEE Trans. Soft. Eng., vol. 32, no. 12, pp. 952-970, 2006.
15. M. Di Penta, D. M. Germán, and G. Antoniol, "Identifying licensing of jar archives using a code-search approach," in MSR'10 Proc. of the Intl. Working Conf. on Mining Software Repositories, 2010, pp. 151-160.
16. A. Hemel, "The GPL Compliance Engineering Guide version 3.5," http://www.loohuis-consulting.nl/ downloads/compliance-manual.pdf, 2010.