PB007 Software Engineering I — Activity Diagram1 Activity Diagram PB007 Software Engineering I Lukáš Daubner daubner@mail.muni.cz PB007 Software Engineering I — Activity Diagram2 Activity Diagram What can the activity diagram represent? PB007 Software Engineering I — Activity Diagram3 Activity Diagram What can the activity diagram represent? ̶ Activities – Who would have guessed ;) PB007 Software Engineering I — Activity Diagram4 Activity Diagram What can the activity diagram represent? ̶ Activities – Who would have guessed ;) ̶ Use Cases ̶ Business Processes ̶ Algorithms ̶ Operations, metody, ... PB007 Software Engineering I — Activity Diagram5 Activity Diagram ̶ Flow of events and actions in an activity ̶ It consists of different types of nodes, connected with edges ̶ Action ̶ Event (asynchronous behavior) ̶ Time events ̶ Parallel flow ̶ Branching ̶ Typically, it is a sequence of commands (Control Flow), but data can be represented as well (Object Flow) PB007 Software Engineering I — Activity Diagram6 Activity Diagram – Example PB007 Software Engineering I — Activity Diagram7 Swimlines ̶ Logical grouping of related actions ̶ Context of actors, use cases, etc.. ̶ If use case is modelled, they can be «include» and «extend» ̶ «include» ̶ Base and included use case have their own swimlanes. ̶ «extend» ̶ If there is an extension point between two actions, decision node is added in between, from which it is possible to move to the extended use case. Afterwards, the control is returned by merge node. ̶ Base and extended use case have their own swimlanes. PB007 Software Engineering I — Activity Diagram8 Swimlines – Include & Extend PB007 Software Engineering I — Activity Diagram9 Work, work In this seminar… ̶ Feedback ̶ Activity ̶ Visual Paradigm demo ̶ Team work on project ̶ Activity Diagram PB007 Software Engineering I — Activity Diagram10 You gotta do what you gotta do Task for this week ̶ Process the feedback ̶ Choose two use cases and create activity diagrams for them ̶ Adequately™ complex (meaning no three-action diagrams) ̶ Choose different use cases than those for textual specification ̶ Submit the report ̶ Don’t forget to include work from previous weeks ̶ Do your part in peer review ̶ Link to roster is in study materials