Chapter 9 Working with Object-Oriented Models

Defining Related Diagrams

Each diagram of the OOM contains specific objects. However, you may want to attach objects in one diagram to another type of diagram in order to see your objects from different angles. You do this on the Related Diagrams tab of the object property sheet. For example, you may use related diagrams to:

Link a class diagram, communication diagram or sequence diagram to a use case to specify the implementation of a use case. When the use case is implemented this way in a class diagram for example and if you delete the use case, the class diagram is not deleted
Specify a class decomposition, and show its links to use case diagrams. Even if you start your analysis with a use case diagram that is considered the highest conceptual level, you can go down to the class diagram, define the classes and go back to the use case diagram to further detail it
Link a use case diagram to a use case to specify the use case decomposition, and show its relations to other use case diagrams. For example, a use case can be expanded into several other use case diagrams if the system needs to be further detailed
Specify a class behavior in a communication or sequence diagram. For example, in a sequence diagram an object is an instance of a class represented in a time-based dynamic environment
Describe the use of an operation in a communication diagram or a sequence diagram since both diagrams specify the behavior of classes and interfaces, and the possible use of their operations
Specify a component behavior via a class diagram to help you detect the context in which a class is used to generate the component

For more information, see the "Defining related diagrams" section in the "Managing Models" chapter of the General Features Guide .