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. State Machine Diagrams

History Pseudostate

PreviousConcurrent BoundaryNextHistory Transition

Last updated 7 months ago

A History Pseudostate in a State Machine Diagram is a special element that allows a Superstate (Composite State) to remember its most recently active immediate substate. When the Superstate is re-entered through the History Pseudostate, it resumes in the last active substate rather than starting from its initial state.

With History Pseudostates in Modeldraw's State Machine Diagram, you can:

  • Model systems that need to remember their last active state within a Superstate

  • Implement "resume" functionality in your state machines

  • Simplify the representation of state re-entry logic

  • Enhance the usability of systems by maintaining context across interruptions

  • Create more flexible and responsive state machines

Understanding History Pseudostate

A History Pseudostate in Modeldraw's State Machine Diagram tool is represented by a circle containing an 'H'. Key points to understand about History Pseudostates in Modeldraw include:

  • It remembers only the last active immediate substate within a Superstate.

  • It should have at least one outgoing transition to a default state, used when the history is blank.

  • It's placed inside the Superstate whose history it's tracking.

A Superstate with a History Pseudostate representing a vending machine