A common conceptual model for clone detection results

Kapser,; Harder,

doi:10.1109/iwsc.2012.6227870

Cited by 7 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…If tools are to be integrated from different vendors, an agreed way to document clones is required. RCF is a step towards a common format [44], but it does not address all needs [72]. A common conceptual model for clone information is a major challenge because of competing requirements (e.g., it should be both generic and efficient) [42].…”

Section: Clone Documentationmentioning

confidence: 99%

“…A common conceptual model for clone information is a major challenge because of competing requirements (e.g., it should be both generic and efficient) [42]. There has been some progress towards a unified model [72]. We expect real practical progress to happen, however, only if different research teams actually start to exchange data -and not just between two teams but among many teams.…”

Section: Clone Documentationmentioning

confidence: 99%

See 1 more Smart Citation

The vision of software clone management: Past, present, and future (Keynote paper)

Roy

Zibran

Koschke

2014

2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE)

View full text Add to dashboard Cite

Duplicated code or code clones are a kind of code smell that have both positive and negative impacts on the development and maintenance of software systems. Software clone research in the past mostly focused on the detection and analysis of code clones, while research in recent years extends to the whole spectrum of clone management. In the last decade, three surveys appeared in the literature, which cover the detection, analysis, and evolutionary characteristics of code clones. This paper presents a comprehensive survey on the state of the art in clone management, with in-depth investigation of clone management activities (e.g., tracing, refactoring, costbenefit analysis) beyond the detection and analysis. This is the first survey on clone management, where we point to the achievements so far, and reveal avenues for further research necessary towards an integrated clone management system. We believe that we have done a good job in surveying the area of clone management and that this work may serve as a roadmap for future research in the area

show abstract

Section: Clone Documentationmentioning

confidence: 99%

Section: Clone Documentationmentioning

confidence: 99%

The vision of software clone management: Past, present, and future (Keynote paper)

Roy

Zibran

Koschke

2014

2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE)

View full text Add to dashboard Cite

show abstract

“…Proposed formats aimed at standardizing tool output include Harder and Göde's Rich Clone Format (RCF) [8] and Duala-Ekoko et al's Clone Region Descriptor (CRD) [7]. Kapser et al [11] also presented a draft proposal for the setup of a unified clone model, and set up an online wiki at http://www.softwareclones.org/ucm [12] for discussion and further proposals, although we noted that the discussion forums on the wiki are unfortunately inactive.…”

Section: Incompatible Tool Output Formatsmentioning

confidence: 99%

Smelling out Code Clones: Clone Detection Tool Evaluation and Corresponding Challenges

Gauci

2015

Preprint

View full text Add to dashboard Cite

Software clones have been an active area of research for the past two decades. However, although numerous clone detection tools are now available, only a small fraction of the literature has focused on tool evaluation, and this is in fact still an open problem. This is mostly due to the fact that standard information retrieval metrics such as recall and precision require a priori knowledge of clones already in the system. Detection tools also typically have a large number of parameters which are difficult to fine-tune for optimal performance on a particular software system, and different outputs produced by different tools add to the complexity of comparing one tool to another. In this review, we further explore the reasons why tool evaluation is still an open challenge, and present the current tools and frameworks targeted at mitigating these problems, focusing on the current standard benchmarks used to evaluate modern clone detection tools, and also presenting a recent method aimed at finding optimal tool configurations.

show abstract

“…The Unified Clone Model (UCM) is the attempt to define a general model for code clones that is capable of representing the results of all commonly known clone detectors [6]. UCM is still in a draft state that was suggested by a workgroup of clone researchers and practitioners.…”

Section: Existing Clone Modelsmentioning

confidence: 99%

The limits of clone model standardization

Harder¹

2013

2013 7th International Workshop on Software Clones (IWSC)

Self Cite

View full text Add to dashboard Cite

Many tools for clone detection exist. Each has its own model of clones and its own data format. This makes it difficult to share results, compare detectors, and replicate existing studies. Although there have been attempts to provide unified clone models in the past, no widely accepted unified clone model and data format has emerged. This paper discusses challenges that may be the reason why this is the case. In this paper we suggest that existing specialized models should be kept and supplemented with one unified model that serves for exchange only.

show abstract

A common conceptual model for clone detection results

Cited by 7 publications

References 2 publications

The vision of software clone management: Past, present, and future (Keynote paper)

The vision of software clone management: Past, present, and future (Keynote paper)

Smelling out Code Clones: Clone Detection Tool Evaluation and Corresponding Challenges

The limits of clone model standardization

Contact Info

Product

Resources

About