collaboration diagram

A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). The concept is more than a decade old although it has been refined as modeling paradigms have evolved.

A collaboration diagram resembles a flowchart that portrays the roles, functionality and behavior of individual objects as well as the overall operation of the system in real time. Objects are shown as rectangles with naming labels inside. These labels are preceded by colons and may be underlined. The relationships between the objects are shown as lines connecting the rectangles. The messages between objects are shown as arrows connecting the relevant rectangles along with labels that define the message sequencing.

Collaboration diagrams are best suited to the portrayal of simple interactions among relatively small numbers of objects. As the number of objects and messages grows, a collaboration diagram can become difficult to read. Several vendors offer software for creating and editing collaboration diagrams.

Read more about collaboration diagram: - The Sun Developer Network explains how collaboration diagrams are generated. - Robert C. Martin wrote a collaboration diagram tutorial in 1997 that remains applicable today. - Agile Modeling offers guidelines for creating collaboration diagrams.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software development groups take many routes to Agile More software development groups are implementing Agile methodologies, but their routes to adoption are far from straight and narrow and vary from... Survey: Agile interest high, but waterfall still used by many While there's a strong interest in new software development techniques, SearchSoftwareQuality.com's recent survey found that many still follow... Ivar Jacobson: Useful app dev practices trump full-blown processes Ivar Jacobson, the father of use cases and a founder of UML, advocates adopting useful software development practices over full-blown processes such...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Capability Maturity Model  (SearchSoftwareQuality.com) rapid application development  (SearchSoftwareQuality.com)