Path: utzoo!attcan!uunet!ingr!jrk
From: jrk@ingr.UUCP (Robert Kennedy)
Newsgroups: comp.edu
Subject: Re: looking for cheating detectors
Message-ID: <2348@ingr.UUCP>
Date: 22 Jul 88 18:06:35 GMT
References: <1403@sbcs.sunysb.edu>
Reply-To: jrk@ingr.UUCP (Robert Kennedy)
Organization: Intergraph Corp. Huntsville, Al
Lines: 15

In article <1403@sbcs.sunysb.edu> paco@sbcs.sunysb.edu (Francisco J Romero) writes:
>
>  I am thinking of a line-counter, keyword-counter,
>  identifier-counter, loop-counter, etc combined together into a unique
>  program that provides a <degree of similarity>  among programs.  Maybe
>  there are more sophisticated ways of detecting cheaters I am not aware of.
>  Any help will be appreciated.                                           

Look at procedure and function call topology (number of parameters, when call
takes place, type of function result, other functions/procedures called, etc).
You could pretty easily write a C program to look for isomorphism between call
trees... This is a pretty good indicator, I would think.

Robert Kennedy
..!uunet!ingr!jrk