CS642 Project Hand-In

Deadlines

What to Turn In

The following items are due on Sunday, December 19, at 11:59 PM (do not wait until the last week to get started):

• README file that describes what you have submitted.
  Think of this file as the "release notes." It should include instructions for building and testing, and a short writeup summarizing the structure of your code. If any features are unfinished or have remaining bugs for whatever reason, they should be mentioned here (as well as in the limitations section of your design document). Documented problems will be penalized less than undocumented problems.
• Final version of your design document.
  Make sure this includes:
  • A "Threat Model" section which explains how your project is secure against different kinds of attacks (man in the middle, replay, etc.) This is very important.
  • XML DTDs for your protocol.
• All your commented code and build files.
• Documentation for how to use your program (command-line syntax, etc).
  If you have implemented a GUI or web form based interface, this is probably less important if your GUI is intuitive.
• Several test cases for each major feature.
  The test cases should include any support files required to run the test cases to completion.
• Anything else you think is important.

Turn-In Procedure

• Create a tarball (i.e., a .tar.gz file) or a ZIP archive with all the files specified above.
• Name the resulting archive cs642-teamN.tar.gz or cs642-teamN.zip, where N is your team number. Your team number is listed here:
  1. Alex Fridgen, Andrego Halim, Jon Wedell
  2. Spencer Jones, Brian Snouffer, Andrew Martin
  3. Rehan Ahmed, Tzu-Han Chou
  4. Mike Choi, Chang Ho Choi, Philip Tilton
  5. Eliot Roush, Jason Tikalsky
  6. Aaron Brown, Ben Farley, Dan Szafir
  7. Wen Loong Goh, Graham Hoke, Jay Lim
  8. Jacob Kapellen, Mark Samuelson, In Young Cho
  9. Amanda Hittson, Fatemah Panahi, Pavithra Seshadri Vijayakrishnan
  10. Thomas Duffield, Zev Weiss, Li-hsiang Kuo
  11. Aditya Thakur, Rohit Koul
• Email the resulting archive to the TA, Sanjib Das, at the address sanjibkd@cs.wisc.edu.

Demonstration

Each team will need to schedule a time slot for a demonstration on the Doodle poll. During this demonstration, you will show your working program in action by demonstrating the major features. You should be prepared to answer questions as well about your code and design. The demonstration will influence your project grade significantly, so be well prepared.