Simultaneous Modification Support based on Code Clone Analysis

Higo, Yoshiki; Ueda, Yuta; Kusumoto, Shoichi; Inoue, Katsuro

doi:10.1109/aspec.2007.44

Cited by 16 publications

(2 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A number of methodologies [15, 23, 24, 44, 45] and metric‐based tools such as CCShaper [22] and Aries [21] have been proposed for semi‐automated extraction of code clones as refactoring candidates. Several tools, such as Libra [46] and CnP [47], have been developed for providing support for simultaneous modification of code clones. Our work is neither on finding potential clones for refactoring nor on providing editing support to apply refactorings.…”

Section: Related Workmentioning

confidence: 99%

Conflict‐aware optimal scheduling of prioritised code clone refactoring

Zibran

Roy

2013

IET softw.

View full text Add to dashboard Cite

Duplicated or similar source code, also known as code clones, are possible malicious 'code smells' that may need to be removed through refactoring to enhance maintainability. Among many potential refactoring opportunities, the choice and order of a set of refactoring activities may have distinguishable effect on the design/code quality measured in terms of software metrics. Moreover, there may be dependencies and conflicts among those refactorings of different priorities. Addressing all the conflicts, priorities and dependencies, a manual formulation of an optimal refactoring schedule is very expensive, if not impossible. Therefore an automated refactoring scheduler is necessary to 'maximise benefit and minimise refactoring effort'. However, the estimation of the efforts required to perform code clone refactoring is a challenging task. This study makes two contributions. First, the authors propose an effort model for the estimation of code clone refactoring efforts. Second, the authors propose a constraint programming (CP) approach for conflict-aware optimal scheduling of code clone refactoring. A qualitative evaluation of the effort model from the developers' perspective suggests that the model is complete and useful for code clone refactoring effort estimation. The authors also quantitatively compared their refactoring scheduler with other wellknown scheduling techniques such as the genetic algorithm, greedy approaches and linear programming. The authors' empirical study suggests that the proposed CP-based approach outperforms other approaches they considered.

show abstract

Section: Related Workmentioning

confidence: 99%

Conflict‐aware optimal scheduling of prioritised code clone refactoring

Zibran

Roy

2013

IET softw.

View full text Add to dashboard Cite

show abstract

“…It generally gets a collection of source code as the input and generate the report of the locations of code clone fragments. CCFinder can also report the locations of code fragments for a specific query code fragments [9]. In the case study, we use the latter feature to locate the defective functions.…”

Section: Case Studiesmentioning

confidence: 99%

Finding similar defects using synonymous identifier retrieval

Yoshida

Hattori

Inoue

2010

Proceedings of the 4th International Workshop on Software Clones

Self Cite

View full text Add to dashboard Cite

When we encounter a defect in one part of a program, it is very important to find other parts of the program that may contain similar defects. In this paper, we propose a novel system to find similar defects in the large collection of source code. This system takes a code fragment containing a defect as the query input, and returns code fragments containing the same or synonymous identifiers which appear in the input fragment. Case studies with two open source systems and their defect data show the advantages of the proposed retrieval system, compared to the code-clone based retrievals.

show abstract

A metric‐based approach to identifying refactoring opportunities for merging code clones in a Java software system

Higo

Kusumoto

Inoue

2008

J. Softw. Maint. Evol.: Res. Pract.

Self Cite

View full text Add to dashboard Cite

A code clone is a code fragment that has other code fragments identical or similar to it in the source code. The presence of code clones is generally regarded as one factor that makes software maintenance more difficult. For example, if a code fragment with code clones is modified, it is necessary to consider whether each of the other code clones has to be modified as well. Removing code clones is one way of avoiding problems that arise due to the presence of code clones. This makes the source code more maintainable and more comprehensible. This paper proposes a set of metrics that suggest how code clones can be refactored. As well, the tool Aries, which automatically computes these metrics, is presented. The tool gives metrics that are indicators for certain refactoring methods rather than suggesting the refactoring methods themselves. The tool performs only lightweight source code analysis; hence, it can be applied to a large number of code lines. This paper also describes a case study that illustrates how this tool can be used. Based on the results of this case study, it can be concluded that this method can efficiently merge code clones. INTRODUCTIONAs the size and complexity of software systems increase, maintenance tasks become more difficult and burdensome. Maintenance of software systems is defined as the modification of a software product after delivery to correct faults, to improve performance or other attributes, or to adapt the products to a modified environment [1]. Arthur stated that only one-fourth to onethird of all life-cycle costs are attributed to software development and Yip and Lam reported that 67% of the life-cycle costs are expended in the operation-maintenance phase of the life cycle [2,3].It is generally thought that the presence of code clones is one factor that makes software maintenance more difficult. A code clone is a code fragment that has identical or similar source code fragments elsewhere in the code. If a code fragment with code clones is modified, it is necessary to consider whether each of the code clones should also be modified. To automatically detect code clones, several methods have been proposed and software tools have been implemented [4][5][6][7][8].Refactoring has recently received a lot of attention. Refactoring is a set of operations to improve the maintainability, understandability, or other attributes of a software system without changing its external behavior. A code clone is one of the typical Bad Smells in the refactoring process [9]. Code clone detection can be perceived as the identification of code fragments to be refactored. From a practical standpoint, it is difficult to identify the code clones that are to be merged. Some code clones are simply unmergeable, or, if they are merged, they make the source code less understandable. Usually, large-scale software systems have complicated intertwining logics that make it difficult to identify the code clones that can be merged and how best to merge them.In this paper, a new method for merging code clones is propo...

show abstract

Simultaneous Modification Support based on Code Clone Analysis

Cited by 16 publications

References 24 publications

Conflict‐aware optimal scheduling of prioritised code clone refactoring

Conflict‐aware optimal scheduling of prioritised code clone refactoring

Finding similar defects using synonymous identifier retrieval

A metric‐based approach to identifying refactoring opportunities for merging code clones in a Java software system

Contact Info

Product

Resources

About