1 / 11

UML StateChart Diagrams

Explore UML activity diagrams, a variation of state machines, illustrating flow of sequential or concurrent actions. Learn notation, criticisms, and more about this widely used tool for system lifecycle visualization.

mvalencia
Download Presentation

UML StateChart Diagrams

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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.

  3. x y A/O Activity Diagrams: Notation • Action State • Subactivity State • Decisions • Swimlanes • Action State • Subactivity State • Decisions • Swimlanes • Action-Object Flow action

  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.

More Related