1. UML StateChart Diagrams
Activity Diagrams

2. Activity Diagrams: What is ?
Variation of a state machine in which the states represent the performance of actions or sub-activities and the transitions are triggered by the completion of the actions or sub-activities.
Describe a flow of sequential or concurrent actions/activities.
Uma actividade pode ser decomposta:
Um caso de utilizacao
Uma operacao de uma classe
Um grupo de casos de utilizacao relacionados entre si
Uma parte de uma actividade de mais alto nivel

3. Activity Diagrams: Notation
Action State
Subactivity State
Decisions
Swimlanes
Action-Object Flow
Action State
Subactivity State
Decisions
Swimlanes
action
Action State – state with an entry action and at least one outgoing x y
A/O

4. Activity Diagrams: Notation
Synch States
Join
Fork

5. Activity Diagrams: When ?
Behavior doesn’t depend on external events.
Tasks that terminate without being interrupt by external events.
Flow of data between tasks.

6. Activity Diagrams: In Action

7. Activity Diagrams: In Action

8. Activity Diagrams: In Action

9. Activity Diagrams vs States
Both represent a lifetime cycle of a system.
Automatic transitions, not handled by external events.
Majority states are action states.

10. Activity Diagrams: Criticism
Impedance Mismatch
Easy to read (not)
Bad understand can originate complex diagrams.

11. Conclusion
Essentially a concurrent diagram, not only sequential tasks.
Parallel tasks, the execution order is not important.
Widely used to describe use cases.