152 |
- establish and document requirements |
- establish and document requirements |
153 |
- design and document the module structure |
- design and document the module structure |
154 |
- design and document the module interfaces |
- design and document the module interfaces |
155 |
- design and document the uses hierarchy |
- design and document the use hierarchy |
156 |
- design and document the module internal structures |
- design and document the module internal structures |
157 |
- write programs |
- write programs |
158 |
- maintain (redesign and redevelopment, keeping documentation |
- maintain (redesign and redevelopment, keeping documentation |
159 |
up to date). |
up to date) |
160 |
|
|
161 |
It should be clear that documentation plays a major role in the |
It should be clear that documentation plays a major role in the |
162 |
ideal software design process, and that there are several different |
ideal software design process, and at different levels of abstraction |
163 |
types of documentation at different levels of abstraction. |
the type of documentation varies. |
164 |
The steps listed above should produce |
The steps listed above should produce |
165 |
documentation which records requirements and design decisions, and |
documentation which records requirements and design decisions, and |
166 |
could be referenced throughout the building of the |
could be referenced throughout the building of the |
930 |
|
|
931 |
Earlier concept-based navigation and map-based navigation have added |
Earlier concept-based navigation and map-based navigation have added |
932 |
horizontal links on top of hierarchical hypertext [brusilovsky02-mapnav]_. |
horizontal links on top of hierarchical hypertext [brusilovsky02-mapnav]_. |
933 |
The structure we discuss in this paper is similar as the diagram becomes a |
The structure we discussed in this paper is similar as the diagram becomes a |
934 |
navigational node, but we don't rely on keywords or heuristics in link |
navigational node, but we don't rely on keywords or heuristics in link |
935 |
creation. |
creation. |
936 |
Further, as the diagram is shown inside a web page, it functions as |
Further, as the diagram is shown inside a web page, it functions as |
960 |
On the other hand, there are also arguments against MetaPost: |
On the other hand, there are also arguments against MetaPost: |
961 |
the error messages received on erroneous input to the UML tool |
the error messages received on erroneous input to the UML tool |
962 |
are difficult to decipher due to the translation layer between. |
are difficult to decipher due to the translation layer between. |
963 |
Abandoning MetaPost might also speed up the compiling process. |
Abandoning MetaPost might also speed up the compilation process. |
964 |
|
|
965 |
Once some of these issues are resolved, we are planning |
We plan, once some of these issues are resolved, |
966 |
to release the glue code as a standalone Free Software package. |
to release the glue code as a standalone Free Software package. |
967 |
|
|
968 |
Finally, we'd like to point out that this tool could benefit from a less |
Finally, we'd like to point out that this tool could benefit from a less |
975 |
=============== |
=============== |
976 |
|
|
977 |
The authors would like to thank Toni Alatalo for discussions regarding |
The authors would like to thank Toni Alatalo for discussions regarding |
978 |
this manuscript. |
UML software and this manuscript. |
979 |
|
|
980 |
.. bibliography:: gzigzag |
.. bibliography:: gzigzag |
981 |
|
|