SDL Modules – Concepts and Tool Support

  • Philipp Becker
  • Marc Krämer
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6598)

Abstract

SDL, ITU’s Specification and Description Language, supports developing systems in a modular and hierarchical way, based on structural type definitions and their instantiations. Also, reuse is supported by the possibility to define collections of type definitions, e.g., as SDL packages, that can be used in different systems. Another important development task that can be supported by packages is the replacement of system parts, i.e., structural instances. This can be achieved, for instance, by replacing the type definition to which an instantiation refers by using another package containing a compatible type. However, we have found that this apparently elegant solution reveals some intricacies in practice. To fully exploit the benefits of packages for the development of complex systems and system versioning, type definitions are typically collected in a considerable number of packages. Moreover, there usually are numerous dependencies among packages, which make their management an error-prone task. Finally, it is not clear which types are compatible such that they can be used as mutual replacements. In this paper, we propose a clean solution for the replacement of system parts. Therefore, we introduce a concept that we call SDL module, which we use to capture compatibility of structural type definitions and replacement rules. We illustrate the applicability of our approach by presenting an in-house development tool to automate the replacement process. This tool can be utilized to speed up the development process, and adapt SDL systems to different platforms and scenarios.

Keywords

SDL MDD Modules Components Interfaces Packages Tool Support 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    International Telecommunication Union: Recommendation Z.100, Specification and Description Language (SDL) (November 2007), http://www.itu.int/rec/T-REC-Z.100/en
  2. 2.
    Ellsberger, J., Hogrefe, D., Sarma, A.: SDL– Formal Object-oriented Language for Communication Systems. Prentice-Hall, Englewood Cliffs (1997)Google Scholar
  3. 3.
    IBM: Rational SDL Suite (2011), http://www-01.ibm.com/software/awdtools/sdlsuite
  4. 4.
    Fliege, I., Geraldy, A., Gotzhein, R., Schaible, P.: A Flexible Micro Protocol Framework. In: Amyot, D., Williams, A.W. (eds.) SAM 2004. LNCS, vol. 3319, pp. 224–236. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  5. 5.
    Oracle Corporation: Java (2011), http://java.sun.com
  6. 6.
    Apache Software Foundation: Maven (2011 ), http://maven.apache.org/
  7. 7.
    Free Software Foundation, Inc.: GNU Make (2011), http://www.gnu.org/software/make/
  8. 8.
    Networked Systems Group: SPaSs Tool Home Page (2011), http://vs.cs.uni-kl.de/activities/spass/
  9. 9.
    International Telecommunication Union: Recommendation Z.106: Common Interchange Format for SDL (August 2002), http://www.itu.int/rec/T-REC-Z.106/en
  10. 10.
    Fliege, I., Grammes, R., Weber, C.: ConTraST - A Configurable SDL Transpiler and Runtime Environment. In: Gotzhein, R., Reed, R. (eds.) SAM 2006. LNCS, vol. 4320, pp. 216–228. Springer, Heidelberg (2006); Revised Selected PapersCrossRefGoogle Scholar
  11. 11.
    Apache Software Foundation: Subversion (2011), http://subversion.apache.org/

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Philipp Becker
    • 1
  • Marc Krämer
    • 1
  1. 1.Networked Systems GroupUniversity of KaiserslauternGermany

Personalised recommendations