Design Document

The design document covers the same material as the refined pitches, bit in a more careful manner. The purpose of the design document is to lay out a consistent, shared vision for the final game. Though you will be turning in a version of the document early in your development cycle, the design document should continue to evolve throughout the project's lifetime. For this reason, we will be using the course wiki.

Your design document should contain the following information (as per the example):

Summary -- a punchy one-or-two sentences that roll up your vision for the game. (Mainly coolness and novelty.)
Gameplay -- some storyboarded scenarios that nail down the core gameplay. Include detailed descriptions of controls, player actions, and results.
Features -- pull out a list of features you know the game needs to have. Categorize by those that are Essential, those that are Nice to have, and those that you'll do if you have Extra time.
Techical -- plan your architecture; figure out what methods you'll use for various important pieces. This is mostly a notes-to-self section.
Schedule -- Week-by-week breakdown of where you want to be. Important details: your prototypes (Nov3), your demo version (Nov17), and the final version (Dec7).

Images

Images can be uploaded to the wiki by inserting an [[Image:something.png]] tag, then clicking that tag to go to an upload page. Since the Image: namespace is wiki-wide, please use a game-specific prefix on your images.