Jump to content

Specification and Description Language: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Manu31415 (talk | contribs)
Related technologies: Change the link from MSC to Message Sequence Chart
Manu31415 (talk | contribs)
Related technologies: TTCN-3 added as a related technology.
Line 41: Line 41:
* MSC [[Message Sequence Chart]]. Another ITU-T related notation to describe the dynamic behavior of a system.
* MSC [[Message Sequence Chart]]. Another ITU-T related notation to describe the dynamic behavior of a system.
* [[ASN.1]] Abstract Syntax Notation One. An ISO standard to describe data types that can be used within SDL.
* [[ASN.1]] Abstract Syntax Notation One. An ISO standard to describe data types that can be used within SDL.
* [[TTCN-3]] Testing and Test Control Notation version 3. A testing language standardized by ITU-T and written by ETSI.


== See also ==
== See also ==

Revision as of 12:34, 22 August 2014

Specification and Description Language (SDL) is a specification language targeted at the unambiguous specification and description of the behaviour of reactive and distributed systems.

Overview

It is defined by the ITU-T (Recommendations Z.100 to Z.106). Originally focused on telecommunication systems, its current areas of application include process control and real-time applications in general.

The Specification and Description Language provides both a graphical Graphic Representation (SDL/GR) as well as a textual Phrase Representation (SDL/PR), which are both equivalent representations of the same underlying semantics. Models are usually shown in the graphical SDL/GR form, and SDL/PR is mainly used for exchanging models between tools. A system is specified as a set of interconnected abstract machines which are extensions of finite state machines (FSM).

The language is formally complete[citation needed], so it can be used for code generation for either simulation or final targets.

The Specification and Description Language covers five main aspects: structure, communication, behavior, data, and inheritance. The behavior of components is explained by partitioning the system into a series of hierarchies. Communication between the components takes place with through gates connected by channels. The channels are of delayed channel type, so communication is usually asynchronous, but when the delay is set to zero (that is, no delay) the communication becomes synchronous.

The first version of the language was released in 1976 using graphical syntax (SDL-76). This was revised in 1980 with some rudimentary semantics (SDL-80). The semantics were refined in 1984 (SDL-84), the textual form was introduced for machine processing and data was introduced. In 1988, SDL-88 was released with a formal basis for the language: an abstract grammar as well as a concrete grammar and a full formal definition. The version released in 1992 (SDL-92) introduced object oriented concepts such as inheritance, abstract generic types etc. with the object-oriented features described by transformations into non-object oriented ones. SDL-2010 is the latest version, an updated version of SDL-2000 that was completely based on object-orientation, rather than description by transformations. This version is accompanied by a UML-Profile: ITU-T Recommendation Z.109 (04/12), SDL-2010 combined with UML. SDL-2010 also introduced the support of C data types as initially introduced by SDL-RT.

Hierarchy level

The Hierarchy level of SDL is structured as follows.

Usually a system agent consists of a number of block agents. Block agent communicate with each other using channels. A block agent consists of process agents (the required structure in SDL-92; SDL-2000 is more flexible). Each process agent is a state machine that contributes to the action carried out by the system. A message stimulus from the environment or another agent to an agent is called a signal. Signals received by a process agent are first placed in a queue (the input port). When the state machine is waiting in a state, if the first signal in the input port is enabled for that state it starts a transition leading to another state. Transitions can output signals to other agents or to the environment. A process agent is allowed to contain procedure types so that the same actions can be invoked from different places. It is also allowed to call a remote procedure type to invoke a procedure in another agent (or even another system) and wait for a response.

SDL tools

The most well-known SDL modelling tools are Telelogic Tau, PragmaDev RTDS, Cinderella, Safire-SDL, and ObjectGeode (now out of the market). PragmaDev RTDS supports both SDL and SDL-RT which is used to develop real-time and embedded software. There are also some open source projects relative to SDL modeling like JADE which is a Java based specification environment, and OpenGEODE, a Python/Qt implementation of an SDL editor from the European Space Agency.

SDL-RT

SDL-RT is based on the ITU Specification and Description Language replacing the data language with C.[1]

  • MSC Message Sequence Chart. Another ITU-T related notation to describe the dynamic behavior of a system.
  • ASN.1 Abstract Syntax Notation One. An ISO standard to describe data types that can be used within SDL.
  • TTCN-3 Testing and Test Control Notation version 3. A testing language standardized by ITU-T and written by ETSI.

See also

References

This article is based on material taken from the Free On-line Dictionary of Computing prior to 1 November 2008 and incorporated under the "relicensing" terms of the GFDL, version 1.3 or later.

  1. ^ "Specification and Description Language – Real Time". Retrieved 2014-03-29. SDL-RT prime use is to develop real time and embedded software. SDL-RT is based on tasks running concurrently that exchange information through messages and synchronize with each other using semaphores.