ACM Home Page
Please provide us with feedback. Feedback
Facilitating software evolution research with kenyon
Full text PdfPdf (327 KB)
Source Foundations of Software Engineering archive
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering table of contents
Lisbon, Portugal
SESSION: Software evolution analysis table of contents
Pages: 177 - 186  
Year of Publication: 2005
ISBN:1-59593-014-0
Also published in ...
Authors
Jennifer Bevan  University of California, Santa Cruz, Santa Cruz, CA
E. James Whitehead, Jr.  University of California, Santa Cruz, Santa Cruz, CA
Sunghun Kim  University of California, Santa Cruz, Santa Cruz, CA
Michael Godfrey  University of Waterloo, Waterloo, Ontario, Canada
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 21,   Downloads (12 Months): 102,   Citation Count: 15
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1081706.1081736
What is a DOI?

ABSTRACT

Software evolution research inherently has several resource-intensive logistical constraints. Archived project artifacts, such as those found in source code repositories and bug tracking systems, are the principal source of input data. Analysis-specific facts, such as commit metadata or the location of design patterns within the code, must be extracted for each change or configuration of interest. The results of this resource-intensive "fact extraction" phase must be stored efficiently, for later use by more experimental types of research tasks, such as algorithm or model refinement. In order to perform any type of software evolution research, each of these logistical issues must be addressed and an implementation to manage it created. In this paper, we introduce Kenyon, a system designed to facilitate software evolution research by providing a common set of solutions to these common logistical problems. We have used Kenyon for processing source code data from 12 systems of varying sizes and domains, archived in 3 different types of software configuration management systems. We present our experiences using Kenyon with these systems, and also describe Kenyon's usage by students in a graduate seminar class.


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
Alonso, O., Devanbu, P., and Gertz, M., "Database Techniques for the Analysis and Exploration of Software Repositories," In MSR '04 {15}, pp. 37--41.
 
2
 
3
Belady, L. A. and Lehman, M. M., "A Model of Large Program Development," IBM Systems Journal, vol. 15(3), 1976, pp. 225--252.
 
4
 
5
Cederqvist, P., "Version Management with CVS" http://www.cvshome.org/docs/manual/
6
 
7
 
8
 
9
 
10
German, D., "Mining CVS Repositories, the softChange experience," In MSR '04 {15}, pp. 17--21.
 
11
12
13
 
14
 
15
Proc. 1st Int'l Workshop on Mining Software Repositories (MSR '04), Edinburgh, Scotland, U.K., May 25, 2004. ACM.
 
16
Proc. 2nd Int'l Workshop on Mining Software Repositories (MSR '05), St. Louis, MO, USA, May 17, 2005. ACM.
 
17
 
18
 
19
Zimmerman, T. and Weissgerber, P., "Preprocessing CVS Data for Fine-Grained Analysis," In MSR '04 {15}, pp. 2--6.
 
20

CITED BY  15

Collaborative Colleagues:
Jennifer Bevan: colleagues
E. James Whitehead, Jr.: colleagues
Sunghun Kim: colleagues
Michael Godfrey: colleagues