Committed to connecting the world

  •  

 

ITU-T Recommendations

Search by number:
Others:
Skip Navigation Links
Content search
Advanced search
Provisional name
ISO/IEC number
Formal description
Study Groups tree viewExpand Study Groups tree view

ITU-T Z.120 (02/2011)

عربي | 中文 | English | Español | Français | Русский
Message Sequence Chart (MSC)
Scope/objective

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.

Coverage

This Recommendation presents a syntax definition for Message Sequence Charts in textual and graphical representation. An informal semantics description is provided.

Application

MSC is widely applicable. It is not tailored for one single application domain. An important area of application for MSC is an overview specification of the communication behaviour for real time systems, in particular telecommunication switching systems. By means of MSCs, selected system traces, primarily "standard" cases, may be specified. Non-standard cases covering exceptional behaviour may be built on them. Thereby, MSCs may be used for requirement specification, interface specification, simulation and validation, test case specification and documentation of real time systems. MSC may be employed in connection with other specification languages, in particular SDL. In this context, MSCs also provide a basis for the design of SDL-systems.

Status/Stability

MSC is stable. This Recommendation is a maintenance update of the 2004 version correcting a number of errors and consolidating Appendix I into the main text. Otherwise it is intended to be the same as the 2004 version, which was a natural continuation of its 1999 version, refining concepts including:

• extended data interface, and references to default SDL interface, defined in ITU-T Z.121;

• uni-directional time constraints;

• in-line high level expressions.
Citation: http://handle.itu.int/11.1002/1000/11063
Approval date: 2011-02-13
Approval process:AAP
Status: In force
Maintenance responsibility: ITU-T Study Group 17
Further details: Patent statement(s)
Development history
Ed. ITU-T Recommendation Status Summary Table of Contents Download
5.1 Z.120 Annex B (04/1998) In force - - here
5 Z.120 (02/2011) In force
here
here
here
4.2 Z.120 (2004) Amd.2 (09/2009) Superseded
here
here
here
4.1 Z.120 (2004) Amd.1 (09/2008) Superseded
here
here
here
4 Z.120 (04/2004) Superseded
here
here
here
3.1 Z.120 (1999) Cor. 1 (12/2001) Superseded
here
here
here
3 Z.120 (11/1999) Superseded
here
here
here
2.1 Z.120 Annex C (10/1996) Superseded - - here
2 Z.120 (10/1996) Superseded - - here
1.1 Z.120 Annex B (03/1995) Superseded - - here
1 Z.120 (03/1993) Superseded -
here
here