Real-time component integration based on transparent distribution

ABSTRACT

This paper introduces a real-time component model that offers a separation of concerns which allows a straight-forward integration of independently developed components. So-called transparent distribution forms the backbone of the integration process. Transparent distribution means that (1) the functional and temporal behavior of a system is the same no matter on which node of a distributed system a component is executed and (2) the developer does not have to care about the differences of local versus distributed execution of a component. We first present the concepts of a component model for real time systems that is well suited for transparent distribution. The component model is based on logical execution time, which abstracts from physical execution time and thereby from both the execution platform and the communication topology. Then we discuss the resulting tool chain and integration process. A case study rounds out the paper.

REFERENCES

• 1: Bosch, 1991, CAN Specification, Version 2. Robert Bosch GmbH, http://www.can.bosch.com/docu/can2spec.pdf
• 2: Christoph Meyer Kirsch, Principles of Real-Time Programming, Proceedings of the Second International Conference on Embedded Software, p.61-75, October 07-09, 2002
• 3: Emilia Coste, Claudiu Farcas, Wolfgang Pree and Josef Templ. Transparent Distribution of TDL modules. Technical Report, University of Salzburg, Austria, 2005.
• 4: Gerald Stieglbauer and Wolfgang Pree. Visual and Interactive Development of Hard Real Time Code. Automotive Software Workshop San Diego (ASWSD 2004)
• 5: Giotto Project, http://www-cad.eecs.berkeley.edu/~fresco/giotto/
• 6: Hermann Kopetz, Real-Time Systems: Design Principles for Distributed Embedded Applications, Kluwer Academic Publishers, Norwell, MA, 1997
• 7: J. Templ, 2004, TDL Specification and Report. Technical Report C059, Department of Computer Science, University of Salzburg, http://www.cs.uni-salzburg.at/pubs/reports/T001.pdf
• 8: OAK_EMUF Dev. Board, Ing. Buero W. Kanis GmbH http://www.kanis.de/home/products/oak_emuf/i_oak.htm
• 9: OSEK Group, 2001, OSEK/VDX Time-triggered Operating System Specification, Version 1.0, http://www.osek-vdx.org/mirror/ttos10.pdf
• 10: T. A. Henzinger, C. M. Kirsch, and S. Matic. Schedule carrying code. In Proc. of the Third International Conference on Embedded Software (EMSOFT), LNCS, Springer-Verlag, 2003.
• 11: Thomas A. Henzinger , Christoph M. Kirsch, The embedded machine: predictable, portable real-time code, Proceedings of the ACM SIGPLAN 2002 Conference on Programming language design and implementation, June 17-19, 2002, Berlin, Germany
• 12: Thomas A. Henzinger , Benjamin Horowitz , Christoph Meyer Kirsch, Giotto: A Time-Triggered Language for Embedded Programming, Proceedings of the First International Workshop on Embedded Software, p.166-184, October 08-10, 2001
• 13: Thomas A. Henzinger , Benjamin Horowitz , Christoph Meyer Kirsch, Embedded Control Systems Development with Giotto, Proceedings of the 2001 ACM SIGPLAN workshop on Optimization of middleware and distributed systems, p.64-72, August 2001, Snow Bird, Utah, United States
• 14: Thomas A. Henzinger, Christoph M. Kirsch, Marco A. A. Sanvido, and Wolfgang Pree. From control models to real-time code using Giotto. IEEE Control Systems Magazine 23(1):50--64, 2003.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement

Additional Classification:
  D. Software
  D.4 OPERATING SYSTEMS
      D.4.7 Organization and Design
          Subjects: Real-time systems and embedded systems

General Terms:
Design, Experimentation, Management, Measurement, Performance