RDF/OWL formalization of the OMG Unified Modeling Language (UML) 2.5.1 metamodel for use in the Linked.Archi architecture knowledge graph. Covers structural classifiers (Class, Interface, Component, Package), behavioral elements (Activity, StateMachine, Interaction), deployment concepts (Node, Artifact), and use cases (Actor, UseCase). Relationship types follow the Linked.Archi three-declaration qualified relationship pattern. This ontology is INFORMED BY the OMG Ontology Definition Metamodel (ODM, formal/2014-09-02) but does NOT apply ODM directly. ODM Annex D maps UML model instances (M1) to OWL; this ontology represents the UML metamodel itself (M2) as OWL classes so that UML model data can be typed in a knowledge graph. We adopt ODM principles (Class→owl:Class, Generalization→rdfs:subClassOf, Package→owl:Ontology) but depart from ODM for associations (three-declaration pattern), enumerations (SKOS), constraints (SHACL), and domain/range (arch:domainIncludes). See the skos:scopeNote for the full comparison. This is not an official OMG document. It is a Linked.Archi interpretation of the UML specification for semantic architecture modeling.
Linked.Archi
Linked.Archi UML 2.5.1 Ontology
Source materials: .reference/omg/uml/formal-17-12-05.pdf — UML 2.5.1 specification (796 pages) .reference/omg/uml/ptc-18-01-01.xmi through ptc-18-01-04.xmi — machine-readable metamodel (242 metaclasses) .reference/omg/odm/ODM-PDF.pdf — ODM 1.1 specification (362 pages) .reference/omg/odm/analysis.md — Analysis of ODM vs Linked.Archi duality .reference/omg/odm/OWLProfile.xmi, RDFProfile.xmi — UML profiles for OWL/RDF (ODM Direction 2, not used) .reference/omg/odm/OWLLibrary.xmi, RDFLibrary.xmi — OWL/RDF vocabulary as UML model libraries
0.1.0: Initial version. Covers UML 2.5.1 structural classifiers, behavioral elements, deployment, use cases, and interactions. Follows ODM mapping rules for MOF→OWL. Relationship types use the Linked.Archi three-declaration pattern.
This ontology uses OWL/RDFS to model the UML metamodel — the inverse of what ODM does. The duality: OMG Stack Linked.Archi (W3C-rooted) ───────── ──────────────────────────── M3: MOF M3: RDFS/OWL (reflective) (defines metamodels) (defines ontologies) M2: UML, BPMN, SysML, OWL M2: uml-onto.ttl (all defined using MOF) (UML metamodel expressed IN OWL) M1: UML model instances M1: RDF individuals (conform to M2) (typed with M2 classes) M0: The real world M0: The real world ODM treats MOF as the universal spine and slots OWL into it as just another M2 metamodel (alongside UML, BPMN, etc.). You author ontologies in UML tools using OWL/RDF profiles. The lingua franca is MOF/XMI; OWL is the payload. Linked.Archi does the inverse: RDFS/OWL is the spine — already reflective, already self-describing — and UML is just one M2 vocabulary expressed in it. The lingua franca is RDF/Turtle; UML (and architectural models) is the payload. This gets you SPARQL, OWL reasoners, SHACL validation, dereferenceable URIs, and the linked-data ecosystem "for free" because models are just RDF. ODM primary use case (authoring OWL ontologies in UML tools) is irrelevant to this stack. What IS relevant: ODM mapping rules (Annex D) as a peer-reviewed reference for how UML constructs should surface in OWL. Where this ontology disagrees with ODM, it is deliberate (three-declaration pattern, SHACL, SKOS, arch:domainIncludes). Note on the M3 framing: The W3C stack is flatter than the four-layer MOF tower. RDFS is reflective (rdfs:Class rdf:type rdfs:Class) and does not need a separate M3 in the OMG sense. We keep the four-layer framing for didactic continuity with OMG-trained colleagues, not because it is structurally necessary. Everything is in one RDF graph; layers are a viewpoint, not a structural fact. See .reference/omg/odm/analysis.md for the full comparison.
A Dependency relating two elements at different abstraction levels. Maps to UML 2.5.1 §7.7 Abstraction.
Abstracts
A whole-part relationship where the part can exist independently of the whole (shared aggregation). Maps to UML 2.5.1 §11.5 Property::aggregation = shared.
Aggregates
A semantic connection between Classifiers. Maps to UML 2.5.1 §11.5 Association. ODM Annex D.3.5 maps UML binary Association to owl:ObjectProperty.
Associated With
A strong whole-part relationship where the part cannot exist without the whole (composite aggregation). Deletion of the whole cascades to the parts. Maps to UML 2.5.1 §11.5 Property::aggregation = composite.
Composed Of
A relationship where a change to the supplier may affect the client. Maps to UML 2.5.1 §7.7 Dependency.
Depends On
A relationship from a DeployedArtifact to a DeploymentTarget. Maps to UML 2.5.1 §19.2 Deployment.
Deployed On
A relationship from an extending UseCase to an extended UseCase. Maps to UML 2.5.1 §18.2 Extend.
Extends
A taxonomic relationship between a more general Classifier and a more specific Classifier. Maps to UML 2.5.1 §9.7 Generalization. ODM Annex D.3.3 maps UML Generalization to rdfs:subClassOf. The direct triple uses this predicate; the qualified form carries metadata.
Generalizes
A relationship that allows the use of unqualified names to refer to members of the imported Package. Maps to UML 2.5.1 §12.2 PackageImport.
Imports Package
A relationship from a base UseCase to an included UseCase. Maps to UML 2.5.1 §18.2 Include.
Includes
A directed relationship between two Packages that indicates that the contents of the merged Package are combined into the receiving Package. Maps to UML 2.5.1 §12.2 PackageMerge.
Merges Package
A relationship between a specification (e.g., Interface) and its implementation (e.g., Class). Maps to UML 2.5.1 §7.7 Realization.
Realizes
A specialized Realization between a BehavioredClassifier and an Interface. Maps to UML 2.5.1 §10.4 InterfaceRealization.
Realizes Interface
A Dependency where the client requires the supplier for its full implementation or operation. Maps to UML 2.5.1 §7.7 Usage.
Uses
The textual body of a Comment or Constraint. Maps to UML 2.5.1 §7.2 Comment::body.
Body
The default value of a Property. Maps to UML 2.5.1 §9.5 Property::defaultValue.
Default Value
An effect Behavior executed when a Transition fires. Maps to UML 2.5.1 §14.2 Transition::effect.
Effect
The file name of an Artifact. Maps to UML 2.5.1 §19.3 Artifact::fileName.
File Name
A guard condition on a Transition or ActivityEdge. Maps to UML 2.5.1 §14.2 Transition::guard.
Guard
Whether the Classifier is abstract. Maps to UML 2.5.1 §9.2 Classifier::isAbstract.
Is Abstract
Whether the Port provides the published functionality of the owning EncapsulatedClassifier. Maps to UML 2.5.1 §11.3 Port::isBehavior.
Is Behavior
Whether the State is a composite state containing Regions. Maps to UML 2.5.1 §14.2 State::isComposite.
Is Composite
Whether the Port is conjugated (provided and required interfaces are swapped). Maps to UML 2.5.1 §11.3 Port::isConjugated.
Is Conjugated
Whether the Property value is derived from other information. Maps to UML 2.5.1 §9.5 Property::isDerived.
Is Derived
Whether the Component is instantiated indirectly. Maps to UML 2.5.1 §11.6 Component::isIndirectlyInstantiated.
Is Indirectly Instantiated
Whether the RedefinableElement cannot be further redefined. Maps to UML 2.5.1 §7.6 RedefinableElement::isLeaf.
Is Leaf
Whether the values of a multi-valued property are ordered. Maps to UML 2.5.1 §7.5 MultiplicityElement::isOrdered.
Is Ordered
Whether the State has multiple Regions (orthogonal). Maps to UML 2.5.1 §14.2 State::isOrthogonal.
Is Orthogonal
Whether the StructuralFeature is read-only. Maps to UML 2.5.1 §9.4 StructuralFeature::isReadOnly.
Is Read Only
Whether the Port is used to provide the published functionality of the owning Component. Maps to UML 2.5.1 §11.3 Port::isService.
Is Service
Whether the Feature is a classifier-level feature. Maps to UML 2.5.1 §9.4 Feature::isStatic.
Is Static
Whether the values of a multi-valued property must be unique. Maps to UML 2.5.1 §7.5 MultiplicityElement::isUnique.
Is Unique
The lower bound of the multiplicity interval. Maps to UML 2.5.1 §7.5 MultiplicityElement::lower.
Lower Bound
The name of a NamedElement. Maps to UML 2.5.1 §7.4 NamedElement::name.
Name
The upper bound of the multiplicity interval. Use -1 for unlimited (*). Maps to UML 2.5.1 §7.5 MultiplicityElement::upper.
Upper Bound
The visibility of a NamedElement (public, private, protected, package). Maps to UML 2.5.1 §7.4 NamedElement::visibility. Values are modeled as SKOS concepts in uml-reference-data.ttl.
Visibility
A qualified relationship representing a UML Abstraction — a Dependency relating elements at different abstraction levels.
Abstraction
An AcceptEventAction waits for the occurrence of one or more specific events. Maps to UML 2.5.1 §16.10 AcceptEventAction.
Accept Event Action
An Action is the fundamental unit of executable functionality. The execution of an Action represents some transformation or processing in the modeled system. Maps to UML 2.5.1 §16.2 Action.
Action
An Activity specifies the coordination of executions of subordinate Behaviors, using a control and data flow model. Maps to UML 2.5.1 §15.2 Activity.
Activity
An ActivityEdge is an abstract class for directed connections between two ActivityNodes. Maps to UML 2.5.1 §15.2 ActivityEdge.
Activity Edge
An ActivityFinalNode is a FinalNode that stops all flows in an Activity. Maps to UML 2.5.1 §15.3 ActivityFinalNode.
Activity Final Node
An ActivityNode is an abstract class for points in the flow of an Activity connected by ActivityEdges. Maps to UML 2.5.1 §15.2 ActivityNode.
Activity Node
An ActivityPartition is a kind of ActivityGroup for identifying ActivityNodes that have some characteristic in common (swim lanes). Maps to UML 2.5.1 §15.6 ActivityPartition.
Activity Partition
An Actor specifies a role played by a user or any other system that interacts with the subject. Actors model a type of role played by an entity that interacts with the subject but which is external to it.
Actor
UML 2.5.1 §18.2: Actors may represent roles played by human users, external hardware, or other systems. An Actor does not necessarily represent a specific physical entity but a particular role of some entity relevant to the specification of its associated UseCases.
A qualified relationship representing a UML shared aggregation — a whole-part relationship where the part can exist independently.
Aggregation
An Artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system. Examples of Artifacts include model files, source files, scripts, and binary executable files.
Artifact
UML 2.5.1 §19.5.1: "An artifact is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system." An Artifact is the source of a Deployment to a Node.
A qualified relationship representing a UML Association — a structural relationship between Classifiers that specifies connections among their instances. Maps to UML 2.5.1 §11.5 Association.
Association
A Behavior is a specification of how its context BehavioredClassifier changes state over time. It is the abstract base for Activity, StateMachine, Interaction, and OpaqueBehavior. Maps to UML 2.5.1 §13.2 Behavior.
Behavior
A Classifier that may have InterfaceRealizations and owned Behaviors. Maps to UML 2.5.1 §10.5 BehavioredClassifier.
Behaviored Classifier
A CallAction is an Action that invokes a Behavior or Operation. Maps to UML 2.5.1 §16.3 CallAction.
Call Action
A Class is a kind of EncapsulatedClassifier whose Features are Properties, Operations, Receptions, Ports, and Connectors. A Class may have attributes (Properties owned by the Class), some of which may represent the ends of binary Associations.
Class
UML 2.5.1 §11.4.3: "Class is a kind of EncapsulatedClassifier whose Features are Properties, Operations, Receptions, Ports and Connectors." Objects of a Class must contain values for each attribute that is a member of that Class, in accordance with the characteristics of the attribute (type, multiplicity).
A Classifier represents a classification of instances according to their features. It is the abstract base for Class, Interface, DataType, Component, and other concrete classifiers. Maps to UML 2.5.1 §9.2 Classifier. ODM maps MOF::Class to owl:Class; Classifier is the UML-level abstraction.
Classifier
A Collaboration defines a set of cooperating roles and their connectors. It represents a pattern of interaction. Maps to UML 2.5.1 §11.7 Collaboration.
Collaboration
A CollaborationUse represents the application of a pattern described by a Collaboration to a specific situation. Maps to UML 2.5.1 §11.7 CollaborationUse.
Collaboration Use
A CombinedFragment defines an expression of InteractionFragments. The operator (alt, opt, loop, break, par, seq, critical, neg, assert, ignore, consider) determines the semantics. Maps to UML 2.5.1 §17.6 CombinedFragment.
Combined Fragment
A textual annotation attached to a set of elements. Maps to UML 2.5.1 §7.2 Comment.
Comment
A CommunicationPath is an association between two DeploymentTargets, through which they are able to exchange signals and messages. Maps to UML 2.5.1 §19.4 CommunicationPath.
Communication Path
A Component represents a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its environment. A Component specifies a formal contract of the services that it provides to its clients and those that it requires from other Components or services in the system in terms of its provided and required Interfaces.
Component
UML 2.5.1 §11.6.3: "A Component is a self-contained unit that encapsulates the state and behavior of a number of Classifiers. A Component is a substitutable unit that can be replaced at design time or run-time by a Component that offers equivalent functionality based on compatibility of its Interfaces." A Component may be manifested by one or more Artifacts, and that Artifact may be deployed to its execution environment.
A qualified relationship representing a UML composite aggregation — a strong whole-part relationship where the part cannot exist without the whole.
Composition
A Connector specifies links that enable communication between two or more instances. Each Connector may be attached to two or more ConnectableElements (Ports, Properties). Maps to UML 2.5.1 §11.2 Connector.
Connector
A ConnectorEnd is an endpoint of a Connector, which attaches the Connector to a ConnectableElement. Maps to UML 2.5.1 §11.2 ConnectorEnd.
Connector End
A condition or restriction expressed in natural language or in a machine-readable language for the purpose of declaring some of the semantics of an element. Maps to UML 2.5.1 §7.6 Constraint.
Constraint
A ControlFlow is an ActivityEdge traversed by control tokens only. Maps to UML 2.5.1 §15.2 ControlFlow.
Control Flow
A ControlNode is an abstract ActivityNode used to coordinate the flows between other nodes. Maps to UML 2.5.1 §15.3 ControlNode.
Control Node
A DataType is a type whose instances are identified only by their value. Maps to UML 2.5.1 §10.2 DataType. ODM Annex D.2.4 (Table D.10) maps to rdfs:Datatype or owl:Class depending on whether it has structural features.
Data Type
A DecisionNode is a ControlNode that chooses between outgoing flows. Maps to UML 2.5.1 §15.3 DecisionNode.
Decision Node
A qualified relationship representing a UML Dependency — a supplier/client relationship where changes to the supplier may affect the client.
Dependency
A qualified relationship representing a UML Deployment — an Artifact is deployed on a DeploymentTarget (Node, Device, ExecutionEnvironment).
Deployment
A DeploymentSpecification specifies a set of properties that determine execution parameters of a component artifact deployed on a node. Maps to UML 2.5.1 §19.3 DeploymentSpecification.
Deployment Specification
A DeploymentTarget is the general concept of a location in which a DeployedArtifact can be deployed. Maps to UML 2.5.1 §19.2 DeploymentTarget.
Deployment Target
A Device is a physical computational resource with processing capability upon which artifacts may be deployed. Maps to UML 2.5.1 §19.4 Device.
Device
The root metaclass for all UML model elements. Maps to UML 2.5.1 §7.2 Element. In the ODM mapping, this corresponds to the root MOF::Element mapped to owl:Class.
Element
A StructuredClassifier that may have Ports. Maps to UML 2.5.1 §11.2 EncapsulatedClassifier.
Encapsulated Classifier
An Enumeration is a DataType whose values are enumerated in the model as EnumerationLiterals. Maps to UML 2.5.1 §10.2 Enumeration. In Linked.Archi, enumeration values are modeled as SKOS concepts in the reference data (see DD-5).
Enumeration
A user-defined data value for an Enumeration. Maps to UML 2.5.1 §10.2 EnumerationLiteral.
Enumeration Literal
An Event is the specification of some occurrence that may potentially trigger effects by an object. Maps to UML 2.5.1 §13.3 Event.
Event
An ExecutionEnvironment is a Node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts. Maps to UML 2.5.1 §19.4 ExecutionEnvironment.
Execution Environment
An ExecutionSpecification is a specification of the execution of a unit of Behavior or Action within the Lifeline (the activation bar). Maps to UML 2.5.1 §17.5 ExecutionSpecification.
Execution Specification
A qualified relationship representing a UML Extend — an extending UseCase conditionally augments the behavior of an extended UseCase.
Extend
An ExtensionPoint identifies a point in the behavior of a UseCase where that behavior can be extended by the behavior of some other UseCase. Maps to UML 2.5.1 §18.2 ExtensionPoint.
Extension Point
A Feature declares a behavioral or structural characteristic of Classifiers. Maps to UML 2.5.1 §9.4 Feature.
Feature
A FinalNode is an abstract ControlNode at which a flow in an Activity stops. Maps to UML 2.5.1 §15.3 FinalNode.
Final Node
A FinalState represents the completion of activity in the enclosing Region. Maps to UML 2.5.1 §14.2 FinalState.
Final State
A FlowFinalNode is a FinalNode that terminates a flow without terminating the overall Activity. Maps to UML 2.5.1 §15.3 FlowFinalNode.
Flow Final Node
A ForkNode is a ControlNode that splits a flow into multiple concurrent flows. Maps to UML 2.5.1 §15.3 ForkNode.
Fork Node
A FunctionBehavior is an OpaqueBehavior that does not access or modify any objects or other external data. Maps to UML 2.5.1 §13.2 FunctionBehavior.
Function Behavior
A qualified relationship representing a UML Generalization — a taxonomic relationship from specific to general Classifier.
Generalization
A qualified relationship representing a UML Include — a base UseCase incorporates the behavior of an included UseCase.
Include
An InformationFlow specifies that one or more information items circulate from its sources to its targets. Maps to UML 2.5.1 §20.2 InformationFlow.
Information Flow
An InformationItem represents an abstraction of data that can be conveyed between two entities. Maps to UML 2.5.1 §20.2 InformationItem.
Information Item
An InitialNode is a ControlNode at which flow starts when the Activity is invoked. Maps to UML 2.5.1 §15.3 InitialNode.
Initial Node
An Interaction is a unit of Behavior that focuses on the observable exchange of information between connectable elements.
Interaction
UML 2.5.1 §17.2: "An Interaction is a unit of Behavior that focuses on the observable exchange of information between connectable elements." Interactions are the semantic foundation for Sequence Diagrams, Communication Diagrams, Timing Diagrams, and Interaction Overview Diagrams.
An InteractionOperand is a region within a CombinedFragment guarded by an InteractionConstraint. Maps to UML 2.5.1 §17.6 InteractionOperand.
Interaction Operand
An InteractionUse refers to an Interaction. It is a means of copying a portion of the referred Interaction into the enclosing Interaction (the "ref" fragment). Maps to UML 2.5.1 §17.7 InteractionUse.
Interaction Use
An Interface is a kind of Classifier that represents a declaration of a set of public Features and obligations that together constitute a coherent service. An Interface specifies a contract; any instance of a Classifier that realizes the Interface shall fulfill that contract.
Interface
UML 2.5.1 §10.4.3: "An Interface specifies a contract; any instance of a Classifier that realizes the Interface shall fulfill that contract. The obligations associated with an Interface are in the form of constraints (such as pre- and postconditions) or protocol specifications." Interfaces may not be instantiated directly.
A qualified relationship representing a UML InterfaceRealization — a BehavioredClassifier fulfills the contract of an Interface.
Interface Realization
A JoinNode is a ControlNode that synchronizes multiple flows. Maps to UML 2.5.1 §15.3 JoinNode.
Join Node
A Lifeline represents an individual participant in the Interaction. Maps to UML 2.5.1 §17.3 Lifeline.
Lifeline
A Manifestation is the concrete physical rendering of one or more model elements by an artifact. Maps to UML 2.5.1 §19.3 Manifestation.
Manifestation
A MergeNode is a ControlNode that brings together multiple alternate flows without synchronization. Maps to UML 2.5.1 §15.3 MergeNode.
Merge Node
A Message defines a particular communication between Lifelines of an Interaction. Maps to UML 2.5.1 §17.4 Message.
Message
A MessageOccurrenceSpecification represents the sending or receiving of a Message. Maps to UML 2.5.1 §17.4 MessageOccurrenceSpecification.
Message Occurrence Specification
A Model is a Package that contains a complete description of the modeled system from a particular viewpoint. Maps to UML 2.5.1 §12.2 Model.
Model
An element that has a name and visibility within a namespace. Maps to UML 2.5.1 §7.4 NamedElement.
Named Element
A named element that can own other named elements, providing a naming scope. Maps to UML 2.5.1 §7.4 Namespace.
Namespace
A Node is a computational resource upon which Artifacts may be deployed, via Deployment relationships, for execution. Nodes can be interconnected through communication paths.
Node
UML 2.5.1 §19.4.3: "A Node is computational resource upon which Artifacts may be deployed, via Deployment relationships, for execution. For advanced modeling applications, Nodes may have complex internal structure defined by nested Nodes." Nodes form a deployment topology.
An ObjectFlow is an ActivityEdge that can have objects or data passing along it. Maps to UML 2.5.1 §15.2 ObjectFlow.
Object Flow
An ObjectNode is an ActivityNode that indicates an instance of a particular Classifier, possibly in a particular state, may be available at a particular point in the Activity. Maps to UML 2.5.1 §15.4 ObjectNode.
Object Node
An OpaqueBehavior is a Behavior whose specification is given in a textual language other than UML. Maps to UML 2.5.1 §13.2 OpaqueBehavior.
Opaque Behavior
A behavioral feature of a Classifier that specifies the name, type, parameters, and constraints for invoking an associated Behavior. Maps to UML 2.5.1 §9.6 Operation.
Operation
A Package is used to group elements and provides a namespace for the grouped elements. Maps to UML 2.5.1 §12.2 Package. ODM Annex D.3.2 maps MOF::Package to owl:Ontology.
Package
A qualified relationship representing a UML PackageImport.
Package Import
A qualified relationship representing a UML PackageMerge.
Package Merge
A named element that may be owned directly by a Package. Maps to UML 2.5.1 §7.4 PackageableElement.
Packageable Element
A specification of an argument used to pass information into or out of an invocation of a BehavioralFeature. Maps to UML 2.5.1 §9.4 Parameter.
Parameter
A Port is a property of an EncapsulatedClassifier that specifies a distinct interaction point between the classifier and its environment or between the classifier and its internal parts. Maps to UML 2.5.1 §11.3 Port.
Port
A PrimitiveType defines a predefined DataType without any substructure. Typical examples are Integer, Boolean, String, and UnlimitedNatural. Maps to UML 2.5.1 §10.2 PrimitiveType.
Primitive Type
A Profile defines limited extensions to a reference metamodel with the purpose of adapting the metamodel to a specific platform or domain. Maps to UML 2.5.1 §12.3 Profile.
Profile
A ProfileApplication is used to show which Profiles have been applied to a Package. Maps to UML 2.5.1 §12.3 ProfileApplication.
Profile Application
A Property is a StructuralFeature that represents an attribute of a Classifier or an end of an Association. Maps to UML 2.5.1 §9.5 Property. ODM Annex D.3.4 maps UML Property to owl:DatatypeProperty (for attributes) or owl:ObjectProperty (for association ends).
Property
A Pseudostate is an abstraction that encompasses different types of transient Vertices in the StateMachine graph (initial, choice, junction, fork, join, etc.). Maps to UML 2.5.1 §14.3 Pseudostate.
Pseudostate
A qualified relationship representing a UML Realization — a relationship between a specification and its implementation.
Realization
An element that, when defined in the context of a classifier, can be redefined more specifically in the context of another classifier that specializes the first. Maps to UML 2.5.1 §7.6 RedefinableElement.
Redefinable Element
A Region is a top-level part of a StateMachine or a composite State, containing States and Transitions. Maps to UML 2.5.1 §14.2 Region.
Region
A SendSignalAction creates a Signal instance and transmits it to the target object. Maps to UML 2.5.1 §16.3 SendSignalAction.
Send Signal Action
A Signal is a specification of a kind of communication between objects in which a reaction is asynchronously triggered in the receiver without a reply. Maps to UML 2.5.1 §10.3 Signal.
Signal
A State models a situation during which some invariant condition holds. The invariant may represent a static situation such as an object waiting for some external event. Maps to UML 2.5.1 §14.2 State.
State
A StateInvariant is a runtime constraint on the participants of the Interaction. Maps to UML 2.5.1 §17.8 StateInvariant.
State Invariant
A StateMachine specifies the behavior of a part of a system through a finite state-transition system. Maps to UML 2.5.1 §14.2 StateMachine.
State Machine
A Stereotype defines how an existing metaclass may be extended as part of a Profile. Maps to UML 2.5.1 §12.3 Stereotype. In the ODM mapping, stereotypes become OWL classes that extend the stereotyped metaclass via rdfs:subClassOf.
Stereotype
A typed feature of a Classifier that specifies the structure of instances. Maps to UML 2.5.1 §9.4 StructuralFeature.
Structural Feature
A Classifier whose behavior can be fully or partly described by the collaboration of owned or referenced instances. Maps to UML 2.5.1 §11.2 StructuredClassifier.
Structured Classifier
A Transition is a directed relationship between a source Vertex and a target Vertex. It may be part of a compound transition, which takes the StateMachine from one stable State configuration to another. Maps to UML 2.5.1 §14.2 Transition.
Transition
A Trigger specifies an Event that may cause the execution of an associated Behavior. Maps to UML 2.5.1 §13.3 Trigger.
Trigger
A Type constrains the values represented by a TypedElement. Maps to UML 2.5.1 §7.5 Type.
Type
A named element that has a type. Maps to UML 2.5.1 §7.5 TypedElement.
Typed Element
A qualified relationship representing a UML Usage — a Dependency where the client requires the supplier for its implementation.
Usage
A UseCase specifies a set of actions performed by its subjects, which yields an observable result that is of value for one or more Actors or other stakeholders of the subject.
Use Case
UML 2.5.1 §18.2: "A UseCase is a kind of BehavioredClassifier that represents a declaration of a set of offered Behaviors. Each UseCase specifies some behavior that a subject can perform in collaboration with one or more Actors." UseCases define the offered behavior of the subject without reference to its internal structure.
A Vertex is an abstraction of a node in a StateMachine graph. It can be the source or target of any number of Transitions. Maps to UML 2.5.1 §14.2 Vertex.
Vertex