40 |
|
|
41 |
http://www.computer.org/software/so1994/s4104abs.htm |
http://www.computer.org/software/so1994/s4104abs.htm |
42 |
|
|
43 |
Abstract |
.. raw:: latex |
|
======== |
|
44 |
|
|
45 |
We present a navigational aid for documentation used in software |
\begin{abstract} |
46 |
development. Based on using readily-authored UML diagrams as multi-ended |
We present a navigational aid for documentation used in software |
47 |
links, we hypertexturally connect two distinct areas of documentation: design |
development. Based on using readily-authored UML diagrams as |
48 |
documents and javadoc program code documentation. |
multi-ended links, we hypertexturally connect two distinct areas |
49 |
|
of documentation: design documents and javadoc program code |
50 |
|
documentation. |
51 |
|
\end{abstract} |
52 |
|
|
53 |
Introduction |
Introduction |
54 |
============ |
============ |
172 |
to allow users to develop a cognitive map of the data structure before |
to allow users to develop a cognitive map of the data structure before |
173 |
moving within it [edwards-hardman89lost-in-hyperspace-onpage-123]_. |
moving within it [edwards-hardman89lost-in-hyperspace-onpage-123]_. |
174 |
|
|
|
Besides UML diagrams are spatial, they are encouraged to be |
|
|
complementary |
|
175 |
|
|
176 |
.. multicontext views versus traditional hierarchical documentation |
.. multicontext views versus traditional hierarchical documentation |
177 |
|
|