ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Specification and Description Language (SDL) Diagrams

Updated on October 20, 2015
Figure 1. Complete overview of a system and it 4 layers
Figure 1. Complete overview of a system and it 4 layers | Source
Figure 2. Using  Specification and Description Language   to take a closer look at finite state machines, with textual information to facilitate understanding
Figure 2. Using Specification and Description Language to take a closer look at finite state machines, with textual information to facilitate understanding | Source
Figure 3. A set of concurrent processes, described using Specification and Description Language
Figure 3. A set of concurrent processes, described using Specification and Description Language | Source

Specification and Description Language (SDL) was initially devised in the early 1970s with a specific task in mind — to describe systems that switched state rapidly and often. The need for this language was in direct retaliation to the types of system that were rising to prominence during this time, namely telecommunication systems that had become highly complex, with heavy traffic loads and real time demands. This exposed the more rigid programming languages and hardware description languages, that were unable to represent switching systems that required standardization on an international scale.

As telecommunication systems developed, so did SDL, moving from focusing solely on sequential behavior to later adding notation for architectural composition, and finally introducing concepts such as types and inheritance. By this time, SDL was a full-time object oriented language, able to be used when modeling a system graphically (SDL/GR) or textually (SDL/PR).

The basic form of an SDL diagram will involve some or all of the following components:

  • Structure — the hierarchy of the system, its blocks, processes and procedures.
  • Communication — signals with optional parameters and channels.
  • Behavior — processes.
  • Data — abstract data types.
  • Inheritance — describing relations and specialization.

Different systems require a different approaches to diagram composition. Here are the three main forms of SDL diagram, and a brief description of their intent:

System architecture/structure

SDL uses a hierarchical structure comprised of 4 levels.

  • System
  • Blocks
  • Processes
  • Procedures

Every SDL diagram is taken as a view of system, be it a simple, single process, or more complex behavior derived from the relationship between a number of blocks. The hierarchy is nested; a system can be decomposed into blocks, each block can be describes as a process, until finally you can see the procedures that make up each process.

The advantages of this style are that a system can seen at any level — information can be shown or hidden, viewed in manageable portions, and paths can be followed individually through all their sub-divisions.

Behavior

When we are describing system behavior using an SDL diagram, we are regarding blocks as finite state machines (FSM). An FSM is ideal form of component for such a diagram, as it is capable of taking on multiple forms, dependent on the type of signal input.

The states an FSM can switch to are clearly and unambiguously shown by the process diagram that is inherent within it. This process diagram describes every input and output of an FSM, the states they change to and from, and the actions they perform depending on which state transition takes place.

Communication

There is rarely direct human contact with a system interface as described by SDL. Transistions and interactions within the system, and with the environment, are governed by signals, which already have a pre-determined cause and effect.

This keeps the blocks, or FSMs, in their finite state and as separate entities to each other — it is not possible for a signal to fundamentally disrupt or change the process within an FSM, only challenge it to make a state transition.

SDL diagrams are ideal candidates for reactive and distributive systems for a number of reasons:

  • Formal and standard language, established internationally and through many fields of industry
  • Highly testable due to formalism of structure and interface
  • Graphical and symbol based, allowing for full interpretation of detail
  • Portable, scalable and open, acting independently of operating systems, processors and distribution methods.
  • Recyclable, able to apply the same processes to many different scenarios

Specification and Description Language began life a tool for telecommunication software engineers, and it remains highly tried in that field today. Indeed, Nokia have developed their own variant named TNSDL to be used exclusively with their systems. At the same time, the user base has widened, and you can find examples of their use in automotive, aviation, and medical industries.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)