Activity diagrams and swimlane diagrams supplement use case diagrams by providing a visual representation of procedural workflow. Activity diagrams show the start and end of a process, decisions as diamonds, and can represent concurrent activity using branches and joins. Swimlane diagrams divide the diagram into lanes to indicate which actor or class is responsible for each activity. Together, these diagram types detail the flow of activities and responsibilities described in use cases.

1. Activity Diagrams
Dan Fleck
Coming up: Activity Diagram

2. Activity Diagram
Coming up: Swimlane Diagrams
Supplements the use-case
by providing a diagrammatic
representation of procedural
flow
Details:
-Start is a single circle
-End is a bulls-eye
-Decisions are diamonds
(guards must be on both
branches of the diamond!)
Questions:
Do we always have a start?
Do we always have an end?
How might we make this
better?

3. Swimlane Diagrams
Coming up: Activity Diagram Example
Allows the modeler to
represent the flow of
activities described by the
use-case and at the same
time indicate which actor
(if there are multiple
actors involved in a
specific use-case) or
analysis class has
responsibility for the
action described by an
activity rectangle

4. Activity Diagram Example
- To show
concurrent activity,
activity diagrams
allow branches
and joins.
- You can also
reference or
include other
activity diagrams
Coming up: Lets Try It
Fork/Bran
ch
Join

5. Lets Try It
Lets create a swimlane activity diagram for
opening a Lemonade stand.
Let’s create a swimlane diagram to apply for and
get a job when you graduate.
Software that translates voice commands into
user input (for whatever OS you use)
Let’s create a swimlane diagram for withdrawing
money from an ATM. – Nope – this is
essentially the homework for next week!
End of presentation