Actor (UML)¶

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

Version: v1 · 2026-09-08 · History
Domain-specific #: 3200
Origin domain: software modeling
Subdomain: software modeling

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.

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. 2. 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) — more general patterns this builds on

Actor (UML) is a kind of Representation Prime

The proposed strict upward parent is prime:representation.

Hierarchy path (1) — routes to 1 parentless root

Actor (UML) → Representation → Abstraction

Neighborhood in Abstraction Space¶

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

Family — Software Modeling & Program Architecture (45 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08