Message sequence chart: Difference between revisions

Revision as of 21:09, 30 January 2021

Latest revision as of 16:43, 10 July 2023

(3 intermediate revisions by 3 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 4 ⟶ 5:

The purpose of recommending MSC (Message Sequence Chart) is to provide a trace language for the specification and description of the communication behaviour of system components and their environment by means of message interchange. Since in MSCs the communication behaviour is presented in a very intuitive and transparent manner, particularly in the graphical representation, the MSC language is easy to

learn, use and interpret. In connection with other languages it can be used to support methodologies for system specification, design, simulation, testing, and documentation.

https://www.mintme.com/token/MSCU

==History==

Line 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 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 103 ⟶ 104:

| volume=37

| issue=11

| pages=8383–100

| year=2002

| author=David Harel