A Communication Diagram models the structural dimension of a scenario by graphically illustrating the interactions between Actors and instances of Classes, Data Types, Interfaces and Signals. Communication Diagrams provide alternative representations of a Sequence Diagram, each one modeling a different execution thread (or \u201cscenario\u201d) through a use case by showing the flow or sequence of messages between associated objects. It is possible to have multiple Communication Diagrams for a single use case.
Communication Diagrams provide help with the architectural design of the system by providing a visual representation of the structure of object collaborations. They can be constructed very quickly, enabling experiments to be carried out with alternative designs based on different objects as collaborators and controllers, and with different messages passing between them.
You can create a Communication Diagram through the context menu of a Package: right-click the Package, point to New, point to UML, point to Behavior, and then click Communication Diagram. You can also create a Communication Diagram for an Event, Operation or Use Case: right-click the item, point to New, and then click Communication Diagram.
The following sections provide information about how a Communication Diagram is used in the model. For more information about an item, property or model part, click it.
For most diagram symbols, you can change the presentation of the symbol through the Style view options (See
Style view options - all diagrams ), and change the showing of Stereotypes and Tag Definitions through the Stereotypes view options (See
Stereotypes view options for a symbol - all diagrams). When a symbol has additional view options for changing its presentation, this icon is shown - to see how the view options can change the presentation, click the icon.