Actor (UML)¶

A modeled role played by an external entity while interacting with the subject of a UML use-case model.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3200
Domain group: Applied Sciences & Engineering
Origin domain: Computer Science & Software Engineering
Subdomain: Software Modeling → Computer Science & Software Engineering

Core Idea¶

An actor is a role rather than a particular person or device, one entity may play several actors and one actor may be realized by many entities, and the actor remains outside the modeled subject boundary. The model abstracts external participants by interaction responsibility, linking each role to use cases through associations while suppressing participant details irrelevant to the subject. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

How would you explain it like I'm…

Parts People Play

When people plan a computer system, they draw who will use it from the outside. An actor is a part someone plays, like "shopper" or "cashier," not a particular person. The same person can play two parts, and lots of people can play the same part. A machine can be an actor too.

A Role That Uses the System

In UML, a picture language for planning software, an actor is anyone or anything outside the system that uses it or works with it, like a customer, a bank, or another computer. It's drawn as a stick figure outside the box that marks the system's edges. An actor is a role, not a particular person: one person can play several roles, and many people can play the same role. Each actor is connected by lines to the use cases, the things it does with the system, like 'buy a ticket.' Details about the actual people are left out, because only the role matters.

External Roles in Use-Case Models

In UML use-case modeling, an actor is a role that some external entity plays when it interacts with the system being modeled, called the subject. Actors are always outside the system boundary. An actor is a role, not an individual: one entity can play several actors, and one actor can be played by many entities, including people, devices, or other systems. Actors are linked to use cases by associations that show who communicates with which functions, and they can be primary (starting the interaction) or supporting. Actors can also be generalized, so a more specific actor inherits the interactions of a more general one. The model keeps only each participant's interaction responsibilities and leaves out other details.

An actor in UML is a role played by an external entity in interaction with a modeled subject, located outside the subject's system boundary. It abstracts participants by interaction responsibility: an actor is a role, not a physical instance, so one entity may play several actors and one actor may be realized by many entities, whether humans, devices, or other systems. Actors connect to use cases through communication associations, may stand in a primary or supporting relation to them, and may participate in generalization hierarchies with other actors. Details of the participant irrelevant to the subject are suppressed. A correct model makes explicit the subject and boundary, the external entity type, the role and its responsibilities, the associated use cases, and the distinction between role and instance.

Scope of Application¶

Actor (UML) belongs to software modeling and is useful where the analyst can specify the typed software modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance are explicit. The scope is broad within that domain but bounded by the need for the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance are explicit.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Actor (UML). Actor (UML) compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed software modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of software modeling because they reuse the typed software modeling carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, The model abstracts external participants by interaction responsibility, linking each role to use cases through associations while suppressing participant details irrelevant to the subject., and type the carrier, state every parameter and convention in the definition, test that the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Actor (UML) Domain-specific

Parents (1) — outgoing typed relations

Actor (UML) is a kind of Representation Prime

It remains its own entry because its identity is fixed by the modeled subject and system boundary, external entity type, actor role and responsibilities, use cases, communication associations, primary or supporting relation, generalization among actors, multiplicity of roles and distinction between role and physical instance.

Hierarchy path (1) — routes to 1 parentless root

Actor (UML) → is a kind of Representation → presupposes Abstraction

Neighborhood in Abstraction Space¶

Actor (UML) sits in a crowded region of the domain-specific corpus (17^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Software Architecture & Modeling Methods (23 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25