FP7 Serenoa (ICT Call 5)Multi-Dimensional Context-Aware Adaptation of Service Front-ends

www.serenoa-fp7.eu

On behalf of Serenoa projectJean Vanderdonckt

Université catholique de Louvainjean.vanderdonckt@uclouvain.be

http://www.slideshare.net/jeanvdd/multidimensional-contextaware-adaptation-of-service-frontends

Overview• Serenoa is aimed at developing a novel, open platform for

enabling the creation of context sensitive service front-ends (SFEs)

• Context-sensitive SFE provides a user interface (UI) that– exhibits some capability to be aware of the context

• User• Platform• Environment

– and to react to changes of this context in a continuous way

• Goal: improving people’s satisfaction and performance compared to traditional SFEs based on manually designed UIs

Technology Domain

Computational Framework Domain

CADS CARF CARFO – OWLDesign Refer.Space Frame.

Adaptation Engine

Runtime UI Generation

Adaptation Engine

Context of Use Management

Methodology

Authoring Tool

Enabling Technologies

Task & Domain

Context + Reference Models (UML)

Advanced Adaptation Algorithms

Abstract UI

Concrete UI

Final UI

Final User Interface (FUI)

WindowWindow

Concrete User Interface (CUI)

AIUTrigger

Abstract Interact.Unit (group)

Abstract User Interface (AUI)

textInputtextInput buttonbutton buttonbutton

AIUDataInputOutput

AIUTrigger

Task & Domain (T&D)

Example: the Google Home PageAccording to the Cameleon Ref. Framework

Cameleon Reference Framework

Final User Interface (FUI)

Concrete User Interface (CUI)

Abstract User Interface (AUI)

Task & Domain (T&D)

Reification: from high- to lower-level T&D → AUI AUI → CUI: e.g., a GUI, a vocal UI CUI → FUI: e.g., HTML, VB for GUI

VoiceXML, X+V for Vocal UI

Abstraction: from low- to higher-level FUI → CUI: e.g., reverse HTML CUI → AUI: e.g. for changing modality AUI → T&D: e.g., for recovering task

Reflexion: at the same level FUI: e.g. transcoding CUI: e.g., graceful degradation AUI: e.g., restructuring T&D: e.g., for retasking

Standardization action with W3C• Step 1: W3C Incubator Group on Model-

Based User Interface Design– The Cameleon Reference Framework is a

reference for expressing the levels of abstraction during user interface development

– Recommended in the final report athttp://www.w3.org/2005/Incubator/model-based-ui/XGR-mbui-20100504/ (July 2010)

Standardization action with W3C• Step 2: Serenoa partners join their effort – IDEAL2 (CTIC):

http://files.morfeo-project.org/mymobileweb/public/specs/ideal2/

– Maria (ISTI): http://giove.isti.cnr.it/tools/MARIA/home

– UsiXML (UCL): www.usixml.eu, www.usixml.org

Standardization action with W3C• Step 3: W3C Charter Group on Model-Based User

Interface Design (http://www.w3.org/wiki/Model-Based_User_Interfaces)– Also see http://www.w3.org/2011/mbui/– Started Feb. 2012, end in Nov. 2013– Lead by Dave Raggett <dsr@w3.org>

• Contents– Introduction to MBUI– Glossary of MBUI terms– Task meta-model– Abstract user interface meta-model

Task meta-model

Abstract UI meta-model(work in progress)

Next steps• Finalizing the meta-models and interchange

formats– UML2.0 Class Diagram and OWL2 Full ontology– XML Schema

• Coverage of use cases• Software implementation compliant with the

W3C MBUI format• Quill – A Collaborative model-based UI editor

using WebSockets– http://www.w3.org/2012/quill/

Thank you very much!• Some links– http://www.w3.org/2011/01/mbui-wg-charter– http

://www.w3.org/wiki/Model-Based_User_Interfaces

– http://www.w3.org/2012/quill/– www.serenoa-fp7.eu