UML+Collaboration+Diagram

http://www.comptechdoc.org/independent/uml/begin/umlcoldiagram.html http://www.developer.com/design/article.php/3102981 Collaboration diagrams are shown by modeling the objects in some designed system and showing relationships in between the objects and different links. The articles focus on how the data is represented and used in the system.   The process can be initiated by defining diagrams, and the elements to be used, which may be objects, associations and messages. The elements are denoted though different symbols, which make it easier to understand the use of data. Each operation being used in the system uses a separate collaboration diagram.  The cited references indicate what different patterns are used to assign object responsibilities. The diagrams are inter-related and large diagrams can be further decomposed into smaller ones.    http://www.edrawsoft.com/uml-collaboration.php http://edn.embarcadero.com/article/31863  A // collaboration diagram // (//__collaboration diagram:__ It is the interaction diagram which reflects a specific event described by a use case in a particular system, how a group of objects collaborate and interact with each other.//) shows association among object roles in a way that a group of messages exchanged among the objects to gain an operation or outcome. UML //Collaboration diagrams//  (interaction diagrams) depict the relationship and collaboration between software objects. The collaboration diagram illustrates messages interchanged between classes and objects (instances). A diagram is created for every system process which relates to iteration (//current development cycle//). This is why all systems operations will produce a collaboration diagram and there will be one diagram representing each system operation.   http://www.webcrawler.com/webcrawler/ws/results/Web/uml%20collaboration%20diagrams/1/417/TopNavigation/Relevance/iq=true/zoom=off/_iceUrlFlag=7?_IceUrl=true http://archive.devx.com/codemag/articles/2002/mayjune/collaborationdiagrams/codemag-1.asp As users start to interact with a software, the objects get in action as they start taking requests from one place to the other, making it possible for the user to get the desired outcome. Although usually all objects have specific purpose but sometimes they need to interact, collaborate, associate, and respond to each other, if a task is not in their given boundaries. These interactions are documented and described in UML through the Sequence diagrams, and the Collaboration Diagrams. The Collaboration diagrams aka communication diagrams, are used to identify relationships between object classes. The blocks in this diagram represents the objects and the arrows shows the relationship or association between them. These diagrams also help in defining the static diagrams for example Class diagrams. They are different from sequence diagram in the sense they look at the Overall view of the relationships, and not care much about the order or sequence of the interactions
 * Osama Masood **
 * Sources: **
 * Summary: **
 *  Syed Muhammad Mujtaba **
 *  Sources: **
 *  Summary: **
 * Syed Tauseef Hasnain Abidi: **
 * <span style="font-size: 9pt; color: #4d4d4d; font-family: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman';">Sources: **
 * <span style="font-size: 9pt; color: #4d4d4d; font-family: 'Verdana','sans-serif'; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman';">Summary: **