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
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.
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.
Connector
Connector    
A connector is a feature that is used in the description of composite structures. It specifies that two or more instances are able to communicate with each other in some way. The connector does not specify how the communication is achieved but simply that it is possible. In practice the instances may be able to communicate because there is a link (instance of an association) connecting the elements or because one instance has access to another through parameter passing.
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.
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.
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.
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.
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.
Multiplicity
Multiplicity    
multiplicity is a property of an association end that specifies the number of instances of the classifier connected at the target end (near end) that can be associated with a single instance of the classifier at the source end (far end). It is specified in the form of a string stipulating a possible infinite number governed by a lower and upper bound.
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
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.
Collaboration
Collaboration    
A collaboration is a static construct that models the way a specific set of instances interact with each other. The instances communicate with each by exchanging stimuli in an overall effort to accomplish some purpose.
Collaboration Occurrence
Collaboration Occurrence    
A collaboration occurrence is a specific application of a collaboration to express a how a specific instance of the collaboration would be carried out by the participating classes or instances.
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.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.