Stereotype (UML)¶

A UML profile mechanism that specializes an existing metaclass with domain-specific semantics, tagged values and notation.

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

Core Idea¶

A stereotype cannot arbitrarily change UML metamodel rules, differs from an ordinary class stereotype and works with tagged values and constraints inside a declared profile. A profile declares an extension from a stereotype to a UML metaclass, model elements apply it and additional properties, constraints and icons convey specialized meaning while remaining valid UML instances. 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¶

Stereotype (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 UML and profile versions, stereotype name, extended metaclass, extension multiplicity and required status, tagged-value properties, constraints, notation and icons, applying model elements and tool interoperability are explicit. The scope is broad within that domain but bounded by the need for the UML and profile versions, stereotype name, extended metaclass, extension multiplicity and required status, tagged-value properties, constraints, notation and icons, applying model elements and tool interoperability are explicit. The entry records a descriptive analytical identity; practical use requires the governing domain's evidence, standards, and safety obligations.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the UML and profile versions, stereotype name, extended metaclass, extension multiplicity and required status, tagged-value properties, constraints, notation and icons, applying model elements and tool interoperability 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 Stereotype (UML). Stereotype (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 UML and profile versions, stereotype name, extended metaclass, extension multiplicity and required status, tagged-value properties, constraints, notation and icons, applying model elements and tool interoperability 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, A profile declares an extension from a stereotype to a UML metaclass, model elements apply it and additional properties, constraints and icons convey specialized meaning while remaining valid UML instances., and type the carrier, state every parameter and convention in the definition, test that the UML and profile versions, stereotype name, extended metaclass, extension multiplicity and required status, tagged-value properties, constraints, notation and icons, applying model elements and tool interoperability are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Stereotype (UML) Domain-specific

Parents (1) — more general patterns this builds on

Stereotype (UML) is a kind of Schema Prime

The proposed strict upward parent is prime:schema.

Hierarchy path (1) — routes to 1 parentless root

Stereotype (UML) → Schema → Abstraction

Neighborhood in Abstraction Space¶

Stereotype (UML) sits in a crowded region of the domain-specific corpus (37^th 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