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

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Asko Soukka <address@hidden>    03/05/21 09:42:19

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        some

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

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.21 
manuscripts/UMLLink/short-paper.rst:1.22
--- manuscripts/UMLLink/short-paper.rst:1.21    Wed May 21 06:41:02 2003
+++ manuscripts/UMLLink/short-paper.rst Wed May 21 09:42:19 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.21 2003/05/21 10:41:02 humppake Exp $
+.. $Id: short-paper.rst,v 1.22 2003/05/21 13:42:19 humppake Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -20,6 +20,8 @@
    Work by Maletic on automatically finding connections among software
    documents using LSI 
    - [humppake] 'automatically', probably not relewant
+   - [humppake] From Maletic, but doesn't seem relevant:
+                http://doi.acm.org/10.1145/585058.585066
 
    Berkeley PhD dissertation by Linton on using RDBMS to store program 
    analysis information
@@ -73,14 +75,16 @@
 [friendly95javadoc-andalso-heesch03doxygen-andalso-devanbu99chime]_.
 Similarly, requirements tracing --- managing relations
 between requirements and design decisions is relatively
-well developed [XXX]_.
+well developed [gotel94reqtracing-andalso-jarke98reqtracing]_.
 
 What is often missing is the connections between
 the design documentation and the embedded documentation.
 This can be daunting to a newcomer; consider the javadoc
 for the interface ``java.security.PublicKey`` in Sun's
-Java2 SDK 1.4.1
-REF?.
+Java2 SDK 1.4.1.
+
+.. REF?. XXX
+
 While the class is easy to find through the package and class lists
 when looking for a class to represent cryptographical public keys,
 the javadoc is not terribly useful: there is no information
@@ -182,7 +186,7 @@
 through the spatial menu in the diagram --- we insert
 elements showing the location where the diagram appears
 in the design documentation into the diagrams as well.
-Figure XXX shows some example HTML pages produced by our system.
+Figure 1 [ref-example]_ shows some example HTML pages produced by our system.
 
 
 ..  Because UML diagrams should be made anyway, it is good start to
@@ -220,7 +224,16 @@
 The implementation in Navidoc
 =============================
 
-  * using lexical UML language
+Navidoc is as a light-weight tool built on top of several existing
+Free Software [fsf02categories]_ tools. 
+
+- main parts: Docutils [goodger02docutils]_, lexical UML language
+
+Navidoc uses several free utilies to convert each
+lexical UML diagram description into final *Portable Network Graphics*
+(PNG) diagram files. Such utilies are *MetaPost* [hobby89metapost]_
+(mpost), which implements a language for picture drawing, and Netpbm
+image file manipulation toolkit. 
 
 - why lexical UML language: