Evaluation experiments on the detection of programming patterns using software metrics

Kontogiannis, Kostas

doi:10.1109/wcre.1997.624575

Cited by 84 publications

(60 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…However, this practice can complicate software maintenance and it has been suggested that too much cloned code is a risk, albeit the practice itself is not generally harmful [13]. Because of these problems, many approaches to detect cloned code have been developed [5,6,9,12,[16][17][18]21]. Empirical studies of cloned code have focused mainly on examining whether code clones are changed consistently [4,10,15,19].…”

Section: Introductionmentioning

confidence: 99%

Is Cloned Code More Stable than Non-cloned Code?

Krinke

2008

2008 Eighth IEEE International Working Conference on Source Code Analysis and Manipulation

111

View full text Add to dashboard Cite

This paper presents a study on the stability of cloned code. The results from an analysis of 200 weeks of evolution of five software system show that the stability as measured by changes to the system is dominated by the deletion of code clones. It can also be observed that additions to a systems are more often additions to non-cloned code than additions to cloned code. If the dominating factor of deletions is eliminated, it can generally be concluded that cloned code is more stable than non-cloned code.

show abstract

Section: Introductionmentioning

confidence: 99%

Is Cloned Code More Stable than Non-cloned Code?

Krinke

2008

2008 Eighth IEEE International Working Conference on Source Code Analysis and Manipulation

111

View full text Add to dashboard Cite

show abstract

“…Such clone classes are useful for further steps such as analysis or removal since they allow to treat the contained clones as a unit. Several approaches for the detection of clones exist, which are text-based [6,17], tokenbased [24,32], tree-based [10,31] and metric-based [30,35] clone detection. For detailed information on clone detection techniques and tools we refer to Roy et al [44].…”

Section: Background 21 Code Clonesmentioning

confidence: 99%

Code clones in feature-oriented software product lines

Schulze

Apel

Kästner

2010

Proceedings of the Ninth International Conference on Generative Programming and Component Engineering

View full text Add to dashboard Cite

Some limitations of object-oriented mechanisms are known to cause code clones (e.g., extension using inheritance). Novel programming paradigms such as feature-oriented programming (FOP) aim at alleviating these limitations. However, it is an open issue whether FOP is really able to avoid code clones or whether it even facilitates (FOP-related) clones. To address this issue, we conduct an empirical analysis on ten feature-oriented software product lines with respect to code cloning. We found that there is a considerable amount of clones in feature-oriented software product lines and that a large fraction of these clones is FOP-related (i.e., caused by limitations of feature-oriented mechanisms). Based on our results, we initiate a discussion on the reasons for FOP-related clones and on how to cope with them. We exemplary show how such clones can be removed by the application of refactoring.

show abstract

“…There are a lot of researches on clone detection and many tools have been developed [21][22][23][24][25][26][27].We could have used those tools instead of CCFinder.…”

Section: Smatmentioning

confidence: 99%

“…There are many literatures for detection of code clones and patterns [17,[21][22][23][24][25][26][27]. Some of those proposed metrics for the clones; however they have not been extended to the similarity of two large software systems.…”

Section: Related Workmentioning

confidence: 99%

Measuring Similarity of Large Software Systems Based on Source Code Correspondence

Yamamoto

Matsushita

Kobayashi

et al. 2005

Product Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. It is an important and intriguing issue to know the quantitative similarity of large software systems. In this paper, a similarity metric between two sets of source code files based on the correspondence of overall source code lines is proposed. A Software similarity MeAsurement Tool SMAT was developed and applied to various versions of an operating system(BSD UNIX). The resulting similarity valuations clearly revealed the evolutionary history characteristics of the BSD UNIX Operating System.

show abstract

Evaluation experiments on the detection of programming patterns using software metrics

Cited by 84 publications

References 14 publications

Is Cloned Code More Stable than Non-cloned Code?

Is Cloned Code More Stable than Non-cloned Code?

Code clones in feature-oriented software product lines

Measuring Similarity of Large Software Systems Based on Source Code Correspondence

Contact Info

Product

Resources

About