What do we need to know about clones? deriving information needs from user goals

2015 IEEE 9th International Workshop on Software Clones, IWSC 2015 - Proceedings

Volumn , Issue , 2015, Pages 51-57

  Basit, Hamid Abdul ^a   Hammad, Muhammad ^b   Jarzabek, Stan ^c   Koschke, Rainer ^d  

^a LAHORE UNIVERSITY OF MANAGEMENT SCIENCES   (Pakistan)

^b Punjab Information Technology Board   (Pakistan)

^c FAST NU   (Pakistan)

^d UNIVERSITY OF BREMEN   (Germany)

Author keywords

[No Author keywords available]

Indexed keywords

BUG LOCALIZATIONS; CLONE DETECTION; PLAGIARISM DETECTION; PROGRAM UNDERSTANDING; REFACTORINGS; USER GOALS;

CLONING;

EID: 84927914689     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/IWSC.2015.7069891     Document Type: Conference Paper

References (50)

1. R. Koschke, Survey of research on software clones, in Duplication, Redundancy, and Similarity in Software, ser. Dagstuhl Seminar Proceedings, no. 06301, 2006.
2. C. K. Roy, M. F. Zibran, and R. Koschke, The vision of software clone management: Past, present and the future, in IEEE Conference on Software Maintenance, Reengineering and Reverse Engineering (CSMR-WCRE), 2014 Software Evolution Week, 2014, pp. 18-33.
3. C. K. Roy, J. R. Cordy, and R. Koschke, Comparison and evaluation of code clone detection techniques and tools: A qualitative approach, Journal of Science of Computer Programming, vol. 74, no. 7, pp. 470-495, May 2009.
4. D. Rattana, R. Bhatiab, and M. Singh, Software clone detection: A systematic review, Information and Software Technology, vol. 55, no. 7, pp. 1165-1199, Jul. 2013.
5. R. Koschke, I. Baxter, M. Conradt, and J. R. Cordy, Software clone management towards industrial application, in Dagstuhl Seminar: Software Clone Management Towards Industrial Application, 2012.
6. J. H. Johnson, Identifying redundancy in source code using fingerprints, in Conference of the Centre for Advanced Studies on Collaborative research, 1993, pp. 171-183.
7. H. A. Basit and S. Jarzabek, Data mining approach for detecting higher-level clones in software, IEEE Trans. Softw. Eng., vol. 35, no. 4, pp. 497-514, Apr. 2009.
8. Y. S. Ma and D. K. Woo, Applying a code clone detection method to domain analysis of device drivers, in Asia-Pacific Software Engineering Conference, 2007, pp. 254-261.
9. A. Chou, J. Yang, B. Chelf, S. Hallem, and D. R. Engler, An empirical study of operating system errors, in Symposium on Operating Systems Principles, 2001, pp. 73-88.
10. Z. Li, S. Lu, S. Myagmar, and Y. Zhou, Copy-paste and related bugs in large-scale software code, IEEE Trans. Softw. Eng., vol. 32, no. 3, pp. 176-192, Mar. 2006.
11. E. Juergens, F. Deissenboeck, B. Hummel, and S. Wagner, Do code clones matter? in Int. Conference on Software Engineering, 2009.
12. E. Juergens, B. Hummel, F. Deissenboeck, and M. Feilkas, Static bug detection through analysis of inconsistent clones, in Testmethoden fur Software (TESO), 2008.
13. S. Bazrafshan, R. Koschke, and N. Göde, Approximate code search in program histories, in Working Conference on Reverse Engineering, 2011, pp. 109-118.
14. J. Li and M. Ernst, CBCD: Cloned buggy code detector, in Int. Conference on Software Engineering, 2012.
15. J. Jang, A. Agrawal, and D. Brumley, ReDeBug: Finding unpatched code clones in entire OS distributions, in Symposium on Security and Privacy, 2012.
16. E. Juergens, F. Deissenboeck, C. Domann, M. Feilkas, B. Hummel, B. Schaetz, J. Streit, and S. Wagner, Can clone detection support quality assessments of requirements specifications? in Int. Conference on Software Engineering, 2010.
17. M. Fowler, Refactoring: Improving the Design of Existing Code. Addison-Wesley, 2000.
18. W.-K. Chen, B. Li, and R. Gupta, Code compaction of matching singleentry multiple-exit regions, in Int. Conference on Static analysis, 2003, pp. 401-417.
19. S. K. Debray, W. Evans, R. Muth, and B. De Sutter, Compiler techniques for code compaction, ACM Transactions on Programming languages and Systems, vol. 22, no. 2, pp. 378-415, 2000.
20. M. Godfrey and Z. Lijie, Using origin analysis to detect merging and splitting of source code entities, IEEE Trans. Softw. Eng., vol. 31, no. 2, pp. 166-181, Feb. 2005.
21. J. J. Hunt and W. F. Tichy, Extensible language-aware merging, in Int. Conference on Software Maintenance, 2002, pp. 511-520.
22. Y. Dubinsky, J. Rubin, T. Berger, S. Duszynski, M. Becker, and K. Czarnecki, An exploratory study of cloning in industrial software product lines, in Conference on Software Maintenance and Reengineering, 2013, pp. 25-34.
23. D. Faust and C. Verhoef, Software product line migration and deployment, Journal of Software: Practice and Experience, vol. 33, no. 10, pp. 933-955, 2003.
24. T. Mende, F. Beckwermert, R. Koschke, and G. Meier, Supporting the grow-and-prune model in software product lines evolution using clone detection, in Conference on Software Maintenance and Reengineering, 2008, pp. 163-172.
25. T. Mende and R. K. F. Beckwermert, An evaluation of code similarity identification for the grow-and-prune model, Journal on Software Maintenance and Evolution, vol. 21, no. 2, pp. 143-169, 2009.
26. R. Koschke, P. Frenzel, A. P. Breu, and K. Angstmann, Extending the reflexion method for consolidating software variants into product lines, Software Quality Journal, vol. 17, no. 4, pp. 331-366, 2009.
27. T. Ishihara, K. Hotta, Y. Higo, H. Igaki, and S. Kusumoto, Inter-project functional clone detection toward building libraries-an empirical study on 13, 000 projects, in Working Conference on Reverse Engineering, 2012, pp. 387-391.
28. M. Bruntink, A. V. Deursen, R. V. Engelen, and T. Tourwe, On the use of clone detection for identifying crosscutting concern code, IEEE Trans. Softw. Eng., vol. 31, no. 10, pp. 804-818, Oct. 2005.
29. M. Godfrey and Q. Tu, Tracking structural evolution using origin analysis, in Int. Workshop on Principles of Software Evolution, 2002, pp. 117-119.
30. M. W. Godfrey, D. M. German, J. Davies, and A. Hindle, Determining the provenance of software artifacts, in Int. Workshop on Software Clones, 2011, pp. 65-66.
31. D. M. German, M. Di Penta, G. Antoniol, and Y.-G. Gúehéneuc, Code siblings: Phenotype evolution, in Int. Workshop on Software Clones, 2009.
32. J. Davies, D. M. German, M. W. Godfrey, and A. Hindle, Software bertillonage: finding the provenance of an entity, in working conference on Mining Software Repositories, 2011, pp. 183-192.
33. E. Merlo, Detection of plagiarism in university projects using metricsbased spectral similarity, in Duplication, Redundancy, and Similarity in Software, ser. Dagstuhl Seminar Proceedings, no. 06301, 2006.
34. T. Kamiya, S. Kusumoto, and K. Inoue, CCFinder: a multilinguistic token-based code clone detection system for large scale source code, IEEE Trans. Softw. Eng., vol. 28, no. 7, pp. 654-670, 2002.
35. J. R. Pate, R. Tairas, and N. A. Kraft, Clone evolution: a systematic review, Journal of Software: Evolution and Process, vol. 25, no. 3, pp. 261-283, 2013.
36. B. Lague, D. Proulx, J. Mayrand, E. M. Merlo, and J. Hudepohl, Assessing the benefits of incorporating function clone detection in a development process, in Int. Conference on Software Maintenance, 1997, pp. 314-321.
37. G. Antoniol, G. Casazza, M. Di Penta, and E. Merlo, Modeling clones evolution through time series, in Int. Conference on Software Maintenance, 2001, pp. 273-280.
38. G. Antoniol, U. Villano, E. Merlo, and M. Di Penta, Analyzing cloning evolution in the Linux kernel, Information and Software Technology, vol. 44, no. 13, pp. 755-765, 2002.
39. M. Kim, V. Sazawal, D. Notkin, and G. Murphy, An empirical study of code clone genealogies, in ACM SIGSOFT Software Engineering Notes, vol. 30, no. 5, 2005, pp. 187-196.
40. Z. Li, S. Lu, S. Myagmar, and Y. Zhou, CP-Miner: Finding copy-paste and related bugs in large-scale software code, IEEE Trans. Softw. Eng., vol. 32, no. 3, pp. 176-192, 2006.
41. T. Lavoie, F. Khomh, E. Merlo, and Y. Zou, Inferring repository file structure modifications using nearest-neighbor clone detection, in Working Conference on Reverse Engineering, 2012, pp. 325-334.
42. S. Giesecke, Generic modelling of code clones, in Duplication, Redundancy, and Similarity in Software, ser. Dagstuhl Seminar Proceedings, no. 06301, 2006, pp. 1-23.
43. B. Lague, D. Proulx, J. Mayrand, E. M. Merlo, and J. Hudepohl, Assessing the benefits of incorporating function clone detection in a development process, in Int. Conference on Software Maintenance, 1997, pp. 314-321.
44. R. Koschke, Frontiers of software clone management, Frontiers of Software Maintenance, pp. 119-128, 2008.
45. J. Krinke, A study of consistent and inconsistent changes to code clones, in Working Conference on Reverse Engineering, 2007, pp. 170-178.
46. M. Toomim, A. Begel, and S. L. Graham, Managing duplicated code with linked editing, in Symposium on Visual Languages and Human Centric Computing, 2004, pp. 173-180.
47. A. Walenstein and A. Lakhotia, The software similarity problem in malware analysis, in Duplication, Redundancy, and Similarity in Software, ser. Dagstuhl Seminar Proceedings, no. 06301, 2006.
48. D. Bruschi, L. Martignoni, and M. Monga, Using code normalization for fighting self-mutating malware, in Int. Symposium on Secure Software Engineering, 2006, pp. 37-44.
49. D. Martin and J. R. Cordy, Analyzing web service similarity using contextual clones, in Int. Workshop on Software Clones, 2011, pp. 41-46.
50. P. Geesaman, J. Cordy, and A. Zouaq, Ontology alignment using bestmatch clone detection, in Int. Workshop on Software Clones, 2013.