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.
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.
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.
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.
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.
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.
Model
Model    
A model is a cohesive and complete representation of a system from a particular perspective. The perspectives are not predefined but there are a number of commonly used perspectives, such as use case model, analysis model, design model which are detailed in the UML Profile for Software Development Processes. Each model can form part of a model hierarchy, whose root is the topLevel package representing the entire entity being modeled (usually a system), and whose individual nodes are the models themselves.
Model Library
Model Library    
A model library is a stereotyped package that has been created with the express purpose of providing model elements that can be used by other elements or packages in the model. A model library is typically reused by a number of different models at different times or locations or by different modelers or teams of modelers.
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.