41 |
links, we hypertexturally connect two distinct areas of documentation: design |
links, we hypertexturally connect two distinct areas of documentation: design |
42 |
documents and javadoc program code documentation. |
documents and javadoc program code documentation. |
43 |
|
|
|
.. 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. |
|
|
|
|
44 |
Introduction |
Introduction |
45 |
============ |
============ |
46 |
|
|
47 |
Software projects manage a large base of evolving documentation, which |
Software projects manage a large base of evolving documentation, whose |
48 |
is inter-related on many levels. Design documentation gives |
parts are |
49 |
architectural views on a more general level, while the program code |
inter-related on many levels. Design documentation shows |
50 |
source files contain minute interface specifications and often also |
architectural views on a more general level, while the program |
51 |
|
source code |
52 |
|
contains minute interface specifications and often also |
53 |
embedded documentation giving details on how the interfaces should be |
embedded documentation giving details on how the interfaces should be |
54 |
used. |
used. |
55 |
|
|