1 / 10

Unified Modeling Language User Guide

Understand the basics of activity diagrams in Unified Modeling Language (UML) for modeling workflows, operations, and system behaviors. Learn about activity, action, transitions, branching, forking, joining, swimlanes, and object flow in the context of software engineering practices. Explore key concepts and terms essential for forward and reverse engineering processes.

Download Presentation

Unified Modeling Language User Guide

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. Unified Modeling LanguageUser Guide Section 4 - Basic Behavioral Modeling Chapter 19 – Activity Diagrams

  2. Overview • Modeling a workflow • Modeling an operation • Forward and reverse Engineering CS6359 Chapter 19

  3. Terms & Concepts • Activity Diagram – shows the flow from activity to activity. • Activity – an ongoing non atomic execution within a state machine. Activities ultimately/ pada akhirnya results in some action. • Action – made up of executable atomic computations that results in a change in state of the system or the return of a value (i.e., calling another operation, sending a signal, creating or destroying an object, or some pure computation. CS6359 Chapter 19

  4. Do trade work() Finish construction Initial state Activity Diagram • Activity diagrams commonly contain: • Activity states and actions states • Transitions • Objects Select site Commission Action state architect Develop plan Bid plan concurrent fork Sequential branch [not accepted] [else] Activity state with submachine concurrent join Do site work object flow : CertificateOfOccupancy [completed] final state CS6359 Chapter 19

  5. Action States & Activity States • Action states: executable, atomic computations (states of the system, each representing the execution of an action) – cannot be decomposed/buang. • Activity states: not atomic; can be further/ lebih jauh decomposed; can be represented by other activity diagrams – a composite whose flow of control is made up of other activity states and action states. CS6359 Chapter 19

  6. Release work order Select Site Reschedule Assign tasks Commission architect Transitions & Branching start state guard expression branch [materials not ready] action state triggerless transition [materials ready] stop state guard expression CS6359 Chapter 19

  7. Forking and Joining • Concurrent flow. • Use synchronization bar to specify the forking and joining of these parallel flows of control. • A synchronization bar is rendered as a thick horizontal or vertical line. fork Do trade Do site work work() join CS6359 Chapter 19

  8. Swimlanes • Useful in modeling workflows of business processes – partition the activity states on an activity diagram into groups, each group representing the business organization responsible for those activities. • A swimlane is a kind of package. • Each swimlaine has a name unique within its diagram (a swimlane really has no deep semantic – just represent some real-world entity). • Every activity belongs/mesti to exactly one swimlane, but transitions may cross lanes. CS6359 Chapter 19

  9. Object Flow • Objects may be involved/ ruwet in the flow of control associated with an activity diagram. • Specify the things that are involved in an activity diagram by placing these objects in the diagram, connected using a dependency to the activity or transition that creates, destroys, or modifies them. • Object flow – the use of dependency relationships and objects (represents the participation of an object in a flow of control). CS6359 Chapter 19

  10. Summary • Activity diagram, Activity, & Action • Action states & Activity states • Transition & Branching • Forking & Joining • Swimlanes • Object flow CS6359 Chapter 19

More Related