Designing a UML 1.5 Component Diagram

From RAD Studio
Jump to: navigation, search

Go Up to UML 1.5 and 2.0 Diagram Procedures

Following are tips and techniques that you can use when working with UML 1.5 Component Diagrams. It can be convenient to start creation of a model with Component Diagrams if you are modeling a large system. For example, a distributed, client-server software system, with numerous interconnected modules. You use Component Diagrams for modeling a logical structure of your system, while you use Deployment Diagrams for modeling a physical structure.

To design a UML 1.5 Component Diagram, follow this general procedure:

  1. Create a hierarchy of Subsystems.

    Tip: You can create nested Subsystems.

  2. Create a hierarchy of Components. The largest component can be the whole system or its major part (for example, server application, IDE, service).

    Tip: You can create nested component nodes. There are two methods for creating a nested component node:You can select an existing component and add a child component inside.Alternatively, you can create two separate components and connect them with an Association-Composition link.

  3. Create interfaces. Each component can have an interface.
  4. Draw links between elements.
  5. You can optionally create shortcuts to related elements of other diagrams.

See Also