By using a component diagram we see the system as a group of nearly independent component or subsystems that interact with each other in a specifically defined way.Įach component is responsible for the action for which it is named and interface(s) it provides. The Figure below is a much larger view of what is involved in a online store. One main benefit of Component diagrams if to simplify the high-level view of the system. Order Processing System Component diagram example
Provided interfaces define "a set of public attributes and operations that must be provided by the classes that implement a given interface". The component stereotype's text is ">" and the component stereotype icon is a rectangle with two smaller rectangles protruding on its left side. A component can be represented as just a rectangle with the component's name and the component stereotype text and/or icon. A component is drawn as a rectangle with optional compartments stacked vertically.