If someone was to put down on paper (uml I guess) the design of a simple platformer, what diagrams should be used. I have always had the trouble of figuring out how to document the different modules of a game and how they relate to each other. Any general suggestions?
http://www.gamedev.net/reference/list.asp?categoryid=23
There are design document articles in that link.
Looked over the topics on gamedev. I understand the structure behind the game desig doc, but was wondering what other tools are used? I am guessing uml class diagrams that show object hierarchies, but what other design formats are helpful? I have done designs before for shopping carts and such, but have never designed/built a complete software system such as a game.
I beleave games fit more in an creative process then other applications, functionality isn’t always(or almost never) kown ahead of time. this makes documentation difficuld I assume
You should think of your design doc as a living document. Get your overall design down. Then try to get a basic demo going. Just enough to get something on the screen. A lot of times this will save you hours of writing, because you can test something quickly to see if it will work. Go back and forth from design doc to programming. You just have to be careful not to overdue programming in an area that isn’t documented yet.