**Component Diagrams represent system architecture, focusing on interface relationships.** Arguably on the list of [[Main UML Diagrams]], Component Diagrams represent system architecture. They are all about interfaces. What provides them, what requires them. In so doing, it represents the [[modularity]] of the system. Components are responsible for one clear thing and interact with each other on a need-to-know basis. Components have required and provided interfaces and also [[UML Ports]] (which are often associated with interfaces).  Component diagrams seem akin to [[SysML]] [[Internal Block Diagram]]s. **** # More ## Source - [Component diagram](https://en.wikipedia.org/wiki/Component_diagram) - more helpful - VisualParadigm’s weirdly good educational material: - [What is Component Diagram?](https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-component-diagram/) ## Related - [[Main UML Diagrams]] - [[UML]]