Supporting Refactoring Activities Using Histories of Program Modification

Authors:
Shinpei Hayashi;Motoshi Saeki;Masahito Kurihara
Affiliations:
The authors are with the Department of Computer Science, Graduate School of Information Science and Engineering, Tokyo Institute of Technology, Tokyo, 152--8552 Japan. E-mail: hayashi@se.cs.titech ...;The authors are with the Department of Computer Science, Graduate School of Information Science and Engineering, Tokyo Institute of Technology, Tokyo, 152--8552 Japan. E-mail: hayashi@se.cs.titech ...;The author is with the Division of Computer Science, Graduate School of Information Science and Technology, Hokkaido University, Sapporo-shi, 060--0814 Japan.
Venue:
IEICE - Transactions on Information and Systems
Year:
2006

Citing 0
Cited 5

Supporting empirical studies by non-intrusive collection and visualization of fine-grained revision history

Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
Seven habits of a highly effective smell detector

Proceedings of the 2008 international workshop on Recommendation systems for software engineering
Extracting prehistories of software refactorings from version archives

LKR'08 Proceedings of the 3rd international conference on Large-scale knowledge resources: construction and application
Actively comparing clones inside the code editor

Proceedings of the 4th International Workshop on Software Clones
An interactive ambient visualization for code smells

Proceedings of the 5th international symposium on Software visualization

Quantified Score

Hi-index	0.00

Visualization

Abstract

Refactoring is one of the promising techniques for improving program design by means of program transformation with preserving behavior, and is widely applied in practice. However, it is difficult for engineers to identify how and where to refactor programs, because proper knowledge and skills of a high order are required of them. In this paper, we propose the technique to instruct how and where to refactor a program by using a sequence of its modifications. We consider that the histories of program modifications reflect developers' intentions, and focusing on them allows us to provide suitable refactoring guides. Our technique can be automated by storing the correspondence of modification patterns to suitable refactoring operations. By implementing an automated supporting tool, we show its feasibility. The tool is implemented as a plug-in for Eclipse IDE. It selects refactoring operations by matching between a sequence of program modifications and modification patterns.