DCDs are part of the use-case realizations and thus members of the UP Design Model.
Discipline | Artifact | Incep. | Elab. | Const. | Trans. |
---|---|---|---|---|---|
IterationÜ | I1 | E1..En | C1..Cn | T1..T2 | |
Business Modeling | Domain Model | s | |||
Requirements | Use-Case Model (SSDs) | s | r | ||
Vision | s | r | |||
Supplementary Specifications | s | r | |||
Glossary | s | r | |||
Design | Design Model | s | r | ||
SW Architecture Document | s | ||||
Data Model | s | r | |||
Implementation | Implementation Model | s | r | r | |
Project Management | SW Development Plan | s | r | r | r |
Testing | Test Model | s | r | ||
Environment | Development Case | s | r |
Inception— The Design Model and DCDs will not usually be started until elaboration because it involves detailed design decisions, which are premature during inception.
Elaboration— During this phase, DCDs will accompany the use-case realization interaction diagrams; they may be created for the most architecturally significant classes of the design.
Note that CASE tools can reverse-engineer (generate) DCDs from source code. It is recommended to generate DCDs regularly from the source code, to visualize the static structure of the system.
Construction— DCDs will continue to be generated from the source code as an aid in visualizing the static structure of the system.
18.224.68.28