Abstract

The aim of Component-Based Software Engineering is to create application from reusable, exchangeable and connectable components. But current component models lack support for important concepts of distributed embedded real-time systems. In this field a component's non-functional properties, e.g. execution time and resource usage, are as important as its functionality. In addition the non-functional properties are influenced by the platform on which the component is executed.

Therefore we propose a component model that separates the component's functionality from the platform-specific issues concurrency, synchronization, and distribution. We present a technique to describe the behavior of a component that is based on Use Case Maps (UCMs) and show how to deduce from these descriptions the behavior of an application that consists of connected components. In our model the UCMs also contain information on real-time requirements of the application.

Moreover we show how to adapt our components to an execution platform and how to create real-time applications with predictable properties from these components.

-- Daniel Amyot - 11 Aug 2006

Discussion

• Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

• A journal version of that paper appeared here