Your V1.0 release is due on Tuesday 12/11/08. Your grade will depend on project deliverables and project management. The deliverables include the Game Design Document, Technical Design Document, and game folder.

1. Game Design Document: This document describes the game you've built and should include, as appropriate the following.
   • Marketing information such as target audience, platform, system requirements, and comparison to similar games.
   • Gameplay information including descriptions of how the game functions, interface, rules, scoring, win/loss conditions, modes and other features, levels, etc.
   • Character design including player's character and nonplayer characters.
   • Story
   • Game world including key locations, maps, modes of travel.
   • Media list including all art and sound.
   Note that this document should involve narrative, not bullet items. You should include screen shots, and images of art assets when appropriate.
2. Technical Game Spec: This document should describe the technical aspects of the game you built including following.
   • Overview of the design
   • Critique of the design with respect to design principles and patterns
   • Description of test plan, how it was carried out, and any known bugs
   • Description of important algorithms, e.g. collision detection
   • Use cases
   • Class diagrams
   • Sequence diagrams
   • Code
   As in the game design document, this should provide a narrative description and critique of the software; diagrams should be included as appendices.
3. Game Installation Folder: A zipped folder that includes the game executable, a README that explains installation procedures and requirements, and a Users' Manual.
4. Final Presentation

Project Management will be evaluated according to the following:

1. Goal Management: You should develop a goal description and breakdown for this project cycle including risk analysis, deadlines, and staffing. This is due on Tuesday Nov. 25.
2. Trac/wiki management: Your trac/wiki pages should be clear and well organized. They should give an immediate snapshot of the progress and current state of your project.
3. Personal logs: Each team member should maintain a personal log that is updated whenever a new ticket is assigned or when work associated with a ticket is performed. The log should provide a snapshot of the number of hours you spent on the project and how that time was spent.