[Gzz-commits] manuscripts/UMLLink umllink.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/04 05:07:38

Modified files:
        UMLLink        : umllink.rst 

Log message:
        a potential (classic) reference about supporting the construction of 
mental models by means of hypermedia, e.g. reducing the amount of fragmentation

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umllink.rst.diff?tr1=1.57&tr2=1.58&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/umllink.rst
diff -u manuscripts/UMLLink/umllink.rst:1.57 
manuscripts/UMLLink/umllink.rst:1.58
--- manuscripts/UMLLink/umllink.rst:1.57        Tue Feb  4 03:56:19 2003
+++ manuscripts/UMLLink/umllink.rst     Tue Feb  4 05:07:38 2003
@@ -2,7 +2,7 @@
 A free software toolchain for bidirectional linking between UML diagrams and 
Javadoc
 
====================================================================================
 
-:Stamp: $Id: umllink.rst,v 1.57 2003/02/04 08:56:19 antont Exp $
+:Stamp: $Id: umllink.rst,v 1.58 2003/02/04 10:07:38 antont Exp $
 
 Introduction
 ============
@@ -32,6 +32,9 @@
 use UML only for planning and document our software architecture in more 
 general level. We keep UML as a common language for intercommunication 
 within our software developer team and within project's all stakeholders.
+(could these stakeholders be identified and described to some extent
+somewhere? it might be interesting to think also towards users/customers,
+who in some methods (ways of using XP) control use cases themselves)
 In this purpose we prefer more well abstracted and comprehensible
 human drawn diagrams than exact spesifications matching source code to 
 every detail: 
@@ -307,6 +310,10 @@
 other way. [#]_
     
 .. [#] edwards-hardman-lost-in-hyperspace, p.123
+
+(See also 'Hypermedia and cognition: designing for comprehension' by Thuring
+et al.  
+http://portal.acm.org/citation.cfm?id=208348&coll=portal&dl=ACM&CFID=7442809&CFTOKEN=15305251#FullText)
 
 We didn't need to look long for a common navigational metatphor to unify our
 two distinct documentation. Since the most of our UML-diagrams included objects