[Gzz-commits] manuscripts/UMLLink short-paper.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/20 13:52:19

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        reqtraceinitrefs

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

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.9 
manuscripts/UMLLink/short-paper.rst:1.10
--- manuscripts/UMLLink/short-paper.rst:1.9     Tue May 20 13:19:53 2003
+++ manuscripts/UMLLink/short-paper.rst Tue May 20 13:52:19 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.9 2003/05/20 17:19:53 tjl Exp $
+.. $Id: short-paper.rst,v 1.10 2003/05/20 17:52:19 tjl Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -33,8 +33,11 @@
      * same basic problem, different approach
 
    Requirements traceability research
-   - [humppake] couldn't find yet
+   http://www.sei.cmu.edu/str/descriptions/reqtracing_body.html
+   http://www.cis.ksu.edu/~hankley/d841/Fa99/chap2.htm
+   http://www.computer.org/proceedings/apsec/0915/09150206abs.htm?SMSESSION=NO
 
+http://www.computer.org/software/so1994/s4104abs.htm
 
 Abstract
 ========
@@ -59,13 +62,20 @@
 .. Since these parts of documentation are semantically dependent
    they should be interlinked together.
 
-There exist plenty of documentation tools to generate well navigable
-documentations from program code source files. Altough, many of them
-are designed to work with many different programming languages, there
-may exist conventions to use specific documentation tool with specific
-programming language (like Javadoc with Java). When a yet another tool
-is used to write the design documentation, linking all documentation
-together by hand would be tedious and error-prone.
+While the generation of easily navigable hypertext 
+from the embedded documentation is essentially
+a solved problem 
+for several languages 
+[friendly95javadoc-andalso-heesch03doxygen-andalso-devanbu99chime]_,
+the connection to design documentation has been more elusive.
+
+..  There exist plenty of documentation tools to generate well navigable
+    documentations from program code source files. Altough, many of
+    them are designed to work with many different programming languages,
+    there may exist conventions to use specific documentation tool with
+    specific programming language (like Javadoc with Java). When a yet
+    another tool is used to write the design documentation, linking all
+    documentation together by hand would be tedious and error-prone.
 
 .. - short description about problem:
      * programming language specific tools like javadoc do generate