Zicomi Systems Logo
contact us  |  your privacy
Company
Services
Products
Support
Resources
  OMG Standards
OMG Logo
UML Element Description
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.
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).
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.
Node Instance
Node Instance    
A node instance represents a distinct instance of a node. It is an actual instance of a resource that carries out the work of the system. It has unique identity as well as attribute values, which determine its state at any point in time. A node instance can exhibit behavior, but only as a result of being an instance of a node. A node instance is an instance of one (and only one) node.
Node
Node    
A node is a physical resource, that carries out some of the work of the system. It can be an electronic, mechanical or human resource.
Message Synchronous
Message Synchronous    
A synchronous message is a visual synonym of a synchronous message. It adds no additional semantics; it is simply an example of the synchronous message adapted for use on a communication diagram. This usage of the synchronous message has the same form as a synchronous message used on other interaction diagrams: a solid line with a solid arrowhead directed from one lifeline to another (possibly reflexive). It has a different appearance from other forms of the synchronous message as it uses a Dewey decimal system (x.y.z) of message sequence labels that indicate the time ordering of messages. There is a single form of presentation in the three different types of interaction diagrams and the two different presentations of the timing diagram.
Actor
Actor    
An actor represents a set of roles that a user plays with an entity (system, subsystem or a class). Actors can be human or other systems, subsystems or classes that represent things outside of the entity. The actor "communicates" with the entity by sending a series of messages backwards and forwards.
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.
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.
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.
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.
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.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.