Deliverable Name | Translations | ![]() |
||||||||||||||
System Designs |
|
|||||||||||||||
Keywords | ||||||||||||||||
Use-Case Realization, Design Model, Classes, Subsystems, Interfaces, Protocols, Data Model | ||||||||||||||||
Description | ||||||||||||||||
A System Design document captures the detailed system design of the system or a sub-system. It does so by describing a Design Model and how that model realizes the individual use-cases of the system/sub-system. The Design Model is described in terms of subsystems, classes/objects, interfaces, protocols, data models, etc. The Design Model is usually not described in detail in a regular word-processing document. Instead, special tools for software analysis and design are used. |
||||||||||||||||
Approval | ||||||||||||||||
The person responsible for Project Technology approves System Design documents. |
Recommended Storage | Timing | Responsibility | ||
\<Client>\<Project>\Xtra\<Sub System>\ | Production | |||
Templates | Important input from | Important input to | ||
|
|