There is no late policy for this course!
If you do not complete the report by the deadline, you will receive 0
You "may" be excused pending discussion with your TA
Now that your game is complete you are ready to write your final report. Your report should chronical the creation of each object used in your gamee. Interactions between objects should also be summarized. Given your report, another programmer should be able to recreate your game in a similar fashion without seeing the application. It is important that you use the language of the course and computer science in general to describe each detail of your game so that a fellow programmer may use it as a blueprint. Now that the application is finished, provide some rationale as to whether it was successful or not. Remember to include all details: what worked, what didn't, and what still needs to be done.
The following slides below describe a template for a rough Software Requirement Specification (SRS). The purpose of this document is to FULLY describe your game, enough so that another programmer would be able to implement it. Follow each section below carefully, and use the language of the course to describe your game.
A brief introduction to the game. This should give the reader the story, background, genre, gameplay style and any other pertinent information about your game.
Describe how you met the following requirements:
(use references to the classes section, example: see the collision method of the ball class)
Summarize the application:
(use references to any previous section)