Projects



Changes between Initial Version and Version 1 of Paose/Documentation/HowTo-CDDs


Ignore:
Timestamp:
Sep 6, 2010, 10:30:29 PM (14 years ago)
Author:
Lawrence Cabac
Comment:

Added Howto CDDs

Legend:

Unmodified
Added
Removed
Modified
  • Paose/Documentation/HowTo-CDDs

    v1 v1  
     1= Howto CDDs =
     2
     3== (1) Description ==
     4
     5CDDs (Coarse Design Diagrams) define the coarse structure of a Mulan MAA (multi-agent application). In the fashion and adopting the syntax of Use Case Diagrams the tool allows to depict agent roles as actors and interactions as cases. Thus the tool defines the coarse matrix of roles and interaction for an MAA, i.e. structure and behavior. In addition to the generation of a folder structure for the specified MAA the tool also offers the export of the matrix to a table (latex) and to produce a html image map output for the diagram.
     6
     7''Note that the tool is in a highly prototypical state, it is called UseCaseComponents, as the name was chosen in early stages of development and the drawing elements are designed using the concept of Net Components.''
     8
     9== (2) Embedment in the PAOSE Development Process ==
     10[[ImageSvg(Paose-detailed-CDD.svg)]]
     11
     12== (3) Usage ==
     13
     14Start Renew and activate the palette for the diagram tools (Tools >> Net Components >> Use Case Components). The tools functions with net drawings: File >> New Net Drawing (Ctrl-N). With the drawing tools from the palette actors, interactions (cases) and arcs (no arrow tip) can be drawn. These drawing elements (actually Net Components) already provide a standard inscription, which can be adapted easily (right-click to edit).
     15
     16The tool allows to generate the folder structure for a Mulan MAA (multi-agent application) in the form of a standard Renew plugin.
     17
     18== Generator ==
     19The Generator of the !UseCase plugin generates skeletons for the system.
     20It facilitates Velocity templates for that cause.
     21Following parts are generated:
     22 - Folder structure of the plugin with source code structur for
     23  - Interactions (. . . /interactions/)
     24  - Roles (. . . /roles/)
     25  - Ontology (. . . /ontology/)
     26  - Knowledge bases (KB) and Roles/Dependencies Diagram (. . . /agents/)
     27 - Ant build-Script (build.xml)
     28 - Plugin configuration (plugin.cfg)
     29 - Start scripts (start.sh, sartCapa.rnw, startKBE.sh)
     30 - Skeleton:  Roles/Dependencies Diagram and a Project-File (!RolesDependencies.mad, pro jects.xml)
     31 - Protégé: Ontology Files (<name>.pprj, <name>.pons, <name>.pint)
     32 - Skeletons: AIPs for all Interactions, containing role names of all Participants. (<interaction>.aip)
     33After generation the plugin compiles with ant, it can be deployed through a repository (subversion) and the domain specific design of the system starts.
     34
     35
     36== (4) Inscriptions (Actors, Interactions): ==
     37(to be done)