Code Similarities Beyond Copy &amp;amp; Paste

Juergens, Elmar; Deissenboeck, Florian; Hummel, Benjamin

doi:10.1109/csmr.2010.33

Cited by 46 publications

(59 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[5] This often leads to numerous duplicated code fragments so called clones-in large software systems. Cloning is problematic for software quality for several reasons:…”

Section: In-depth Analysismentioning

confidence: 99%

Economic Effect of Cloning on Software Maintenance

KaurGoraya¹,

Chela²

2012

IJAIS

View full text Add to dashboard Cite

Software maintenance accounts for the majority of the total life cycle costs of successful software systems. Half of the maintenance effort is not spent on bug fixing or adaptation to changes of the technical environment, but on evolving and new functionality. The demand of software's has increased with the development of technology and communication systems. With this the maintenance effects which is a vital factor. The software's are not identical if we contrast them with past, present and future, due to development of new programming languages and their principles. To improve the quality of any software, maintenance is must. Cloning in source code files makes it difficult to modify. Several models are designed to overcome this problem. This paper presents the extension of analytical cost model to evaluate the cloning. As the size and the complexity of software increase, it also becomes essential to develop high-quality software, costeffectively within a specified period. This paper presents a study on the cloned code, the large open source systems are used, various other new parameters are added to calculate clone.

show abstract

“…[5] This often leads to numerous duplicated code fragments so called clones-in large software systems. Cloning is problematic for software quality for several reasons:…”

Section: In-depth Analysismentioning

confidence: 99%

Economic Effect of Cloning on Software Maintenance

KaurGoraya¹,

Chela²

2012

IJAIS

View full text Add to dashboard Cite

show abstract

“…This does, however, not imply behavioural similarity. Type-4 clones [28], "wide miss" clones [20], and Simions [17] refer to the same phenomenon: behaviourally similar code fragments that have no common origin. Unlike cloned code, these fragments are likely to differ greatly in their structure [17].…”

Section: Related Workmentioning

confidence: 99%

“…Approaches to detect re-implementations therefore are constrained to resort to approximations. Second, previous work [9], [17] concludes that existing approaches, such as clone detection or random testing approaches [16], do not provide satisfactory results to detect re-implementations in practice.…”

Section: Introductionmentioning

confidence: 99%

“…Nevertheless, developers tend to re-implement existing functionality [18], [3], missing out on the benefits of reuse opportunities. Furthermore, this can result in the creation of "Simions" [17], independent reimplementations of existing functionality that do not share a common origin in terms of code. Simions have long term negative effects in the form of increased development and maintenance efforts.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Novel Approach to Detect Unintentional Re-implementations

Bauer

Jürgens²

2014

2014 IEEE International Conference on Software Maintenance and Evolution

View full text Add to dashboard Cite

Abstract-Unintentional re-implementation of existing functionality is an issue frequently reported in practice and causes increased efforts for development and maintenance. However, instances are hard to find with existing approaches. For practitioners, this increases maintenance risks, such as inconsistent bug fixing, and hinders quality improvement efforts. For researchers, this hinders a reliable quantification of the issue.We propose a pragmatic approach combining identifierbased concept location with static analysis to detect candidate re-implementations between two sets of source code. We present initial results from applying the approach to detect reimplementations of utility functionality present in libraries within a sample of Java projects.

show abstract

“…The presence of similar code also indicates the presence of a missed opportunity for reuse. [7] DEAD CODE Dead code is code that is never used. This code includes unused methods and variables.…”

Section: Duplicate Codementioning

confidence: 99%

Establishing Quantitative Software Metrics in Department of the Navy Programs

Johnson¹

2016

View full text Add to dashboard Cite

Code Similarities Beyond Copy & Paste

Cited by 46 publications

References 19 publications

Economic Effect of Cloning on Software Maintenance

Economic Effect of Cloning on Software Maintenance

A Novel Approach to Detect Unintentional Re-implementations

Establishing Quantitative Software Metrics in Department of the Navy Programs

Contact Info

Product

Resources

About