[Gzz-commits] manuscripts/UMLLink article.rst

[Tuukka Hastrup]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuukka Hastrup <address@hidden> 03/02/12 09:46:40

Modified files:
        UMLLink        : article.rst 

Log message:
        add back references, rewording

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.8 manuscripts/UMLLink/article.rst:1.9
--- manuscripts/UMLLink/article.rst:1.8 Wed Feb 12 07:23:58 2003
+++ manuscripts/UMLLink/article.rst     Wed Feb 12 09:46:39 2003
@@ -4,7 +4,7 @@
 
 Alternative title: "Bridging Javadoc to design documentation via UML diagrams"?
 
-:Stamp: $Id: article.rst,v 1.8 2003/02/12 12:23:58 tuukkah Exp $
+:Stamp: $Id: article.rst,v 1.9 2003/02/12 14:46:39 tuukkah Exp $
 
 Points for HT people
 ====================
@@ -120,6 +120,11 @@
 * (XXX Free Software vs. Open Source vs. Open Software vs. Open Project...)
 
 
+Diagrams
+========
+
+
+
 Introduction
 ============
 
@@ -131,13 +136,26 @@
 semantically dependent, in practice they are often linked scarcely -- if at 
 all.
 
-The Unified Modeling Language (UML) is the standard way to visually describe
-software constructs in diagrams. It was originally developed for descriptions 
+The Unified Modeling Language (UML) is the standard way to XXX visually 
+describe software constructs in diagrams _[#]. It was originally developed 
+for descriptions 
 on an abstract level (many constructs cannot be directly expressed in 
-any programming language), but current trend is to use it also on the concrete 
+any programming language) _[#], but current trend is to use it also on the 
+concrete 
 level, as to fully unify the architectural documentation and program code: the 
-program code might be generated from highly detailed diagrams, or exact 
-diagrams be produced from the source code.
+program code might be generated from highly detailed diagrams _[#], or exact 
+diagrams be produced from the source code _[#].
+
+
+.. [#] ``XXX`` booch-jacobson-rumbaugh-uml-user-guide? 
+
+.. [#] booch-jacobson-rumbaugh-uml-user-guide p.15
+       booch-jacobson-rumbaugh-uml-reference-manual p.4
+
+.. [#] harrison-barton-raghavachari00uml-to-java
+
+.. [#] pierce-tilley02connecting-documentation-rose
+
 
 Against this trend, we still use UML only to plan and document our software 
 architecture on general level. UML functions as a common language for 
@@ -200,8 +218,8 @@
 Up to this article all steps except the last one are implemented. The
 existing tools we selected as the basis for our documentation tool are:
 Javadoc [XXX], Docutils [XXX], and our own UML diagram description
-tool. The UML tools also use several free utilies to convert
-the lexical UML description into final *Portable Network
+tool. Further, the UML tool uses several free utilies to convert
+each lexical UML description into final *Portable Network
 Graphics* (PNG) diagram files. Such utilies are *MetaPost* [XXX] (mpost), 
 which implements a language for picture drawing, and Netpbm image file 
 manipulation toolkit. Besides Javadoc, all tools used are Free