Your project document
=====================
Due Wednesday December 10, 2008.

On the same date, turn in your team/self evaluation.
See file hitchhikers-couch-potatoes (same directory).

It is important that your code itself is appropriately documented.
In the project document you reflect on your project experience
and tell the story behind your project. There are two parts.

Part 1. 
=======
highlights the difficulties you had and motivates
your important design decisions. It also compares your original 
road map with the actual road taken by your project.

Go in greater depth with how you approach secret derivatives.
(Because we covered how to deal with classic derivatives in class and the midterm.)
Also cover classic derivatives but you may summarize those at high level.

Suggested outline:

Your general impression of the project: How did you experience it?

Difficulties you encountered. 
  How did you solve them. 
  Which approaches worked best for solving difficulties?

Important design decisions and their motivation.

Include a class dictionary covering our exchange languages and
an optional UML class diagram.

Your initial roadmap and the actual road taken.

Part 2.
=======
analyzes the quality of the system that you developed.

Answer the question: How well does your product implement the requirements?

Turn in your regression tests for your player in the appendix to your
project document.

The entire document, excluding the appendix,
should not be longer than 5 pages.