Component diagrams

In UML, component diagrams show the structure of the software system, which describes the software components, their interfaces, and their dependencies. You can use component diagrams to model software systems at a high level or to show components at a lower, package level.

This type of diagram supports component-based development in which a software system is divided into components and interfaces that are reusable and replaceable.

Component diagrams are useful for the following reasons:
You can also use component diagrams to depict the following physical parts of a software system:
Note: Component diagrams are distinct from deployment diagrams. A component diagram defines the composition of components and artifacts in the system. A deployment diagram shows components and artifacts in relation to where they are used in the deployed system.

The following topics describe model elements in component diagrams:

Related tasks
Modeling the component and services view of an application
Specifying relationships in UML diagrams
Adding interfaces to modeling diagrams
Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.