| Document | Description |
|---|---|
| View Our Process | 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, 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 |
| See Our Design | Use good object oriented design and design patterns; critique your design often and refactor when necessary. Document your design and code |
| Download Product | 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? |
| Read Our Docs | 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 |
| Document | Description |
|---|---|
| CoolPresentations | Our presentations |
| CodeDocuments | How ever are we going to design our game...??? I got it! |
| GoodLinks | A page full of wonderful links for us to utilize |
| PlanDocuments | Lots of documents telling you what we're gonna do before we do it |
| PrototypeCountry | A list of our prototypes |
| To Do | A basic TODO list (meant for developers, not necessarily for graders) |
|
Topic ProjectThree . { |
|
Revision r1.9 - 06 Dec 2004 - 03:36 GMT - AaronArvey Parents: WebHome |
Copyright © 1999-2003 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback. |