Zicomi Systems Logo
contact us  |  your privacy
Company
Services
Products
Support
Resources
  OMG Standards
OMG Logo
  Have You Heard?
UML Diagrams
Zicomi Systems publishes some UML example diagrams online from the world famous UML dictionary.
more...
Version 2.5 Released
Zicomi Systems is delighted to announce that version 2.5 of Zicomi Mentor is released. With support for UML 2.0 and all thirteen UML diagrams
more...
Zicomi Systems' Director
speaks about the UML at Objects by Design - an informative interview
more...
Partner Programme
Zicom Systems is delighted to announce a new world wide partner programme, become a partner today.
more...
OMG Member
Zicom Systems is made a member of the OMG!
UML Element Description
Data Store
Data Store    
A data store node is a type of central buffer node and can therefore store (buffer) tokens. It adds the additional mechanism to keep a copy of the tokens even when they are passed out of the node via an outgoing object flow. Whenever an incoming token contains an object or piece of data that already exists in the data store the incoming token replaces the existing one.
Decision Node
Decision Node    
A decision node is a control node that has one incoming flow and two or more outgoing flows. When a token arrives at a decision node it is offered to all the outgoing flows, one (and only one) of which accepts the token. Tokens cannot be detained at the node, nor are they copied; they are passed onto an outgoing flow. The guards (conditions) on the outgoing flows determine which flow will accept the token. The incoming flow and all outgoing flows must be either all control flows or all object flows.
Deep History
Deep History    
A deep history is a kind of pseudostate that acts as a marker or placeholder. It represents the most recent active substate of the containing composite state, and the substates of that substate. It is not a state itself but a diagrammatic representation or marker for the "condition" of the composite state down to any level, at the time it was last exited.
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.
Deployment
Deployment    
A deployment is a type of dependency. It is a directed relationship between one or more deployed artifacts and a deployment target. The deployment target is the location where the artifact is deployed and can be a device, execution environment or a property. The deployment can be used to describe the relationship at a type or instance level. A component deployment is a specialized form of deployment that can have one or more deployment specifications that govern the way the artifact is deployed.
Deployment (nested)
Deployment (nested)    
A deployment (nested) is a visual synonym of a deployment. It is an alternative and useful way of expressing the deployment relationship. It is often more visually appealing to audiences not familiar with the UML as the containment of an artifact inside a deployment target such as a node is easier to understand. When there are a large number of artifacts deployed to a particular deployment target it is often more appropriate to use the deployment relationship in its linear form as the contents of the deployment target can become congested.
Deployment Specification
Deployment Specification    
A deployment specification is an artifact that specifies a set of properties that governs the way an artifact will execute on a node. Typically a deployment specification specifies the properties for a particular type of execution environment. It is itself a type of artifact and therefore a classifier and can have instances.
Deployment Specification Instance
Deployment Specification Instance    
A deployment specification instance is a distinct instance of a deployment specification. While the deployment specification specifies a set of properties that govern the way an artifact will execute on a node, a deployment specification instance gives these properties actual values. Typically a deployment specification specifies values of the properties for a particular type of execution environment. It is itself a type of artifact instance and is owned by a deployment.
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.
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.
Device
Device    
A device is a type of node. It is a physical resource and has the power to perform computations. Artifacts and components can be deployed to a device and typically rely upon services offered by the device to carry out their work. A device may be composed of other devices as part of a hierarchy of nested devices.
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.
Disjoint
Disjoint    
Disjoint is a constraint added to a set of generalization relationships to indicate that an instance of the parent may be an instance of one and only one of the children within the set.
Duration Constraint
Duration Constraint    
A duration constraint is a type of interval constraint that specifies that one or more model elements must conform to a restriction specified by a duration interval. A duration constraint is not the duration interval itself but a constraint, which associates the interval with one or more elements, specifying how the interval restricts the duration semantics of the element(s).
Element Import
Element Import    
An element import is a directed relationship between a packageable element (arrowhead end) and an importing namespace (tail end). The element that is pointed to is added to the namespace, allowing the element to be used in the namespace without any qualification. A name can be added to the element import relationship, which is used as an alias (alternative name) for the element in the importing namespace. The visibility of the element in the importing namespace is by default public.
Element Import (Access)
Element Import (Access)    
An element import with the keyword access is a directed relationship between a packageable element (arrowhead end) and an importing namespace (tail end). The element that is pointed to is made accessible to the namespace, allowing the element to be used in the namespace without any qualification. It is different from an element import with keyword import because it does not import the element into the namespace but rather just allows it to be accessed. A name can be added to the element import relationship, which is used as an alias (alternative name) for the element in the importing namespace. The visibility of the element in the importing namespace is by default public.
Entity
Entity    
An entity is a stereotyped class, that has the responsibility of providing services to a number of entity classes and thus in turn to boundary classes.
Entry Connection Point Reference
Entry Connection Point Reference    
An entry connection point reference represents the entry point to a submachine state. It provides a target for a transition to a submachine state and is the only way that a submachine state can be referenced. A submachine state may have any number of entry connection point references and these represent entry point pseudostates defined in the submachine state.
Entry Point
Entry Point    
An entry point is a pseudostate that marks the point of entry to the region in a state machine in which it is enclosed. It has a single outgoing transition to a vertex in the same region. An entry point can only be defined for the top most regions of a state machine and not for regions owned by other regions. Each topmost region of a state machine can contain one (and only one) entry point.
Event Occurrence (General Value)
Event Occurrence (General Value)    
An event occurrence is both a type of interaction fragment and a type of message end. Event occurrences mark the points on a lifeline where events occur. An event occurrence is the basic unit of meaning in an interaction. A lifeline is used to describe the way an instance, or a classifier playing a role, changes over time and event occurrences mark the points on lifelines where messages start or end.
Exception Edge
Exception Edge    
An exception edge is a type of activity edge drawn as a lighting bolt. It connects the executable node that is being protected by an exception handler to an exception input node on the border of the exception handler.
Exception Handler
Exception Handler    
An exception handler is an element that allows an action (protected node) to be protected by specifying an alternate action to execute when a certain condition or event occurs in the execution of the protected node. The alternate action called the handler has an input pin, which specifies the type of the exception. The handler will only be invoked if the type of the exception is the same or a child of the type specified by the handler.
Execution Environment
Execution Environment    
An execution environment is a type of node. It is a logical resource that acts as a location to deploy specific types of artifacts and components, and has the power to perform computations. Artifacts and components can be deployed to an execution environment and typically rely upon services offered by the execution environment to carry out their work.
Execution Occurrence
Execution Occurrence    
An execution occurrence (activation) represents a period in the participant 's lifetime when it is performing an action or waiting for another participant to complete an action and return. A lifeline can have a number of execution occurrences that and these will be positioned along the lifeline, obscuring the dashed line.
Exit Connection Point Reference
Exit Connection Point Reference    
An exit connection point reference represents the exit point to a submachine state. It provides a source for a transition leaving a submachine state and is the only way that a submachine state can be referenced. A submachine state may have any number of exit connection point references and these represent exit point pseudostates defined in the submachine state.
Exit Point
Exit Point    
An exit point is a pseudostate that marks the point of exit from the region in a state machine in which it is enclosed. It may have one or more incoming transitions from vertices in the same region. An exit point can only be defined for the top most regions of a state machine and not for regions owned by other regions. Each topmost region of a state machine can contain any number of exit points.
Expansion Node
Expansion Node    
An expansion node is a type of object node. They are used exclusively with expansion regions. An object flow that arrives at an expansion node contains a collection of objects or data, which are separated by the expansion node before being passed onto elements within the region. A region must have one or more expansion nodes receiving input and may have any number of expansion nodes as output including the case of having no output expansion node.
Extend
Extend    
Extend is a relationship that may exist between two use cases, the base use case and the extension use case. It is said to be conditional in the sense that a set of extension points defines conditions under which the insertion will occur. The extension points are defined in a separate section of the use case.
Extension Point
Extension Point    
An extension point is a feature of a use case and acts as a reference to a location in the (extended) use case at which the behavior of the use case may be extended by the insertion of additional behavior from another (extending) use case. A use case may have any number of extension points and these are used in conjunction with the extend relationship which contains reference to the extension points and conditions which govern whether the extending behavior will be inserted.
Final State
Final State    
A final state represents the last or "final" state of the enclosing composite state. There may be more than one final state at any level signifying that the composite state can end in different ways or conditions. When a final state is reached and there are no other enclosing states it means that the entire state machine has completed its transitions and no more transitions can occur.
Flow Final Node
Flow Final Node    
A flow final is a type of final node that consumes the incoming token. When a token arrives at a flow final the token is consumed. No other part of the enclosing activity is affected. Since there are no outgoing flows from a flow final node the effect is simply to remove tokens from the activity.
Fork (Horizontal)
Fork (Horizontal)    
A fork can be orientated horizontally or vertically. Both orientations have exactly the same semantics the difference is simply that when transition are parallel to the x axis a vertically orientated fork is required whereas when transitions are parallel to the y axis a horizontally orientated fork is required.
Fork (Vertical)
Fork (Vertical)    
A fork is a pseudostate that acts to split a single incoming transition into two or more concurrent outgoing transitions. All of the outgoing transitions fire at the same time.
Fork Node
Fork Node    
A fork node can be orientated horizontally or vertically. Both orientations have exactly the same semantics the difference is simply that when flows are parallel to the x-axis a vertically orientated fork node is required, whereas when flows are parallel to the y-axis a horizontally orientated fork is required.
Fork Node
Fork Node    
A fork node is a control node that has a single incoming flow and two or more outgoing flows. Incoming tokens are offered to all outgoing flows (edges). The outgoing flows can be guarded which gives them a mechanism to accept or reject a token. If the token is accepted by an outgoing edge it is duplicated so as to create a copied token for each outgoing flow that has accepted the token. The incoming flow and all outgoing flows must be either all control flows or all object flows. Tokens cannot be detained at the node; the token copying is effectively instantaneous.
Found Message
Found Message    
A found message is a kind of message where the receiver (event occurrence) is known but the sender (event occurrence) is not known. It is assumed that the sender exists but is outside the scope of the model.
Framework
Framework    
A framework is a stereotyped package that contains elements that specify an architecture or part of an architecture that can be reused. The extent of the framework may be for an entire system or may be restricted to a part of a system.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.