ACM Home Page
Please provide us with feedback. Feedback
A change-aware development environment by recording editing operations of source code
Full text PdfPdf (364 KB)
Source
International Conference on Software Engineering archive
Proceedings of the 2008 international working conference on Mining software repositories table of contents
Leipzig, Germany
SESSION: Bugs and changes table of contents
Pages 31-34  
Year of Publication: 2008
ISBN:978-1-60558-024-1
Authors
Takayuki Omori  Ritsumeikan University, Kusatsu, Japan
Katsuhisa Maruyama  Ritsumeikan University, Kusatsu, Japan
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 45,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1370750.1370758
What is a DOI?

ABSTRACT

Understanding a program and its evolution is not satisfied only by looking at a current snapshot of its source code. Thus, a developer often examines a sequence of its snapshots stored in repositories of versioning systems, and identifies differences between two successive snapshots. Unfortunately, such differences do not represent individual changes of the source code. This paper proposes a mechanism for recording all editing operations a developer has applied to source code on an integrated development environment. The paper also shows a running implementation of the mechanism built as an Eclipse plug-in, which is called OperationRecorder. The experimental results with a small-scale program substantiate that it has a practical use from the viewpoint of its performance.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
MySQL 5.0 Reference Manual, 9.5 Data Type Storage Requirements. http://www.mysql.com/.
 
2
T. Apiwattanapong, A. Orso, and M. J. Harrold. A differencing algorithm for object-oriented programs. In Proc. ASE'04, pages 2--13, 2004.
 
3
G. Canfora, L. Cerulo, and M. D. Penta. Identifying changed source code lines from version repositories. In Proc. MSR'07, page 14, 2007.
 
4
B. Fluri, M. Würsch, M. Pinzger, and H. C. Gall. Change distilling: Tree differencing for fine-grained source code change extraction. IEEE Trans. Softw. Eng., 33(11):725--743, 2007.
 
5
S. Horwitz. Identifying the semantic and textual differences between two versions of a program. In Proc. PLDI'90, pages 234--245, 1990.
 
6
M. Kim and D. Notkin. Program element matching for multi-version program analyses. In Proc. MSR'06, pages 58--64, 2006.
 
7
I. Neamtiu, J. S. Foster, and M. Hicks. Understanding source code evolution using abstract syntax tree matching. In Proc. MSR'05, pages 1--5, 2005.
 
8
S. Raghavan, R. Rohana, D. Leon, A. Podgurski, and V. Augustine. Dex: A semantic-graph differencing tool for studying changes in large code bases. In Proc. ICSM'04, pages 188--197, 2004.
 
9
R. Robbes. Mining a change-based software repository. In Proc. MSR'07, page 15, 2007.
 
10
T. Sager, A. Bernstein, M. Pinzger, and C. Kiefer. Detecting similar java classes using tree algorithms. In Proc. MSR'06, pages 65--71, 2006.
 
11
K. A. Schneider, C. Gutwin, R. Penner, and D. Paquette. Mining a software developer's local interaction history. In Proc. MSR'04, 2004.
 
12
W. Yang. Identifying syntactic differences between two programs. Software--Practice and Experience, 21(7):739--755, 1991.

Collaborative Colleagues:
Takayuki Omori: colleagues
Katsuhisa Maruyama: colleagues