Prepare your Design Review Package
Review Phase 2
Today is the beginning of phase II, in which you'll develop the alpha version of your game. The alpha should implement your core architecture. You should create a goal stack that includes all phase II deliverables as well as all aspects of your game that are "architecturally significant" (Head First calls them three Q's of architecture):
Essential Use Cases: Identify the alpha use cases that form the core of your system. The alpha should be a small, playable game but you should not promise to include anything that is non-essential.
Things you do not understand: These are features or other aspects of your game that are high risk because of their ambiguity. For example, an underlying model that will be used in your game that you don't yet understand. Even if you don't plan to implement it in the alpha, it may have an impact on your architecture so you should resolve the ambiguity in this phase.
Things that may be hard to do: These are features or other aspects of your game that are high risk because they could be difficult to implement. For example, if you've never done any networking and your game is online and multi-player, you should (at least) do some networking "proofs of concept" to resolve the ambiguity during this phase. After you create your goal stack you should finish making plans for the coming week.
Review Rubrics for Upcoming Deliverables
Last Modified Tuesday, 02-Oct-2012 12:40:35 PDT