Object Oriented Software Engineering View all facts Glossary Help |
subject > representation > coding technique > diagram > UML diagram > interaction diagram > collaboration diagram |
collaboration diagram | ||||
subject | fact |
collaboration diagram | can help validate class diagrams | |
can represent aspects of a design pattern | ||
contains a communication link between each pair of objects involved in the sending of a message; the messages themselves are attached to this link | ||
has definition A UML interaction diagram showing a set of objects connected by communications links | ||
has part communication link | ||
is better than sequence diagram when you are deriving an interaction diagram from a class diagram | ||
is similar to an instance diagram except that it does not show links of associations | ||
is a subtopic of 5.1 - What is UML? | ||
is drawn as as a graph with a set of objects and actors as the vertices | ||
is a kind of interaction diagram | ||
shows the relationships that exist among objects and actors | ||
interaction diagram | can be used to define the protocol used when two components communicate with each other | |
has purpose to better understand the sequence of messages | ||
helps you to visualize how the system runs | ||
models the dynamic aspects of a software system | ||
should be created after developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction | ||
UML diagram | describes aspects of the architectural model | |
has part constraint | ||
has part note | ||
see also Unified Modelling Language | ||
diagram | has advantages it conveys or summarizes complex concepts or mechanisms more easily than other techniques | |
has problems | ||
should have a label if its meaning is not obvious, using a caption or pop-up label that appears when the user moves the mouse over it |
Kinds of collaboration diagram :
Next interaction diagram: sequence diagram Up: interaction diagram