Hi,
As I know, protocol sm is used to describe the protocol between
classes/components,
which means it concerns only to the external view of classes/components
(behaviours exposed via classes' interfaces)
While behaviour sm can be used to model the internal behaviours of
classes/components,
which means it provide a comprehensive detail of classes/components.
That's why in the state of protocol sm, Entry/exit/do behaviours are not
necessary.
Best regards.
======================================
Thanh-Liem Phan
PhD student of LGI2P
Ecole des Mines d'Ales (Site de Nimes)
Parc Scientifique Georges Besse
F - 30035 Nimes Cedex 1
Mobile: +33 6.37.35.06.46
Email: [email protected]
Le 14/11/2011 14:29, Topcased user list where issues are discussed a
écrit :
Hy,
Thanks for your anwser and I will look to your references and maybe I will be
able to explain what I understood.
Cordialement,
Bernard Granier
CE Plateforme Système
[email protected]
01 58 11 32 51
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Topcased user
list where issues are discussed
Sent: Monday, November 14, 2011 2:26 PM
To: [email protected]
Subject: Re: [Topcased-users] differences between behaviorial and protocole
state machine ?
Hi Bernard
see : http://www.uml-diagrams.org/state-machine-diagrams.html
see also : "A Step-by-step Process to Build Conform UML Protocol State
Machines" (Lanoix, Souquières, 2006)
[Reading UML superstructure document, I do not understand "clearly" the
differences between behavorial and protocol state machine.]
So did I, and I still haven't found why a State in a protocol state machine
does not have Entry/Exit/do behavior... so If you find this justification in
the standard, please tell me where
Best regards
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
#
" Ce courriel et les documents qui lui sont joints peuvent contenir des informations
confidentielles ou ayant un caractère privé. S'ils ne vous sont pas destinés, nous vous
signalons qu'il est strictement interdit de les divulguer, de les reproduire ou d'en
utiliser de quelque manière que ce soit le contenu. Si ce message vous a été transmis par
erreur, merci d'en informer l'expéditeur et de supprimer immédiatement de votre système
informatique ce courriel ainsi que tous les documents qui y sont attachés."
******
" This e-mail and any attached documents may contain confidential or proprietary
information. If you are not the intended recipient, you are notified that any
dissemination, copying of this e-mail and any attachments thereto or use of their
contents by any means whatsoever is strictly prohibited. If you have received this e-mail
in error, please advise the sender immediately and delete this e-mail and all attached
documents from your computer system."
#
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
