Message versus signal to call a method in a digram sequence

I am studying a UML sequence diagram and I came across a method call, so I noticed that there are two ways to make a call to a behavior method in Unified Modeling Language (UML), which is a signal and a message, but I don’t know, I know how indicate which one and on the basis of what? I mean, when to use the message and when to use the signal, because I consider this a very important design decision and should be well chosen?

+4
source share
2 answers

Actually it is, but I think that the terminology you use is not very accurate (message and signal). All kind of communication between two objects in a sequence diagram is considered a message .

However, there are two main types of messages: synchronous and asynchronous .

A normal method call, when the invoke method call is blocked until the method completes, is a synchronous call, a synchronous message. Invoker will receive the return value from the called method and continue its own execution. As a result, there is only one thread of execution.

, - . - SMS-, UDP .. .

.

+2

http://www.uml-diagrams.org/sequence-diagrams.html

.. operation, signal...

/, " ",

.. .

/ (). ( )

( 100%, , )


EDIT: , , - / (broadcast) @Aleks

" " , , , Copyright © 1999 by Addison Wesley Longman, Inc. ,

Message..Semantics

.. - () (), () ( ). ...

.. . . , ..

.. - , . .

EDIT: , Enterprise Architect

, - ( ) " "

3 different message types as supported by Enterprise Architect

0

Source: https://habr.com/ru/post/1540038/


All Articles