uml 2.0 activity diagrams
DESCRIPTION
UML 2.0 Activity Diagrams. UML : Activity diagram. Aim: Description of business workflows (as in HW) High-level description of UC scenarios Detailed description of dynamic behavior Methods Actions of statecharts Two levels of abstraction Action (akció): atomic operation - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/1.jpg)
UML 2.0 Activity Diagrams
![Page 2: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/2.jpg)
UML : Activity diagram
• Aim: – Description of business workflows (as in HW)– High-level description of UC scenarios– Detailed description of dynamic behavior
• Methods• Actions of statecharts
• Two levels of abstraction– Action (akció): atomic operation– Activity (aktivitás): high-level grouping of actions
• Combined control and data flow model– semantics dataflow networks
![Page 3: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/3.jpg)
Activity diagram• Graph model:
– Activity nodes: • Object (objektum )• Action (akció) • Control (vezérlés)
– decision, merge (döntés)
– fork, join (párh. tevékenység)
– initial (kezdőpont)
– final (végpont – minden út)
– flow final (token nyelő – egy út)
– Activity edges: flow• Data/object (Adatfolyam)• Control (Vezérlési folyam)
Executable action node
Object node
![Page 4: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/4.jpg)
Example: Process Order
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
![Page 5: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/5.jpg)
Example: Process Order
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Parameter
Initial node
Final nodeObjectAction
Merge
Activity
Decision
JoinFork
Data flow
Control flow
![Page 6: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/6.jpg)
Example: Process Order II.
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
If one thread terminates, the other may continue
![Page 7: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/7.jpg)
Data flow and Control flow• Data Flow: data token
– Object node Action node• An object node is a channel / queue • An object may be linked to multiple action nodes• Output actions are competing for the data token (i.e. the object)
– Type conformance: object type < input type of action
• Control flow: control token (ordering constraint between two actions)– All predecessor actions should be terminated prior to
starting the current action– The current action should terminate prior to starting any
of the successor actions
![Page 8: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/8.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 9: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/9.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 10: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/10.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 11: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/11.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 12: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/12.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 13: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/13.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 14: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/14.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 15: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/15.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 16: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/16.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 17: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/17.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 18: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/18.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 19: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/19.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 20: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/20.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 21: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/21.jpg)
Receive Order
Fill Order
Ship Order
RequestedOrder
Close Order
Send Invoice
Make Payment
Accept Payment
Invoice
[order accepted]
[order rejected]
Process OrderRequested Order: Order
<pre> Order complete<post> Order closed
Example: Process Order
![Page 22: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/22.jpg)
Semantics: Dataflow Networks
– Tokens: • control + several data
– Channel: object node• Stores the tokens
– Node: action node• Processing tokens
– Edges: • Flow of tokens
• weights: how many tokens are in the flow at a time?
– Firing rule:• Behaviour of a node
NodeA
NodeB
Channel(control)
Channel(data)
NodeC
2Control token
Data tokens
![Page 23: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/23.jpg)
NodeA
OUT1 OUT2
IN2IN1
Semantics: Dataflow Networks
• Firing rule (cont.):– precondition:
• input tokens + curr. state
– postcondition• output tokens + new state
![Page 24: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/24.jpg)
NodeA
OUT1 OUT2
IN2IN1
Semantics: Dataflow Networks
• Firing rule (cont.):– precondition:
• input tokens + curr. state
– postcondition• output tokens + new state
• Execution of a firing: – Is there token on all inputs
with • Right amount?• Right type?
![Page 25: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/25.jpg)
NodeA
OUT1 OUT2
IN2IN1
Semantics: Dataflow Networks
• Firing rule (cont.):– precondition:
• input tokens + curr. state
– postcondition• output tokens + new state
• Execution of a firing: – Is there token on all inputs
with• Right amount?• Right type?
– Execution of action
![Page 26: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/26.jpg)
NodeA
OUT1 OUT2
IN2IN1
Semantics: Dataflow Networks
• Firing rule (cont.):– precondition:
• input tokens + curr. state
– postcondition• output tokens + new state
• Execution of a firing: – Is there token on all inputs
with• Right amount?• Right type?
– Execution of action– Sending the output tokens
![Page 27: UML 2.0 Activity Diagrams](https://reader033.vdocuments.mx/reader033/viewer/2022061506/568138a4550346895da060dc/html5/thumbnails/27.jpg)
Partitioning of Activities
Receive Order
Fill Order
Ship Order
Close Order
Send Invoice
Make Payment
Accept Payment
[order accepted]
[order rejected]
Invoice
Cu
sto
me
r A
cco
unt
ing
Ord
er
BudapestGyőr