ACM Home Page
Please provide us with feedback. Feedback
An Eclipse-based course project snapshot and submission system
Full text PdfPdf (114 KB)
Source OOPSLA workshop on eclipse technology eXchange archive
Proceedings of the 2004 OOPSLA workshop on eclipse technology eXchange table of contents
Vancouver, British Columbia, Canada
Pages: 52 - 56  
Year of Publication: 2004
Authors
Jaime Spacco  University of Maryland, MD
David Hovemeyer  University of Maryland, MD
William Pugh  University of Maryland, MD
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 13,   Citation Count: 3
Additional Information:

abstract   references   cited by   collaborative colleagues  

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

ABSTRACT

Much research has been done on techniques to teach students how to program. However, it is usually difficult to quantify exactly how students work. Instructors typically only see students' work when they submit their projects or come to office hours. Another common problem in introductory programming courses is that student code is only subjected to rigorous testing once it has been submitted. Both of these problems can be viewed as a lack of feedback between students and instructors.We have built an Eclipse plugin to address this lack of feedback. The plugin has two main functions. First, it captures, to a central CVS repository, the complete state of a student's project every time he or she saves, adds, or removes a file. This produces a fine-grained history of the evolution of each student's project. Second, the plugin allows the student to submit his or her project to a central server. The submit server automatically compiles and performs limited testing of the student's submission, providing feedback on how close the project is to fulfilling the project requirements.Our goal is to provide instructors and researchers with far more detailed information about how students learn and work, and provide feedback to students that will help them focus on achieving the goals of the projects we assign.


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
 
2
CVS. http://www.cvshome.org, 2004.
3
 
4
M. Kölling, B. Quig, A. Patterson, and J. Rosenberg. The BlueJ system and its pedagogy. Journal of Computer Science Education, 13(4), December 2003.
 
5
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.
6
7
8

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