In the development of application software for networked embedded systems a significant step to improve interoperability and reuse consisted in relying on a service layer providing an abstract interface through a well-defined programming paradigm (e.g., object-oriented, tuplespace or database). During application development this layer can provide a simulation model of the actual platform while during implementation it can be mapped onto an actual middleware. During application development the choice of the programming paradigm is driven by productivity while during deployment the choice of the middleware is driven by efficiency and availability. Keeping the same programming paradigm in these two phases limits design-space exploration while changing paradigm requires to re-write the application. In this work we describe 1) a SystemC-based service layer providing different paradigms, i.e., object-oriented and tuple space, 2) design reasons for translating the application between these paradigms, and 3) a methodology for this translation.

AME: an Abstract Middleware Environment for Validating Networked Embedded Systems Applications / F., Fummi; G., Perbellini; Quaglia, Davide; Vinco, Sara. - (2007), pp. 187-194. (Intervento presentato al convegno IEEE High-Level Design and Test Workshop (HLDVT) tenutosi a Irvine, CA, USA nel Nov. 7-9) [10.1109/HLDVT.2007.4392812].

AME: an Abstract Middleware Environment for Validating Networked Embedded Systems Applications

QUAGLIA, Davide;VINCO, SARA
2007

Abstract

In the development of application software for networked embedded systems a significant step to improve interoperability and reuse consisted in relying on a service layer providing an abstract interface through a well-defined programming paradigm (e.g., object-oriented, tuplespace or database). During application development this layer can provide a simulation model of the actual platform while during implementation it can be mapped onto an actual middleware. During application development the choice of the programming paradigm is driven by productivity while during deployment the choice of the middleware is driven by efficiency and availability. Keeping the same programming paradigm in these two phases limits design-space exploration while changing paradigm requires to re-write the application. In this work we describe 1) a SystemC-based service layer providing different paradigms, i.e., object-oriented and tuple space, 2) design reasons for translating the application between these paradigms, and 3) a methodology for this translation.
2007
9781424414802
File in questo prodotto:
Non ci sono file associati a questo prodotto.
Pubblicazioni consigliate

I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.

Utilizza questo identificativo per citare o creare un link a questo documento: https://hdl.handle.net/11583/2529488
 Attenzione

Attenzione! I dati visualizzati non sono stati sottoposti a validazione da parte dell'ateneo