|
Component Diagram Sample
|
|
The Component Diagram helps to model the physical aspect of an Object-Oriented software system.
|
|
| |
|
Component
|
|
A component is a subtype of Class which provides for a Component having attributes and operations, and being able to participate in Associations and Generalizations. A Component may form the abstraction for a set of realizingClassifiers that realize its behavior. In addition, because a Class itself is a subtype of an EncapsulatedClassifier, a Component may optionally have an internal structure and own a set of Ports that formalize its interaction points.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 150)
|
|
| |
|
Component implements 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)
|
|
| |
|
Component has provided Port (typed by Interface)
|
|
Ports represent interaction points between a classifier and its environment. The interfaces associated with a port specify the nature of the interactions that may occur over a port. The required interfaces of a port characterize the requests which may be made from the classifier to its environment through this port. The provided interfaces of a port characterize requests to the classifier that its environment may make through this port.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 189)
|
|
| |
|
Component uses 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)
|
|
| |
|
Component has required Port (typed by Interface)
|
|
Ports represent interaction points between a classifier and its environment. The interfaces associated with a port specify the nature of the interactions that may occur over a port. The required interfaces of a port characterize the requests which may be made from the classifier to its environment through this port. The provided interfaces of a port characterize requests to the classifier that its environment may make through this port.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 189)
|
|
| |
|
Component has complex Port (typed by provided and required Interfaces)
|
|
Ports represent interaction points between a classifier and its environment. The interfaces associated with a port specify the nature of the interactions that may occur over a port. The required interfaces of a port characterize the requests which may be made from the classifier to its environment through this port. The provided interfaces of a port characterize requests to the classifier that its environment may make through this port.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 189)
|
|
| |
|
Assembly connector
|
|
An assembly connector is a connector between two components that defines that one component provides the services that another component requires. An assembly connector is a connector that is defined from a required interface or port to a provided interface or port.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 160)
|
|
| |
