IEICE TRANSACTIONS on Fundamentals
A Feature Analysis of Co-changed Code Clone by Using Clone Metrics
Summary :
Code clones are duplicated or similar code fragments, and they have been known as major entities affecting the software maintainability. Sometimes there are “co-changes” in pair of code clones: when a code fragment is changed, the clone of the fragment is also changed. Such a co-change is one of key event to discuss the successful management of code clone. This paper analyzes the trends of co-changed code clones by using the length and the content of code clones. The empirical results show that: (1) there would be a specific length of clone to be mostly co-changed (around 60-100 tokens), and (2) code clones without any “control flow keywords” have a higher possibility to be co-changed than the others.
- Publication
- IEICE TRANSACTIONS on Fundamentals Vol.E95-A No.9 pp.1498-1500
- Publication Date
- 2012/09/01
- Publicized
- Online ISSN
- 1745-1337
- DOI
- 10.1587/transfun.E95.A.1498
- Type of Manuscript
- Special Section LETTER (Special Section on Software Reliability Engineering)
- Category
Authors
Keyword
Latest Issue
Copyrights notice of machine-translated contents
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Cite this
Copy
Myrizki SANDHI YUDHA, Ryohei ASANO, Hirohisa AMAN, "A Feature Analysis of Co-changed Code Clone by Using Clone Metrics" in IEICE TRANSACTIONS on Fundamentals,
vol. E95-A, no. 9, pp. 1498-1500, September 2012, doi: 10.1587/transfun.E95.A.1498.
Abstract: Code clones are duplicated or similar code fragments, and they have been known as major entities affecting the software maintainability. Sometimes there are “co-changes” in pair of code clones: when a code fragment is changed, the clone of the fragment is also changed. Such a co-change is one of key event to discuss the successful management of code clone. This paper analyzes the trends of co-changed code clones by using the length and the content of code clones. The empirical results show that: (1) there would be a specific length of clone to be mostly co-changed (around 60-100 tokens), and (2) code clones without any “control flow keywords” have a higher possibility to be co-changed than the others.
URL: https://global.ieice.org/en_transactions/fundamentals/10.1587/transfun.E95.A.1498/_p
Copy
@ARTICLE{e95-a_9_1498,
author={Myrizki SANDHI YUDHA, Ryohei ASANO, Hirohisa AMAN, },
journal={IEICE TRANSACTIONS on Fundamentals},
title={A Feature Analysis of Co-changed Code Clone by Using Clone Metrics},
year={2012},
volume={E95-A},
number={9},
pages={1498-1500},
abstract={Code clones are duplicated or similar code fragments, and they have been known as major entities affecting the software maintainability. Sometimes there are “co-changes” in pair of code clones: when a code fragment is changed, the clone of the fragment is also changed. Such a co-change is one of key event to discuss the successful management of code clone. This paper analyzes the trends of co-changed code clones by using the length and the content of code clones. The empirical results show that: (1) there would be a specific length of clone to be mostly co-changed (around 60-100 tokens), and (2) code clones without any “control flow keywords” have a higher possibility to be co-changed than the others.},
keywords={},
doi={10.1587/transfun.E95.A.1498},
ISSN={1745-1337},
month={September},}
Copy
TY - JOUR
TI - A Feature Analysis of Co-changed Code Clone by Using Clone Metrics
T2 - IEICE TRANSACTIONS on Fundamentals
SP - 1498
EP - 1500
AU - Myrizki SANDHI YUDHA
AU - Ryohei ASANO
AU - Hirohisa AMAN
PY - 2012
DO - 10.1587/transfun.E95.A.1498
JO - IEICE TRANSACTIONS on Fundamentals
SN - 1745-1337
VL - E95-A
IS - 9
JA - IEICE TRANSACTIONS on Fundamentals
Y1 - September 2012
AB - Code clones are duplicated or similar code fragments, and they have been known as major entities affecting the software maintainability. Sometimes there are “co-changes” in pair of code clones: when a code fragment is changed, the clone of the fragment is also changed. Such a co-change is one of key event to discuss the successful management of code clone. This paper analyzes the trends of co-changed code clones by using the length and the content of code clones. The empirical results show that: (1) there would be a specific length of clone to be mostly co-changed (around 60-100 tokens), and (2) code clones without any “control flow keywords” have a higher possibility to be co-changed than the others.
ER -
English
