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
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.
Package Contents
Package Contents    
Package Contents can be indicated using the anchor symbol. This denotes that the packages that are attached to the non-anchor end of the relationship are contained within the anchor package. This is an alternative notation to packages being graphically contained or placed inside other packages.
Package Import
Package Import    
A package import is a directed relationship between a package (arrowhead end) and an importing namespace (tail end). The members of the referenced package can be used in the importing namespace without any qualification of the element name. A name can be added to the package import relationship, which is used as an alias (alternative name) for the elements in the importing namespace. The visibility of the elements in the importing namespace is by default public.
Package Import (Access)
Package Import (Access)    
A package import with the keyword access is a directed relationship between a package (arrowhead end) and an importing namespace (tail end). The members of the referenced package can be used in the importing namespace without any qualification of the element name. It is different from a package import with keyword import because it does not import the members of the other package into the namespace, but rather just allows them to be referenced. The visibility of the elements in the importing namespace is by default public.
Package Merge
Package Merge    
A package merge is a directed relationship between two packages that is used when elements of one package (tail end) represent the same concept as those in another package (arrowhead end). It is a convenient way of representing a set of generalizations and redefinitions between two packages. It is termed a merge because the relationship means that elements with the same name and of the same type from one or more packages will be merged into a single element in the merging package (tail end). This is achieved by the use of generalizations and redefinitions.
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.
Parallel (Combined Fragment)
Parallel (Combined Fragment)    
A parallel interaction operator (signified by the value of par) defines a combined fragment where the messages contained in the operands can be interleaved. It thus defines the set of traces that can occur at the same time or overlap with each other with respect to time.
Parallel Expansion Region
Parallel Expansion Region    
When the value of parallel is specified for the mode of an expansion region, execution of the region can occur concurrently. 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.
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.
Permission
Permission    
A permission is a type of dependency and therefore a directed relationship between one or more clients (tail end) and one or more suppliers (arrowhead end). The relationship signifies that the elements at the tail end (client) require access to the elements at the arrowhead end (supplier) and that this access is granted (permitted). There are no standard stereotypes of a permission defined in the UML.
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.
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.
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.
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.
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).
Receipt Signal
Receipt Signal    
A receipt signal is a type of state that represents the receipt of a signal on an activity diagram. The state does not have actions or internal transitions. It simply represents the receipt of the signal, which causes the outgoing transition to fire. A dashed arrow may be drawn from the object sending the signal to the receipt signal. The signal signature is written inside the pentagon.
Recursive Message
Recursive Message    
A recursion message is a message where an instance is both the caller and the receiver of the message.
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).
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.
Region
Region    
A region is a part of a state machine or composite state. It contains (encloses) vertices and transitions. It can have one (and only one) initial pseudostate and any number of final states. A composite state with one region is called a non-orthogonal (simple) composite state and one with two or more regions is called an orthogonal state.
Region (Combined Fragment)
Region (Combined Fragment)    
A critical region interaction operator (signified by the value of region) defines a combined fragment where the messages contained in the operand cannot be interleaved with other messages from other lifelines enclosed in the region. It expresses that a set of traces are to be treated atomically and cannot be interrupted or affected by other traces.
Reply Message
Reply Message    
A reply message denotes a return from a procedure call. This is an explicit representation of the return, which if it is not present, is implied in the synchronous message.
Reply Message (State)
Reply Message (State)    
A reply message (state) is a visual synonym of a reply message. It adds no additional semantics; it is simply an example of the reply message adapted for use on a timing diagram. This usage of the reply message has the same form as a reply message used on other interaction diagrams: a dashed line with an open arrowhead directed from one execution occurrence to another (possibly reflexive). It is listed separately because the message ends give it a different appearance from other examples. The reply represents an explicit representation of a return from a synchronous message. There is a single form of presentation in the three different types of interaction diagrams and the two different presentations of the timing diagram.
Reply Message (Value)
Reply Message (Value)    
A reply message (value) is a visual synonym of a reply message. It adds no additional semantics; it is simply an example of the reply message adapted for use on a timing diagram. This usage of the reply message has the same form as a reply message used on other interaction diagrams: a dashed line with an open arrowhead directed from one execution occurrence to another (possibly reflexive). It is listed separately because the message ends give it a different appearance from other examples. The reply represents an explicit representation of a return from a synchronous message. There is a single form of presentation in the three different types of interaction diagrams and the two different presentations of the timing diagram.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.