Evaluating the relation between changeability decay and the characteristics of clones and methods

Lozano, Ángela; Wermelinger, Michel; Nuseibeh, Bashar

doi:10.1109/asew.2008.4686327

Cited by 14 publications

(9 citation statements)

References 20 publications

(28 reference statements)

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It was widely believed that cloned code is a code smell and many empirical studies of clone properties [20,21,26,36,15] have investigated differences between cloned and non-cloned code.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Searching for better configurations: a rigorous approach to clone evaluation

Wang

Harman

Jia

et al. 2013

Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering

131

105

View full text Add to dashboard Cite

Clone detection finds application in many software engineering activities such as comprehension and refactoring. However, the confounding configuration choice problem poses a widely-acknowledged threat to the validity of previous empirical analyses. We introduce desktop and parallelised cloud-deployed versions of a search based solution that finds suitable configurations for empirical studies. We evaluate our approach on 6 widely used clone detection tools applied to the Bellon suite of 8 subject systems. Our evaluation reports the results of 9.3 million total executions of a clone tool; the largest study yet reported. Our approach finds significantly better configurations (p < 0.05) than those currently used, providing evidence that our approach can ameliorate the confounding configuration choice problem.

show abstract

“…It was widely believed that cloned code is a code smell and many empirical studies of clone properties [20,21,26,36,15] have investigated differences between cloned and non-cloned code.…”

Section: Introductionmentioning

confidence: 99%

“…To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. ESEC/FSE '13, August [18][19][20][21][22][23][24][25][26]2013, Saint Petersburg, Russia Copyright 13 ACM 978-1-4503-2237-9/13/08 ...$15.00.…”

Section: Introductionmentioning

confidence: 99%

Searching for better configurations: a rigorous approach to clone evaluation

Wang

Harman

Jia

et al. 2013

Proceedings of the 2013 9th Joint Meeting on Foundations of Software Engineering

131

105

View full text Add to dashboard Cite

show abstract

“…There are several reports on the experiences of such code clone analyses on open source software [3], [6], [9], [10]. Recently, code clone detections and analyses have started to be applied to industrial software systems in companies [12]: however, few reports on industrial software systems are open to the public because of security or other kinds of reasons.…”

Section: Introductionmentioning

confidence: 97%

An Experience Report on Analyzing Industrial Software Systems Using Code Clone Detection Techniques

Yoshida

Higo

Kusumoto

et al. 2012

2012 19th Asia-Pacific Software Engineering Conference

View full text Add to dashboard Cite

A variety of application results of code clone detection and analysis has been reported. There are many reports of code clone detection and analysis on open source software whereas few reports on industrial systems are open to the public. This paper reports an experience of code clone analysis on a governmental project. In the project, a software system was developed by multiple Japanese vendors. We detected and analyzed code clones in the system, and found that there were many code clones in the project, however we concluded that the presence of the code clones did not have negative impacts on the maintenance of the system because of the following reasons: (1) when different modules are similar to each other in the design document, they also share many code clones in the source code;(2) code clones located in trusted modules, which are libraries maintained by one of the companies.

show abstract

“…Although using tools increases the reliability, by following the same protocol in all case studies and reducing possible bias, it also increases the chances of undetected problems in the data collection and analysis. However, these tools are the result of several iterations analyzing the evolution of clones [15,13,14] and therefore the number of undetected bugs should be low. Notice that choices in the experiment setup could affect significantly the types of clones found, and therefore their evolution.…”

Section: Threats To Validitymentioning

confidence: 99%

“…In previous work we measured changes and co-changes of methods while cloned vs. while not cloned [15], we compared the ease to change cloned methods vs. not-cloned-methods [13], and the relation between method characteristics and their ease to change [14]. Our previous work tried to find trends on the effect of clones in methods using measurements that depended on the periods cloned and not cloned of each method analyzed.…”

Section: Introductionmentioning

confidence: 99%

Tracking clones' imprint

Lozano

Wermelinger

2010

Proceedings of the 4th International Workshop on Software Clones

Self Cite

View full text Add to dashboard Cite

Cloning imprint is the lasting effect of cloning on applications. This paper aims to analyze the clone imprint over time, in terms of the extension of cloning, the persistence of clones in methods, and the stability of cloned methods. Such level of detail requires an improvement in the clone tracking algorithms previously proposed, which is also presented.We found that cloned methods are cloned most of their lifetime, cloned methods have a higher density of changes, and that changes in cloned methods tend to be customizations to the clone environment.

show abstract

Evaluating the relation between changeability decay and the characteristics of clones and methods

Cited by 14 publications

References 20 publications

Searching for better configurations: a rigorous approach to clone evaluation

Searching for better configurations: a rigorous approach to clone evaluation

An Experience Report on Analyzing Industrial Software Systems Using Code Clone Detection Techniques

Tracking clones' imprint

Contact Info

Product

Resources

About