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

Action

PreviousActivity FinalNextFlow

Last updated 7 months ago

An Action in an Activity Diagram represents a single step or task within the activity being modeled. It is the fundamental unit of behavior in an Activity Diagram and depicts a specific operation or function that occurs as part of the overall process.

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

  • Represent individual steps or tasks in your process

  • Break down complex activities into manageable, discrete operations

  • Show the sequence of work being performed in your activity

  • Provide clear, concise descriptions of each step in the process

  • Model both simple and complex behaviors within your system or workflow

Understanding Action

An Action in Modeldraw's Activity Diagram tool is represented by a rounded rectangle with the action's name inside. Key points to understand about Actions include:

  • Actions are the most fundamental elements of behavior in Activity Diagrams.

  • Each Action should have a clear, descriptive name indicating what it does.

  • An Action is considered to be atomic, meaning it's executed as a single, uninterrupted unit of work.

  • Actions can have one or more incoming flows and one or more outgoing flows.

  • Unlike composite activities or sub-processes, an Action doesn't have any internal flow or structure visible in the diagram.

  • Actions are typically named using a verb-noun format to clearly describe the operation being performed.

Remember to use clear, concise names for your Actions that accurately describe the step or task being performed.

Actions and Flows