Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!spf
From: spf@clyde.UUCP
Newsgroups: comp.edu
Subject: Re: Cheating on Programming Assignments
Message-ID: <7917@clyde.ATT.COM>
Date: Tue, 31-Mar-87 14:28:22 EST
Article-I.D.: clyde.7917
Posted: Tue Mar 31 14:28:22 1987
Date-Received: Thu, 2-Apr-87 00:39:09 EST
References: <248@rruxa.UUCP>
Sender: lp@clyde.ATT.COM
Reply-To: spf@bonnie.UUCP (Steve Frysinger)
Organization: AT&T Bell Laboratories, Whippany NJ
Lines: 32

In article <248@rruxa.UUCP> gwl@rruxa.UUCP writes:
>
>          I have thought of a possible aid in solving this problem and I
>would like some opinions from others to determine if this is an appropriate
>step to take on this matter.  
>It would be very simple to require them to not only
>hand in a program listing with supporting output, but to also require them
>to hand in the source on a floppy disk so that I may actually subject them
>to my own test cases.  

Since my students are on a VM/CMS system (blech), my variation of this
is "testing by walking around".  Remember that you don't have to test
EVERYONE'S program; if the student considers it reasonably likely that
you'll test theirs, that's generally sufficient.  So in my case, I
tell them to hand in their compiler listing and data sets, and to keep the 
program in their directory (the compiler listing alarms syntax
errors, so I don't have to read for syntax too).  Then in lab, while
their working on the next project, and I'm walking around helping out,
I periodically ask to run someone's previous project with me there
(often providing my own test data to try and break notarious weak
spots, like boundary conditions or ridiculus input).  Since they don't
know if I'll run theirs or not, they are discouraged from "cheating"
or even lesser crimes.  I've caught one or two cheaters, but mostly
I find programs that work ONLY for my required test data, and break
otherwise.
  The floppy idea will work nicely, though I still recommend
occassionaly running the program IN THE STUDENT'S PRESENCE.
It's an enlightening experience to see someone else run your program
and react to your user interface (which I stress).

Cheers!
Steve