Thomas Chestna provides an update on the Scrutiny plagiarism detection project. Key points include: - Scrutiny analyzes code structure and tokenizes files to create hashes for plagiarism detection across many languages. - Chestna has added the ability to ignore instructor-provided code and optimized tar file processing ahead of schedule. Support for back assignments is also complete. - A functional SQLite3 database has been implemented to store assignment hashes. Adding open source projects directly may no longer be feasible due to the database design. - Remaining work includes adding removal of assignments from the database, along with optimizations, safety checks, and security improvements. Feedback is welcomed on the project status.

1. Scrutiny Update
Thomas Chestna
RCOS Summer 2011
7/29/2011

2. Recap: What is Scrutiny?
Open source plagiarism detection for software
code.
Tokenizes input files and creates hashes
based on structure of code.
Supports a vast multitude of languages.
Original idea by Rob Escriva who has been
mentoring me on this project.

3. What was my schedule?
th
By July 8 support for ignoring instructor
provided code.
nd
By July 22 a functional database
implementation will be completed.
By the end of the month support for running
against back assignments will be completed.
August will be spent adding several open
source projects to the database and
functionality to be hosted on a server.

4. So where am I now?
The ability to ignore instructor code.
Various fixes in output file. “#include <string>”
now shows as it should.
The processing of tar files has been sped up
due to optimization.
Support for back assignments has also been
added.

5. And more!
In addition the support of a database is now
complete.
Database implimented using sqlite3 because
its in the python standard library and Scrutiny's
needs aren't that high.
Has the option to just add something straight
to the database without printing out
comparisons.

6. What's left?
Due to how the database works adding open
source projects from a distribution stand point
no longer seems to be a good idea.
Support for removing assignments from the
database will be added.
Various optimizations, safety checks, and
security.

7. Questions and suggestions?