 - 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.
 |
Learn more about Traditional software models (RUP, V-Model, CMM, Waterfall) |
| Can traditional project management and agile development coexist?: Are traditional project managers and agile practitioners fundamentally at odds? Or can they live together and even complement each other? |
| 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 traditional development practices. |
  |
CMMI: Good process doesn't always lead to good quality: Having a process such as CMMI in place doesn't guarantee quality software or systems, says Bill Curtis, co-author of CMM. You can still have defects. |
| Addressing software quality issues with development models, methods: Each development model has its own practices for building quality software. The challenge is determining which one fits your needs. The resources here can help you decide. |
| Testers debate differences between waterfall, Agile test automation: Two professional testers continue the timeless debate, agile vs waterfall, which is the best methodology for test-driven software development. |
| Test-driven testing face-off: Waterfall vs. Agile: Most software test pros pick a preferred methology and stand by it, in this tip two testers square-off, one advocating for agile development, the other in the waterfall corner. |
| Solving problems with session-based test management: A veteran software tester gives real-life examples of using session-based test management in Scrum, RUP and in a completely ad hoc environment. |
| Best practices for moving testers from waterfall to agile development: Software testers moving from a waterfall environment to the agile development model don't have to be driven to the head-banging stage of frustration. |
| LAST UPDATED: |
08 Mar 2007
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
