gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/UMLLink article.rst


From: Tuomas J. Lukka
Subject: [Gzz-commits] manuscripts/UMLLink article.rst
Date: Sat, 15 Feb 2003 07:10:36 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/02/15 07:10:36

Modified files:
        UMLLink        : article.rst 

Log message:
        key words: can't forget to mention what this is about

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.52 
manuscripts/UMLLink/article.rst:1.53
--- manuscripts/UMLLink/article.rst:1.52        Sat Feb 15 07:07:29 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 07:10:36 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.52 2003/02/15 12:07:29 benja Exp $
+.. :Stamp: $Id: article.rst,v 1.53 2003/02/15 12:10:36 tjl Exp $
 
 .. Points for HT people
    ====================
@@ -136,7 +136,7 @@
 Abstract
 ========
 
-We describe automatic linking of design documentation to javadoc
+We describe automatic linking of software engineering design documentation to 
javadoc
 through UML diagrams embedded in both, acting as multi-target nexus links.
 Our simple implementation as a Free Software toolchain is in daily use
 in our project.
@@ -150,8 +150,8 @@
 Software projects manage a large base of evolving documentation, which
 is inter-related on many levels. Design documentation gives
 architectural views on a more general level, while the program code
-source files contain interfaces and embedded documentation
-giving all the minute details on how the computer should act. Although
+source files contain interfaces and often embedded documentation
+giving details on how the interfaces should be used. Although
 these two parts of documentation are semantically dependent, linking
 them is tedious -- if even possible -- when they are authored using different
 software.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]