Workshop: Integration of Asterics, MyUI and URC for adaptive User Interfaces in Smart Environments
Place and time
|Location:||Hochschule der Medien (Stuttgart - Media University)
Nobelstraße 5, d-70569 Stuttgart https://goo.gl/maps/LbjnR
|Date:||Feb. 10th 2015; 10:00-17:00 CET|
|Hosts:||Gottfried Zimmermann, Lukas Smirek|
|related to:||Prosperity4All, T. 203.3|
- Invite to regular telecons on every other Tue at 3pm CET.
- Finish the REST interface for ARE (UCY)
- Direct communication from ARE to UCH based on OSGi component (UCY)
- Event emission from ARE to any web application (HTML interface)
- Extend ACS to define mappings of user actions to thermostat socket elements - define an OSGi bundle for the thermostat socket (KII)
- Future (and more complex): Implement an OSGi bundle generator for any given user interface socket (KII)
- Implement MyUI runtime based on web components and glue code for UCH (FHG)
- Converter for converting a Socket Description to Interaction Situations (FHG+HDM)
- Find thermostat that is widely available on the European market
- Release device template for thermostat (HDM)
- Define resource properties to mark up alternative user interface components on the resource server (HDM)
- Let students implement alternative user interfaces for thermostat, some of them with ARE (HDM)
- Validation of the development process involved.
- Video tutorial for a thermostat UI?
- Smart-Home group meeting on every other Tuesday at 3pm CET. Lead: UCY.
- Invitations to email@example.com. Everybody should make sure that they are subscribed to this list, see http://lists.gpii.net/cgi-bin/mailman/listinfo/smarthouses.
Description of figure
At runtime, the following components are used:
- A wall-mounted thermostat with a small display and buttons. This is inaccessible for many persons.
- The UCH communicating with the thermostat through a proprietary interface. Inside the UCH a UI socket represents the state of the thermostat.
- An HTML interface (GUI) running in a web browser on a mobile device. In the HTML interface, glue code communicates with a UI socket running on the UCH.
- The Asterics Runtime Environment (ARE). It communicates with the HTML interface (GUI) via Events, but can also directly communicate with the socket in the UCH via REST.
At development time, several components support the runtime components:
- The URC socket builder generates a Socket Description to be used by the UCH.
- The MyUI Interaction Modeller, generating a self-adapting HTML Interface (GUI) that will run in a web browser.
- A converter could convert a Socket Description (generated by the URC Socket Builder) into Interaction Situations to be consumed by the MyUI Interaction Modeller.
- The Asterics Configuration Suite (ACS) defining an Asterics model (& mapping) to be used by the ARE.
|10:30-11:00|| Introduction to Asterics (UCY):
|11:00-11:30|| Introduction to MyUI (Fraunhofer):
|11:30-12:00|| Introduction to URC (HDM):
Connection between ARE and HTML Interface:
Alternative communications (see sketch):
Still required (based on Linz meeting):
Direct link between ACS and UCH:
Steps of interaction at runtime:
|16:00-17:00|| Further Planning:
T203.3 Runtime Environment (Leader: UCY, Duration: M6-M30)
The Prosperity4All runtime environment will include three major modules to accessible user interfaces:
- Support of diverse AT (represented by AsTeRICS).
- Universal Remote Console (URC) to access a variety of products and services via a personal interaction device (represented by URC).
- Run-time adaptations to cover temporal changes of user needs (e.g. during one day, or in the course of ageing or rehabilitation) and to overcome barriers of use directly when they occur (represented by MyUI).
For this purpose, adaptations of the three existing runtime environments will be required together with enhancements of multi-platform support:
- (a) Adaptation and integration of the AsTeRICS Runtime Environment (UCY) This activity will adapt the AsTeRICS Runtime Environment (ARE) specification and design in order to support major platforms (e.g. Windows, Mac, Linux) and adhere to the notion of accessibility for all. It will be implemented and integrated into the overall architecture and will aim principally to complemend the functionality of the model-driven programming environment. The runtime environment is responsible for hosting the models designed using the model-driven environment, which can be automatically deployed and executed through the dynamic composition of software modules on the runtime toolkit. This will allow serving the dynamic deployment of diverse Prosperity4All modules (e.g. sensors) on different platforms, forming part of the overall infrastructure that intends to support modular development of deployable AT applications. The Java OSGi framework serves as the technology for implementing the runtime toolkit on major platforms, since it defines a set of principles for designing and developing software in the form of interoperable software modules/plug-ins. The runtime environment design and implementation process will be hugely assisted by building on the architecture design knowledge of the ARE and exploiting the implementation for porting to other platforms. The development activities include: · Adapting the AsTeRICS Runtime Environment to major platforms · Integration of Prosperity4All modules for data and event exchange with other components and user interfaces
- (b) Adaptation and integration of the URC runtime environment (HDM) This activity will integrate the URC runtime environment with the context-driven approach of MyUI and the AT environment provided by Asterics. We will adapt the current URC runtime libraries (based on the URC socket approach) to interface and collaborate with the MyUI and Asterics interfaces at runtime. (
- c) Adaptation and integration of the MyUI Runtime Environment (FHG) This activity will adapt the MyUI Runtime environment to work with AT as plugged and configured by AsTerRICS and with the Prospoerity4All Intelligence modules which detect the current context. For this purpose specific interfaces will be developed to capture information about current AT I/O devices, user needs and environmental factors. This information will be interpreted and processed by the MyUI runtime environment to generate and adapt accessible user interfaces. Finally, the MyUI runtime environment will be adapted to benefit from new HTML 5 capabilities.