Software design description: Difference between revisions

Revision as of 21:36, 2 May 2019

Revision as of 20:13, 18 June 2019

Line 8:

#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 (computing)|interface design]]'' (''inappropriate link to "User Interface"'') describes internal and external program interfaces, as well as the design of the [[User interface design|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.