| Design Document |
Article Index for Design |
Website Links For Design |
Information AboutDesign Document |
| CATEGORIES ABOUT DESIGN DOCUMENT | |
| documents | |
| software development | |
|
'']] A design document is a description of a Software product that a software designer writes in order to give a Software Development team an overall guidance of the architecture of the software project. It usually accompanies an architecture diagram and has pointers to the detailed feature specifications of smaller pieces of the design. A design document is practically required to coordinate a large team under a single vision. A design document needs to be stable reference, and outline all parts of the software and how they will work. The document should give a fairly complete description while maintaining a high-level view of the software. The Software Design Document (SDD) is a comprehensive Software Design model consisting of four distinct but interrelated activities: data design, architectural design, interface design, and procedural design. The SDD contains the following documents: # Data Design # Architecture Design # Interface Design # Procedural Design 1. The '' Data Design '' describes structures that reside within the software. Attributes and relationships between Data Object s dictate the choice of Data Structures . 2. The '' Architecture Design '' uses information flow characteristics, and maps them into the program structure. Transformation mapping method is applied to exhibit distinct boundaries between incoming and outgoing data. The Data Flow diagrams allocate control input, processing, and output along three separate modules. 3. The '' Interface Design '' describes internal and external program interfaces as well as the design of human interface. Internal and external interface design are based on the information obtained from the analysis model. 4. The '' Procedural Design '' describes structured programming concepts using graphical, tabular, and textual notations. These design mediums enable the designer to represent procedural detail that facilitates translation to code. This blueprint for implementation forms the basis for all subsequent software engineering work. There are two kinds of design documents: HLDD - High Level Design Document and LLDD - Low Level Design Document For Game Design , the document will often be between 50-200 pages. |
|
|