[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 07:50:47

Modified files:
        UMLLink        : article.rst 

Log message:
        Don't deprecate ourselves *quite* so much

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.55 
manuscripts/UMLLink/article.rst:1.56
--- manuscripts/UMLLink/article.rst:1.55        Sat Feb 15 07:19:42 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 07:50:46 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.55 2003/02/15 12:19:42 humppake Exp $
+.. :Stamp: $Id: article.rst,v 1.56 2003/02/15 12:50:46 tjl Exp $
 
 .. Points for HT people
    ====================
@@ -162,18 +162,21 @@
 developed for descriptions on an abstract level (many constructs
 cannot be directly expressed in any programming language)
 [booch-jacobson-rumbaugh98uml-user-guide-onpage-12]_, but the current
-trend is to use it also on the concrete level, as to fully unify the
+trend in research 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
-[harrison-barton-raghavachari00uml-to-java]_, or diagrams
-may be produced from the source code
+[harrison-barton-raghavachari00uml-to-java]_. 
+Another use of UML is in reverse engineering, where
+diagrams may be produced from the source code
 [pierce-tilley02connecting-documentation-rose]_.
 
-Against this trend, we still use UML only to plan and document our software 
-architecture on a general level. UML functions as a common language for 
-communication within our software development team, and for this purpose we
-prefer human-drawn diagrams that abstract from the gory details
-of code to be more comprehensible to us:
+In this article we focus on the more conventional use of UML
+to plan and document software 
+architecture on a general level. 
+UML can function as a common language for 
+communication within a software development team, and for this purpose 
+human-drawn (non-autogenerated) diagrams show the semantically meaningful
+features at the right level of abstraction are preferred:
 
    "You draw diagrams to visualize a system from different
    perspectives, so a diagram is a projection into a system.