Embed Size (px)
Citation preview
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 1
activity diagram
construction system(not automated)
initial node
final node
activity edge(control flow)
activityselect site
commissionarchitect
develop plan
bid plan
finishconstruction
do site work do trade work()
[notaccepted]
Booch, Jacobson, Rumbaugh. The Unified Modeling Language User Guide.Adddison-Wesley. 1999. Fig. 19.1
[accepted]
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 2
place order
give credit cardnumber
deliver to carrier
add in shippinglog
receive order
take order
take credit info process order
process creditcard info
customerorderdesk
accounting
pack in box
notifyaccounting
record shipping
send shippingnotification
shipping
activity diagram
with activity
partitions(swimlanes)
order processing(partially automated)
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 3
Booch, Jacobson, Rumbaugh. The Unified Modeling Language User Guide.Adddison-Wesley. 1999. Fig. 19.9
request product
continue work
receive order
pay bill
close order
process order
pull materials
ship order
bill customer
customer sales warehouse
activity diagram
with joins and forks
order processing(partially automated)
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 4
activity diagram with [ guard conditions ]and decision nodes
display currentconfiguration
get orderrequest
display purchaseform
get purchasedetails
store order
e-mail orderdetails
[timeout]
[incomplete]
[OK]
Maciaszek, L.A. Requirements Analysis and Systems Design: DevelopingInformation Systems with UML. Addison Wesley. 2001. Fig 2.26
online order processing
(automated)
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 5
check diary
advise notavailable
calculate price
advise priceaccept terms
check clientcredit
advise clientcredit no good
book reservationpay
request roomand date
guest reception accounts
book hotel room(partially automated)
guard conditionsneed to be added
guard conditionsneed to be added
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 6
activity diagrams for existing or proposed systems
high level
low level
• model business activities (processes or tasks)
• 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 7
getFirst(AdvertCollection::)
action (operation in a class)
class that containsthe operation
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 activity diagrams 8
object flow
state of objectbefore activity
state of objectafter activity
can be broken down into sub-activities
