Software Engineering Activity Diagram.
Software Engineering Activity Diagram.
EXPERIMENT NO. 5
A.1 AIM: - To draw the behavioral view diagram: Activity diagram
A.2 Prerequisite
Determine the desired flow of action and their interaction with each other
A.3 Outcome
After successful completion of this experiment students will be able to -
A.4 Theory
Activity diagrams are flow charts that are used to show the workflow of a system.
They also:
● Show what activities can be done in parallel, and any alternate paths through the flow.
Activity diagrams may be created to represent the flow across use cases or they may be
created to represent the flow within a particular use case. Later in the life cycle, activity
diagrams may be created to show the workflow for an operation.
• Swimlane (vertical)
• Swimlane (horizontal): Swim lane- depicts which human organization is responsible
for an activity. Organization – sales, finance, marketing, purchasing etc. Swim lane
indicates that activity is performed by a person or persons within the organization.
Grade:
In an activity diagram, branches represent conditional or decision points where the flow of
control diverges based on a condition. Fork and join, on the other hand, are used to represent
parallel activities. Fork is used to create parallel paths, allowing multiple activities to occur
simultaneously. Join is used to synchronize parallel paths, ensuring that the control flow
waits until all parallel activities have completed before continuing.