| Previous | UML Classes | Table of Contents | UML Packages | Next |
The ComponentRealization concept is specialized in the Components package to (optionally) define the Classifiers that realize
the contract offered by a component in terms of its provided and required interfaces. The component forms an abstraction from
these various Classifiers.
•
Realization (from Dependencies ) on page 131
(merge increment)
In the metamodel, a ComponentRealization is a subtype of Dependencies ::Realization.
No additional attributes
Issue 8976 -add ‘abstraction’ and ‘realizingClassifier’ entries
• abstraction : Component [0..1] The Component that own this Realization and which is implemented by its realizing classifiers.{Subsets Element::owner, DirectedRelationship ::source, Dependency ::client}
• realizingClassifier : Classifier [1] A classifier that is involved in the implementation of the Component that owns this Realization. {Subsets Dependency ::supplier, DirectedRelationship ::target}
No additional constraints
Issue 9119 - replace first sentence
A component’s behavior may typically be realized (or implemented) by a number of Classifiers. In effect, it forms an abstraction
for a collection of model elements. In that case, a component owns a set of Component Realization Dependencies to these Classifiers.
In effect, it forms an abstraction for a collection of model elements. In that case, a component owns a set of Realization
Dependencies to these Classifiers.
It should be noted that for the purpose of applications that require multiple different sets of realizations for a single
component specification, a set of standard stereotypes are defined in the UML Standard Profile. In particular, «specification»
and «realization» are defined there for this purpose.
A component realization is notated in the same way as the realization dependency (i.e., as a general dashed line with an open
arrow-head).
The following changes from UML 1.x have been made: Realization is defined in UML 1.4 as a ‘free standing’ general dependency
- it is not extended to cover component realization specifically. These semantics have been made explicit in UML 2.0.