[Gzz-commits] manuscripts/UMLLink article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/02/15 04:43:14

Modified files:
        UMLLink        : article.rst 

Log message:
        Twids

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.40 
manuscripts/UMLLink/article.rst:1.41
--- manuscripts/UMLLink/article.rst:1.40        Sat Feb 15 04:38:32 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 04:43:14 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.40 2003/02/15 09:38:32 humppake Exp $
+.. :Stamp: $Id: article.rst,v 1.41 2003/02/15 09:43:14 tjl Exp $
 
 .. Points for HT people
    ====================
@@ -133,7 +133,10 @@
    * user interfaces
    * spatial menus
 
+Abstract
+========
 
+XXX !!!
 
 Introduction
 ============
@@ -222,14 +225,14 @@
 software design process contains the following steps
 [parnas-clements86rational-onpage-252-255]_:
 
-  a) establish and document requirements
-  b) design and document the module structure
-  c) design and document the module interfaces
-  d) design and document the uses hierarchy
-  e) design and document the module internal structures
-  f) write programs
-  g) maintain (redesign and redevelopment, keeping documentation
-     up to date).
+  - establish and document requirements
+  - design and document the module structure
+  - design and document the module interfaces
+  - design and document the uses hierarchy
+  - design and document the module internal structures
+  - write programs
+  - maintain (redesign and redevelopment, keeping documentation
+    up to date).
 
 It should be clear that documentation plays major role in the
 ideal software design process. Steps listed above should produce
@@ -335,7 +338,7 @@
 | hard to find explanations       | no overall picture of classes'    |
 | for a particular class.         | roles                             |
 +---------------------------------+-----------------------------------+
-| UML diagrams                    | -                                 |
+| UML diagrams                    | ---                               |
 +---------------------------------+-----------------------------------+
 | written and organized by        | written by humans, organized      |
 | humans                          | rigidly by package structure      |
@@ -431,10 +434,10 @@
 | Conceptual            | Specification         | Implementation     |
 +=======================+=======================+====================+
 | probably no links     | can link Java         | can link all       |
-| to javadoc            | interface             | classes            |
-|                       |                       |                    |
+| to javadoc            | interfaces and        | classes            |
+|                       | some classes          |                    |
 +-----------------------+-----------------------+--------------------+
-| the design            | can link also Java    | can link all       |
+| the design            | can link some Java    | can link all       |
 | documentation         | packages              | packages           |
 | packages could be     |                       |                    |
 | linked withing the    |                       |                    |