98 |
are and how one creates them. |
are and how one creates them. |
99 |
These diagrams certainly exist for all properly managed |
These diagrams certainly exist for all properly managed |
100 |
medium-to-large scale software projects --- the problem is getting |
medium-to-large scale software projects --- the problem is getting |
101 |
them to where it matters. |
them to where it matters without having to manually insert |
102 |
|
links into the low-level documentation. |
103 |
|
|
104 |
.. at ``http://java.sun.com/j2se/1.4.1/docs/api/java/security/PublicKey.html``. |
.. at ``http://java.sun.com/j2se/1.4.1/docs/api/java/security/PublicKey.html``. |
105 |
|
|
167 |
team. Each UML diagram is meant to expose a particular aspect |
team. Each UML diagram is meant to expose a particular aspect |
168 |
of the design. |
of the design. |
169 |
Therefore |
Therefore |
170 |
a single program element may appear on several distinct diagrams, |
a single program element often appears on several distinct diagrams, |
171 |
that |
that |
172 |
together create a multicontext view for the element. |
together create a multicontext view for the element. |
173 |
|
|