Message sequence chart

A message sequence chart (or MSC) is an interaction diagram from the SDL family standardized by the International Telecommunication Union.

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.

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.

History

The first version of the MSC standard was released on March 12, 1993.

The 1996 version added references, ordering and inlining expressions concepts, and introduced HMSC[1] (High-level Message Sequence Charts), which are the way of expressing a sequence of MSCs.

The MSC 2000 version[2] added object orientation, refined the use of data and time in diagrams, and added the concept of remote method calls.[3]

Latest version has been published in February 2011.

Symbols in MSC

The existing symbols are:

  • MSC head, lifeline, and end: a vertical line with a box at the top, and a box or a cross at the bottom.
  • Instance creation: horizontal dashed arrow to the newly created instance.
    Dynamic process creation in an MSC
  • Message exchange: horizontal arrow.
  • Control flow: horizontal arrow with the 'call' prefix, dashed arrow for reply symbol, method and suspension symbols in between.
    Call operation in an MSC
  • Timers: start, cancel, time out.
  • Time interval: relative and absolute with a dashed vertical arrow.
    Time constraint in an MSC
  • Conditions: usually used to represent a state of the underlying state machine.
  • Action: a box.
  • In-line expressions: alternative composition, sequential composition, exception, optional region, parallel composition, iteration (loop).
  • Reference: reference to another MSC.
    MSC Reference in an MSC
  • Data concept: The user can use any data concept, if binding is undefined the default data concept is the one from SDL as defined in Z.121 recommendation.
  • Coregion: a double dashed instance line to describe unordered events.

Symbol extensions
  • SDL-RT has introduced:
    • a semaphore instance representation.
      SDL-RT Semaphore extension to MSC
    • a save symbol to save messages.

Comparison to UML

UML 2.0 Sequence Diagram is strongly inspired by the ITU-T MSC. Still, for historical reasons, 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 need not be on the same computer.
  • 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 interaction diagrams in UML.[4]

However, proponents of MSC such as Ericsson think that MSC is better than UML 2.0 for modelling large or complex systems.[5]

Live Sequence Charts

David Harel suggested that MSC had shortcomings such as:

  • MSC propose a weak partial ordering semantics that makes it impossible to capture some behavioral requirements,
  • The relationship between the MSC requirements and the executable specification is not clear,

and proposed Live Sequence Charts (LSC) as an extension on the MSC standard .[6][7][8]

See also
  • PSC Property Sequence Chart, a way to describe properties in an MSC[9] or a Sequence Diagram.
  • SDL Specification and Description Language, an MSC related ITU-T language.
  • Interaction diagrams in UML.

References
  1. "HMSC". sdl-forum.org. Retrieved 2009-09-19.
  2. Øystein Haugen. "MSC 2000" (PDF). Ericsson. Archived from the original (PDF) on 2011-06-07. Retrieved 2009-09-19.
  3. "What is new in MSC 2000 relative to MSC 96". sdl-forum.org. Retrieved 2009-09-19.
  4. Ekkart Rudolph; Jens Grabowski; Peter Graubmann (1999). "Towards a Harmonization of UML-Sequence Diagrams and MSC". University of Göttingen. Retrieved 2014-08-25.
  5. Øystein Haugen (June 2000). "UML 2.0 vs. SDL/MSC – Ericsson Position Statement" (PDF). Ericsson. Retrieved 2009-09-19.
  6. David Harel (2003-04-08). "Message Sequence Charts" (PDF). Archived from the original (PDF) on 2006-08-26. Retrieved 2009-09-20.
  7. David Harel (2005-02-22). "LSCs: Breathing Life into Message Sequence Charts". Formal Methods in System Design. 19: 45–80. doi:10.1023/A:1011227529550.
  8. David Harel (2002). "Multiple instances and symbolic variables in executable sequence charts". ACM SIGPLAN Notices. 37 (11): 83. CiteSeerX 10.1.1.20.5984. doi:10.1145/583854.582429.
  9. Emmanuel Gaudin; Eric Brunel (2013). SDL 2013: Model-Driven Dependability Engineering. Lecture Notes in Computer Science. 7916. Springer. pp. 19–35. doi:10.1007/978-3-642-38911-5_2. ISBN 978-3-642-38910-8.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.