2010 6th Central and Eastern European Software Engineering Conference (CEE-SECR) 2010
DOI: 10.1109/cee-secr.2010.5783148
|View full text |Cite
|
Sign up to set email alerts
|

Clone detection: Why, what and how?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2014
2014
2016
2016

Publication Types

Select...
3
1
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 12 publications
0
4
0
Order By: Relevance
“…This can greatly increase the amount of time required to debug and release software. Perhaps even more costly are clone induced errors not located until the maintenance phase of software's life cycle [10] [11]. Therefore, since clones can impede the risk of quality and bugs, we accept they function as an external quality factor for metric validation.…”
Section: B Code Clonesmentioning
confidence: 99%
See 2 more Smart Citations
“…This can greatly increase the amount of time required to debug and release software. Perhaps even more costly are clone induced errors not located until the maintenance phase of software's life cycle [10] [11]. Therefore, since clones can impede the risk of quality and bugs, we accept they function as an external quality factor for metric validation.…”
Section: B Code Clonesmentioning
confidence: 99%
“…Mathur [11] defined three runtime cohesion metrics as an extension to the original LCOM-Henderson-Sellers metric:…”
Section: A Runtime Metricsmentioning
confidence: 99%
See 1 more Smart Citation
“…Duplicated code can be a source of maintenance problems [2], e.g., when a problem in the implementation needs to be corrected in multiple locations. Copied code also results in an unnecessarily large implementation that can be more difficult to understand.…”
Section: B Quality Modelmentioning
confidence: 99%