Software Design
Spring 2006


A few details about the final reports:

1) The final report is due at midnight on Thursday 4 May.
Please email it to me as a single document in PDF.  The
subject line of your email must be

Software Design Final Report

Also, please drop off a hard copy at my office by 10am on
Friday 5 May.

2) You will probably want to incorporate the material you
have already written into the final report, but you should
not turn in copies of the previous reports.  The final
report should be one coherent document.

3) For full credit, your report must have the elements
described in the project description document I gave you.
These are:

  * A final refinement of the design, including any changes
since the previous iteration and an explanation of why the change
occurred.

       (this section should include at least one UML diagram)

  * An analysis of the outcome.  Did you achieve your minimum
deliverable?  If not, why not?  Did you achieve your maximum
deliverable?  If so, what went right (that is, why was the project
easier to complete than you thought)?

  * A reflection on your design.  What was the best decision
that you made?  What would you do differently next time?

  * A reflection on the division of labor.  Were you able to
divide the project in a way that allowed the members of the team
to work independently and then integrate their work into a whole?

In addition, I would like you to include one section that was
not in the document I gave you (sorry):

  * Bug report: what was the most difficult bug you had to find?
How did the bug manifest itself?  What did you do to find it?
How long did it take?  What was the cause of the problem?  In
retrospect, what could you have done to find it faster?

4) Please include your code as an Appendix to the final report.
You should only include code you wrote.  If there is additional
code that you got from me or another source, you should mark
it clearly.

Please make an effort to format your printout so that it is readable.
Don't let lines of code or comments wrap around.  Use whitespace to
make the structure of the code clear.  Include appropriate comments.


Thank you.  If you follow these instructions carefully, it will
be easier for me to evaluate (and appreciate) your work.