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
Component (Icon Presentation)
Component (Icon Presentation)    
A component is a modular, deployable and replaceable part of a system, it contains model elements and packages them to present a set of interfaces.
Component Instance
Component Instance    
A component instance (lugged) is a visual synonym of a component instance. It adds no additional semantics; it is simply an alternative presentation of the element. This presentation style was used in versions of UML prior to UML 2.0. It has been superseded but may still be used as an alternative presentation.
Subsystem
Subsystem    
A subsystem is a grouping or package of model elements that has operations and interfaces. It has the characteristics of a package and a classifier. While a subsystem is a behavior element, it has no intrinsic behavior of it s own, the behavior is provided by the elements in the realization compartment of the subsystem.
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.
Object
Object    
An object represents a distinct instance of a class. It has unique identity as well as attribute values, which determine its state at any point in time. An object can exhibit behavior, but only as a result of being an instance of a class. An object is an instance of one and only one class.
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.
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.
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.
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.
Assembly Connector
Assembly Connector    
An assembly connector is a kind of connector that is specialized for use in component modeling. It is used to connect the provided interface or port of one component to the required interface or port of another component.
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.
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.
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.
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.
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.
Artifact (Keyword Presentation)
Artifact (Keyword Presentation)    
An artifact (keyword presentation) is a visual synonym of an artifact. It adds no additional semantics; it is simply an alternative presentation of the element. The standard form of this element is considered to be the artifact displayed with a small icon in the top left hand corner of a classifier rectangle.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.