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
Abstract Class
Abstract Class    
An abstract class is a class that cannot be directly instantiated. . It cannot have attributes or methods and but can contain abstract operations. It is semantically equivalent to an interface, and can participate in relationships such as generalization dependencies, and association with some restrictions.
Activity Partition
Activity Partition    
An activity partition is a type of activity group that specifies that a number of elements in an activity have something in common. Partitions may be oriented horizontally or vertically, and except in the case that a partition is a dimension can contain other partitions down to any level of nesting. Partitions have no effect on the execution of an activity or the nodes and edges contained within it.
Actor
Actor    
An actor can be represented by a classifier (rectangular) symbol. Both this form and the more commonly seen stick-person form have the same semantics. The rectangular form is sometimes used when representing a system actor but it can also be used to represent a human actor. When an actor has properties and these need to be displayed as part of a diagram the rectangular form can be used; the properties appear in a separate compartment.
Alternatives (Combined Fragment)
Alternatives (Combined Fragment)    
An alternatives interaction operator (signified by the value of alt) defines a combined fragment where one or more behavior options or choices are expressed. One (and only one) of the alternatives (operands) can execute and only when the guard condition evaluates to TRUE.
Artifact (Icon Presentation)
Artifact (Icon Presentation)    
An artifact is the specification of 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. An artifact is a classifier and as such can have instances, which are the development or runtime expressions (instances) of the artifact.
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.
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.
Assert (Combined Fragment)
Assert (Combined Fragment)    
An assertion interaction operator (signified by the value of assert) defines a combined fragment where the messages contained in the fragment are the only valid messages that can occur in the context. If any other messages occur they are considered to be invalid.
Association Class
Association Class    
An association class has the behavior of both an association and a class. It gives an association the ability to have attributes and operations like a class. It has two distinct parts to its structure: an association part and a class part.
Attribute
Attribute    
An attribute is a string item listed in the attribute compartment of a classifier. An attribute defines an aspect or dimension of a classifier. An attribute may be assigned a value when an instance of a classifier is created. It is semantically equivalent to a classifier having a composite association with another classifier of the type specified in the attribute expression.
Break (Combined Fragment)
Break (Combined Fragment)    
A break interaction operator (signified by the value of break) defines a combined fragment where the messages enclosed within the fragment are performed instead of the messages in the outer (enclosing) fragment. The break operator is typically used when a given message or set of messages will halt the performance of the enclosing set of messages.
Central Buffer
Central Buffer    
A central buffer is a type of object node, which gives the node the capability of storing (buffering) tokens. It manages the tokens that arrive at incoming flows (edges) from one or more object nodes and selects which tokens and in what order these tokens will be presented to the downstream object nodes via the outgoing flows (edges).
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.
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.
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 (keyword)
Component (keyword)    
A component (keyword) is a visual synonym of a component. It adds no additional semantics; it is simply an alternative presentation of the element.
Component (lugged)
Component (lugged)    
A component (lugged) is a visual synonym of a component. 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.
Component Instance
Component Instance    
A component instance represents a distinct instance of a component. It has a unique identity and attribute values, which determine its state at any point in time. A component instance can exhibit behavior, but only as a result of being an instance of a component. A component instance is an instance of one and only one component.
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.
Consider (Combined Fragment)
Consider (Combined Fragment)    
A consider interaction operator (signified by the value of consider) defines a combined fragment where the messages listed are to be considered within the fragment. The messages defined as part of the operator are drawn in the fragment.
Data Store
Data Store    
A data store node is a type of central buffer node and can therefore store (buffer) tokens. It adds the additional mechanism to keep a copy of the tokens even when they are passed out of the node via an outgoing object flow. Whenever an incoming token contains an object or piece of data that already exists in the data store the incoming token replaces the existing one.
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.
Exception Handler
Exception Handler    
An exception handler is an element that allows an action (protected node) to be protected by specifying an alternate action to execute when a certain condition or event occurs in the execution of the protected node. The alternate action called the handler has an input pin, which specifies the type of the exception. The handler will only be invoked if the type of the exception is the same or a child of the type specified by the handler.
Execution Occurrence
Execution Occurrence    
An execution occurrence (activation) represents a period in the participant 's lifetime when it is performing an action or waiting for another participant to complete an action and return. A lifeline can have a number of execution occurrences that and these will be positioned along the lifeline, obscuring the dashed line.
Expansion Node
Expansion Node    
An expansion node is a type of object node. They are used exclusively with expansion regions. An object flow that arrives at an expansion node contains a collection of objects or data, which are separated by the expansion node before being passed onto elements within the region. A region must have one or more expansion nodes receiving input and may have any number of expansion nodes as output including the case of having no output expansion node.
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.
Ignore (Combined Fragment)
Ignore (Combined Fragment)    
An ignore interaction operator (signified by the value of ignore) defines a combined fragment where the messages listed are to be ignored within the fragment. This means that these messages are insignificant in the context of the fragment and can be ignored.
Input Pin
Input Pin    
An input pin is a type of object node, that gives the node the capability of storing (buffering) tokens. Input pins are owned by actions and tokens may accumulate at an input pin waiting to be consumed by the action. Input pins only have incoming flows all of which must be object flows, and they provide values to the actions that consume the tokens.
Interaction Occurrence
Interaction Occurrence    
An interaction occurrence stands in the place of an interaction or portion of an interaction. An interaction occurrence is a diagrammatic device for reusing or copying the contents of an interaction to another diagram.
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.
Loop (Combined Fragment)
Loop (Combined Fragment)    
A loop interaction operator (signified by the value of loop) defines a combined fragment where the messages contained in the fragment are repeated a number of times. The guard contains a lower bound defining the minimum number of times the operand must loop, an upper bound defining the maximum number of times the operand will be executed and a boolean expression (evaluated after the operand has looped the minimum number of times) which if false will terminate the loop.
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.
Negative (Combined Fragment)
Negative (Combined Fragment)    
A negative interaction operator (signified by the value of neg) defines a combined fragment where the enclosed traces are all invalid. The operator is used to express the fact that the traces cannot occur. By implication any traces not enclosed in the negative interaction operator are valid. A combined fragment with a negative operator can have one (and only one) operand.
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.
Operation
Operation    
An operation is a string item listed in the operation compartment of a classifier. The operations define the behavior of the classifier and the work that the classifier can carry out. An operation can take a list of parameters and return a type. Its visibility can be restricted and other factors, such as concurrency, can be specified using the property-string.
Option (Combined Fragment)
Option (Combined Fragment)    
An option interaction operator (signified by the value of opt) defines a combined fragment where there is a choice between a single defined set of traces occurring or no traces. It is semantically equivalent to an alternatives operator (alt) where there is a single choice between a set of traces and an empty alternative.
Output Pin
Output Pin    
An output pin is a type of object node, which gives the node the capability of storing (buffering) tokens. Tokens produced by actions may accumulate at output pins before being passed onto other downstream object nodes via object flows. Output pins have only incoming flows all of which must be object flows. They receive tokens produced by the actions.
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.
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.
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
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.
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.
Strict Sequencing (Combined Fragment)
Strict Sequencing (Combined Fragment)    
A strict sequencing interaction operator (signified by the value of strict) defines a combined fragment where the sequence of the event occurrences must occur in the order they are defined regardless of which lifeline is involved.
Subject (System) Boundary
Subject (System) Boundary    
A subject (system) boundary is a type of partition that represents the boundary between the thing you are representing with the use cases (inside the boundary) and the actors (outside the boundary). Its most typical usage is the boundary of an entire system. Use cases can be used to represent subsystems and classes and so the boundary may be more specific than an entire system. A package with a stereotype topLevel can be used as a boundary and name space within the use case model to denote the same thing as the use case boundary.
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.
Swimlanes
Swimlanes    
Swimlanes divide or partition activity diagrams into a number of "lanes", which typically organize the diagram into a number of regions of responsibility. Each lane may have a name, which signifies the responsibility or governance of the elements that lie within it.
Use Case Package
Use Case Package    
A use case package is a package that is used to partition or group, use cases, actors, relationships, diagrams or other use case packages.
Weak Sequencing (Combined Fragment)
Weak Sequencing (Combined Fragment)    
A weak sequencing interaction operator (signified by the value of seq) defines a combined fragment where the order of event occurrences within one operand are significant and event occurrences on different lifelines can be interleaved, but event occurrences on the same lifeline, in different operands must occur in the order of the operands. Thus event occurrences in the first operand must occur before event occurrences in the second operand if they are on the same lifeline.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.