Skip to main content

Differences between sequence diagrams and collaboration diagrams


Technote (FAQ)


Question

What are the differences between a sequence diagram and a collaboration diagram in IBM Rational Rose products?

Answer

The main differences between sequence and collaboration diagrams: sequence diagrams show time-based object interaction while collaboration diagrams show how objects associate with each other.

When you work in either a collaboration or sequence diagram, it is possible to view the corresponding diagram by pressing the F5 key. For example, if you are working on a sequence diagram, when you press F5, Rose will automatically create a collaboration diagram with the same diagram name and model elements. If you make a change to one diagram and then press F5, the change will appear on the corresponding diagram as well.

Note: When toggling from a sequence diagram to a collaboration diagram, you
might need to rearrange the collaboration diagram model elements.

====== COLLABORATION DIAGRAM:

Collaboration diagrams and sequence diagrams are alternate representations of an interaction. A collaboration diagram is an interaction diagram that shows the sequence of messages that implement an operation or a transaction.

Collaboration diagrams show objects, their links, and their messages. They can also contain simple class instances and class utility instances. Each collaboration diagram provides a view of the interactions or structural relationships that occur between objects and object-like entities in the current model.

The Create Collaboration Diagram Command creates a collaboration diagram
from information contained in the sequence diagram. The Create Sequence
Diagram Command creates a sequence diagram from information contained in the
interaction's collaboration diagram. The Goto Sequence Diagram and Goto
Collaboration Diagram commands traverse between an interaction's two
representations.

Collaboration diagrams contain icons representing objects. You can create
one or more collaboration diagrams to depict interactions for each logical
package in your model. Such collaboration diagrams are themselves contained
by the logical package enclosing the objects they depict.

======= SEQUENCE DIAGRAM

A sequence diagram is a graphical view of a scenario that shows object interaction in a time-based sequence of what happens first, what happens next. Sequence diagrams establish the roles of objects and help provide essential information to determine class responsibilities and interfaces. This type of diagram is best used during early analysis phases in design because they are simple and easy to comprehend. Sequence diagrams are normally associated with use cases.

Sequence diagrams are closely related to collaboration diagrams and both are alternate representations of an interaction. There are two main differences between sequence and collaboration diagrams: sequence diagrams show time-based object interaction while collaboration diagrams show how objects associate with each other.

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Rose Modeler
Software Development Rational Rose Professional VisualBasic
Software Development Rational Rose Professional Ada
Software Development Rational Rose Professional C++
Software Development Rational Rose Professional J

Historical Number

12790

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

Rational Rose Enterprise

General information


Software version:
7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4


Operating system(s):
AIX, HP-UX, IRIX, Linux, Solaris, Windows


Reference #:
1123475


Modified date:
2012-04-18

Translate my page

Content navigation