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
Gate
Gate    
A gate is a type of message end that represents the connection point between a message that exists within an interaction fragment and a message outside the interaction fragment. A gate is a formal mechanism for connecting messages ensuring that every message has a sender and a receiver. Gates can exist in a number of contexts: formal gates used in interactions, actual gates used in interaction occurrences and expression gates used in combined fragments.
General Ordering
General Ordering    
A general ordering is a named element that relates two event occurrences (message ends) specifying that the event occurrence at the tail end must occur before the event occurrence at the arrowhead end of the message.
Generalization
Generalization    
Generalization is a relationship of classification between a more general element (parent) and a more specific element (child). The head of the arrow is attached to the "parent" and the tail is attached to the "child". It is a taxonomic relationship that can exist between a number of types of UML elements including classifiers and associations.
Generalization (tree)
Generalization (tree)    
When a number of children are "siblings" and thus share a generalization relationship with the same parent, the individual lines may be combined together to form a branching tree. This is simply a convenient way of representing the "family " as it reduces the visual complexity of the diagram. It does not add any other meaning, and each line can be considered a separate relationship in its own right.
Ignore (Combined Fragment)
Ignore (Combined Fragment)    
An ignore interaction operator (signified by the value of ignore) defines a combined fragment where the messages listed are to be ignored within the fragment. This means that these messages are insignificant in the context of the fragment and can be ignored.
Include
Include    
Include is a relationship that may exist between two use cases, a base use case and an addition use case. It means a base use case may insert behavior from an addition use case. The relationship is said to be unconditional in the sense that if the insertion occurs; all the behavior of the addition use case is unconditionally inserted.
Incomplete
Incomplete    
Incomplete is a constraint added to a set of generalization relationships to indicate that all children have not been specified. This means that an instance of the parent is not necessarily an instance of any of the children. All children that are governed by the constraint must have the same discriminator.
Initial
Initial    
An initial is a kind of pseudostate that represents the starting point in a region of a state machine. It has a single outgoing transition to the default state of the enclosing region, and has no incoming transitions. There can be one (and only one) initial state in any given region of a state machine. It is not itself a state but acts as a marker.
Initial Node
Initial Node    
An initial node is a type of control node which initiates flow in an invoked activity. It has no incoming flows and one or more outgoing flows. The outgoing flows may be guarded with conditions that determine if they will accept tokens. When an activity is invoked tokens are offered to all outgoing flows. There may be zero or more initial nodes in any activity. While other control nodes cannot detain tokens an initial node can retain a token if the guard on an outgoing flow prevents a token from being accepted when the activity starts.
Input Pin
Input Pin    
An input pin is a type of object node, that gives the node the capability of storing (buffering) tokens. Input pins are owned by actions and tokens may accumulate at an input pin waiting to be consumed by the action. Input pins only have incoming flows all of which must be object flows, and they provide values to the actions that consume the tokens.
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).
Interaction Occurrence
Interaction Occurrence    
An interaction occurrence stands in the place of an interaction or portion of an interaction. An interaction occurrence is a diagrammatic device for reusing or copying the contents of an interaction to another diagram.
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.
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 (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.
Interruptible Activity Region
Interruptible Activity Region    
An interruptible activity region is a type of activity group which provides a mechanism for destroying all tokens and terminating all behaviors in the section of the activity enclosed within the boundary of the region. An interruptible activity region can contain any number of nodes and flows. When a token is accepted by a special kind of edge called an interrupting flow (edge), which is designated by a lightning bolt, it leaves the region and all other tokens are destroyed and behaviors within the region are terminated.
Interrupting Edge
Interrupting Edge    
An interrupting edge is a type of activity edge drawn as a lighting bolt. It connects a node inside a region to a node outside the region in the same activity. When a token leaves a region via an interrupting edge all other tokens in the region are consumed and all behaviors in the region are halted.
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.
Iterative Expansion Region
Iterative Expansion Region    
When the value of iterative is specified for the mode of an expansion region, execution within the region must occur in sequence. An expansion region is a type of activity group that contains one or more actions. These actions are executed multiple times depending on the number of elements in the input collection that arrive at one or more expansion nodes positioned on the edge of the region. The results of the actions may be placed in one or more expansion nodes acting as outputs.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.