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: Tuukka Hastrup
Subject: [Gzz-commits] manuscripts/UMLLink article.rst
Date: Sat, 15 Feb 2003 09:58:35 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuukka Hastrup <address@hidden> 03/02/15 09:58:35

Modified files:
        UMLLink        : article.rst 

Log message:
        removed CFP categories comment, reworded intro slightly

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

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.65 
manuscripts/UMLLink/article.rst:1.66
--- manuscripts/UMLLink/article.rst:1.65        Sat Feb 15 09:21:14 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 09:58:34 2003
@@ -9,65 +9,10 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.65 2003/02/15 14:21:14 tjl Exp $
+.. :Stamp: $Id: article.rst,v 1.66 2003/02/15 14:58:34 tuukkah Exp $
 
 .. Points for HT people
    ====================
-
-   from HT03 "Call for Papers: Topics for submissions":
-    * Hypertext and hypermedia construction
-          * Link authoring
-          * Link maintenance
-          * (X)Link databases
-          * Web authoring
-          * Automated Web generation
-          * Metadata and annotation
-          * Multimedia and Synchronisation 
-    * New hypermedia environments
-          * Grid and E-Science
-          * Scholarly and scientific communication
-          * Pervasive information architectures
-          * Semantic Web
-          * Knowledge Management
-          * Virtual and augmented reality environments 
-    * Hypermedia navigation strategies
-          * User interface and interactions
-          * Adaptive hypermedia
-          * Browsing assistance
-          * Fluid Links
-          * Trails
-          * Co-operative Hypermedia 
-    * Web site design and evaluation
-          * Structuring hypermedia documents for reading and retrieval
-          * Large-scale and distributed Web environments
-          * Metrics and measurement
-          * Web structures characterization
-          * Innovative web hypertexts
-          * Link analysis
-          * Effects of hypermedia on business or industry
-          * Experiences with the application of hypermedia
-          * Innovative hypertexts and novel uses of hypertext and hypermedia 
-    * Hypermedia architectures
-          * Hypermedia infrastructure technologies
-          * Hypermedia middleware and components
-          * Web Integration
-          * Architecture issues
-          * Link Services
-          * Open hypermedia architectures
-          * Large-scale distributed hypermedia
-          * Theories, models, architectures, standards, and frameworks 
-    * Applications
-          * Hypertext in workflow management systems
-          * Web-based hypermedia dramarose
-          * Hypermedia in fiction, scholarship, and technical writing
-          * Hypermedia in education and training
-          * Hypermedia and time: narratives and storyboarding
-          * Hypertext rhetoric and criticism
-          * Interactive games and entertainment
-          * Museums and archives 
-
-.. Our work in relation to those:
-
    technical architecture:
     * open document base (html) allows:
        * incorporation of several sources via their own tools (Javadoc, reST)
@@ -132,6 +77,7 @@
    * web
    * user interfaces
    * spatial menus
+   * navigational maps
 
 Abstract
 ========
@@ -160,10 +106,11 @@
 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 often embedded documentation
+source files contain minute specifications of interfaces and often also 
+embedded documentation
 giving details on how the interfaces should be used. Although
 these two parts of documentation are semantically dependent, linking
-them by hand is tedious and error-prone since they are authored using different
+them by hand is tedious and error-prone when they are authored using different
 software. 
 
 In this article, we present a navigational aid for software engineering 
documentation.




reply via email to

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