Content deleted Content added
m Reverted 1 edit by 59.96.70.56 (talk) to last revision by LilHelpa. (TW) |
|||
Line 3:
A '''software design description''' (a.k.a. '''software design document''' or '''SDD''') is a written description of a [[software]] product, that a software designer writes in order to give a [[software development]] team overall guidance to the architecture of the software project. An SDD usually accompanies an architecture diagram with pointers to detailed feature specifications of smaller pieces of the design. Practically, the description is required to coordinate a large team under a single vision, needs to be a stable reference, and outline all parts of the software and how they will work.
==Composition==
The SDD usually contains the following information:
#The ''[[Data-driven design|data design]]'' describes structures that reside within the software. Attributes and relationships between [[data object]]s dictate the choice of [[data structures]].
#The ''[[Software architecture|architecture design]]'' uses information flowing characteristics, and maps them into the program structure. The 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.
#The ''[[interface design]]'' describes internal and external program interfaces, as well as the design of human interface. Internal and external interface designs are based on the information obtained from the analysis model.
#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.
== IEEE 1016 ==
| |||