like UML sequence diagrams,
are used to explore the dynamic nature of your software. Collaboration diagrams show the message flow between objects
in an OO application, and also imply the basic associations (relationships)
between classes. Collaboration
diagrams are often
like UML sequence diagrams,
are used to explore the dynamic nature of your software. Collaboration diagrams show the message flow between objects
in an OO application, and also imply the basic associations (relationships)
between classes. Collaboration
diagrams are often used to:
- Provide a birds-eye view of a collection of collaborating objects, particularly
within a real-time environment.
functionality to classes by exploring the behavioral aspects of a system.
- Model the logic of the implementation of a complex operation, particularly one
that interacts with a large number of other objects.
- Explore the roles that objects take within a system, as well as the different
relationships they are involved with when in those roles.
There are guidelines for:
Figure 1. An Instance-Level UML
- Use Instance-Level Diagrams To Explore Object Design Issues. Instance-level UML Collaboration diagrams, such as the one
1, depict interactions between objects (instances). Instance-level diagrams are typically created to explore the internal
design of object-oriented software.
- Use Specification-Level Diagrams to Explore Roles. Specification-level UML Collaboration diagrams, such as the
one shown in
Figure 4, are used to analyze and explore the roles taken by domain classes
within a system.
- Collaboration Diagrams Do Not Model Process Flow.
- When Sequence Is Important Use a Sequence Diagram.
- Apply Sequence Diagram Guidelines To Instance-Level Collaboration
Diagrams. Because UML Collaboration diagrams d