Component diagram: Difference between revisions
| Line 16: | Line 16: | ||
==Symbols== |
==Symbols== |
||
This may have a visual stereotype in the top right of the rectangle of a small rectangle with two even smaller rectangles jutting out on the left. |
|||
The lollipop, a small circle on a stick represents an implemented or provided interface. The socket symbol is a semicircle on a stick that can fit around the lollipop. This socket is a dependency or needed interface.<ref name="Ambler">{{cite web|url=http://www.agilemodeling.com/artifacts/componentDiagram.htm|title=Introduction to UML 2 Component Diagrams|last=Ambler|first=Scott W.|accessdate=16 September 2012}}</ref> |
The lollipop, a small circle on a stick represents an implemented or provided interface. The socket symbol is a semicircle on a stick that can fit around the lollipop. This socket is a dependency or needed interface.<ref name="Ambler">{{cite web|url=http://www.agilemodeling.com/artifacts/componentDiagram.htm|title=Introduction to UML 2 Component Diagrams|last=Ambler|first=Scott W.|accessdate=16 September 2012}}</ref> |
||
Revision as of 08:56, 11 February 2013
| UML diagram types |
|---|
| Structural UML diagrams |
| Behavioral UML diagrams |
In the Unified Modeling Language, a component diagram depicts how components are wired together to form larger components and or software systems. They are used to illustrate the structure of arbitrarily complex systems.
Overview
Components are wired together by using an assembly connector to connect the required interface of one component with the provided interface of another component. This illustrates the service consumer - service provider relationship between the two components.
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."[1]
When using a component diagram to show the internal structure of a component, the provided and required interfaces of the encompassing component can delegate to the corresponding interfaces of the contained components.
A delegation connector is a "connector that links the external contract of a component (as specified by its ports) to the internal realization of that behavior by the component’s parts."[1]
The example above illustrates what a typical Insurance policy administration system might look like. Each of the components depicted in the above diagram may have other component diagrams illustrating their internal structure.
Symbols
This may have a visual stereotype in the top right of the rectangle of a small rectangle with two even smaller rectangles jutting out on the left.
The lollipop, a small circle on a stick represents an implemented or provided interface. The socket symbol is a semicircle on a stick that can fit around the lollipop. This socket is a dependency or needed interface.[2]
References
- ^ a b OMG Unified Modeling Language (UML), Superstructure, V2.1.2, p.154.
- ^ Ambler, Scott W. "Introduction to UML 2 Component Diagrams". Retrieved 16 September 2012.
 | This article needs additional citations for verification. (February 2009) |
External links
- UML 2 Component Diagram Guidelines by Scott W. Ambler
- Component Diagrams in UML 2
- UML 2 Component Diagrams
| Actors |
|  | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Concepts |
| ||||||||||||
| Diagrams |
| ||||||||||||
| Derived languages | |||||||||||||
| Other topics | |||||||||||||
 | This Unified Modeling Language article is a stub. You can help Wikipedia by expanding it. |