82 |
+ the javadoc output filestructure follows the |
+ the javadoc output filestructure follows the |
83 |
hierarchical tree structure of java packages and classes |
hierarchical tree structure of java packages and classes |
84 |
|
|
85 |
|
(Normal links):: |
86 |
|
|
87 |
|
reST <-> reST Alternate View |
88 |
|
|
89 |
|
this occurs, when the same diagram is |
90 |
|
explicitly referred in two or more architectural |
91 |
|
documents |
92 |
|
|
93 |
|
javadoc -> javadoc Alternate View? |
94 |
|
|
95 |
|
We can browse through all classes, which |
96 |
|
are part of the diagram. Inside the diagram |
97 |
|
only focusing changes. |
98 |
|
|
99 |
|
UML in javadoc -> reST Detail->Summary |
100 |
|
|
101 |
|
UML in reST -> Javadoc General->Spesific or Summary->Detail |
102 |
|
|
103 |
|
Trigg classifies the following type-pairs for bi-directional |
104 |
|
links, which can are interpreted oppositionally depending on |
105 |
|
the direction |
106 |
|
|
107 |
|
- Generalization/Specification |
108 |
|
- Abstraction/Example |
109 |
|
- Formalization/Application |
110 |
|
- Summarization/Detail |
111 |
|
- Simplification/Complication |
112 |
|
|
113 |
|
:: |
114 |
|
|
115 |
|
reST <-> javadoc Generalization/Specification |
116 |
|
|
117 |
soved issuas not affecting anymore |
soved issuas not affecting anymore |
118 |
---------------------------------- |
---------------------------------- |
119 |
|
|