[Gzz-commits] manuscripts/UMLLink short-paper.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/20 15:32:59

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        abstract

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/short-paper.rst.diff?tr1=1.13&tr2=1.14&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.13 
manuscripts/UMLLink/short-paper.rst:1.14
--- manuscripts/UMLLink/short-paper.rst:1.13    Tue May 20 15:29:51 2003
+++ manuscripts/UMLLink/short-paper.rst Tue May 20 15:32:59 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.13 2003/05/20 19:29:51 tjl Exp $
+.. $Id: short-paper.rst,v 1.14 2003/05/20 19:32:59 tjl Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -40,13 +40,15 @@
 
    http://www.computer.org/software/so1994/s4104abs.htm
 
-Abstract
-========
+.. raw:: latex
 
-We present a navigational aid for documentation used in software
-development. Based on using readily-authored UML diagrams as multi-ended 
-links, we hypertexturally connect two distinct areas of documentation: design
-documents and javadoc program code documentation. 
+    \begin{abstract}
+    We present a navigational aid for documentation used in software
+    development. Based on using readily-authored UML diagrams as
+    multi-ended links, we hypertexturally connect two distinct areas
+    of documentation: design documents and javadoc program code
+    documentation.  
+    \end{abstract}
 
 Introduction
 ============
@@ -170,8 +172,6 @@
     to allow users to develop a cognitive map of the data structure before
     moving within it [edwards-hardman89lost-in-hyperspace-onpage-123]_.
 
-Besides UML diagrams are spatial, they are encouraged to be
-complementary 
 
 .. multicontext views versus traditional hierarchical documentation