Prediction of run-time resource consumption in multi-task component-based software systems

J. Muskens, M.R.V. Chaudron

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

10 Citations (Scopus)


Embedded systems must be cost-effective. This imposesstrict requirements on the resource consumption of their applications. It is therefore desirable to be able to determine the resource consumption of applications as early as possible in its development. Only then, a designer is able to guarantee that an application will fit on a target device. In this paper we will present a method for predicting run-time resource resource consumption in multi-task component based systems based on a design of an application. In [5] we describe a scenario based resource prediction technique and show that it can be applied to non-pre-emptive non-processing resources, like memory. In this paper we extend this technique, which enables us to handle pre-emptive processing resources and their scheduling policies. Examples of these class of resources are CPU and network. For component based software engineering the challenge is to express resource consumption characteristics per component, and to combine them to do predictions over compositions of components. To this end, we propose a model and tools, for combining individual resource estimations of components. These composed resource estimations are then used in scenarios (which model run-time behavior) to predict resource consumption.
Original languageEnglish
Title of host publicationComponent-Based Software Engineering (Proceedings 7th International Symposium, CBSE 2004, Edinburgh, UK, May 24-25, 2004)
EditorsI. Crnkovic, J.A. Stafford, H.W. Schmidt, K.C. Wallnau
Place of PublicationBerlin
ISBN (Print)3-540-21998-6
Publication statusPublished - 2004

Publication series

NameLecture Notes in Computer Science
ISSN (Print)0302-9743


Dive into the research topics of 'Prediction of run-time resource consumption in multi-task component-based software systems'. Together they form a unique fingerprint.

Cite this