Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Extending UsiXML to support User-aware Interfaces


Published on

Mobile and portable devices require the definition of new user interfaces (UI) capable of reducing the level of attention required by users to operate the applications they run to improve the calmness of them. To carry out this task, the next generation of UIs should be able to capture information from the context and act accordingly. This work defines an extension to the UsiXML methodology that specifies how the information on the user is modeled and used to customize the UI. The extension is defined vertically through the methodology, affecting all layers of the methodology. In the Tasks & Concepts layer, we define the user environment of the application, where roles and individuals are characterized to represent different user situations. In the Abstract UI layer, we relate groups of these individuals to abstract interaction objects. Thus, user situations are linked to the abstract model of the UI. In the Concrete UI layer, we specify how the information on the user is acquired and how it is related to the concrete components of the UI. This work also presents how to apply the proposed extensions to a case of study. Finally, it discusses the advantages of using this approach to model user-aware applications.

Published in: Technology, Education
  • Be the first to comment

Extending UsiXML to support User-aware Interfaces

  1. 1. Extending UsiXML to support User-aware Interfaces<br />Ricardo Tesoriero12<br /><br />Jean Vanderdonckt1<br /><br />1 Universitécatholique de Louvain<br />2 University of Castilla-La Mancha<br />
  2. 2. Agenda<br />Introduction<br />Scope<br />The UsiXML framework<br />The UsiXML extensions<br />The Study Case: Healthy Menu<br />Conclusions & future work<br />
  3. 3. Introduction<br />Ubiquitous computing is everywhere…<br />Many computers are shared by each of us<br />Information overload<br />Calm Technology [1]<br />Context-aware UIs<br />Multi-modal UIs<br />At home<br />At work<br />Public spaces<br />Personal devices<br />Ticket machines<br />Digital blackboards<br />Navigators<br />[1] M. Weiser and J. S. Brown. The coming age of calm technology. The next fifty years of computing, pp. 75-85. Copernicus. 1997.<br />
  4. 4. Scope: User-aware UIs<br />The context is any information that can be used to characterize the situation of an entity (person, place or object) that is considered relevant to the interaction between a user and an application [2].<br />Feature space for context [3]<br />Focus on<br />Partially boarded<br />From user perspective<br />[2] A. Dey. Understanding and using context. Personal and Ubiquitous computing, 5, pp. 4-7. 2001<br />[3] A. Schmidt, M. Beigl, H. W. Gellersen. There is more to context than location. Computer & Graphics, 23(6), pp. 893-901. 1999<br />
  5. 5. The UsiXML Framework<br />Defines a development process based on the Cameleon Reference Framework [4] to build multi-device interactive applications.<br />MDA toaddresstheproblem<br />fromdifferentperspectives.<br />Context of Use<br />Tasks & Concepts<br />CIM (TaskModel and DomainModel)<br />Abstract UI<br />TransformationModel<br />PIM (AbstractUserInterfaceModel)<br />Mapping Model<br />Concrete UI<br />PSM (ConcreteUserInterfaceModel)<br />Concretization<br />ISM (SourceCode)<br />Final UI<br />Abstraction<br />[4] G. Calvary, J. Coutaz, D. Thevenin, Q. Limbourg, L. Bouillon, J. Vanderdonckt. A unifying reference framework for multi-target user interfaces. Interacting with Computers, 15(3), pp. 289-308. 2003<br />
  6. 6. The ContextModel (context of use)<br />Fixeddescription of theUserCharacteristics / Capabilities<br />i.e.<br />systemExperience<br />deviceExperience<br />browserCapablities<br />hardwarePlatform<br />softwarePlatform<br />etc.<br />
  7. 7. The UsiXML extension<br />Characterizeusercapabilitiesaccordingtotheapplicationdomainorcapabilities<br />Express differentuser «situations» in terms of thesecharacteristics<br />Extensions<br />Modifications<br />
  8. 8. The Task & Concepts LayerUserModel & TaskModel extensions<br />Task-Individual Relationship<br />User Feature level: defines the features of the user that affect the UI in terms of Roles and Features (i.e. Patient[R].temperature[F])<br />RoleSpecialization (common characteristics)<br />User Profile level: characterizes the features according to runtime situations in terms of Individuals and Feature Constraints (i.e. PatientWithFever[I].temperature[F] > 38.5[FCo])<br />RoleCharacterization (i.e. Patient[R]<->PatientWithFever)<br />Note: R=Role, I=Individual, F=Feature <br />and Fco=Feature Constraint<br />TaskModel extension<br />Allowed<br />Not allowed<br />Feature level<br />Profile level<br />
  9. 9. The AUI extension<br />ContainerObserves “enables / disables, show/hides” AbstarctContainer<br />FacetObserves “enables / disables” a Facet of an AbstarctInteractionComponent modifying its behavior.<br />MappingModel<br />facet<br />Extension to the MappingModel<br />UserModel<br />
  10. 10. The CUI extension<br />CUI extension<br />Sensors & Interpreters (Polling and Event-driven)<br />Mapping extension<br />Interpreter Updates (Interpreter -> Feature)<br />MappingModel<br />UserModel<br />CUI Extension<br />Extension to MappingModel<br />
  11. 11. The transformation process and the FUI<br />AUI<br />CUI<br />ObserversIndivoduals<br />from Mapping<br />Observed by<br />Interpreters from CUI<br />Updates<br />UpdatesIndividual<br />from Mapping<br />Individuals from T&C<br />Sensors from CUI<br />
  12. 12. The study case The Healthy Menu<br />The goal of the application is the presentation of dishes according to the role and the biophysical state of the user.<br />The User Model<br />
  13. 13. Task model and AUI<br />*<br />
  14. 14. The Healthy MenuMapping model<br />AUI mappings<br />Containers<br />Oc(aPatient, PatientMenu)<br />Oc(aNurse, NurseMenu)<br />Oc(aDoctor, DoctorMenu)<br />Oc(aVisitor, VisitorMenu)<br />Facets<br />Of (anUser, nAccept) Of (anUser, oIdNumber)<br />Of (anUser, cAccept) Of (anUser, oDesease)<br />Of (anUser, nReject)<br />Of (anUser, cReject)<br />Of (aPatientWithHipoGlycemia, oDrink) Of (aPatientWithFever, iDrink)<br />Of (aPatientWithHipoGlycemia, oMeal) Of (aPatientWithFever, oMeal)<br />Of (aPatientWithHipoGlycemia, oDessert) Of (aPatientWithFever, iDessert)<br />Of (aPatientWithHyperGlycemia, oDrink) Of (aNormalPatient, iDrink)<br />Of (aPatientWithHyperGlycemia, oMeal) Of (aNormalPatient, iMeal)<br />Of (aPatientWithHyperGlycemia, oDessert) Of (aNormalPatient, iDessert)<br />
  15. 15. CUI – FUI (Normal Patient)<br />Temp. Sensor<br />Gluc. Sensor<br />interpreter<br />interpreter<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />
  16. 16. CUI – FUI (Patient With Fever)<br />Temp. Sensor<br />interpreter<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />Wineisout!<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />Green Salad Only!<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />
  17. 17. CUI – FUI (Patient With Hipo/Hyper glucemy)<br />Gluc. Sensor<br />interpreter<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />StrictDiet!<br />isRefinedBy/isAbstarctedInto<br />isRefinedBy/isAbstarctedInto<br />
  18. 18. Conclusions<br />This work exposes a model-based approach to develop user-aware multi-platform and multi-modal UIs following the UsiXML framework<br />This approach encourages the separation of the user modeling from the application domain to improve the model reuse<br />It covers from the conceptual modeling of the user environment to the specification of the sensing infrastructure<br />The user modeling is divided in two levels of abstraction<br />The specification of User Features (Roles)<br />The quantification of User Features (Individuals)<br />Providing designers the ability to define custom features of user profiles / Roles<br />
  19. 19. Future Work<br />The definition of an extension of the user awareness to model the social awareness of UIs<br />The inclusion of the location awareness as part of the UI specification<br />The definition of a common feature-based framework allowing designers to express characteristics that are related to the combination of the social and location features of context-aware UIs, such as the co-location of users<br />
  20. 20. Thankyouverymuchforyourattenttion!<br />Questions, Suggestions, Critics and Comments are always welcomed!<br />Ricardo Tesoriero12<br /><br />Jean Vanderdonckt1<br /><br />1 Universitécatholique de Louvain<br />2 University of Castilla-La Mancha<br />This work was founded by:<br />