1 / 27

UML 2.0 Activity Diagrams

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

maite-jimenez
Télécharger la présentation

UML 2.0 Activity Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UML 2.0 Activity Diagrams

  2. 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

  3. 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) Object node Executable action node

  4. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  5. Example: Process Order Activity Control flow Fork Join <pre> Order complete<post> Order closed Process OrderRequested Order: Order Initial node [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Merge Decision Parameter Send Invoice Close Order Make Payment Accept Payment Invoice Data flow Action Object Final node

  6. Example: Process Order II. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice If one thread terminates, the other may continue

  7. 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

  8. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  9. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  10. Example: Process Order <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice

  11. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  12. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  13. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  14. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  15. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  16. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  17. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  18. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  19. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  20. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  21. <pre> Order complete<post> Order closed Process OrderRequested Order: Order [order rejected] Receive Order Fill Order Ship Order RequestedOrder [order accepted] Send Invoice Close Order Make Payment Accept Payment Invoice Example: Process Order

  22. Node A Node B Channel(control) Channel(data) 2 Control token Data tokens Node C 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

  23. IN1 IN2 Node A OUT1 OUT2 Semantics: Dataflow Networks • Firing rule (cont.): • precondition: • input tokens + curr. state • postcondition • output tokens + new state

  24. 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? IN1 IN2 Node A OUT1 OUT2

  25. IN1 IN2 Node A OUT1 OUT2 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

  26. IN1 IN2 Node A OUT1 OUT2 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

  27. Partitioning of Activities Győr Budapest [order rejected] Order Receive Order Fill Order Ship Order Close Order [order accepted] Send Invoice Accept Payment Accounting Invoice Make Payment Customer

More Related