[go: up one dir, main page]

0% found this document useful (0 votes)
115 views17 pages

Activity Diagram

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
115 views17 pages

Activity Diagram

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

21CSC101T

Object Oriented Design and Programming

ACTIVITY DIAGRAM
Activity Diagram
 Activity diagram is UML behavior diagram which emphasis on the
sequence and conditions of the flow
 It shows a sequence of actions or flow of control in a system.
 It is like to a flowchart or a flow diagram.
 It is frequently used in business process modeling. They can also describe
the steps in a use case diagram.
 The modeled Activities are either sequential or concurrent.
Benefits
 It illustrates the logic of an algorithm.
 It describes the functions performed in use cases.
 Illustrate a business process or workflow between users and the system.
 It Simplifies and improves any process by descriptive complex use cases.
 Model software architecture elements, such as method, function, and
operation.
Symbols and Notations
Activity
 Is used to illustrate a set of actions.
 It shows the non-interruptible action of objects.
Symbols and Notations
Action Flow
 It is also called edges and paths
 It shows switching from one action state to another. It is represented as an
arrowed line.
Symbols and Notations
Decisions and Branching
 A diamond represents a decision with alternate paths.
 When an activity requires a decision prior to moving on to the next
activity, add a diamond between the two activities.
 The outgoing alternates should be labeled with a condition or guard
expression. You can also label one of the paths "else."
Symbols and Notations
Guards
 In UML, guards are a statement written next to a decision diamond that
must be true before moving next to the next activity.
 These are not essential, but are useful when a specific answer, such as
"Yes, three labels are printed," is needed before moving forward.
Symbols and Notations
Synchronization
 A fork node is used to split a single incoming flow into multiple
concurrent flows. It is represented as a straight, slightly thicker line in an
activity diagram.
 A join node joins multiple concurrent flows back into a single outgoing
flow.
 A fork and join mode used together are often referred to as
synchronization.
Symbols and Notations
Synchronization
Symbols and Notations
Time Event
 At a definite point of time this action or activity starts a flow.
Symbols and Notations
Merge Event
 A merge event brings together multiple flows that are not concurrent.

Final State or End Point


 An arrow pointing to a filled circle nested inside another circle represents
the final action state.
Symbols and Notations
Swimlane and Partition
 A way to group activities performed by the same actor on an activity
diagram or to group activities in a single thread
Activity Diagram
Activity Diagram with Swimlane
Activity Diagram without Swimlane

You might also like