32 |
Requirements traceability research |
Requirements traceability research |
33 |
- [humppake] couldn't find yet |
- [humppake] couldn't find yet |
34 |
|
|
|
Abstract |
|
|
======== |
|
|
|
|
|
.. This could still be good: |
|
|
|
|
|
We present a navigational aid for documentation used in software |
|
|
development. Based on using readily-authored UML diagrams as |
|
|
multi-ended links, we hypertexturally connect two distinct areas of |
|
|
documentation: design documents and javadoc program code |
|
|
documentation. Connecting the distinct areas is essential because it |
|
|
could help new developers in getting productive and supports |
|
|
development processes where both design and implementation change |
|
|
continuously. |
|
|
|
|
|
We also describe the lightweight implementation as a supplement to a |
|
|
Free Software toolchain. To achieve bi-directional linking, the |
|
|
implementation after-treats HTML pages generated by other tools, |
|
|
injecting into referred pages links back to the referring imagemap of |
|
|
each UML diagram. Each diagram also servers as a spatial context for |
|
|
navigation within target nodes. |
|
|
|
|
35 |
- short description about problem: |
- short description about problem: |
36 |
* how to make fragmented documentation connected with |
* how to make fragmented documentation connected with |
37 |
minimum additional work |
minimum additional work |
42 |
* generate higher level design documentation |
* generate higher level design documentation |
43 |
* connect these levels via UML diagrams drawn design documentation |
* connect these levels via UML diagrams drawn design documentation |
44 |
|
|
45 |
|
- why UML |
46 |
|
* UML as de facto standard for describing software architecture |
47 |
|
* diagrams already exists, so why not use them |
48 |
|
* probably not best for navigation, but still better than nothing |
49 |
|
|
50 |
- why UML-diagrams would work as menus |
- why UML-diagrams would work as menus |
51 |
* human made abstraction of the system |
* human made abstraction of the system |
52 |
* don't link to everywhere, but to the most essential places |
* don't link to everywhere, but to the most essential places |
72 |
* separate navidoc version coming up |
* separate navidoc version coming up |
73 |
|
|
74 |
- future |
- future |
|
* fenfire |
|
75 |
|
* fenfire |