|
 |
|
|
Object diagram |
|
Object diagram shows a snapshot of instances of things in class diagrams. Similar to class diagrams, object diagrams show the static design of system but from the real or prototypical perspective.
|
|
|
Use case diagram
|
Class diagram
|
Sequence diagram
|
Communication diagram
|
State machine diagram
|
Activity diagram
|
Component diagram
|
Deployment diagram
|
Package diagram
|
Object diagram
|
Composite structure diagram
|
Timing diagram
|
Interaction overview diagram
|
|
|
|
|
Object diagram |
|
|
|
Notation
 | | Aggregation (Shared association) |  | | Association (Without aggregation) | |  | | Class |  | | Composition (Composite association) | |  | | Constraint |  | | Dependency | |  | | Generalization |  | | Instance Specification | |  | | Link |  | | Note | |  | | Realization | |
| DefinitionObject diagram shows a snapshot of instances of things in class diagrams. Similar to class diagrams, object diagrams show the static design of system but from the real or prototypical perspective. |
|
| |
Aggregation (Shared association) | |  | | Definition | | A kind of association that has one of its end marked shared as kind of aggregation, meaning that it has a shared aggregation. |
| | Properties | | | Name | The name of aggregation. | | Visibility | Determines where the aggregation appears within different namespaces within the overall model, and its accessibility. | | Association End From | The source of aggregation. | | Association End To | The target of aggregation. | | Documentation | Description of aggregation. | | Abstract | If true, the aggregation does not provide a complete declaration and can typically not be instantiated. An abstract aggregation is intended to be used by other aggregations. | | Leaf | Indicates whether it is possible to further specialize an aggregation. If the value is true, then it is not possible to further specialize the aggregation. | | Derived | Specifies whether the aggregation is derived from other model elements such as other aggregations or constraints. |
|
|
|
| | | Association (Without aggregation) | |  | | Definition | An association specifies a semantic relationship that can occur between typed instances. It has at least two ends represented by properties, each of which is connected to the type of the end. More than one end of the association may have the same type.
An end property of an association that is owned by an end class or that is a navigable owned end of the association indicates that the association is navigable from the opposite ends; otherwise, the association is not navigable from the opposite ends. |
| | Properties | | | Name | The name of association. | | Visibility | Determines where the association appears within different namespaces within the overall model, and its accessibility. | | Association End From | The source of association. | | Association End To | The target of association. | | Documentation | Description of association. | | Abstract | If true, the association does not provide a complete declaration and can typically not be instantiated. An abstract association is intended to be used by other associations. | | Leaf | Indicates whether it is possible to further specialize an association. If the value is true, then it is not possible to further specialize the association. | | Derived | Specifies whether the association is derived from other model elements such as other associations or constraints. |
|
|
|
| | | Class | |  | | Definition | | A class describes a set of objects that share the same specifications of features, constraints, and semantics. Class is a kind of classifier whose features are attributes and operations. Attributes of a class are represented by instances of Property that are owned by the class. Some of these attributes may represent the navigable ends of binary associations. |
| | Properties | | | Name | The name of class. | | Parent | The model element that owns the class. | | Visibility | Determines where the class appears within different namespaces within the overall model, and its accessibility. | | Documentation | Description of class. | | Abstract | If true, the class does not provide a complete declaration and can typically not be instantiated. An abstract class is intended to be used by other classes. | | Leaf | Indicates whether it is possible to further specialize a class. If the value is true, then it is not possible to further specialize the class. | | Root | Indicates whether the class has no ancestors. (true for no ancestors) | | Active | Determines whether an object specified by this class is active or not. If true, then the owning class is referred to as an active class. If false, then such a class is referred to as a passive class. | | Business model | Set it to make the class become a "business class" | | Attributes | Refers to all of the Properties that are direct (i.e., not inherited or imported) attributes of the class. | | Operations | An operation is a behavioral feature of a class that specifies the name, type, parameters, and constraints for invoking an associated behavior. Operations here refers to the operations owned by the class. | | Template Parameters | A TemplateableElement that has a template signature is a specification of a template. A template is a parameterized element that can be used to generate other model elements using TemplateBinding relationships. The template parameters for the template signature specify the formal parameters that will be substituted by actual parameters (or the default) in a binding.
A template parameter is defined in the namespace of the template, but the template parameter represents a model element that is defined in the context of the binding.
A templateable element can be bound to other templates. This is represented by the bound element having bindings to the template signatures of the target templates. In a canonical model a bound element does not explicitly contain the model elements implied by expanding the templates it binds to, since those expansions are regarded as derived. The semantics and well-formedness rules for the bound element must be evaluated as if the bindings were expanded with the substitutions of actual elements for formal parameters | | Class Code Details | Properties of class in implementation (code) level. Settings in this page is programming language specific, and will affect the code being generated. | | Java Annotations | A Java annotation is a metadata that can be added to Java source code for annotation purposes. | | ORM Query | Available only to ORM Persistable class, ORM Query lets you define the ORM Qualifiers and named queries of the class. |
|
|
|
| | | Composition (Composite association) | |  | | Definition | | An association may represent a composite aggregation (i.e., a whole/part relationship). Only binary associations can be aggregations. Composite aggregation is a strong form of aggregation that requires a part instance be included in at most one composite at a time. If a composite is deleted, all of its parts are normally deleted with it. Note that a part can (where allowed) be removed from a composite before the composite is deleted, and thus not be deleted as part of the composite. Compositions may be linked in a directed acyclic graph with transitive deletion characteristics; that is, deleting an element in one part of the graph will also result in the deletion of all elements of the subgraph below that element. Composition is represented by the isComposite attribute on the part end of the association being set to true. |
| | Properties | | | Name | The name of composition. | | Visibility | Determines where the association appears within different namespaces within the overall model, and its accessibility. | | Association End From | The source of association. | | Association End To | The target of association. | | Documentation | Description of association. | | Abstract | If true, the composition does not provide a complete declaration and can typically not be instantiated. An abstract composition is intended to be used by other compositions. | | Leaf | Indicates whether it is possible to further specialize a composition. If the value is true, then it is not possible to further specialize the composition. | | Derived | Specifies whether the composition is derived from other model elements such as other compositions or constraints. |
|
|
|
| | | Constraint | |  | | Definition | | A condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element. |
| | Properties | | | Name | The name of constraint. It is optional and is commonly omitted. | | Expression | The condition that must be true when evaluated in order for the constraint to be satisfied. | | Documentation | Description of constraint. |
|
|
|
| | | Dependency | |  | | Definition | | A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation. This means that the complete semantics of the depending elements is either semantically or structurally dependent on the definition of the supplier element(s). |
| | Properties | | | Name | The name of dependency. | | Supplier | The element(s) independent of the client element(s), in the same respect and the same dependency relationship. In some directed dependency relationships (such as Refinement Abstractions), a common convention in the domain of class-based OO software is to put the more abstract element in this role. Despite this convention, users of UML may stipulate a sense of dependency suitable for their domain, which makes a more abstract element dependent on that which is more specific. | | Client | The element(s) dependent on the supplier element(s). In some cases (such as a Trace Abstraction) the assignment of direction (that is, the designation of the client element) is at the discretion of the modeler, and is a stipulation. | | Visibility | Determines where the dependency appears within different namespaces within the overall model, and its accessibility. | | Documentation | Description of dependency. |
|
|
|
| | | Generalization | |  | | Definition | | A generalization is a taxonomic relationship between a more general classifier and a more specific classifier. Each instance of the specific classifier is also an indirect instance of the general classifier. Thus, the specific classifier inherits the features of the more general classifier. |
| | Properties | | | Name | The name of generalization. | | General | References the general classifier in the Generalization relationship. | | Specific | References the specializing classifier in the Generalization relationship. | | Visibility | Determines where the generalization relationship appears within different namespaces within the overall model, and its accessibility. | | Documentation | Description of generalization relationship. | | Substitutable | Indicates whether the specific classifier can be used wherever the general classifier can be used. If true, the execution traces of the specific classifier will be a superset of the execution traces of the general classifier. |
|
|
|
| | | Instance Specification | |  | | Definition | | An instance specification is a model element that represents an instance in a modeled system. An instance specification specifies existence of an entity in a modeled system and completely or partially describes theentity. |
| | Properties | | | Name | The name of instance Specification. | | Specification | A specification of how to compute, derive, or construct the instance. | | Documentation | Description of instance Specification. | | Classifiers | The classifier or classifiers of the represented instance. If multiple classifiers are specified, the instance is classified by all of them. | | Slots | A slot giving the value or values of a structural feature of the instance. An instance specification can have one slot per structural feature of its classifiers, including inherited features. It is not necessary to model a slot for each structural feature, in which case the instance specification is a partial description. |
|
|
|
| | | Link | |  | | Definition | | An association declares that there can be links between instances of the associated types. A link is a tuple with one value for each end of the association, where each value is an instance of the type of the end. |
| | Properties | | | Name | The name of link. | | From | The source of link. | | To | The target of link. | | Specification | A specification of how to compute, derive, or construct the instance. | | Classifiers | The classifier or classifiers of the represented instance. If multiple classifiers are specified, the instance is classified by all of them. | | Slots | A slot giving the value or values of a structural feature of the instance. An instance specification can have one slot per structural feature of its classifiers, including inherited features. It is not necessary to model a slot for each structural feature, in which case the link is a partial description. | | Documentation | Description of link. |
|
|
|
| | | Note | |  | | Definition | | A note (comment) gives the ability to attach various remarks to elements. A comment carries no semantic force, but may contain information that is useful to a modeler. |
| | Properties | | | Name | The name of note. | | Documentation | Specifies a string that is the comment. |
|
|
|
| | | Realization | |  | | Definition | | Realization is a specialized abstraction relationship between two sets of model elements, one representing a specification (the supplier) and the other represents an implementation of the latter (the client). Realization can be used to model stepwise refinement, optimizations, transformations, templates, model synthesis, framework composition, etc. |
| | Properties | | | Name | The name of realization relationship. | | Supplier | The element(s) independent of the client element(s), in the same respect and the same dependency relationship. In some directed dependency relationships (such as Refinement Abstractions), a common convention in the domain of class-based OO software is to put the more abstract element in this role. Despite this convention, users of UML may stipulate a sense of dependency suitable for their domain, which makes a more abstract element dependent on that which is more specific. | | Client | The element(s) dependent on the supplier element(s). In some cases (such as a Trace Abstraction) the assignment of direction (that is, the designation of the client element) is at the discretion of the modeler, and is a stipulation. | | Visibility | Determines where the realization relationship appears within different namespaces within the overall model, and its accessibility. | | Mapping | A composition of an Expression that states the abstraction relationship between the supplier and the client. In some cases, such as Derivation, it is usually formal and unidirectional. In other cases, such as Trace, it is usually informal and bidirectional. The mapping expression is optional and may be omitted if the precise relationship between the elements is not specified. | | Documentation | Description of realization relationship. |
|
|
|
|
| |
| Definition of notations is quoted from Object Management Group Unified Modeling Language (OMG UML) Superstructure Version 2.2 and former versions (for notations that do not exist anymore in latest specification). |
| |
|
Use case diagram
|
Class diagram
|
Sequence diagram
|
Communication diagram
|
State machine diagram
|
Activity diagram
|
Component diagram
|
Deployment diagram
|
Package diagram
|
Object diagram
|
Composite structure diagram
|
Timing diagram
|
Interaction overview diagram
|
|
|
|
|
 |
|
