44 |
|
|
45 |
\begin{abstract} |
\begin{abstract} |
46 |
We present a navigational aid for documentation used in software |
We present a navigational aid for documentation used in software |
47 |
development. Based on using readily-authored UML diagrams as |
development. Based on using human-made UML diagrams as |
48 |
multi-ended links, we hypertexturally connect two distinct areas |
multi-ended links, we hypertextually connect two distinct areas |
49 |
of documentation: design documents and |
of documentation: design documents and |
50 |
documentation embedded in the program code, such as Javadoc. |
documentation embedded in the program code, such as Javadoc. |
51 |
\end{abstract} |
\end{abstract} |
60 |
|
|
61 |
Software projects manage a large base of evolving documentation, whose |
Software projects manage a large base of evolving documentation, whose |
62 |
parts are |
parts are |
63 |
inter-related on many levels. |
interrelated on many levels. |
64 |
Design documentation shows |
Design documentation shows |
65 |
architectural views on a more general level, while |
architectural views on a more general level, while |
66 |
the source code (in e.g. Java and nowadays often also C++) |
the source code usually contains |
67 |
contains |
embedded documentation such as Javadoc [friendly95javadoc]_ giving details on the concrete |
|
embedded documentation giving details on the concrete |
|
68 |
classes and methods. |
classes and methods. |
69 |
|
|
70 |
.. Since these parts of documentation are semantically dependent |
.. Since these parts of documentation are semantically dependent |