1989
DOI: 10.1145/65738.65741
|View full text |Cite
|
Sign up to set email alerts
|

Automating the execution of student programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

1991
1991
2005
2005

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 26 publications
(6 citation statements)
references
References 0 publications
0
6
0
Order By: Relevance
“…Other methods used to collect students' work online include email [Dawson-Howe 1995] and requiring students to store their work in a specified folder [Isaacson and Scott 1989;Ghosh et al 2002].…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Other methods used to collect students' work online include email [Dawson-Howe 1995] and requiring students to store their work in a specified folder [Isaacson and Scott 1989;Ghosh et al 2002].…”
Section: Related Workmentioning
confidence: 99%
“…Tools and techniques to assist in the automatic testing of programs include the use of shell scripts [Isaacson and Scott 1989], copying submitted files to the teacher's filespace [Reek 1989], and transferring ownership of submitted files to the teacher [MacPherson 1997]. Since students' programs may exploit loopholes in the system (either accidentally or deliberately), automatic testing is often performed in a restricted environment designed to minimise the possibility of damage to the system [Cheang et al 2003;Hurst 1996].…”
Section: Related Workmentioning
confidence: 99%
“…This avoids security problems, but leaves a large burden on the instructor, because students will invariably make mistakes in the testing process, and submissions will require further evaluation without tools to assist in that process. MacPherson [6] simply transfers ownership of files from students to the instructor at an appropriate time, while Isaacson and Scott [8] require students to place files readable by the instructor in directories under the instructor's filestore. In this latter work, some limits are imposed on CPU time and file sizes, but both of these have minimal security features, and still require significant manual effort in terms of marking beyond efforts to compile and run the submitted programs.…”
Section: Discussionmentioning
confidence: 99%
“…Isaacson and Scott [8] use a C shell script for automating the compilation and testing of student programs against sets of test data once students have placed their program files in an appropriate directory structure. Similarly, Reek's TRY program [2] copies student programs into the instructor's filestore, runs them against sets of test input data, and produces a log file that can be used to provide feedback to students.…”
Section: Related Workmentioning
confidence: 99%
“…Other packages have been developed by, for instance, Collier at Northern Arizona University, Kay at UCLA, Isaacson and Scott at the University of Northern Colorado (Isaacson & Scott, 1989) and Reek at RIT (Reek, 1989). A major problem with most of these initiatives is that of security, and a decision was finally taken that local software was required.…”
Section: The Warwick Solution: Bossmentioning
confidence: 99%