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
Deployment
Deployment    
A deployment is a type of dependency. It is a directed relationship between one or more deployed artifacts and a deployment target. The deployment target is the location where the artifact is deployed and can be a device, execution environment or a property. The deployment can be used to describe the relationship at a type or instance level. A component deployment is a specialized form of deployment that can have one or more deployment specifications that govern the way the artifact is deployed.
Deployment (nested)
Deployment (nested)    
A deployment (nested) is a visual synonym of a deployment. It is an alternative and useful way of expressing the deployment relationship. It is often more visually appealing to audiences not familiar with the UML as the containment of an artifact inside a deployment target such as a node is easier to understand. When there are a large number of artifacts deployed to a particular deployment target it is often more appropriate to use the deployment relationship in its linear form as the contents of the deployment target can become congested.
Deployment Specification
Deployment Specification    
A deployment specification is an artifact that specifies a set of properties that governs the way an artifact will execute on a node. Typically a deployment specification specifies the properties for a particular type of execution environment. It is itself a type of artifact and therefore a classifier and can have instances.
Deployment Specification Instance
Deployment Specification Instance    
A deployment specification instance is a distinct instance of a deployment specification. While the deployment specification specifies a set of properties that govern the way an artifact will execute on a node, a deployment specification instance gives these properties actual values. Typically a deployment specification specifies values of the properties for a particular type of execution environment. It is itself a type of artifact instance and is owned by a deployment.
Node Instance
Node Instance    
A node instance represents a distinct instance of a node. It is an actual instance of a resource that carries out the work of the system. It has unique identity as well as attribute values, which determine its state at any point in time. A node instance can exhibit behavior, but only as a result of being an instance of a node. A node instance is an instance of one (and only one) node.
Node
Node    
A node is a physical resource, that carries out some of the work of the system. It can be an electronic, mechanical or human resource.
Node Association
Node Association    
A node association is a structural relationship between two nodes. It represents a physical connection between the two nodes; the connection may express a communication path or a type of network.
Artifact Instance
Artifact Instance    
An artifact instance represents a distinct instance of an artifact. It is a piece of information that is utilized or created as part of a software development process or is produced as a product of a running system. It has a unique identity and state and defines the values of the properties specified in the artifact of which it is an example. An artifact instance can exhibit behavior, but only as a result of being an instance of an artifact.
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.
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.
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.
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.
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.