UML activity diagram: Difference between revisions
m (using an external editor) |
m (using an external editor) |
||
| Line 5: | Line 5: | ||
'''UML activity diagrams''' refer to [[software engineering]] method modeled with [[UML]] to describe work flows, business processes and other procedures. | '''UML activity diagrams''' refer to [[software engineering]] method modeled with [[UML]] to describe work flows, business processes and other procedures. | ||
UML activity diagrams are | UML activity diagrams are a kind of behavior diagram. UML activity diagrams seem to be somewhat similar '''UML state machine diagrams''' which in turn are similar to [[Petri net]]s. | ||
See also: [[UML]] | See also: [[UML]] | ||
== Architecture of activity diagrams == | == Architecture of activity diagrams == | ||
The basic concept of activity and all other behavior diagrams are '''actions'''. {{quotation|An action is the fundamental unit of behavior specification. An action takes a set of inputs and converts them into a set of outputs, though either or both sets may be empty. This clause defines semantics for a number of specialized actions, as described below. Some of the actions modify the state of the system in which the action executes. The values that are the inputs to an action may be described by value specifications, obtained from the output of actions that have one output (in StructuredActions), or in ways specific to the behaviors that use them. For example, the activity flow model supports providing inputs to actions from the outputs of other actions. ([http://www.omg.org/technology/documents/formal/uml.htm UML, version 2.1.2])}}. | |||
Simple Activity diagrams consist of: | Simple Activity diagrams consist of: | ||
| Line 18: | Line 20: | ||
{{quotation|The starting point of the diagram is the initial node, and the activity final node is the ending. An activity diagram can have zero or more activity final nodes. In between activities are represented by rounded rectangles.}} ([http://en.wikipedia.org/wiki/Activity_diagram Wikipedia], retrieved 11:08, 4 June 2008 (UTC). | {{quotation|The starting point of the diagram is the initial node, and the activity final node is the ending. An activity diagram can have zero or more activity final nodes. In between activities are represented by rounded rectangles.}} ([http://en.wikipedia.org/wiki/Activity_diagram Wikipedia], retrieved 11:08, 4 June 2008 (UTC). | ||
=== Nodes === | === Basic Nodes === | ||
According to Conrad Bock (2003), there there are three kinds of node in activity models: | According to Conrad Bock (2003), there there are three kinds of node in activity models: | ||
| Line 49: | Line 51: | ||
* A fat black dot inside a circle | * A fat black dot inside a circle | ||
* A circle with an x represents the end of a flow (not the whole activity) | * A circle with an x represents the end of a flow (not the whole activity) | ||
=== Signals === | |||
Actions in a diagram also can respond to signals (instead of the flow) | |||
; Time signals | |||
* Represented like an hour glass | |||
; Accept signal | |||
* Represented by a concave pentagon (a smashed-in rectangle) | |||
=== Activity edges (links) === | === Activity edges (links) === | ||
; Control edges | ; Control edges | ||
These edges can be drawn in various ways: | These edges can be drawn with '''arrows''' in various ways: | ||
* Represented by an arrow from an activity node to another | * Represented by an arrow from an activity node to another | ||
* Represented by an arrow from an activity showing parameters with pins from a node to another | * Represented by an arrow from an activity showing parameters with pins from a node to another | ||
* An arrow to a | * An arrow to a '''connecto'''r (a small circle with a letter) and then from a same connector to a activity node | ||
* Activity node to object node to activity node (with arrows) | * Activity node to object node to activity node (with arrows) | ||
| Line 62: | Line 74: | ||
* Represented by an arrow | * Represented by an arrow | ||
=== | === Partitions and subactivities === | ||
; Subactivities | |||
* Activities can be decomposed into subactivities | * Activities can be decomposed into subactivities | ||
* A rake in an action node signals a subactivity | * A rake in an action node signals a subactivity | ||
* The subsidiary activity diagram has an input and an output parameter (object nodes) | * The subsidiary activity diagram has an input and an output parameter (object nodes) | ||
; Partititions | |||
* An activity can be partitioned in a swimlanes | |||
* Each represents a player (see examples below) | |||
=== Partitions === | === Partitions === | ||
Activity diagrams can be partioned according to roles (e.g. learner A, learner B, group A, teacher) | Activity diagrams can be partioned according to roles (e.g. learner A, learner B, group A, teacher) | ||
== Typical patterns == | == Typical patterns == | ||
Revision as of 17:49, 5 June 2008
Definition
UML activity diagrams refer to software engineering method modeled with UML to describe work flows, business processes and other procedures.
UML activity diagrams are a kind of behavior diagram. UML activity diagrams seem to be somewhat similar UML state machine diagrams which in turn are similar to Petri nets.
See also: UML
Architecture of activity diagrams
The basic concept of activity and all other behavior diagrams are actions. “An action is the fundamental unit of behavior specification. An action takes a set of inputs and converts them into a set of outputs, though either or both sets may be empty. This clause defines semantics for a number of specialized actions, as described below. Some of the actions modify the state of the system in which the action executes. The values that are the inputs to an action may be described by value specifications, obtained from the output of actions that have one output (in StructuredActions), or in ways specific to the behaviors that use them. For example, the activity flow model supports providing inputs to actions from the outputs of other actions. (UML, version 2.1.2)”.
Simple Activity diagrams consist of:
- Initial node.
- Activity final node.
- Activities in between
“The starting point of the diagram is the initial node, and the activity final node is the ending. An activity diagram can have zero or more activity final nodes. In between activities are represented by rounded rectangles.” (Wikipedia, retrieved 11:08, 4 June 2008 (UTC).
Basic Nodes
According to Conrad Bock (2003), there there are three kinds of node in activity models:
- Action nodes operate on control and data values that they receive, and provide control and data to other actions.
- Control nodes route control and data tokens through the graph. These include constructs for choosing between alternative flows (decision points), for proceeding along multiple flows in parallel (forks), and so on.
- Object nodes hold data tokens temporarily as they wait to move through the graph. Figure 3 shows the notation for some of the activity nodes to be discussed. Contrary to the names, control nodes coordinate both data flow and control flow in the graph, and object nodes can hold both objects and data
- Activity nodes
- Represented by a rectangle with rounded corners
- Action nodes should have a label
- Object nodes
- Represented by a rectangle with a label
- Decision and merge control node
- Represented by a lozange
- Fork and join control node
- Represented by a line
- One or more activities can join
- One or more activities can fork
- Initial node
- Represented by a fat black dot
- There can be only one
- Final nodes
- A fat black dot inside a circle
- A circle with an x represents the end of a flow (not the whole activity)
Signals
Actions in a diagram also can respond to signals (instead of the flow)
- Time signals
- Represented like an hour glass
- Accept signal
- Represented by a concave pentagon (a smashed-in rectangle)
Activity edges (links)
- Control edges
These edges can be drawn with arrows in various ways:
- Represented by an arrow from an activity node to another
- Represented by an arrow from an activity showing parameters with pins from a node to another
- An arrow to a connector (a small circle with a letter) and then from a same connector to a activity node
- Activity node to object node to activity node (with arrows)
- Object Flow edges
- Represented by an arrow
Partitions and subactivities
- Subactivities
- Activities can be decomposed into subactivities
- A rake in an action node signals a subactivity
- The subsidiary activity diagram has an input and an output parameter (object nodes)
- Partititions
- An activity can be partitioned in a swimlanes
- Each represents a player (see examples below)
Partitions
Activity diagrams can be partioned according to roles (e.g. learner A, learner B, group A, teacher)
Typical patterns
Inspired from Activity Diagram
- Accept Event Action
- An action that waits for the occurrence of an event meeting specified conditions
- Activity Final
- Data Store
- Decision Node
- Flow Final
- Fork Node
- InitialNode
- Join Node
- Merge Node
- Object Node
- Send Signal Action
- Object Flow
Examples
A simple example
The following example taken from D7.2 UNFOLD outcomes 2 contains the following elements:
- A start node
- An end node
- Two join/break (the fat lines)
- Three activities
Educational examples
Activity diagrams can be used to describe learning designs of CSCL scenarios. A good example are collaborative learning flow pattern (Hernández-Leo et al., 2005b).
Below some more pictures that show that activity diagrams are popular withing the IMS Learning Design community.
The next example shows a diagram for competency-based learning with two major alternatives, advising-then-anticipating and anticipating-then-advising. (IMS LD Best Practice specification)
The following example taken from the IMS LD Best Practice specification shows a diagram for problem-based learning
Links
- Summaries of UML activity diagrams
- Wikipedia:Unified_Modeling_Language (Wikipedia)
- Activity diagram (Wikipedia)
- Introductions to activity diagrams
- UML 2 Activity Diagrams, and UML 2 Activity Diagram Guidelines by Scott W. Ambler, Ambysoft.
- UML 2 Activity and Action Models by Conrad Bock, U.S. National Institute of Standards and Technology
- Activity Diagram, UML 2 Diagrams, Visual Paradigm Gallery.
- Standards
- Unified Modeling Language (UML), version 2.1.2. There are two specifications that comprise the UML 2.1.2 specification: Superstructure and Infrastructure. There are also two specifications that relate to the UML2 specification (Diagram Interchange and Object Constraint Language).
References
Bock, Conrad (2003). "UML 2 Activity and Action Models", Journal of Object Technology, vol. 2, no. 4, July-August 2003, pp. 43-53. http://www.jot.fm/issues/issue_2003_07/column3
- Fowler, M. (2000). UML distilled (3rd ed.). Upper Saddle River, NJ: Addison-Wesley. ISBN 0321193687
- Hernández-Leo, D., Asensio-Pérez, J.I., Dimitriadis, Y., Bote-Lorenzo, M.L., Jorrín-Abellán, I.M., Villasclaras-Fernández, E.D. (2005b). Reusing IMS-LD Formalized Best Practices in Collaborative Learning Structuring. Advanced Technology for Learning 2(4):223-232. http://dx.doi.org/10.2316/Journal.208.2005.4.208-0865 - PDF
- IMS Global Learning consortium (2003). IMS Learning Design Best Practice and Implementation Guide, HTML, retrieved 11:08, 4 June 2008 (UTC).