Object Oriented Software Engineering   View all facts   Glossary   Help

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

collaboration diagram comparison table

Subject	have part	have	model	be	have advantages	is a kind of	is a subtopic of	describe	have purpose	create after	validate	have problems	has part	use	help	convert into	represent	draw as	show	contain	see also
simple collaboration diagram	communication link	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	the dynamic aspects of a software system	similar to an instance diagram except that it does not show links of associations	it conveys or summarizes complex concepts or mechanisms more easily than other techniques	collaboration diagram	8.1 - Interaction Diagrams	aspects of the architectural model	to better understand the sequence of messages	developing a class diagram and a use case model because you need to know the actors and objects involved in an interaction	class diagrams	can be hard for users to interact with or interpret not usable by blind people it can be expensive to program diagram drawing software	note	to define the protocol used when two components communicate with each other	you to visualize how the system runs	a sequence diagram	aspects of a design pattern	as a graph with a set of objects and actors as the vertices	the relationships that exist among objects and actors	a communication link between each pair of objects involved in the sending of a message; the messages themselves are attached to this link	Unified Modelling Language

Next interaction diagram: sequence diagram    Up: interaction diagram