Manifestation   A manifestation is an abstraction dependency that describes the physical embodiment of a packageable model element in an artifact. An artifact can have any number of manifestations each of which is a dependency on a single model element.

Explanation

A manifestation is a relationship that describes the dependency that an artifact has on a particular model element. The artifact is said to utilize or embody the particular element meaning that the artifact requires the model element; the artifact is the client and the packageable model element is the supplier. An artifact typically manifests a number of model elements and when an artifact is deployed to a node it is possible to derive the model elements that are deployed to the node by virtue of them being manifested in the artifact. In our natural language we use the word manifest to mean a list of cargo or passengers on an aircraft or other vehicle, the UML meaning is presumably derived from this usage.

Related Entries

Artifact (Icon Presentation)  Used Together An artifact is related to a manifestation because they are used together. The manifestation is an abstraction dependency relationship and the artifact is the client in this relationship. The supplier is the model element that is pointed to by the arrow of the manifestation relationship.

Dependency  Base Type A dependency is a related to a manifestation because it is the base element for the manifestation, which is a stereotyped abstraction dependency. A manifestation has the same semantics as the more generalized dependency but is used specifically between an artifact and a model element, where the artifact acts as the client and the model element as the supplier.