A Systematic Review on Code Clone Detection

Ain, Qurat Ul; Butt, Wasi Haider; Anwar, Muhammad Waseem; Azam, Farooque; Maqbool, Bilal

doi:10.1109/access.2019.2918202

Cited by 109 publications

(58 citation statements)

References 69 publications

(136 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Moreover, to not miss any relevant studies, backward snowballing technique has also been applied by tracking the references of the selected studies. Furthermore, software project scope definition elements have been searched manually and using the SLR from 1994 to 2020 in well-renowned repositories, therefore according to some existing recent SLR studies, the used electronic data sources are sufficient to generalize the results of the study [122]- [132]. Further, the framework has not been statistically validated therefore, using Structural Equation Modeling (SEM) for statistically validating the framework using a larger number of experts would be fruitful for future research.…”

Section: Discussionmentioning

confidence: 99%

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Hassan

Asghar

2021

IEEE Access

View full text Add to dashboard Cite

Software project scope definition is complicated due to the diversity and magnitude of the information needed. An inadequate scope definition often results in project failure as it continues to emerge as the major cause of delays, changes/rework, and cost and schedule overruns. Literature mentions different tools and methods to verify, quantify, and control software scope definition. However, none of these methods and tools help in defining a complete scope. Since a well-defined scope in the early stages is a core ingredient for project success, therefore, previously we developed a method that includes 45 elements of the software project scope definition. Although these elements are noteworthy for project scope, some may influence others; and should be concentrated on more when defining the scope of the software projects. The objective of this present study is that it builds on our previous research and uses Interpretive Structural Modeling (ISM) to extract the interrelationships among the elements and Decision Making Trial and Evaluation Laboratory (DEMATEL) to determine the intensity of these relationships. Experts from academia and the software development industry were consulted to identify the relationships among the elements. ISM-DEMATEL approach indicates that the project manager's competence is the main driver. Further, requirements, stakeholders' expectations, cost estimates, project schedule, resource estimation, project summary, communication, consultation, top management support are among the most influential elements that are critical to focus on. Moreover, the findings of the study provide project managers with a better understanding of the elements and their interconnections thus, helping in achieving a better scope definition.INDEX TERMS Interpretive structural modeling (ISM), decision making trial and evaluation laboratory (DEMATEL), scope definition, scope elements, scope management, software projects.

show abstract

Section: Discussionmentioning

confidence: 99%

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Hassan

Asghar

2021

IEEE Access

View full text Add to dashboard Cite

show abstract

“…As mentioned by Chénard et al and Fenske et al the use of CCD techniques can help to achieve this. Even though, the CCD community provides plenty of CCD tools [2,8,19,44,49] the use of CCD tools found little application in the MDD domain so far to extract information from reference applications. Most frameworks in the MDD domain focus on either a single GPL or domain.…”

Section: Related Workmentioning

confidence: 99%

“…Similar code parts of different kinds can be detected by CCD tools. Since the code clone detection community is very active, plenty of such tools for the popular GPLs and markup languages (ML) are available [2,19]. The code clones based on textual similarity are categorised into three types.…”

Section: Step 2: Clustering Of Reference Applicationsmentioning

confidence: 99%

Mining of DSLs and generator templates from reference applications

Rost

2020

Proceedings of the 23rd ACM/IEEE International Conference on Model Driven Engineering Languages and Systems: Companion Proceedi

View full text Add to dashboard Cite

Domain-Specific Languages (DSLs) found application in different domains. The development of Model-Driven Development (MDD) components is facilitated by a wealth of frameworks like EMF, Xtext, and Xtend. However, the development of the necessary IDE components still can take up to several weeks or even months until it can be used in a production environment. The first step during the development of such an MDD infrastructure is to analyse a set of reference applications to deduce the DSL used by the domain experts and the templates used in the generator. The analysis requires technical expertise and is usually performed by MDD infrastructure developers, who have to adhere to a close communication with domain experts and are exposed to high cognitive load and time-consuming tasks. The objective of this PhD project is to reduce the initial effort during the creation of new MDD infrastructure facilities for either a new domain or newly discovered platforms within a known domain. This should be made possible by the (semi-)automatic analysis of multiple codebases using Code Clone Detection (CCD) tools in a defined process flow. Code clones represent schematically redundant and generic code fragments which were found in the provided codebase. In the process, the key steps include (i) choosing appropriate reference applications (ii) distinguishing the codebase by clustering the files, (iii) reviewing the quality of the clusters, (iv) analysing the cluster by tailored CCD, and (v) transforming of the code clones, depending on the code clone type, to extract a DSL and the corresponding generator templates. CCS CONCEPTS • Information systems → Clustering; • Software and its engineering → Domain specific languages; Model-driven software engineering.

show abstract

“…I N the field of software development, programmers prefer to copy and paste a piece of source code directly from another source code fragment, even if there are minor modifications, so that they look similar or even identical. This is called software/code cloning [1], [2], some researchers also call it code duplication [3]- [5]. Many reasons exist for code cloning; the main reason is that code clones can help programmers to finish their tasks more quickly.…”

Section: Introductionmentioning

confidence: 99%

A Survey of Software Clone Detection From Security Perspective

Zhang

Sakurai

2021

IEEE Access

View full text Add to dashboard Cite

In software engineering, if two code fragments are closely similar with minor modifications, or even identical as a result of copy-paste behavior, they are called software/code clones. Code clones can cause trouble in software maintenance and the debugging process because identifying all copied compromised code fragments in other locations is time-consuming. Researchers have been studying code clone detection issues for a long time, and the discussion mainly focuses on software engineering management and system maintenance. Another considerable issue is that code cloning provides an easy way for attackers to maliciously inject code. A thorough survey of code clone identification/detection from the security perspective is indispensable for providing a comprehensive review of previous related studies and proposing potential research directions. This paper satisfies the above requirements. We review and introduce previous security-related studies following three classifications and various comparison criteria. We then discuss three further research directions: (i) deep learning-based code clone vulnerability detection, (ii) vulnerable code clone detection for 5G-Internet of Things devices, and (iii) real-time detection methods for more efficiently detecting clone attacks. These methods are more advanced and adaptive to technological development and still have sufficient research space for future studies.

show abstract

A Systematic Review on Code Clone Detection

Cited by 109 publications

References 69 publications

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Mining of DSLs and generator templates from reference applications

A Survey of Software Clone Detection From Security Perspective

Contact Info

Product

Resources

About