Modeling Software Using the Component Diagram


In This Chapter

  • Defining the Component diagram for UML 1.4 and 2.0
  • Defining and modeling component types
  • Defining and modeling component containment
  • Defining and modeling dependencies
  • Defining and modeling «reside» and «implement» dependencies
  • Defining and modeling interfaces and ports
  • Defining and modeling connectors


Once the logical design is completed using the Use Case, Class, and Interaction diagrams, the next step is to define the physical implementation of your design. The physical implementation must address three issues:

  1. The physical description of the software. The Component diagram models the physical implementation of the software specified by the logical requirements in Class diagram.
  2. The layout of the hardware. The Deployment diagram (discussed in Chapter 16) models the physical architecture of the hardware.
  3. The integration of the software and the hardware. The combined Deployment and Component diagrams (covered in Chapter 17) model the integration and distribution of the software across the hardware.

Classes describe the logical organization and intent of your software design. Components describe the physical implementations of your software design.

The purpose of the Component diagram is to define physical ...

Get UML™ Bible now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.