Your project document
=====================
Due Monday April 14, 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. 

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.

How difficult was it to take over code from the undergraduates.

Part 2.
=======
Analyze the quality of the system that you developed.
Answer the question: How well does your product implement the requirements?

Outline your testing strategy for the project.
See chapter 43 of the text book on ruthlesss testing.
What kind of regression testing did you use?

The entire document should not be longer than 5 pages.