The graphical editor dedicated to the Activity Diagram has been specified from the UML 2.0 Superstructure Specification document. Feel free to bring your own remarks about the way UML concepts were represented in this diagram : we could discuss about that on the user mailing list.
1. Creation of the diagram
1.1. From the wizard
You can use the creation wizard to create a new activity diagram. Select the corresponding Template to initialize the model.
The root element of the UML model is a Model and it contains a Package that also contains an Activity as its children element. The diagram is then linked with the Activity.
1.2. From an existing diagram
The activity diagram is necessarily associated with an Activity model object.
Then you can create a new diagram by selecting an Activity node in the Outline : "
" and select " Activity Diagram ".2. Editing of the Diagram
2.1. Basic editing
2.1.1. Activity
An Activity is the specification of parametrized behaviour as the coordinated sequencing of subordinate units whose individual elements are actions. This is the root model object of an Activity Diagram.
2.1.2. Control Nodes
A Control Node may be created into an Activity model object (at the diagram level). These nodes are used to coordinate flows in an activity and the number of flows that can be connected (as input and/or output) depends on the type of the control node : however, this is not checked during the creation of the Flow, but it should be checked in a further step (an OCL check for example).
2.1.3. Object Nodes
An Object Node may be created into an Activity model object (at the diagram level). These nodes are used to define object flows in an activity.
2.1.4. Actions
2.1.5. ExpansionRegion
An ExpansionRegion is a structured activity region that executes multiple times corresponding to elements of an input collection.
2.1.6. ActivityPartition
An ActivityPartition is a kind of activity group for identifying actions that have some characteristic in common. Partitions divide the nodes and edges to constrain and show a view of the contained nodes.
2.1.7. Control Flow
A Control Flow is an edge that starts an activity node after the previous one is finished. Objects and data cannot pass along a control flow edge.
2.1.8. Object Flow
An Object Flow is an activity edge that can have objects or data passing along it. An object flow models the flow of values to or from object nodes.
2.1.9. Exception Handler
An Exception Handler is an element that specifies a body to execute in case the specified exception occurs during the execution of the protected node.
2.2. Advanced editing
3. Diagram Example
_______________________________________
By Jacques LESCOT, Anyware Technologies
August, 31 2006