Skip to content

UML Profile

Package a coherent, additive customization of UML as stereotypes, extensions, properties, constraints, and supporting definitions that apply domain vocabulary to standard UML model elements without replacing their UML identity.

Version
v2 · 2026-09-06 · History
Domain-specific #
3023
Origin domain
software and systems modeling
Subdomain
uml extensibility
Aliases
Profile (UML)

Core Idea

A UML profile is UML's standardized mechanism for packaging a coherent, additive adaptation of an existing metamodel—most often the UML metamodel—for a domain, platform, or method. A profile establishes a namespace, references the metaclasses available for extension, and defines stereotypes whose Extensions attach new terminology, notation, typed properties, and constraints to selected metaclasses. Applying the profile to a model package makes its public stereotypes available for application to eligible UML model elements. The underlying element remains an instance of its UML metaclass: an Interface stereotyped as Home, for example, is still an Interface, now accompanied by an instance of the stereotype and its property values.

Scope of Application

UML Profiles live within UML-based software and systems modeling and adjacent model-driven engineering practices. Their literal scope ends where there is no UML-compatible reference metamodel, stereotype/Extension semantics, and profile application.

Standardized domain modeling languages built on UML. SysML v1 reuses a subset of UML 2 and specifies extensions primarily through the UML profile mechanism; its stereotypes add systems-engineering concepts while its model libraries supply reusable elements. That is a large-scale, standards-governed use of the mechanism, not merely a local tool customization.

Clarity

UML Profile clarifies modeling decisions by forcing four levels that diagrams often blur to be named separately.

First identify the language level. Is the team extending UML through a profile, designing a new metamodel, or merely creating reusable user-model elements? If a proposed domain concept must be a genuinely new modeling element with semantics that cannot remain a Class, Activity, Component, Dependency, or other UML metaclass instance, a profile may be the wrong mechanism.

Manages Complexity

The profile mechanism manages the tension between domain expressiveness and ecosystem reuse. A team that models real-time analysis, systems requirements, enterprise architecture, or a platform directly in unextended UML must repeatedly explain how generic Classes, Activities, Components, and Dependencies should be interpreted. A team that builds a wholly new metamodel must supply editors, validation, interchange, transformation, training, and governance for a separate language. A UML Profile occupies the middle: it packages the domain delta while retaining a UML base that tools and practitioners already understand.

Abstract Reasoning

The signature licenses predictions about a proposed or existing customization.

Base-identity prediction. If a stereotype extends Component, every valid application must accompany a model element that is an instance of that metaclass or a permitted specialization under UML's rules. If users need the domain object to exist independently of any such element, the profile formulation is probably forcing a new language concept into an unsuitable base.

Knowledge Transfer

Within UML-centered modeling, profile knowledge transfers literally across domains by role. A real-time profile, a systems-engineering profile, a platform profile, and an organization-specific governance profile can differ completely in vocabulary while sharing the same architecture: reference metamodel, Profile namespace, stereotypes, Extensions, properties, constraints, ProfileApplication, and profiled elements. A practitioner can transfer the construction and audit procedure without pretending that GaStep, Requirement, or a platform-specific stereotype has the same domain meaning elsewhere.

Relationships to Other Abstractions

Local relationship map for UML ProfileParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.UML ProfileDOMAINPrime abstraction: Formalization — presupposesFormalizationPRIME

Current abstraction UML Profile Domain-specific

Parents (1) — more general patterns this builds on

  • UML Profile presupposes Formalization Prime

    Presupposes prime:formalization. A UML Profile exists as the explicit result of deliberately rendering a domain's modeling vocabulary into a typed, rule-governed artifact that can be applied, checked, exchanged, and versioned.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

UML Profile sits in a sparse region of the domain-specific corpus (82nd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Document Models, Mapping & Maintenance (20 abstractions)

Nearest neighbors

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