Please, select the article type as “ VSI: SWClones”, from the “Choose Article Type” pull-down menu during the submission process. Follow the submission instructions given on this site.
#Clone x 4en cloning software reviews software#
Hitesh Sajnani, Tools for Software Engineers (TSE), Microsoft ( )Ĭhaiyong Ragkhitwetsagul, Mahidol University, Thailand ( )Īll manuscripts and any supplementary material should be submitted through the Elsevier Editorial System at. Initial Author Revisions Due: 15 December 2020Īuthor Notifications for First Revision: 1 March 2021 Initial Author Notifications: 15 September 2020 Other applications of clone detection and analysis techniques
#Clone x 4en cloning software reviews code#
Security implications of software code cloning
Higher-level clones in models and designsĬlone-aware software design and development Source code clone detection supported by other development artifactsĬlone typologies: kinds, cause and effects, management strategies, etc.Ĭlone evolution and approaches to managing variationĬlone analysis in families of similar systems and software product linesĮconomic and trade-off models for clone managementĮffects of clones on system complexity and qualityĮvaluation and benchmarking of clone detection methods Similarity measures of source code and other development artifactsĬlone detection across multiple programming languagesĬlone detection applied to non-source code artifacts Use cases for clones and clone management in the software lifecycle Industrial experience with clones and clone management Techniques and studies of code clone search, detection, analysis, and management Topics of interest include, but are not limited to: Surveys and (Systematic) Literature Reviews are out of the scope of the special issue and will be desk-rejected. We also encourage submission of extended papers from the 14th International Workshop on Software Clones (IWSC 2020). We invite the submission of high-quality papers describing original and significant work in all areas of software clones including (but not limited to) new techniques in code clone detection, semantic clone detection, empirical clone studies, clone management, clone analysis. Nevertheless, it has been agreed in the clone research community that code clones need to be detected and an appropriate clone management process is required. There are also studies showing that cloned code is more stable than non-cloned code. However, recent studies also show that code clones are not always bad and can also be beneficial such as in the case of software product lines, or hardware variation. Software clone research is of high relevance for software engineering research and practice today.Ĭode clones are well-known as one of the code smells and a cause for bug propagation and increasing software maintenance cost. Software clones are often a result of copying and pasting as an act of ad-hoc reuse by programmers, and can occur at many levels, from simple statement sequences to blocks, methods, classes, source files, subsystems, models, architectures and entire designs, and in all software artifacts (code, models, requirements or architecture documentation, etc.).