<?xml version="1.0" encoding="UTF-8"?>
<modsCollection xmlns="http://www.loc.gov/mods/v3">
<mods ID="Mondal-2020-A">
    <titleInfo>
        <title>A survey on clone refactoring and tracking</title>
    </titleInfo>
    <name type="personal">
        <namePart type="given">Manishankar</namePart>
        <namePart type="family">Mondal</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <name type="personal">
        <namePart type="given">Chanchal</namePart>
        <namePart type="given">K</namePart>
        <namePart type="family">Roy</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <name type="personal">
        <namePart type="given">Kevin</namePart>
        <namePart type="given">A</namePart>
        <namePart type="family">Schneider</namePart>
        <role>
            <roleTerm authority="marcrelator" type="text">author</roleTerm>
        </role>
    </name>
    <originInfo>
        <dateIssued>2020</dateIssued>
    </originInfo>
    <typeOfResource>text</typeOfResource>
    <genre authority="bibutilsgt">journal article</genre>
    <relatedItem type="host">
        <titleInfo>
            <title>Journal of Systems and Software, Volume 159</title>
        </titleInfo>
        <originInfo>
            <issuance>continuing</issuance>
            <publisher>Elsevier BV</publisher>
        </originInfo>
        <genre authority="marcgt">periodical</genre>
        <genre authority="bibutilsgt">academic journal</genre>
    </relatedItem>
    <abstract>Abstract Code clones, identical or nearly similar code fragments in a software system’s code-base, have mixed impacts on software evolution and maintenance. Focusing on the issues of clones researchers suggest managing them through refactoring, and tracking. In this paper we present a survey on the state-of-the-art of clone refactoring and tracking techniques, and identify future research possibilities in these areas. We define the quality assessment features for the clone refactoring and tracking tools, and make a comparison among these tools considering these features. To the best of our knowledge, our survey is the first comprehensive study on clone refactoring and tracking. According to our survey on clone refactoring we realize that automatic refactoring cannot eradicate the necessity of manual effort regarding finding refactoring opportunities, and post refactoring testing of system behaviour. Post refactoring testing can require a significant amount of time and effort from the quality assurance engineers. There is a marked lack of research on the effect of clone refactoring on system performance. Future investigations in this direction will add much value to clone refactoring research. We also feel the necessity of future research towards real-time detection, and tracking of code clones in a big-data environment.</abstract>
    <identifier type="citekey">Mondal-2020-A</identifier>
    <identifier type="doi">10.1016/j.jss.2019.110429</identifier>
    <location>
        <url>https://gwf-uwaterloo.github.io/gwf-publications/G20-113001</url>
    </location>
    <part>
        <date>2020</date>
        <detail type="volume"><number>159</number></detail>
        <detail type="page"><number>110429</number></detail>
    </part>
</mods>
</modsCollection>

%0 Journal Article
%T A survey on clone refactoring and tracking
%A Mondal, Manishankar
%A Roy, Chanchal K.
%A Schneider, Kevin A.
%J Journal of Systems and Software, Volume 159
%D 2020
%V 159
%I Elsevier BV
%F Mondal-2020-A
%X Abstract Code clones, identical or nearly similar code fragments in a software system’s code-base, have mixed impacts on software evolution and maintenance. Focusing on the issues of clones researchers suggest managing them through refactoring, and tracking. In this paper we present a survey on the state-of-the-art of clone refactoring and tracking techniques, and identify future research possibilities in these areas. We define the quality assessment features for the clone refactoring and tracking tools, and make a comparison among these tools considering these features. To the best of our knowledge, our survey is the first comprehensive study on clone refactoring and tracking. According to our survey on clone refactoring we realize that automatic refactoring cannot eradicate the necessity of manual effort regarding finding refactoring opportunities, and post refactoring testing of system behaviour. Post refactoring testing can require a significant amount of time and effort from the quality assurance engineers. There is a marked lack of research on the effect of clone refactoring on system performance. Future investigations in this direction will add much value to clone refactoring research. We also feel the necessity of future research towards real-time detection, and tracking of code clones in a big-data environment.
%R 10.1016/j.jss.2019.110429
%U https://gwf-uwaterloo.github.io/gwf-publications/G20-113001
%U https://doi.org/10.1016/j.jss.2019.110429
%P 110429

Markdown (Informal)

[A survey on clone refactoring and tracking](https://gwf-uwaterloo.github.io/gwf-publications/G20-113001) (Mondal et al., GWF 2020)

• A survey on clone refactoring and tracking (Mondal et al., GWF 2020)

ACL

• Manishankar Mondal, Chanchal K. Roy, and Kevin A. Schneider. 2020. A survey on clone refactoring and tracking. Journal of Systems and Software, Volume 159, 159:110429.