You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

An Overview of RTT: A Design Framework for Real-Time Systems

Fulltext:


Authors:

Christer Norström, Jukka Mäki-Turja, Jan Gustafsson, Kristian Sandström, Ellus Brorson

Publication Type:

Journal article

Venue:

Journal of Parallel and Distributed Computing

Abstract

RealTimeTalk (RTT) is a design framework for developing distributed real-time applications with both hard and soft requirements. The framework supports design via hierarchical decomposition.We believe that object-orientation is the best way to go about structuring a problem, hence the RTT language is based on Smalltalk with an analysis frontend to infer type information for run-time safety, and to yield more precise estimations of execution times.Unlike most real-time systems, RTT does not force the designer to embed constructs for timing requirements, communication, and synchronization in the code. Rather, such information is specified on a higher level of abstraction using graphical tools. This not only keeps the code "clean" but also simplifies timing analysis and resource allocation.A comparison with other real-time systems concludes the paper.

Bibtex

@article{Norstrom60,
author = {Christer Norstr{\"o}m and Jukka M{\"a}ki-Turja and Jan Gustafsson and Kristian Sandstr{\"o}m and Ellus Brorson},
title = {An Overview of RTT: A Design Framework for Real-Time Systems},
month = {August},
year = {1996},
journal = {Journal of Parallel and Distributed Computing},
url = {http://www.es.mdu.se/publications/60-}
}