95 |
Our simple implementation as a Free Software toolchain is in daily use |
Our simple implementation as a Free Software toolchain is in daily use |
96 |
in our project. |
in our project. |
97 |
|
|
98 |
We present a navigational aid for software engineering documentation. |
We present a navigational aid for documenation used in software |
99 |
Based on using UML diagrams as multi-ended links, we hypertexturally |
development. Based on using UML diagrams as multi-ended links, we |
100 |
connect two |
hypertexturally connect two distinct areas of documentation: design |
101 |
distinct areas of software engineering documentation: design documents and javadoc. |
documents and javadoc program code documentation. We also describe the |
102 |
|
lightweight implementation as a supplement to a Free Software toolchain. |
103 |
|
|
104 |
and its lightweight implementation |
Connecting the distinct areas is essential because it could help new developers |
105 |
on top of a Free Software |
in getting productive and support development processes where both design and |
106 |
[fsf02categories]_ toolchain. |
implementation change continuously. |
|
The HTML is generated by existing tools and modified after generation by our software. |
|
107 |
|
|
108 |
XXX !!! |
To achieve bi-directional linking, the implementation after-treats HTML pages |
109 |
|
generated by other tools, injecting into referred pages links back to the |
110 |
|
referring imagemap of each UML diagram. |
111 |
|
|
112 |
|
The software is currently a part of and in use at our software project. |
113 |
|
|
114 |
Introduction |
Introduction |
115 |
============ |
============ |