|
Class Diagram Sample
|
|
Class Diagram provides an overview of the target system by describing the objects and classes inside the system and the relationships between them.
|
|
| |
|
Class
|
|
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.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 47)
|
|
| |
|
Interface
|
|
An interface is a kind of classifier that represents a declaration of a set of coherent public features and obligations. An interface specifies a contract; any instance of a classifier that realizes the interface must fulfill that contract. The obligations that may be associated with an interface are in the form of various kinds of constraints (such as pre- and post-conditions) or protocol specifications, which may impose ordering restrictions on interactions through the interface.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 87)
|
|
| |
|
Package
|
|
A package is a namespace for its members, and may contain other packages. Only packageable elements can be owned members of a package. By virtue of being a namespace, a package can import either individual members of other packages, or all the members of other packages.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 110)
|
|
| |
|
Aggregation
|
|
AggregationKind is an enumeration type that specifies the literals for defining the kind of aggregation of a property.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 36)
|
|
| |
|
Association
|
|
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.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 36)
|
|
| |
|
Composition
|
|
AggregationKind is an enumeration type that specifies the literals for defining the kind of aggregation of a property. Indicates that the property is aggregated compositely, i.e., the composite object has responsibility for the existence and storage of the composed objects (parts).(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 36)
|
|
| |
|
Dependency
|
|
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).(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 60)
|
|
| |
|
Generalization
|
|
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.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 71)
|
|
| |
|
InterfaceRealization
|
|
An InterfaceRealization is a specialized Realization relationship between a Classifier and an Interface. This relationship signifies that the realizing classifier conforms to the contract specified by the Interface.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 90)
|
|
| |
|
Realization
|
|
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.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 131)
|
|
| |
|
Usage
|
|
A usage is a relationship in which one element requires another element (or set of elements) for its full implementation or operation. In the metamodel, a Usage is a Dependency in which the client requires the presence of the supplier.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 139)
|
|
| |
|
PackageMerge
|
|
A package merge is a directed relationship between two packages, that indicates that the contents of the two packages are to be combined. It is very similar to Generalization in the sense that the source element conceptually adds the characteristics of the target element to its own characteristics resulting in an element that combines the characteristics of both.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 114)
|
|
| |
|
PackageImport(public)
|
|
A package import is defined as a directed relationship that identifies a package whose members are to be imported by a namespace.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 113)
|
.png)
|
| |
|
PackageImport(private)
|
|
A package import is defined as a directed relationship that identifies a package whose members are to be imported by a namespace.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 113)
|
.png)
|
| |
