initial node
activity
diagram
activity
select site
commission
architect
activity edge
(control flow)
develop plan
bid plan
[not
accepted]
[accepted]
do site work
do trade work()
finish
construction
construction system
(not automated)
final node
Booch, Jacobson, Rumbaugh. The Unified Modeling Language User Guide.
Adddison-Wesley. 1999. Fig. 19.1
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
1
customer
order
desk
accounting
place order
take order
give credit card
number
take credit info
shipping
activity
diagram
with
activity
partitions
process order
process credit
card info
(swimlanes)
pack in box
add in shipping
log
deliver to carrier
record shipping
receive order
notify
accounting
send shipping
notification
order processing
(partially automated)
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
2
customer
sales
warehouse
request product
process order
pull materials
continue work
ship order
receive order
bill customer
activity
diagram
with joins
and forks
pay bill
close order
Booch, Jacobson, Rumbaugh. The Unified Modeling Language User Guide.
Adddison-Wesley. 1999. Fig. 19.9
University of Toronto at Scarborough
© Kersti Wain-Bantin
order processing
(partially automated)
CSCC40 activity diagrams
3
online order
processing
(automated)
display current
configuration
[timeout]
get order
request
display purchase
form
[incomplete]
get purchase
details
activity diagram with
[ guard conditions ]
and decision nodes
[OK]
store order
e-mail order
details
Maciaszek, L.A. Requirements Analysis and Systems Design: Developing
Information Systems with UML. Addison Wesley. 2001. Fig 2.26
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
4
guest
reception
request room
and date
accounts
check diary
guard conditions
need to be added
advise not
available
check client
credit
calculate price
accept terms
advise price
advise client
credit no good
guard conditions
need to be added
pay
book reservation
book hotel room
(partially automated)
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
5
activity diagrams for existing or proposed systems
high level
• model business activities
(processes or tasks)
low level
• model a use case using object flows
• describe the logic of an operation
can be used
• before objects/classes identified
• again when system design is mature
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
6
action (operation in a class)
getFirst
(AdvertCollection::)
class that contains
the operation
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
7
object flow
state of object
before activity
state of object
after activity
can be broken down
into sub-activities
University of Toronto at Scarborough
© Kersti Wain-Bantin
CSCC40 activity diagrams
8