ACM Home Page
Please provide us with feedback. Feedback
Software repository mining with Marmoset: an automated programming project snapshot and testing system
Full text PdfPdf (6.63 MB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 30 ,  Issue 4  (July 2005) table of contents
SESSION: Mining Software Repositories (MSR) table of contents
Pages: 1 - 5  
Year of Publication: 2005
ISSN:0163-5948
Also published in ...
Authors
Jaime Spacco  University of Maryland, College Park, MD
Jaymie Strecker  University of Maryland, College Park, MD
David Hovemeyer  University of Maryland, College Park, MD
William Pugh  University of Maryland, College Park, MD
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 47,   Citation Count: 5
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Most computer science educators hold strong opinions about the "right" approach to teaching introductory level programming. Unfortunately, we have comparatively little hard evidence about the effectiveness of these various approaches because we generally lack the infrastructure to obtain sufficiently detailed data about novices' programming habits.To gain insight into students' programming habits, we developed Marmoset, a project snapshot and submission system. Like existing project submission systems, Marmoset allows students to submit versions of their projects to a central server, which automatically tests them and records the results. Unlike existing systems, Marmoset also collects finegrained code snapshots as students work on projects: each time a student saves her work, it is automatically committed to a CVS repository.We believe the data collected by Marmoset will be a rich source of insight about learning to program and software evolution in general. To validate the effectiveness of our tool, we performed an experiment which found a statistically significant correlation between warnings reported by a static analysis tool and failed unit tests.To make fine-grained code evolution data more useful, we present a data schema which allows a variety of useful queries to be more easily formulated and answered.


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
CheckStyle. http://checkstyle.sourceforge.net, 2005.
 
2
CVS. http://www.cvshome.org. 2004.
 
3
Eclipse.org main page. http://www.eclipse.org, 2004.
4
5
6
 
7
 
8
JUnit, testing resources for extreme programming. http://junit.org, 2004.
 
9
Y. Liu, E. Stroulia, K. Wong, and D. German. Using CVS historical information to understand how students develop software. In Proceedings of the International Workshop on Mining Software Repositories, Edinburgh, Scotland, May 2004.
 
10
PMD. http://pmd.sourceforge.net, 2005.
11
 
12
K. A. Schneider, C. Gutwin, R. Penner, and D. Paquette. Mining a software developer's local interaction history. In Proceedings of the International Workshop on Mining Software Repositories, Edinburgh, Scotland, May 2004.
13


Collaborative Colleagues:
Jaime Spacco: colleagues
Jaymie Strecker: colleagues
David Hovemeyer: colleagues
William Pugh: colleagues