UNIVERSIDAD TECNOLOGICA DE LA RIVIERA MAYA

SOFTWARE DEVELOPMENT METHODOLOGIES AND MODELING

STUDENT:

VAZQUEZ MENA MOISES AARON

TEACHER:

PROFESOR: JUAN ANTONIO DOMINGUEZ

DATE

20 DE JULIO DE 2024
INDEX
INTRODUCTION.........................................................................................3
What are Communication/Collaboration Diagrams?..........................................3
Purpose and Use.........................................................................................3
characteristics.............................................................................................4
Advantages.................................................................................................4
Disadvantages.............................................................................................4
Symbols in Communication/Collaboration Diagrams................................5

........................6
EXAMPLE...................................................................................................7
CONCLUSION.............................................................................................8
BIBLIOGRAPHY..........................................................................................9
INTRODUCTION
Communication diagrams, also known as collaboration diagrams, are key tools in
the field of software engineering and systems modeling. These diagrams are part
of the Unified Modeling Language (UML) and are used to represent the interaction
between different components of a system, whether software or hardware.

What are Communication/Collaboration

Diagrams?
Communication diagrams focus on the interaction between objects or parts of the
system, highlighting how they communicate with each other through messages.
Unlike sequence diagrams, which emphasize the temporal order of messages,
communication diagrams emphasize the organizational structure of the objects and
their relationships.

Purpose and Use

The primary purpose of communication diagrams is to provide a clear and detailed
view of how system components collaborate to fulfill certain processes or
functionalities. These diagrams are useful in various stages of software
development, including:

1. Requirements Analysis: They help understand how different components

need to interact to meet system requirements.
2. System Design: They facilitate the planning and organization of component
interactions during the design phase.
 3. Documentation: They serve as a detailed reference that documents the
system's behavior and structure, useful for both developers and other
stakeholders.

characteristics
The main elements of a communication diagram include:

 Objects/Participants: The entities interacting within the system,

represented as rectangles labeled with the object's name and its class.
 Links/Associations: The connections between objects that allow
communication, represented by lines.
 Messages: The interactions sent from one object to another, often labeled
with the message name and, optionally, parameters.

Advantages
1. Structural Clarity: They help visualize the system's structure and how
components are interrelated.
2. Ease of Communication: They facilitate communication among
development team members and stakeholders by providing an
understandable visual representation.
3. Problem Detection: They help identify potential design issues and points
for improvement in component interactions.

Disadvantages
1. Complexity in Large Systems: In very large or complex systems,
communication diagrams can become difficult to manage and understand.
2. Focus on Structure: While they show how components communicate, they
do not always capture the temporal flow of interactions as clearly as
sequence diagrams.
Symbols in Communication/Collaboration
Diagrams
Communication diagrams use a specific set of symbols to represent the various
components and interactions within a system.

1. Objects/Participants

 Rectangle: Objects or participants in the interaction are represented by

rectangles. Inside the rectangle, the object's name and its class are written
in the format objectName : ClassName.

2. Links/Associations

 Line: A line represents a link or association between objects, indicating a

relationship that allows communication.

3. Messages

 Arrow: Arrows along the lines between objects indicate the direction of
message flow. Messages are labeled with the message name, and
optionally, parameters and sequence numbers.
  Numbered Sequence: To show the order of messages, numbers are
often prefixed to message names. This helps clarify the sequence of
interactions.

4. Combined Fragment (Optional)

 Dashed Rectangle: A dashed rectangle, called a combined fragment, can

be used to group a set of interactions, especially when dealing with
conditions or loops.
5. Conditions (Optional)

 Brackets: Conditions can be specified using brackets. These conditions

determine when a particular message is sent.

EXAMPLE
Scenario

The customer (Customer) places an order through an e-commerce system, which

is processed by the order system (OrderSystem) and confirmed by the shipping
service (ShippingService).

Communication Diagram
Participants:

 Customer: Represents the user placing the order.

 OrderSystem: Handles the order logic.
 ShippingService: Responsible for confirming the shipment.

Interactions:

1. The Customer sends a message "placeOrder(order)" to the OrderSystem.

2. The OrderSystem processes the order and sends a message
"confirmOrder(order)" to the ShippingService.
3. The ShippingService confirms the order and sends a message
"sendConfirmation(order)" back to the OrderSystem.
4. Finally, the OrderSystem sends a response "orderConfirmed()" to the
Customer.
 DIAGRAM

Diagram Description

1. Customer initiates the interaction by sending the message

"placeOrder(order)" to the OrderSystem.
2. OrderSystem receives the order and sends "confirmOrder(order)" to the
ShippingService to process the shipment.
3. ShippingService confirms the order and responds to the OrderSystem with
"sendConfirmation(order)".
4. Finally, OrderSystem notifies the Customer that the order has been
confirmed with the message "orderConfirmed()".

CONCLUSION
In summary, communication/collaboration diagrams are a valuable tool in system
modeling, providing a clear view of how system components interact. Although
they have limitations, their ability to enhance understanding and communication
among team members makes them an essential tool for the design and analysis of
complex systems. Using them in combination with other modeling tools can offer a
more comprehensive and detailed perspective of the developing system.
BIBLIOGRAPHY
"UML Communication Diagrams"
Autor: IBM Developer
Enlace: IBM Developer - UML Communication Diagrams
Descripción: Un artículo que proporciona una introducción a los diagramas de
comunicación, con ejemplos y explicaciones prácticas.

"Understanding UML Collaboration Diagrams"

Autor: Object Management Group (OMG)
Enlace: OMG - UML Collaboration Diagrams
Descripción: Documentación oficial de UML que incluye información sobre los
diagramas de colaboración.

"UML Communication Diagram Tutorial"

Enlace: TutorialsPoint - UML Communication Diagram
Descripción: Un tutorial que explica los diagramas de comunicación con ejemplos
y detalles prácticos.