
Code cloning is the code fragment similar to one another in the form of semantics and syntax. In the software development process, it is reuse approach of existing code. While developing a new software version, all the software modules may not be altered or redevelop. Some existing modules are copied with or without modification introducing to the generation of code clones. This is done for saving the developers efforts and time. But there is an issue, if a bug is discovered in some code fragment, then such contents must be discovered by means of clone detectors, to avoid inclusion of such errors or bugs. Clones are made due to reuse approach and programming approach. Reuse approach contain simple reuse by copy/paste activity of design, functionalities and logic. Programming approach involves merging of two similar systems, system development with generative programming approach and delay in restructuring. Code is developed on distributed system. It is difficult to find out code clones on these systems. We need an effective way to detect the clones. Earlier research and tools developed till now can find only Type-I, Type-II and some part of Type-III clones. Detection of Type-IV clone estimates a challenge in current scenario. Some tools are very slow and take lot of time for comparing codes and also their precision is low. Thus they are limited to Type-I and Type-II clones. The tools oriented on PDG are able to find Type-III clones. Time required to detect the clones by existing tools is high due to large number of comparisons. This sets the basis as a metaphor for our current research. The motive of our approach is to reduce comparisons and improve precision. Our proposed method detects duplicate code in efficient way by using Decentralized Computing and Code reduction. Significant efforts are applied to address Type-III and various other clones that set challenging aspects in the research.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 5 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Top 10% |
