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

[Asko Soukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Asko Soukka <address@hidden>    03/05/22 05:16:10

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        experiences

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

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.32 
manuscripts/UMLLink/short-paper.rst:1.33
--- manuscripts/UMLLink/short-paper.rst:1.32    Wed May 21 16:05:52 2003
+++ manuscripts/UMLLink/short-paper.rst Thu May 22 05:16:10 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.32 2003/05/21 20:05:52 humppake Exp $
+.. $Id: short-paper.rst,v 1.33 2003/05/22 09:16:10 humppake Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -170,11 +170,11 @@
     \includegraphics[height=9cm]{short-trav-3.gen.eps}\hskip .4cm%
     \end{centering}
     \caption{
-    Examples. a) A javadoc class documentation page with three embedded
-    diagrams. The class' location/role in diagrams is highlighted. b)
+    Examples. Left: A javadoc class documentation page with three embedded
+    diagrams. The class' location/role in diagrams is highlighted. Middle:
     A design documentation page that was achieved from one of the diagrams
-    in a). Diagram is originally described in this page and is therefore
-    shown in full size. c) A C++ documentation page of an another class
+    in left. Diagram is originally described in this page and is therefore
+    shown in full size. Right: A C++ documentation page of an another class
     from the same diagam. Also two other diagrams are embedded to show
     more using contexts of the class.
     }
@@ -362,15 +362,24 @@
 Experiences
 ===========
 
-  * WWW statistics from himalia: 2003/01 - 2003/03
+The statistics of our projects WWW server show that diagrams
+connecting javadoc to design documentationg have increased the usage
+of project's design documentation and traversing between documentation
+levels is very common. In the period of three months (Jan 03 till end
+of Mar 03) at least 9% of all design documentation page request came
+by traversing from javadoc to design documentation via diagrams. On
+the other hand at least 11% of all javadoc visits came from design
+documentation via diagrams.
+
+..   * WWW statistics from himalia: 2003/01 - 2003/03
+
+       - design documentation pages loaded 639 times
+       - design documentation pages reached from javadoc 59 times
+       - javadoc pages loaded 1604 times
+       - javadoc pages reached from design docs 179 times
+       - summa summarum: at leasts 10% all hits came via diagrams
 
-    - design documentation pages loaded 639 times
-    - design documentation pages reached from javadoc 59 times
-    - javadoc pages loaded 1604 times
-    - javadoc pages reached from design docs 179 times
-    - summa summarum: at leasts 10% all hits came via diagrams
-
-  * anecdotes - has someone used it?
+     * anecdotes - has someone used it?
 
 Conclusion
 ==========