Zicomi Systems Logo
contact us  |  your privacy
Company
Services
Products
Support
Resources
  OMG Standards
OMG Logo
UML Element Description
Actor Generalization
Actor Generalization    
Actor generalization is a way of factoring out commonality that exists between a number of actors. The actors must be of the same type or family, and have associations with the same set of use cases. The specialized actors may add or remove associations, and can always stand in the place of the parent or more generalized actor. The more generalized actor is often, but not always, abstract.
Actor Generalization (tree)
Actor Generalization (tree)    
Actor generalization can be represented in a single path (tree). When a number of generalization relationships exist and the children have the same parent the lines can be combined into a single path and drawn with a tree. This doesn't change the semantics of the individual relationships; it is simply a more compact and convenient style for representing the relationships. A tree that has three branches represents three discrete and separately defined generalization relationships.
Association
Association    
An association is a semantic or structural relationship between classifiers. An association has a name and consists of at least two association ends. The association ends are simply the end parts of the association where they connect to classifiers. It is the association's ends that may have a number of adornments that express the rich structural semantics of the relationship.
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.
Complete
Complete    
Complete is a constraint added to a set of generalization relationships to indicate that all children have been specified. This means that any instance of the parent must be an instance of at least one of the children within the set. All children that are governed by the constraint must have the same discriminator.
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.
Disjoint
Disjoint    
Disjoint is a constraint added to a set of generalization relationships to indicate that an instance of the parent may be an instance of one and only one of the children within the set.
Generalization
Generalization    
Generalization is a relationship of classification between a more general element (parent) and a more specific element (child). The head of the arrow is attached to the "parent" and the tail is attached to the "child". It is a taxonomic relationship that can exist between a number of types of UML elements including classifiers and associations.
Generalization (tree)
Generalization (tree)    
When a number of children are "siblings" and thus share a generalization relationship with the same parent, the individual lines may be combined together to form a branching tree. This is simply a convenient way of representing the "family " as it reduces the visual complexity of the diagram. It does not add any other meaning, and each line can be considered a separate relationship in its own right.
Incomplete
Incomplete    
Incomplete is a constraint added to a set of generalization relationships to indicate that all children have not been specified. This means that an instance of the parent is not necessarily an instance of any of the children. All children that are governed by the constraint must have the same discriminator.
IsNavigable
IsNavigable    
The value of the isNavigable property specifies whether an association can be traversed from the source (far end) to the target (near end). It is indicated graphically by an open headed arrow.
Link
Link    
A link is an instance of an association. While an association connects classifiers to show structural relationships, the link (association instance) connects classifier instances. It is a list of the references between classifier instances. Its most common expression is a reference to two classifier instances in its binary form: an n-ary association will have n-ary links. Properties such as aggregation can be used with a link, however multiplicity and ordering may not as they have no meaning.
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.
Overlapping
Overlapping    
Overlapping is a constraint added to a set of generalization relationships to indicate that an instance of one child may simultaneously be an instance of another.
Realization
Realization    
A realize signifies that a relationship exists between a set of elements that form a specification (the client) and another set of elements that form the implementation (the supplier).
Receipt Signal
Receipt Signal    
A receipt signal is a type of state that represents the receipt of a signal on an activity diagram. The state does not have actions or internal transitions. It simply represents the receipt of the signal, which causes the outgoing transition to fire. A dashed arrow may be drawn from the object sending the signal to the receipt signal. The signal signature is written inside the pentagon.
Sending Signal
Sending Signal    
A sending signal is a representation of an action that sends a signal. The action has one incoming transition and one outgoing transition. The signal is always sent asynchronously; the object receiving the signal may be shown, with a dashed arrow drawn from the pentagon to the object. The signal signature is written inside the pentagon.
Use Case Generalization
Use Case Generalization    
Use case generalization is a relationship between two use cases indicating that the child (tail end) is more specific than the parent (arrow head end).
Use Case Generalization (tree)
Use Case Generalization (tree)    
Use case generalization can be represented in a single path (tree). When a number of generalization relationships exist and the children have the same parent the lines can be combined into a single path and drawn with a tree. This doesn't change the semantics of the individual relationships; it is simply a more compact and convenient style for representing the relationships. A tree that has three branches represents three discrete and separately defined generalization relationships.
Unified Modeling Language and UML are either registered

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

United States and/or other countries.