RE: Design Documents

[Brad Broerman <bbroer@one.net>]

Well, a design document begins with a high level description of the 
application: what is is to do. From this, it describes the major systems / 
portions of the application, data flows, transactions, etc. Then, it would 
describe the design of these systems one by one, beaking them down into 
their components and data flows.
   Usually, at the medium and lower levels, we use flow charts and class 
diagrams to show the data flows, process flows, and the interfaces of the 
various components. Possibly some pseudo code could be used to describe the 
way that major functions in the components should work.
   The purpose of the design document is to put your thoughts down in 
writing, so that everyone on the team (including clients / management) are 
all on the same page, and so that everyone can agree on the final set of 
requirements. It also serves as a road map while coding is going on.

 I hope this helps...
-----Original Message-----
From:	Rob Quill [SMTP:rob@quills.madasafish.com]
Sent:	Tuesday, January 23, 2001 3:47 PM
To:	Gameprogrammer Mailing List
Subject:	Design Documents

Hi all,

Do any of you know what a design document looks like. Have you got any
examples??

Thanks,
Rob.

=================================================================
The GameProgrammer.Com mailing list is for the open discussion
of any topic related to the art, science, and business of
programming games. This list is especially tolerant of beginners.
We were all beginners once

To SUBSCRIBE or UNSUBSCRIBE please visit:
http://gameprogrammer.com/mailinglist.html

=================================================================
The GameProgrammer.Com mailing list is for the open discussion
of any topic related to the art, science, and business of
programming games. This list is especially tolerant of beginners.
We were all beginners once

To SUBSCRIBE or UNSUBSCRIBE please visit:
http://gameprogrammer.com/mailinglist.html