Knowledge

Message sequence chart

Source 📝

31: 166: 118: 62:
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
34:
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
63:
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.
200: 146: 132: 234:
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.
237:
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).
254:
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.
251:
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.
652: 642: 421: 316: 175: 52: 603: 56: 477: 97:
The MSC 2000 version added object orientation, refined the use of data and time in diagrams, and added the concept of remote method calls.
160:
In-line expressions: alternative composition, sequential composition, exception, optional region, parallel composition, iteration (loop).
657: 129:
Control flow: horizontal arrow with the 'call' prefix, dashed arrow for reply symbol, method and suspension symbols in between.
117: 647: 223:
is strongly inspired by the ITU-T MSC. Still, for historical reasons, the default basic principles are quite different:
425: 364: 174:
Data concept: The user can use any data concept, if binding is undefined the default data concept is the one from
322: 272: 261: 558: 30: 291: 112:
MSC head, lifeline, and end: a vertical line with a box at the top, and a box or a cross at the bottom.
35:
goes back to the disconnected state.2 - The switch grants the connection and the call is established.
446: 563: 48: 528: 484: 637: 599: 591: 568: 520: 297:
The relationship between the MSC requirements and the executable specification is not clear,
220: 75: 313:
Property Sequence Chart, a way to describe properties in an MSC or a Sequence Diagram.
17: 631: 399: 342: 199: 549:(2002). "Multiple instances and symbolic variables in executable sequence charts". 532: 145: 595: 546: 508: 473: 283: 131: 590:. Lecture Notes in Computer Science. Vol. 7916. Springer. pp. 19–35. 524: 301:
and proposed Live Sequence Charts (LSC) as an extension on the MSC standard .
154:
Conditions: usually used to represent a state of the underlying state machine.
294:
semantics that makes it impossible to capture some behavioral requirements,
165: 572: 453: 371: 268: 115:
Instance creation: horizontal dashed arrow to the newly created instance.
375: 319:
Specification and Description Language, an MSC related ITU-T language.
71:
The first version of the MSC standard was released on March 12, 1993.
621: 260:
It has been said that MSC has been considered as a candidate for the
191: 181:
Coregion: a double dashed instance line to describe unordered events.
511:(2005-02-22). "LSCs: Breathing Life into Message Sequence Charts". 143:
Time interval: relative and absolute with a dashed vertical arrow.
310: 198: 164: 144: 130: 116: 29: 94:
harts), which are the way of expressing a sequence of MSCs.
422:"Towards a Harmonization of UML-Sequence Diagrams and MSC" 420:
Ekkart Rudolph; Jens Grabowski; Peter Graubmann (1999).
100:
Latest version has been published in February 2011.
447:"UML 2.0 vs. SDL/MSC – Ericsson Position Statement" 588:SDL 2013: Model-Driven Dependability Engineering 74:The 1996 version added references, ordering and 286:suggested that MSC had shortcomings such as: 8: 400:"What is new in MSC 2000 relative to MSC 96" 78:expressions concepts, and introduced HMSC ( 562: 275:for modelling large or complex systems. 334: 27:Interaction diagram from the SDL family 586:Emmanuel Gaudin; Eric Brunel (2013). 197:a semaphore instance representation. 163:Reference: reference to another MSC. 57:International Telecommunication Union 7: 267:However, proponents of MSC such as 178:as defined in Z.121 recommendation. 126:Message exchange: horizontal arrow. 653:Unified Modeling Language diagrams 121:Dynamic process creation in an MSC 25: 203:SDL-RT Semaphore extension to MSC 140:Timers: start, cancel, time out. 513:Formal Methods in System Design 208:a save symbol to save messages. 643:Formal specification languages 271:think that MSC is better than 1: 624:message sequence chart (MSC) 445:Øystein Haugen (June 2000). 596:10.1007/978-3-642-38911-5_2 323:Interaction diagrams in UML 55:family standardized by the 674: 658:Software modeling language 622:ITU-T Recommendation Z.120 108:The existing symbols are: 478:"Message Sequence Charts" 149:Time constraint in an MSC 135:Call operation in an MSC 525:10.1023/A:1011227529550 426:University of Göttingen 169:MSC Reference in an MSC 204: 170: 150: 136: 122: 41:message sequence chart 36: 18:Message Sequence Chart 573:10.1145/583854.582429 202: 168: 148: 134: 120: 33: 279:Live Sequence Charts 262:interaction diagrams 648:Telephone exchanges 551:ACM SIGPLAN Notices 290:MSC propose a weak 49:interaction diagram 205: 171: 151: 137: 123: 37: 605:978-3-642-38910-8 215:Comparison to UML 186:Symbol extensions 16:(Redirected from 665: 610: 609: 583: 577: 576: 566: 543: 537: 536: 505: 499: 498: 496: 495: 489: 483:. Archived from 482: 470: 464: 463: 461: 460: 451: 442: 436: 435: 433: 432: 417: 411: 410: 408: 407: 396: 390: 389: 387: 386: 380: 374:. Archived from 369: 363:Øystein Haugen. 360: 354: 353: 351: 350: 339: 292:partial ordering 221:Sequence Diagram 194:has introduced: 21: 673: 672: 668: 667: 666: 664: 663: 662: 628: 627: 618: 613: 606: 585: 584: 580: 545: 544: 540: 507: 506: 502: 493: 491: 487: 480: 472: 471: 467: 458: 456: 449: 444: 443: 439: 430: 428: 419: 418: 414: 405: 403: 402:. sdl-forum.org 398: 397: 393: 384: 382: 378: 367: 362: 361: 357: 348: 346: 345:. sdl-forum.org 341: 340: 336: 332: 307: 281: 217: 188: 106: 69: 28: 23: 22: 15: 12: 11: 5: 671: 669: 661: 660: 655: 650: 645: 640: 630: 629: 626: 625: 617: 616:External links 614: 612: 611: 604: 578: 564:10.1.1.20.5984 557:(11): 83–100. 538: 500: 476:(2003-04-08). 465: 437: 412: 391: 355: 333: 331: 328: 327: 326: 320: 314: 306: 303: 299: 298: 295: 280: 277: 258: 257: 256: 255: 252: 246: 245: 241: 240: 239: 238: 235: 229: 228: 216: 213: 212: 211: 210: 209: 206: 187: 184: 183: 182: 179: 172: 161: 158: 157:Action: a box. 155: 152: 141: 138: 127: 124: 113: 105: 104:Symbols in MSC 102: 68: 65: 26: 24: 14: 13: 10: 9: 6: 4: 3: 2: 670: 659: 656: 654: 651: 649: 646: 644: 641: 639: 636: 635: 633: 623: 620: 619: 615: 607: 601: 597: 593: 589: 582: 579: 574: 570: 565: 560: 556: 552: 548: 542: 539: 534: 530: 526: 522: 518: 514: 510: 504: 501: 490:on 2006-08-26 486: 479: 475: 469: 466: 455: 448: 441: 438: 427: 423: 416: 413: 401: 395: 392: 381:on 2011-06-07 377: 373: 366: 359: 356: 344: 338: 335: 329: 324: 321: 318: 315: 312: 309: 308: 304: 302: 296: 293: 289: 288: 287: 285: 278: 276: 274: 270: 265: 263: 253: 250: 249: 248: 247: 243: 242: 236: 233: 232: 231: 230: 226: 225: 224: 222: 214: 207: 201: 196: 195: 193: 190: 189: 185: 180: 177: 173: 167: 162: 159: 156: 153: 147: 142: 139: 133: 128: 125: 119: 114: 111: 110: 109: 103: 101: 98: 95: 93: 89: 85: 81: 77: 72: 66: 64: 60: 58: 54: 50: 46: 42: 32: 19: 587: 581: 554: 550: 541: 516: 512: 503: 492:. Retrieved 485:the original 468: 457:. Retrieved 440: 429:. Retrieved 415: 404:. Retrieved 394: 383:. Retrieved 376:the original 358: 347:. Retrieved 337: 300: 282: 266: 259: 218: 107: 99: 96: 91: 87: 83: 79: 73: 70: 61: 44: 40: 38: 547:David Harel 509:David Harel 474:David Harel 284:David Harel 632:Categories 494:2009-09-20 459:2009-09-19 431:2014-08-25 406:2009-09-19 385:2009-09-19 365:"MSC 2000" 349:2009-09-19 330:References 82:igh-level 559:CiteSeerX 519:: 45–80. 227:Lifelines 51:from the 638:Diagrams 454:Ericsson 372:Ericsson 305:See also 269:Ericsson 264:in UML. 219:UML 2.0 90:equence 76:inlining 47:) is an 533:1551133 273:UML 2.0 86:essage 67:History 602:  561:  531:  343:"HMSC" 244:Arrows 192:SDL-RT 529:S2CID 488:(PDF) 481:(PDF) 450:(PDF) 379:(PDF) 368:(PDF) 600:ISBN 43:(or 592:doi 569:doi 521:doi 317:SDL 311:PSC 176:SDL 53:SDL 45:MSC 634:: 598:. 567:. 555:37 553:. 527:. 517:19 515:. 452:. 424:. 370:. 59:. 39:A 608:. 594:: 575:. 571:: 535:. 523:: 497:. 462:. 434:. 409:. 388:. 352:. 325:. 92:C 88:S 84:M 80:H 20:)

Index

Message Sequence Chart

interaction diagram
SDL
International Telecommunication Union
inlining




SDL
SDL-RT

Sequence Diagram
interaction diagrams
Ericsson
UML 2.0
David Harel
partial ordering
PSC
SDL
Interaction diagrams in UML
"HMSC"
"MSC 2000"
Ericsson
the original
"What is new in MSC 2000 relative to MSC 96"
"Towards a Harmonization of UML-Sequence Diagrams and MSC"
University of Göttingen
"UML 2.0 vs. SDL/MSC – Ericsson Position Statement"

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.