Component Diagram
Last updated
Was this helpful?
Last updated
Was this helpful?
A Component Diagram represents the high-level structure of a system, showing software components, their dependencies, and interfaces. It is used to visualize module-level architecture and how components interact within a system.
Refer to the official documentation for more details -
Components
Represented as rectangles with a small box (or <<component>>
stereotype).
Define independent modules of a system (e.g., UserService
, PaymentService
).
Interfaces
Represented as circles or <<interface>>
notation.
Show exposed functionalities of components.
Dependencies
Dashed arrows indicate dependency relationships (e.g., one component depends on another).
Relationships
Provided/Required Interfaces – Shows what a component offers or consumes.
Direct Communication – Arrows representing message passing.
This represents a Microservices Architecture in a banking system.