Message sequence chart: Difference between revisions

Content deleted Content added
Addbot (talk | contribs)
m Bot: Migrating 2 interwiki links, now provided by Wikidata on d:q1923934 (Report Errors)
Manu31415 (talk | contribs)
I have removed the UML Sequence Chart picture that actually does not exist. And I have listed the usual misunderstanding between UML Sequence Diagram and ITU-T MSC.
Line 1:
[[File:Typical MSC (Message Sequence Chart).png|thumb|The diagram shows three entities. At start the phone is disconnected. A user tries to establish a connection. A connection request is sent to the switch and a timer is started. An alternative deals with two possibles responses: 1 - The timer goes off because the switch did not reply and the phone goes back to the disconnected state.2 - The switch grants the connection and the call is established.]]
[[Image:CheckEmail.svg|thumb|250px|right|Example of a simple [[Unified Modeling Language|UML]] message sequence chart.]]
A '''message sequence chart''' (or '''MSC''') is an interaction diagram from the [[Specification and Description Language|SDL]] family very similar to [[Unified Modeling Language|UML]]'s [[sequence diagram]], standardized by the [[International Telecommunication Union]].
 
The main area of application for message sequence charts is as for communication behaviour in [[Real-time computing|real-time systems]], more specifically telecommunication [[electronic switching system]]s.
Line 29:
 
==Comparison to UML==
UML Sequence Diagram looks very similar to the ITU-T MSC but the default basic principles are quite different:
* Lifelines
:* In an MSC, the vertical lines are autonomous execution entities. They usually represent state machines executing in parallel. The state machines might not even be on the same machine.
:* In a Sequence Diagram, a vertical line is usually an object. The object can be active (in its own thread of execution) or passive (in the execution context of an active object).
* Arrows
:* In an MSC an arrow is usually an asynchronous message sent from one entity to another one. Once the message is sent the sending entity resumes its execution.
:* In a Sequence Diagram an arrow is usually understood as an operation call on a class. It is therefore synchronous and the calling entity hangs until the operation returns.
It has been said that MSC has been considered as a candidate for the [[Unified Modeling Language#Interaction diagrams|interaction diagrams]] in UML.<ref>{{cite web
| url=http://www.swe.informatik.uni-goettingen.de/publications/ER_JG_PG/SDL99-Harmonization.ps.gz