Activity Diagram
PB007 Software engineering I
Marián Macik
originally by Stanislav Chren
Week 04
Software engineering I (PB007) Activity Diagram Week 04 1 / 9
Diagram aktivít
Activity diagram represents flow of events and actions in an activity. It
consists of different types of nodes that are connected with directed edges
The Activities usually represent:
use cases
operations and methods
algorithms
business processes
Software engineering I (PB007) Activity Diagram Week 04 2 / 9
Basic elements
Software engineering I (PB007) Activity Diagram Week 04 3 / 9
Activity diagram - example
Software engineering I (PB007) Activity Diagram Week 04 4 / 9
Swimlanes
Swimlane (Activity partition) represents a logical grouping of related
actions (e.g. based on actors, use cases, ...). In our case they usually
represent individual uses cases connected with include or extend .
include
Base and included use case have their own swimlanes.
extend
If there is an extension point between Action1 and Action2, a
decision node is added after Action1, which allows transition either to
the Action2 or to the extending use case. Afterwards, the flow returns
to the Action2 via the merge node. Each of the use cases has its own
swimlane.
Software engineering I (PB007) Activity Diagram Week 04 5 / 9
Information sources
http://sourcemaking.com/uml/modeling-business-systems/
external-view/activity-diagrams
http://sce.uhcl.edu/helm/rationalunifiedprocess/
process/modguide/md_bactd.htm
Software engineering I (PB007) Activity Diagram Week 04 6 / 9
Tasks
Fix the problems from the previous week and finalize the textual
specification of the chosen use cases.
Select additional 2 use cases for which you will create the activity
diagrams. They must be different from the use cases with the textual
specification. The selection should be approved by the seminar tutor.
Generate a PDF report and upload it to the homework vault
(Week 04).
Software engineering I (PB007) Activity Diagram Week 04 7 / 9
Rules for report submission
1 Submit the PDF report, not the VP source file and not an exported image.
2 PDF report must be created using the procedure shown on the seminars
including the report settings.
3 The name of the PDF report file should be lastname1-lastname2-lastname3
of the team members.
4 PDF report must contain all diagrams modelled until now.
5 PDF report must be uploaded to the homework vault by the specified
deadline.
6 PDF report must be uploaded to the correct homework vault. The name of
the homework vault is always specified on the slides.
7 Each team uploads only a single PDF report for the whole team.
8 Submitted diagrams must be clear and readable.
9 Submitted diagrams should not contain serious mistakes. At least, they
should not contain mistakes mentioned in the Catalogue of common
mistakes.
Software engineering I (PB007) Activity Diagram Week 04 8 / 9
VP report settings
Software engineering I (PB007) Activity Diagram Week 04 9 / 9