27 |
|
|
28 |
Yi-Farn Chen`s CHIME system for linking software documents |
Yi-Farn Chen`s CHIME system for linking software documents |
29 |
- [humppake] devanbu99chime |
- [humppake] devanbu99chime |
30 |
|
|
31 |
* crosslinking source code using html |
* crosslinking source code using html |
32 |
|
|
33 |
|
* same basic problem, different approach |
34 |
|
|
35 |
Requirements traceability research |
Requirements traceability research |
36 |
- [humppake] couldn't find yet |
- [humppake] couldn't find yet |
37 |
|
|
50 |
Software projects manage a large base of evolving documentation, whose |
Software projects manage a large base of evolving documentation, whose |
51 |
parts are |
parts are |
52 |
inter-related on many levels. Design documentation shows |
inter-related on many levels. Design documentation shows |
53 |
architectural views on a more general level, while the program |
architectural views on a more general level, while |
54 |
source code |
the source code (in e.g. Java and nowadays often also C++) |
55 |
contains minute interface specifications and often also |
contains |
56 |
embedded documentation giving details on how the interfaces should be |
embedded documentation giving details on the concrete |
57 |
used. |
classes and methods. |
58 |
|
|
59 |
.. Since these parts of documentation are semantically dependent |
.. Since these parts of documentation are semantically dependent |
60 |
they should be interlinked together. |
they should be interlinked together. |
216 |
Conclusion |
Conclusion |
217 |
========== |
========== |
218 |
|
|
219 |
|
Our approach is different from most tools, |
220 |
|
which rely more on automatically generated links [XXX], |
221 |
|
or inserting connections to the source code [devanbu99chime]_. |
222 |
|
|
223 |
|
|
224 |
.. - future |
.. - future |
225 |
* fenfire |
* fenfire |
226 |
|
|