[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/UMLLink umllink.rst
From: |
Tuukka Hastrup |
Subject: |
[Gzz-commits] manuscripts/UMLLink umllink.rst |
Date: |
Tue, 11 Feb 2003 07:35:08 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Changes by: Tuukka Hastrup <address@hidden> 03/02/11 07:35:08
Modified files:
UMLLink : umllink.rst
Log message:
rewordings trying to ensure understanding
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/umllink.rst.diff?tr1=1.60&tr2=1.61&r1=text&r2=text
Patches:
Index: manuscripts/UMLLink/umllink.rst
diff -u manuscripts/UMLLink/umllink.rst:1.60
manuscripts/UMLLink/umllink.rst:1.61
--- manuscripts/UMLLink/umllink.rst:1.60 Wed Feb 5 20:19:49 2003
+++ manuscripts/UMLLink/umllink.rst Tue Feb 11 07:35:08 2003
@@ -2,7 +2,7 @@
A free software toolchain for bidirectional linking between UML diagrams and
Javadoc
====================================================================================
-:Stamp: $Id: umllink.rst,v 1.60 2003/02/06 01:19:49 humppake Exp $
+:Stamp: $Id: umllink.rst,v 1.61 2003/02/11 12:35:08 tuukkah Exp $
2nd round todo:
===============
@@ -29,10 +29,11 @@
industry-standard language for specifying, visualizing, constructing,
and documenting the products in software engineering. Recently, various
approaches have been developed towards unifying software architecture
-design and code. This is done by generating the source code from the UML-based
-architectural model [#]_ or the reverse-engeneering documentation from
-the code [#]_. Nowadays UML seem to be taken in CASE tools even almost
-as a visual language, though it's not primarly designed to be a
+design and program source code. This is done by generating the source code
+from the UML-based
+architectural model [#]_ or by reverse-engineering the documentation from
+the code [#]_. Nowadays UML seems to be taken in CASE tools even almost
+as a visual programming language, though it's not primarly designed to be a
programming language [#]_.
.. [#] ``XXX`` booch-jacobson-rumbaugh-uml-user-guide?
@@ -44,13 +45,13 @@
.. [#] booch-jacobson-rumbaugh-uml-user-guide p.15
booch-jacobson-rumbaugh-uml-reference-manual p.4
-Against the trend of unifying the architectural documentation and code
-fully using UML, we tend still to define the details in the source code and
-use UML only for planning and document our software architecture in more
+Against this trend of using UML to fully unify the architectural documentation
+and code, we tend still to define the details in the source code and
+use UML only to plan and document our software architecture on more
general level. We keep UML as a common language for intercommunication
-within our software developer team and within project's all stakeholders.
-In this purpose we prefer more well abstracted and comprehensible
-human drawn diagrams than exact spesifications matching source code to
+within our software development team and within project's all stakeholders.
+In this purpose we prefer better abstracted and more comprehensible
+human-drawn diagrams to exact spesifications matching source code to
every detail:
"You draw diagrams to visualize a system from different
@@ -64,11 +65,12 @@
.. [#] booch-jacobson-rumbaugh-uml-user-guide, p.24
-Altough, even if the architectural documentation won't fully match with
+Altough, even if the architectural documentation won't fully match the
details of current implementation, we feel important to enable fast
-transitions between them. In this article, we present the tools we
+transition between them. In this article, we present the tools we
developed for using UML diagrams as multiple-ended hyperlinks between the
-architectural documents and javadoc generated java source documentation.
+architectural documents and the documentation generated from source code by
+Javadoc.
Background
==========