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. Use Case Diagrams

Actor

PreviousUse Case DiagramsNextUse Case

Last updated 7 months ago

An Actor in a Use Case Diagram represents an external entity that interacts with the system. It can be a person, an organization, or another system that has a role in interacting with the system being modeled.

With Actors in Modeldraw's Use Case Diagram, you can:

  • Identify and represent the different users or external systems that interact with your system

  • Clarify the boundaries of your system by showing what's external to it

  • Illustrate the various roles that interact with your system's functionalities

  • Create a foundation for defining the system's use cases and their associations

  • Demonstrate the scope of your system from an external perspective

Understanding Actor

An Actor in Modeldraw's Use Case Diagram tool is typically represented by a stick figure. Actors are essential components of Use Case Diagrams as they initiate use cases and interact with the system. Key points to understand about Actors include:

  • An Actor represents a role rather than a specific individual or system. For example, "Customer" could be an Actor, representing anyone who uses the system as a customer.

  • Actors are always external to the system being modeled. They represent the users or systems that interact with your system.

  • A single Actor can be associated with multiple Use Cases, indicating that they can perform various actions within the system.

  • Actors can have parent-child relationships, where one Actor is a more specialized version of another.

  • Not all Actors are human users. They can also represent other systems, organizations, or even time (e.g., a scheduler).

Remember that Actors should represent distinct roles that interact with your system. When naming Actors, choose clear and descriptive names that reflect their roles in relation to the system.

An Actor