/[gzz]/manuscripts/UMLLink/short-paper.rst
ViewVC logotype

Diff of /manuscripts/UMLLink/short-paper.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.47 by tjl, Thu May 29 16:44:46 2003 UTC revision 1.48 by tjl, Thu May 29 17:22:18 2003 UTC
# Line 94  for the interface ``java.security.Public Line 94  for the interface ``java.security.Public
94  While the class is easily found through the package and class lists  While the class is easily found through the package and class lists
95  when looking for a class representing cryptographical public keys,  when looking for a class representing cryptographical public keys,
96  the javadoc is not terribly useful: it lacks the information  the javadoc is not terribly useful: it lacks the information
97  there on how to create objects that implement this interface.  on how to create objects that implement this interface.
98  Currently, the only relevant links are on an accompanying ``Use`` page,  The only relevant links are on an accompanying ``Use`` page,
99  which lists all the references to this interface elsewhere in the  which lists all the references to this interface in any method
100    prototypes elsewhere in the
101  documentation.  documentation.
102  Further, those lists lack information about the contextual importance of  The list does not give information about the contextual importance of
103  the mentionings --- the methods for  the items --- the methods for
104  creating a ``PublicKey`` are listed alongside eg. the methods  creating a ``PublicKey`` are listed alongside eg. the accessor methods
105  that return a ``PublicKey`` contained in another object.  that return a ``PublicKey`` contained in another, unrelated object.
106    
107  Far more helpful would be a link to the design  Far more helpful would be a link to the design
108  documentation, even just a diagram showing the intended  documentation, even just a diagram showing the intended
# Line 206  a common language for communication with Line 207  a common language for communication with
207  team. Each UML diagram is meant to expose a particular aspect  team. Each UML diagram is meant to expose a particular aspect
208  of the design.  of the design.
209  Therefore  Therefore
210  a single program element often appears on several distinct diagrams,  a single program element often appears on several separate diagrams
211  that  that
212  together create a multicontext view for the element.  together create a multicontext view for the element.
213    

Legend:
Removed from v.1.47  
changed lines
  Added in v.1.48

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26