A Middleware Architecture for Human-Centred Pervasive Adaptive Applications

Abstract

As software is more and more interweaving with our everyday life, designing software in a way that it reflects and respects the user and her emotional physical conditions, cognitive engagement, and emotional state, become imperative. However, how such humancentred pervasive adaptive applications are to be designed and realized is still hardly understood. Both engineering approaches and runtime support for such applications are still in their infancy. In this paper, we present the REFLECTive middleware, a framework that facilitates the development and operation of such applications. The middleware is explained on the base of an envisioned example, the affective music player. By offering design patterns geared towards pervasive adaptive applications and leveraging them for achieving adaptivity, the REFLECTive middleware support a systematic and clear approach to engineering and deploying human-centred pervasive adaptive applications in daily life situations.

Directing Physiology and Mood through Music: Validation of an Affective Music Player

“…There is no best bootstrap yet, but a combination of user input and music features to predict the mood that a song will induce would probably be most accepted by a user. Such an AMP is currently implemented in a working carrier application (see [45]). …”

Reflective assistance for eldercare environments

“…Also it takes into account the recorded user behaviour patterns. For example, if the user mood is to be improved by music and lightening, emotional user state is directly correlated with music player control and lightening control, taking into accoint previous experiences with a concrete user [7].…”

“…The initial application domain of the reflective approach has been entertainment [7] and vehicular embedded control [8]. Recently, the application domain has been extended smart homes, medicare and ambient assisted living.…”

3pc

“…Behavior adaptation is offered by some approaches, for example, Puppeteer [De Lara et al 2001] and REFLECT [Schroeder et al 2008]. Context adaptation is so far only supported by few systems, such as, REFLECT [Schroeder et al 2008] and Vainio et al [2008].…”

“…As an example, iROS [Johanson et al 2002] assembles loosely coupled applications from components at runtime using an asynchronous EventHeap. REFLECT [Schroeder et al 2008] builds applications from software components. By specifying provide and demand ports for each component, the middleware can construct applications dynamically.…”