In this project, you'll design and build a computer game. The details of the game are entirely up to you. The project planning and management are largely up to you. You will present your final game during the course exam period, Friday, December 17, 2004 at 2 PM. Your grade for the project will be based on the following:

• Process 30%: Use the tools and practices we have studied in class and document the process on your wiki.
  • Iterative development
  • Schedule major milestones
  • Weekly planning meeting
  • Risk analysis
  • Use feasibility analysis and prototyping
  • Work breakdown, Pert, and Gantt charts
  • Progress report every Thursday (~10 minutes) including an overview of progress and long terms goals, evaluation of the work you completed over the previous week, and plans for next week.
  • UML: Use cases, class and sequence diagrams for domain analysis, design, and software documentation
  • Testing: test early and often including unit test, integration tests, and playtests
  • Feature and code freezes for major milestones
  • Individual logs
  • CVS
• Design 30%: Use good object oriented design and design patterns; critique your design often and refactor when necessary. Document your design and code.
• Product 30%: Build a good game.
  • Are game objectives clear?
  • Is the interface intuitive?
  • Is the game easy to learn, hard to master?
  • Are the graphics good?
  • Is sound used well?
  • Is the concept good?
  • Is the game well implemented; e.g. no bugs, well tuned, good frame rate, etc.?
  • Is this a great game?
• Documents/presentations 10%
  • Concept presentation including class survey for feedback
  • Game spec
  • Alpha release/design review presentation including surveys for feedback on design and playtesting
  • Final presentation
  • Final report
  • User's guide