NOTE
Component Diagrams
Describing coarse-grained modules/components, provided interfaces, dependencies, and boundaries.
This is a historical learning note and may contain outdated or incomplete understanding.
A component diagram shows coarse software units and how they depend on or interact with each other. A component may be a module, subsystem, service, library, adapter, or other independently meaningful unit.
Use stable responsibilities and interfaces as the center of the diagram. If every source package appears, the diagram is operating at too low a level for architectural communication.