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

Decision / Merge

PreviousFlowNextFork / Join

Last updated 7 months ago

The Decision / Merge element in an Activity Diagram serves a dual purpose. As a Decision node, it represents a point where the flow can take alternative paths based on a condition. As a Merge node, it brings together multiple alternative paths without synchronization.

With Decision / Merge nodes in Modeldraw's Activity Diagram, you can:

  • Model points of conditional branching in your process

  • Represent the convergence of alternative paths

  • Create complex workflows with multiple possible routes

  • Show how different conditions affect the flow of your activity

  • Simplify diagrams by using the same symbol for both branching and merging

Understanding Decision / Merge

A Decision / Merge node in Modeldraw's Activity Diagram tool is represented by a diamond shape. Key points to understand about Decision / Merge nodes include:

  • The same symbol is used for both decision points and merging points.

  • When used as a Decision, it has one incoming flow and multiple outgoing flows.

  • When used as a Merge, it has multiple incoming flows and one outgoing flow.

  • In its Decision role, each outgoing flow represents a possible path based on a condition.

  • In its Merge role, it represents where alternative paths come back together.

  • Unlike Join nodes, Merge nodes don't synchronize concurrent flows.

  • The role (Decision or Merge) is determined by how it's used in the diagram.

Remember that the context and connections determine whether the node functions as a Decision or a Merge.

A Decision