Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!cmcl2!phri!roy
From: roy@phri.UUCP
Newsgroups: comp.edu
Subject: Re: Cheating on Programming Assignments
Message-ID: <2625@phri.UUCP>
Date: Tue, 31-Mar-87 08:52:10 EST
Article-I.D.: phri.2625
Posted: Tue Mar 31 08:52:10 1987
Date-Received: Sat, 4-Apr-87 04:14:22 EST
References: <248@rruxa.UUCP>
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 18

In article <248@rruxa.UUCP> gwl@rruxa.UUCP talks about ways to prevent
cheating on programming assignments.  In particular, what to do about
people who hand in their code and some faked output.

	When I was learning FORTRAN, our assignments were in the form of
"write a program which reads input in 1X,3F14.4 format and does foo to it."
When we were sure we had the program working, we would hand in our decks
and the prof would insert his own data cards and run the program.

	It's trivial to do the same thing today.  Tell each student to
prepare an executable file called, for example, assignment1 in his home
directory which the prof will then run using his own data set.
-- 
Roy Smith, {allegra,cmcl2,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016

"you can't spell deoxyribonucleic without unix!"