Project Turnin Procedures

You do not need to submit a detailed description of everything you did for the project. One partner does need to submit your binary and source code by the due date to the Catalyst Dropbox

Your turnin should be a zip file containing two folders:

• binary

  In this folder, you will place:

  1. Your binary (a.k.a., executable). You need to put the release version of your executable here.
  2. Any files needed by the executable.
  3. A README.txt file that lists anything "out of the ordinary" that you did for your project.

  You don't need to list requirements or standard bells and whistles. You do need to describe anything that lies outside of the range of options on the project web page and which you think merits consideration for extra credit. Also, if you did your development under Linux, please note that as well.

• source

  This is where you put all your source code. (Basically everything)

We will also need to submit your artifact separately through the artifact turnin page linked on the class home page for artifact turnins.

The grading will consist of a staff member running your project right out of the binary directory and stepping through the features. We will verify the timestamp of the executable. We will consult source code as needed.