[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 13:19:53

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        twid

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

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.8 
manuscripts/UMLLink/short-paper.rst:1.9
--- manuscripts/UMLLink/short-paper.rst:1.8     Tue May 20 12:58:43 2003
+++ manuscripts/UMLLink/short-paper.rst Tue May 20 13:19:53 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.8 2003/05/20 16:58:43 tjl Exp $
+.. $Id: short-paper.rst,v 1.9 2003/05/20 17:19:53 tjl Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -27,8 +27,11 @@
  
    Yi-Farn Chen`s CHIME system for linking software documents
    - [humppake] devanbu99chime
+
      * crosslinking source code using html
 
+     * same basic problem, different approach
+
    Requirements traceability research
    - [humppake] couldn't find yet
 
@@ -47,11 +50,11 @@
 Software projects manage a large base of evolving documentation, whose
 parts are
 inter-related on many levels. Design documentation shows
-architectural views on a more general level, while the program 
-source code 
-contains minute interface specifications and often also
-embedded documentation giving details on how the interfaces should be
-used.
+architectural views on a more general level, while 
+the source code (in e.g. Java and nowadays often also C++)
+contains
+embedded documentation giving details on the concrete
+classes and methods.
 
 .. Since these parts of documentation are semantically dependent
    they should be interlinked together.
@@ -212,6 +215,11 @@
 
 Conclusion
 ==========
+
+Our approach is different from most tools,
+which rely more on automatically generated links [XXX],
+or inserting connections to the source code [devanbu99chime]_.
+
 
 .. - future
     * fenfire