109 |
Design |
Design |
110 |
====== |
====== |
111 |
|
|
112 |
|
What can we link? |
113 |
|
|
114 |
|
- Perspectives to UML class diagrams, or classifiers in general: |
115 |
|
Cook and Daniels, Designing Object Systems: Object-Oriented Modeling |
116 |
|
with Syntropy. Prentice Hall, 1994. Referred in Fowler and Scott: UML distilled, |
117 |
|
2nd ed., Addison-Wesley. |
118 |
|
|
119 |
|
- Conceptual |
120 |
|
|
121 |
|
- probably no links |
122 |
|
|
123 |
|
- Specification |
124 |
|
|
125 |
|
- can link Java interfaces |
126 |
|
|
127 |
|
- Implementation |
128 |
|
|
129 |
|
- can link all classes |
130 |
|
|
131 |
|
- can be useful to link even concept with the class that eventually implemented |
132 |
|
it. |
133 |
|
|
134 |
|
|
135 |
|
|
136 |
Documentation's reader's point of view |
Documentation's reader's point of view |
137 |
--------------------------------------- |
--------------------------------------- |
138 |
|
|
153 |
+ "focus+context menu"-metaphor for diagrams needs that we can |
+ "focus+context menu"-metaphor for diagrams needs that we can |
154 |
"step back" from class documentation back to architecture |
"step back" from class documentation back to architecture |
155 |
documentation |
documentation |
156 |
|
Advantage over paper: SOME: see the contexts of a class, |
157 |
|
traverse them |
158 |
- step 3; backlinks to the architecture documentation |
- step 3; backlinks to the architecture documentation |
159 |
+ all this (UML and rerer backlinks) drawn into diagram for consistency |
+ all this (UML and rerer backlinks) drawn into diagram for consistency |
160 |
Advantage over paper: MAJOR: multi-end links easily traversable, |
Advantage over paper: MAJOR: multi-end links easily traversable, |