Modeldraw
  • Welcome to Modeldraw
  • Getting Started
    • Quickstart Guide
  • FAQ
  • UML Designer
    • Common Elements
      • Comment
      • Comment Link
      • Dependency
      • Realization
      • Frame
    • Class Diagrams
      • Class
      • Association
      • Generalization
      • Composition
      • Aggregation
      • Enumeration
      • Interface
      • Association Class Link
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Sequence Diagrams
      • Lifeline
      • Activation Bar
      • Synchronous Message
      • Asynchronous Message
      • Return Message
      • Found Message
      • Interaction Frame
    • Use Case Diagrams
      • Actor
      • Use Case
      • Association
      • System Boundary
      • Generalization
      • Include Relationship
      • Extend Relationship
    • State Machine Diagrams
      • State
      • Initial State
      • Final State
      • Transition
      • Superstate
      • Concurrent Boundary
      • History Pseudostate
      • History Transition
    • Package Diagrams
      • Package
    • Deployment Diagrams
      • Node
      • Communication Path
      • Deployed Artifact
      • Internet
    • Activity Diagrams
      • Initial Node
      • Activity Final
      • Action
      • Flow
      • Decision / Merge
      • Fork / Join
      • Partitions
      • Flow Final
      • Send Signal
      • Accept Signal
      • Time Signal
    • Component Diagrams
      • Component
      • Ball (Interface Realization)
      • Socket (Required Interface)
    • Communication Diagrams
      • Object
      • Link
  • Wireframes
    • Views
    • Layouts
    • Components
Powered by GitBook
On this page
  1. UML Designer
  2. Activity Diagrams

Flow

PreviousActionNextDecision / Merge

Last updated 7 months ago

A Flow in an Activity Diagram represents the transition between two elements, showing the sequence and direction in which actions and other elements occur within the activity. It illustrates the path of execution through the diagram.

With Flows in Modeldraw's Activity Diagram, you can:

  • Show the sequence of actions and decisions in your process

  • Connect different elements of your activity diagram

  • Indicate the direction of progression through the activity

  • Represent the logical order of steps in your workflow

  • Illustrate alternative paths and parallel processes

Understanding Flow

A Flow in Modeldraw's Activity Diagram tool is represented by an arrow connecting two elements. Key points to understand about Flows include:

  • Flows are always directed, showing the progression from one element to another.

  • Flows connect various elements such as Actions, Decision nodes, Fork/Join nodes, and Initial/Final nodes.

  • Flows should not create direct loops back to the same element.

  • Some elements (like Decision nodes) can have multiple outgoing flows.

  • When an element has only one outgoing flow, it's assumed that this flow is taken automatically after the element's execution.

  • Flows can be labeled with guard conditions to show when they are followed.

Actions and Flows