A Perspective on the Future of Middleware-based Software Engineering

Issarny, Valérie; Caporuscio, Mauro; Georgantas, Nikolaos

doi:10.1109/fose.2007.2

Cited by 84 publications

(98 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thank to our multi-cycle weaving we are able to work on the system domain as well as on the environmental domain. More than situated systems now we can build decentralized context-adaptive systems that continuously adapt their behavior according to infrastructure evolution [14]. The multi-cycle approach enables us from now on to direct ourselves toward context-awareness in a similar way as described previously in section 1.…”

Section: For Context-awarenessmentioning

confidence: 99%

See 1 more Smart Citation

Context adaptative systems based on horizontal architecture for ubiquitous computing

Ferry¹,

Lavirotte²,

Tigli³

et al. 2009

Proceedings of the 6th International Conference on Mobile Technology, Application &Amp; Systems - Mobility '09

View full text Add to dashboard Cite

Many adaptative context-aware middleware exist and mostly rely on so-called vertical architectures that offer a functional decomposition for context-awareness. This architecture has a weak point: it leads to data centralization. Our mechanism for adaptation: the Aspects of Assemblies is based on a horizontal architecture. This type of architecture separate the system into behavior and is based on a decentralized approach. However, after having shown some limitations of AAs in the field of context-awareness we will introduce a way to improve them using a multi-cycle weaving approach. Then, using this approach we will be able to build contextadaptative systems that interact directly with their environment. Finally we will evaluate our approach in term of reactivity.

show abstract

Section: For Context-awarenessmentioning

confidence: 99%

“…To do such adaptations there are various approach: altering data that are processed or modifying internal processing [14]. The first is used to configure algorithms, components or strategies, the second aims to exchange algorithms, components or strategies with others.…”

Section: Adaptationmentioning

confidence: 99%

Context adaptative systems based on horizontal architecture for ubiquitous computing

Ferry¹,

Lavirotte²,

Tigli³

et al. 2009

Proceedings of the 6th International Conference on Mobile Technology, Application &Amp; Systems - Mobility '09

View full text Add to dashboard Cite

show abstract

“…This means that interoperability on the middleware level is also required. The mobility and availability of a huge number of heterogeneous resources at the same time entail further requirements such as scalability and resource-discovery (Issarny et al, 2007).…”

Section: Device Integrationmentioning

confidence: 99%

Internet of things: why we are not there yet

Sorce¹,

Gentile²

2014

IJAHUC

View full text Add to dashboard Cite

Twenty-one years past since Weiser's vision of ubiquitous computing (UbiComp) has been written, and it is yet to be fully fulfilled despite of almost all the needed technologies already available. Still, the widespread interest in UbiComp and the results in some of its fields pose a question: why we are not there yet? It seems we miss the 'octopus' head. In this paper, we will try to depict the reasons why we are not there yet, from three different points of view: interaction media, device integration and applications.

show abstract

“…While each guarantees somewhat different properties as emphasized by somewhat different usage scenarios, component-based design, model-driven architecture, and web services all can be grouped as addressing this desire in a similar manner. In fact, they can be seen as evolving from one another, with component-based design focusing on reuse of the individual component, model-driven architecture on standardization of components into reusable middleware [30,40], and web services on reuse of components and middleware across distributed and decentralized applications.…”

Section: Component-based Designmentioning

confidence: 99%