Various methods for Measuring Similarity and code clone detection
Keywords:
Code Clone, source code, duplicate fragments, problems and domain modelAbstract
Code clones means duplicate fragments of source code, have been identified as “a major source of faults, which means that duplicating can be a considerable problem during development and maintenance”. As a consequence, a large body of planned has been industrialized on how to prevent, or spot and remove code clones. The problem with code clones is that they are related only by their resemblance, i.e., implicitly rather than explicitly which makes it difficult to notice them. Therefore, changes like promotions or patches that are often meant to affect all clones in a similar way are frequently not applied to all of them uniformly. Code clone helps the developers from probable mistakes, to save time and exertion in planning the logic, to help in decoupling of classes or components and more important it reduces development cost. But identical code is generally considered as unwanted for number of reasons. Introduction of bad design and lack of good legacy structure or concept may be caused due to code clones. Probably the biggest problem in model clone detection is defining exactly what a model clone is just as for code clones a small part of a domain model of the “Library Management System”.
References
Störrle, Harald. "Effective and Efficient Model Clone Detection." Software, Services, and Systems. Springer International Publishing, 2015. 440-457.
Chen, Jian, et al. "Detecting Android Malware Using Clone Detection."Journal of Computer Science and Technology 30.5 (2015): 942-956.
Wyss-Coray, Anton, et al. "Biomarkers of aging for detection and treatment of disorders." U.S. Patent Application No. 13/575,437.
Ritu garg, et al. "Code Clone v/s Model Clones: Pros and Cons." International Journal of Computer Applications (0975 – 8887) Volume 89 – No 15, March 2014.
Patil, Ritesh V., et al. "Software code cloning detection and future scope development-Latest short review." Recent Advances and Innovations in Engineering (ICRAIE), 2014. IEEE, 2014.
B. Baker. “Finding Clones with Dup: Analysis of an Experiment." IEEE Transactions on Software Engineering. vol. 33. no. 9. pp. 608-621. 2007.
B. Baker. "On Finding Duplication and Near-Duplication in Large Software Systems", in Proceedings of the Second U’orking Conference on Reverse Engineering (WCRE 195). pp. 86-95. Toronto. Ontario. Canada. July 1995.
C .K. Roy. J.R. Cordy and R. Koschke, “Comparison and Evaluation of Code Clone Detection Techniques and Tools: A Qualitative Approach." Science of Computer Programming, vol.74. no. 7. pp. 470-495. May 2009.
Chao Liu. Chen ChenJiawei Han and Philip S. Yu.,"GPLAG: Detection of Software Plagiarism by Program Dependence Graph Analysis", In the Proceedings of the 13”’ ACM SIGKDD International Conference on Knowledge Discovery and Data Mining. pp. 872-881. Philadelphia. USA. August 2006.
EttoreMerlol. "Detection of Plagiarism in University Projects Using Metrics- based Spectral Similarity." In the Dagsmhl Seminar: Duplication, Redundancy, and Similaritv in Software. 2007.
Downloads
Published
How to Cite
Issue
Section
License

This work is licensed under a Creative Commons Attribution 4.0 International License.
Authors contributing to this journal agree to publish their articles under the Creative Commons Attribution 4.0 International License, allowing third parties to share their work (copy, distribute, transmit) and to adapt it, under the condition that the authors are given credit and that in the event of reuse or distribution, the terms of this license are made clear.
