Content deleted Content added
m →History: clean up, typo(s) fixed: in March 12, 1993 → on March 12, 1993 |
Arianwen88 (talk | contribs) #suggestededit-add 1.0 Tags: Mobile edit Mobile app edit Android app edit |
||
| (4 intermediate revisions by 4 users not shown) | |||
Line 1:
{{Short description|Interaction diagram from the SDL family}}
[[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.]]
A '''message sequence chart''' (or '''MSC''') is an [[interaction diagram]] from the [[Specification and Description Language|SDL]] family standardized by the [[International Telecommunication Union]].
Line 58 ⟶ 59:
* 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.{{fact|date=November 2022}}
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
Line 97 ⟶ 98:
| author=David Harel
| doi=10.1023/A:1011227529550
| s2cid=1551133
|author-link = David Harel}}</ref><ref>{{cite journal
| title=Multiple instances and symbolic variables in executable sequence charts
Line 102 ⟶ 104:
| volume=37
| issue=11
| pages=
| year=2002
| author=David Harel
| |||