Communication diagram

Communication diagram

Le diagramme de communication est similaire au time diagram. La différence entre ces deux diagrammes est que le premier ne possède pas de ligne de vie. Le diagramme place les objets (les participants) et les interactions entre eux. Cela permet de visionner le comportement collectif d’objets en vue de réaliser une opération. Le diagramme de communication représente les collaborations (collection d’objets) : les relations, les fonctionnalité et les communications.

We use the communication diagram when starting a project, it helps to clarify the field of study, to frame the project. It is also useful to represent the collaboration between the field of study and the partners using the flows in, out, external actors and related fields.

Objects and communication

Objects are represented by a rectangle containing the name of the class and / or the name of the object. The objects communicate via messages: synchronous in full arrow, asynchronous in empty arrow, go message in solid line, return message in dotted line.

  • Synchronous: A message is sent from one object to another, and the first object waits until the action has finished.
  • Asynchronous: A message is sent from one object to another, but the first object does not wait for the action to complete.
  • Go: Each arrow represents a progression from one step to another in the sequence. Most asynchronous.
  • Return: The explicit return of an object to which the message was sent.

The messages have an indication to the message sent:

  • Messages sent at the same time: Using the Number-Letter notation
  • Messages invoked several times: Loop constraint * [i = 0..9]
  • Messages sent to a condition: Adding a logical expression [condition = true]
  • Messages sent to itself: A loop
uml communication diagram
To share
en_GBEN
%d bloggers like this: