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

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Asko Soukka <address@hidden>    03/05/21 15:38:49

Modified files:
        .              : gzigzag.bib 
        UMLLink        : short-paper.rst 

Log message:
        ref

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/gzigzag.bib.diff?tr1=1.115&tr2=1.116&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/short-paper.rst.diff?tr1=1.29&tr2=1.30&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.29 
manuscripts/UMLLink/short-paper.rst:1.30
--- manuscripts/UMLLink/short-paper.rst:1.29    Wed May 21 15:20:57 2003
+++ manuscripts/UMLLink/short-paper.rst Wed May 21 15:38:49 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.29 2003/05/21 19:20:57 humppake Exp $
+.. $Id: short-paper.rst,v 1.30 2003/05/21 19:38:49 humppake Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -378,9 +378,9 @@
 for example, generates diagrams of class
 inheritance tree for that purpose.
 
-- other analysis software
+.. - other analysis software
 
-- autogen not comparable to design doc
+.. - autogen not comparable to design doc
 
 Of course, generated documentation may give well detailed information
 from the current implementation, but the design documentation should
@@ -389,10 +389,10 @@
 of too detailed diagrams (meanless for us) and prefer fully human
 created diagrams in our design documentation.
                                                             
-- how are UMLs embedded into documentation
+.. - how are UMLs embedded into documentation
 
 Our approach is different from most tools,
-which rely more on automatically generated links [XXX],
+which rely more on automatically generated links [maletic03recovering]_,
 or inserting connections to the source code [devanbu99chime]_.
 
 .. - future
Index: manuscripts/gzigzag.bib
diff -u manuscripts/gzigzag.bib:1.115 manuscripts/gzigzag.bib:1.116
--- manuscripts/gzigzag.bib:1.115       Tue May 20 05:52:55 2003
+++ manuscripts/gzigzag.bib     Wed May 21 15:38:48 2003
@@ -3393,6 +3393,14 @@
     year = "1999"
 }
 
address@hidden,
+    author = "Andrian Marcus, Jonathan I. Maletic",
+    title = "Recovering Documentation-to-Source-Code Traceability Links using 
Latent Semantic Indexing",
+    booktitle = "International Conference on Software Engineering",
+    pages = "125--137",
+    year = "2003"
+}
+
 @inproceedings{horowitz85sodos,
  author = {Ellis Horowitz and Ronald Williamson},
  title = {SODOS\x{2014}a software documentation support environment: its use},
@@ -5743,6 +5751,32 @@
     pages = {56--66},
     location = {North Falmouth, Massachusetts, United States},
 }
+
address@hidden -------------------------
address@hidden Requirements traceability
address@hidden -------------------------
+
address@hidden,
+ author = {Orlena C. Z. Gotel and Antony C. W. Finkelstein},
+ title = {An analysis of the requirements traceability problem},
+ journal = {Proceedings of the First International Conference on Requirements 
Engineering},
+ year = {1994},
+ pages = {94--101},
+ publisher = {IEEE},
+ }
+
address@hidden,
+ author = {Matthias Jarke},
+ title = {Requirements tracing},
+ journal = {Communications of the ACM},
+ volume = {41},
+ number = {12},
+ year = {1998},
+ issn = {0001-0782},
+ pages = {32--36},
+ doi = {http://doi.acm.org/10.1145/290133.290145},
+ publisher = {ACM Press},
+ }
 
 @comment ----------
 @comment Cryptology