UML Component diagrams show the dependencies among software
components,
including the classifiers that specify them, such as implementation
classes;
and the artifacts that implement them, such as source-code files,
binary-code
files.
It is a simple, high-level diagram, which refers to physical components
in
a design. It is used to show how code is actually divided into modules.
While
package diagrams show logical or conceptual division, component
diagrams are
used to show physical division used for implementation.
A Component diagram shows the dependencies among software
components, including
source code, binary code and executable components. Some components
exist
at compile time, some exist at link time, and some exist at run time.
Components are physical units including:
The elements of the Component diagram are available in the tool bar:
Create component
items. Note that components can be nested.
Create inheritance
relationships between components.
Add
interface to the diagram.
Create artifact within the diagram.
Create an implementation
relationship between a component and its interfaces.
Indicate dependency
relationships among the diagram items.