Difference between revisions of "MSC tutorial"

From TASTE
Jump to: navigation, search
(Created page with "= Introduction = MSC stands for '''Message Sequence Chart''' and it is a standard from the ITU-T: https://www.itu.int/rec/T-REC-Z.120. The MSC standard describes a language...")
 
(Introduction)
Line 11: Line 11:
 
There are two major uses of MSC in a system development lifecycle:
 
There are two major uses of MSC in a system development lifecycle:
  
* For the specification of the expected behaviour of a system and production of validation material
+
* For the '''specification''' of the expected behaviour of a system and production of validation material
 
* For the observation and recording of the actual system behaviour  
 
* For the observation and recording of the actual system behaviour  
  
 
The following sections present the language semantics and syntax, and the use of MSC within TASTE.
 
The following sections present the language semantics and syntax, and the use of MSC within TASTE.
 +
 +
= Basic MSC Concepts =
 +
 +
Basic MSC represent scenarios of operation that exhibit the system components and their interactions.
 +
 +
== Environment ==
 +
 +
The environment of a system is represented by a box around the diagram. The environment corresponds to any entity that can send messages to the instances that are visible in the current MSC chart.
 +
 +
== Instance ==
 +
 +
An '''instance''' in a MSC is represented by a box and a vertical line. It corresponds to a component of the system.
 +
 +
:[[File:ClipCapIt-210224-142807.PNG]]
 +
 +
In its textual form, an instance is declared like this:
 +
 +
instance Ground_Segment;
 +
...
 +
endinstance;
 +
 +
== Message ==
 +
 +
A message is a signal optionally containing parameters, and that corresponds to an asynchronous interaction between two instances.

Revision as of 13:40, 24 February 2021

Introduction

MSC stands for Message Sequence Chart and it is a standard from the ITU-T: https://www.itu.int/rec/T-REC-Z.120.

The MSC standard describes a language used to capture a system's operational scenarios in a formal way, with the support of both a textual and graphical representation.

This is an example of a basic MSC chart:

ClipCapIt-210224-141633.PNG

There are two major uses of MSC in a system development lifecycle:

  • For the specification of the expected behaviour of a system and production of validation material
  • For the observation and recording of the actual system behaviour

The following sections present the language semantics and syntax, and the use of MSC within TASTE.

Basic MSC Concepts

Basic MSC represent scenarios of operation that exhibit the system components and their interactions.

Environment

The environment of a system is represented by a box around the diagram. The environment corresponds to any entity that can send messages to the instances that are visible in the current MSC chart.

Instance

An instance in a MSC is represented by a box and a vertical line. It corresponds to a component of the system.

ClipCapIt-210224-142807.PNG

In its textual form, an instance is declared like this:

instance Ground_Segment;
...
endinstance;

Message

A message is a signal optionally containing parameters, and that corresponds to an asynchronous interaction between two instances.