Object Oriented Software Engineering   View all facts   Glossary   Help

subject > representation > coding technique > diagram > UML diagram > interaction diagram > collaboration diagram > simple collaboration diagram

simple collaboration diagram
subject			fact

simple collaboration diagram	can be converted into a sequence diagram
	is a subtopic of 8.1 - Interaction Diagrams
	is a kind of collaboration diagram
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 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 drawn as as a graph with a set of objects and actors as the vertices
	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 can be hard for users to interact with or interpret not usable by blind people it can be expensive to program diagram drawing software
	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

Up: collaboration diagram