Design Doc: Or how to translate for the Pure Programmer.

oXYnary

I have seen a few tuts on making Design Docs, but I guess I'm asking. Whats a good one that gives enough overview to describe the game, goals, and point system. As well how the file structure, plug ins and such work without getting to the degree that its a technical overview versus the game overview.

Any good examples? Having a disconnect between what I'm attempting to describe and what my programmer "wants" to know. Or how I write up the game outline and what he feels is important.

So the result would be:
"I understand what this game is, how it functions and gives me enough basis so I can at least begin organizing a programming framework"

PatrickL

Some suggested reading on the topic:

http://www.gamedev.net/topic/591941-question-on-design-docs-how-to/ and http://www.sloperama.com/advice.html

Specifically,
http://www.sloperama.com/advice/specs.htm
http://www.sloperama.com/advice/lesson13.htm

These helped me a lot when I was trying to set the appropriate tone in my design documentation.

arrangemonk

edit: nvm