Zicomi Systems Logo
contact us  |  your privacy
Company
Services
Products
Support
Resources
  OMG Standards
OMG Logo
UML Element Description
Component (Icon Presentation)
Component (Icon Presentation)    
A component is a modular, deployable and replaceable part of a system, it contains model elements and packages them to present a set of interfaces.
Component (keyword)
Component (keyword)    
A component (keyword) is a visual synonym of a component. It adds no additional semantics; it is simply an alternative presentation of the element.
Component Instance
Component Instance    
A component instance represents a distinct instance of a component. It has a unique identity and attribute values, which determine its state at any point in time. A component instance can exhibit behavior, but only as a result of being an instance of a component. A component instance is an instance of one and only one component.
Assembly Connector
Assembly Connector    
An assembly connector is a kind of connector that is specialized for use in component modeling. It is used to connect the provided interface or port of one component to the required interface or port of another component.
Port
Port    
A port is both a connectable element and a structural feature of an encapsulated classifier. A port specifies the way a classifier interacts with its external environment or the way the internal environment of the classifier provides services to its external environment. A port may be connected directly to other elements in its external environment but typically uses interfaces to declare either the services that it provides or the services that it requires. A port can be connected to the internal environment of the classifier by connectors. The connectors forward incoming requests to elements in the internal environment or outgoing requests to the ports.
Port typed by Provided Interface
Port typed by Provided Interface    
A port typed by provided interface is both a connectable element and a structural feature of an encapsulated classifier. The provided interface specifies the services that the classifier offers through this port. Requests that arrive at the port are handled either directly by the classifier or by one or more of its parts.
Port typed by Required Interface
Port typed by Required Interface    
A port typed by required interface is both a connectable element and a structural feature of an encapsulated classifier. The required interface specifies the services that the classifier uses (requires) through the port. Requests that arrive at the port are provided by the classifier that realizes the interface specified by the port.
Part
Part    
A part is a property of a classifier and is used to represent the structural composition of a classifier. A part represents a set of instances either owned by the classifier or referenced by the classifier. The instances corresponding to its part may be created when the instance of the containing classifier is created or at some other point in its lifetime. When the containing classifier is destroyed all instances representing the parts are also destroyed. A part can declare a multiplicity, which indicates the allowable number of instances corresponding to the property (part) that can exist within the containing classifier. The multiplicity expression typically follows the name but may be placed in the top right hand corner of the part. Parts may be related to each other using connectors.
Delegation Connector
Delegation Connector    
A delegation connector is a kind of connector that is specialized for use in component modeling. It is used to show how the specification of behavior is realized by a component. When a delegation connector is specified, any signals arriving at the port will be passed (delegated) onto an internal part, which may be another component or a part owned by the component. Similarly when a component needs to communicate with its external environment, these signals are passed from the internal part or component to a port or interface via a delegation connector.
Dependency
Dependency    
A dependency is a type of relationship that signifies that one element, or group of elements, acting as the client depends on another element or group of elements that act as a supplier. It is a weak relationship that denotes that if the supplier is changed the client may be affected. It is a unidirectional relationship.
Connector
Connector    
A connector is a feature that is used in the description of composite structures. It specifies that two or more instances are able to communicate with each other in some way. The connector does not specify how the communication is achieved but simply that it is possible. In practice the instances may be able to communicate because there is a link (instance of an association) connecting the elements or because one instance has access to another through parameter passing.
Interface (Required)
Interface (Required)    
A required interface is a type of classifier that specifies services that another classifier needs (requires) to carry out its work. A required interface is an external view of the classifier and does not indicate how the classifier will actually perform its work, just an aspect of what it requires to do so. A required interface is an expression of a contract that the classifier has with other parts of the system.
Subsystem
Subsystem    
A subsystem is a grouping or package of model elements that has operations and interfaces. It has the characteristics of a package and a classifier. While a subsystem is a behavior element, it has no intrinsic behavior of it s own, the behavior is provided by the elements in the realization compartment of the subsystem.
Interface (Provided)
Interface (Provided)    
An interface (provided) specifies a set of abstract operations. The operations are the external view of the classifier and do not reveal to the client the way that the operations are implemented by the classifier. An interface is conceptually an abstract classifier without attributes. A classifier is said to "implement an interface" if it provides the implementation of all or some of the operations declared by the interface. This relationship is shown by a realization drawn from the classifier with the arrow pointing to the interface. An interface cannot have instances.
Interface
Interface    
An interface can be represented by a classifier (rectangular) symbol. Both this form, and the more commonly seen "lollipop" (small circle and stem) form, have the same semantics. The circular form is often used when a structural view of a system is required. When an interface has operations and these need to be displayed as part of a diagram the rectangular form can be used, the operations appear in a separate compartment.
Artifact (Icon Presentation)
Artifact (Icon Presentation)    
An artifact is the specification of a piece of information that is utilized or created as part of a software development process or is produced as a product of a running system. An artifact is a classifier and as such can have instances, which are the development or runtime expressions (instances) of the artifact.
Artifact Instance
Artifact Instance    
An artifact instance represents a distinct instance of an artifact. It is a piece of information that is utilized or created as part of a software development process or is produced as a product of a running system. It has a unique identity and state and defines the values of the properties specified in the artifact of which it is an example. An artifact instance can exhibit behavior, but only as a result of being an instance of an artifact.
Realization
Realization    
A realize signifies that a relationship exists between a set of elements that form a specification (the client) and another set of elements that form the implementation (the supplier).
Attribute
Attribute    
An attribute is a string item listed in the attribute compartment of a classifier. An attribute defines an aspect or dimension of a classifier. An attribute may be assigned a value when an instance of a classifier is created. It is semantically equivalent to a classifier having a composite association with another classifier of the type specified in the attribute expression.
Operation
Operation    
An operation is a string item listed in the operation compartment of a classifier. The operations define the behavior of the classifier and the work that the classifier can carry out. An operation can take a list of parameters and return a type. Its visibility can be restricted and other factors, such as concurrency, can be specified using the property-string.
Class
Class    
A class represents some concept, physical or otherwise, in the system being modeled. Classes describe sets of things or concepts that have similar attributes, behavior and relationships. They are a higher order concept to objects, which represent instances of the class.
Object
Object    
An object represents a distinct instance of a class. It has unique identity as well as attribute values, which determine its state at any point in time. An object can exhibit behavior, but only as a result of being an instance of a class. An object is an instance of one and only one class.
Package
Package    
A package is a grouping of model elements. Packages group any set of zero or more model elements, including packages themselves, with the condition that no model element exists in more than one package. The package also defines the extent of names.
Artifact (Keyword Presentation)
Artifact (Keyword Presentation)    
An artifact (keyword presentation) is a visual synonym of an artifact. It adds no additional semantics; it is simply an alternative presentation of the element. The standard form of this element is considered to be the artifact displayed with a small icon in the top left hand corner of a classifier rectangle.
Component (lugged)
Component (lugged)    
A component (lugged) is a visual synonym of a component. It adds no additional semantics; it is simply an alternative presentation of the element. This presentation style was used in versions of UML prior to UML 2.0, it has been superseded but may still be used as an alternative presentation.
Comment (Note)
Comment (Note)    
A comment can contain textual information or graphical symbols that add additional information to a diagram or model. The information can take many forms from very formal, in the case of constraints, to conversational, in the case of working notes. Comments can be placed anywhere in a model or diagram, and simply by their proximity and alignment; they can be applicable to one or more elements. They may also be attached either to one or more elements by a comment attaching line.
Comment (Note) Attaching Line
Comment (Note) Attaching Line    
A comment attaching line is a dashed line that is used to attach a comment (note) to a model element in a diagram. The comment (note) attaching line is not a UML relationship and has no semantics beyond signifying that the contents of a comment apply to the model element it is attached to. A comment may be attached to any number of model elements or may exist in isolation and by placement in proximity to one or more model elements signify that it applies to those elements.
Diagram
Diagram    
A diagram is a graphical device for representing a part of a UML model. A model is typically comprised of a number of diverse elements that are vertices connected by edges in a graph representing the semantic and structural elements of the model. A UML diagram will typically display a subset of the model and will commonly consist of a number of elements that have structural or behavioral significance when viewed together. A diagram has a frame that acts as a boundary to separate its contents-area from other diagrams and a heading which contains a string that lists the kind of diagram, its name and parameters of the namespace.
Composite
Composite    
The value of composite for the aggregation property of an association end signifies a whole-part relationship between two classifiers where the whole has responsibility for the parts. An association, with one of its ends specifying a value of composite, is commonly called a composition relationship. It is stronger than an unadorned association end, adding the concept of whole (filled diamond end) and part relationship. It is also stronger than an aggregate, because the classifier at the whole end has responsibility for the lifetime of any parts. Only one end of a binary association can be adorned with a composition symbol. Formally it is one of three values that can be set for the aggregation property of an association end the others being none and aggregate.
Aggregate
Aggregate    
The value of aggregate for the aggregation property of an association end signifies a whole-part relationship between two classifiers. An association, with one of its ends specifying a value of aggregate is commonly called an aggregation relationship. It is a stronger than an unadorned association end, adding a concept of a whole (hollow diamond end) part relationship. The whole does not have responsibility for the lifetime of the parts. Only one end of a binary association can be adorned with an aggregation symbol. Formally it is one of three values that can be set for the aggregation property of an association end the others being none and composite.
Association End
Association End    
An association end is the endpoint of an association that marks the point at which the line connects with a classifier. An association end has a name (role name) and a series of properties that determine the semantics of how the classifier participates in the relationship. A binary association has exactly two association ends and an n-ary association has 'n' association ends.
Public Visibility
Public Visibility    
When the value of public is specified for the visibility property of an association end it signifies that other classifiers in addition to the classifier connected at the source end of the association can traverse the relationship and use the role name in expressions.
Protected Visibility
Protected Visibility    
When the value of protected is specified for the visibility property of an association end it signifies that the classifier at the source (far) end of the association and its descendants may traverse the relationship and use the role name in expressions.
IsNavigable
IsNavigable    
The value of the isNavigable property specifies whether an association can be traversed from the source (far end) to the target (near end). It is indicated graphically by an open headed arrow.
Private Visibility
Private Visibility    
When the value of private is specified for the visibility property of an association end it signifies only the classifier connected at the source (far) end may traverse the relationship and use the role name in expressions.
Multiplicity
Multiplicity    
multiplicity is a property of an association end that specifies the number of instances of the classifier connected at the target end (near end) that can be associated with a single instance of the classifier at the source end (far end). It is specified in the form of a string stipulating a possible infinite number governed by a lower and upper bound.
Package Visibility
Package Visibility    
When the value of package is specified for the visibility property of an association end it signifies that any classifier that is contained in the same package as the association (or any nested sub package) may traverse the relationship and use the role name in expressions.
Non-Navigable
Non-Navigable    
An association end is non-navigable if it is marked with an x. This icon is optional and is used to indicate that the classifier at the other end (source) of the association has no access to the classifier at the end (target) marked with the x.
Ordered
Ordered    
The value ordered can be set for the ordering property of an association end. This signifies that instances of the classifiers at the target end of the association are ordered. Any operation that adds or changes the instances is responsible for maintaining the order. The multiplicity at the target end must be greater than one since a value of one or less would specify a set with one or less elements, for which ordering would be meaningless.
Bag
Bag    
A value of bag specified for the property string of an association end indicates that the same instance can appear more than once in the collection. By default an association end is a set of instances, meaning that there cannot be duplicate elements. By setting the value to bag this default behavior is overridden and duplicates can occur.
Sequence
Sequence    
A value of sequence specified for the property string of an association end indicates that the collection of instances are an ordered bag. This means that the collection is ordered but can contain duplicated instances. It does not specify the basis for the order.
Subsets
Subsets    
A value of subsets specified for the property string of an association end indicates that the collection does not contain all the available instances defined by the named property. This is an application of the mathematical concept of subset, which means that every instance at the association end marked as subsets, must exist in the parent property.
Create Dependency
Create Dependency    
A create dependency is a usage dependency that signifies that one or more of the operations on the client (tail end) create instances of the supplier classifier (arrowhead end).
Manifestation
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.
Instantiate Dependency
Instantiate Dependency    
An instantiate dependency is a usage dependency that exists between classifiers and indicates that the client classifier (tail end) creates instances of the supplier (arrowhead end).
Trace Dependency
Trace Dependency    
A trace dependency is an abstraction dependency between a supplier and a client that indicates that one or more elements in one model represent an analogous concept in another model. Its meaning depends on the relationship between the models.
Send Dependency
Send Dependency    
A send dependency is a type of usage dependency that exists between an operation in a classifier and a signal. It signifies that the operation (tail end) can send the signal. (arrowhead end).
Derive Dependency
Derive Dependency    
A derive dependency is an abstraction dependency that indicates that the client (tail end) can always be calculated from the supplier (arrowhead). This implies that the client is strictly redundant, and may be modeled for performance reasons or ease of use.
Unordered
Unordered    
The value unordered for the ordering property signifies that instances of the classifiers at the target end of the association are not ordered. This is the default value for this property and if a value for the property is not specified then the value by default is unordered. The multiplicity at the target end must be greater than one since a value of one or less would specify a set with one or less elements, for which ordering would be meaningless.
Refine Dependency
Refine Dependency    
A refine dependency is an abstraction dependency that implies that the client (tail end) is a refinement or more evolved element. This refinement may signify different version of the same element or extensions.
Call Dependency
Call Dependency    
A call dependency connects an operation in one class, the source to an operation in another class, the target. The relationship may be made less precise by attaching either the source or target or both ends to the classes that contain the operations.
Redefines
Redefines    
A value of redefines specified for the property string indicates that the association end is redefined with the name specified. This mechanism allows an association end to be recast using a new name and potentially new properties that are more appropriate at any given level of specialization (redefinition).
Union
Union    
A value of union specified for the property string indicates that the association end is derived by the union of the subsets with the name specified. This mechanism allows the classifier at the association end marked with union to specify its instances based on the union of its subsets. This is an application of the mathematical concept of union of sets and subsets. This implies that the collection is a set and cannot be a bag since a union results in a set, which means it cannot have duplicate elements.
Derived
Derived    
A value of derived indicated by a forward slash (/) either prefixing the name or in isolation, indicates that the association end is derived. This means that its value can be calculated from other properties of the instance.
Unified Modeling Language and UML are either registered

trademarks or trademarks of Object Management Group, Inc. in the

United States and/or other countries.