Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Systematic Generation of Abstract User Interfaces

An abstract user interface is defined according the Came¬leon Reference Framework as a user interface supporting an interactive task abstracted from its implementation, independently of any target computing platform and interaction modality. While an abstract user interface could be specified in isolation, it could also be produced from various models such as a task model, a domain model, or a combination of both, possibly based on information describing the context of use (i.e., the user, the platform, and the environment). This paper presents a general-purpose algorithm that systematically generates all potential abstract user interfaces from a task model as candidates that could then be refined in two ways: removing irrelevant candi-dates based on constraints imposed by the temporal operators and grouping or ungrouping candidates according to constraints imposed by the context of use. A model-driven engineering environment has been developed that applies this general-purpose algorithm with multiple levels of refinement ranging from no contextual consideration to full-context consideration. This algorithm is exemplified on a some sample interactive application to be executed in various contexts of use, such as different categories of users using different platforms for the same task.

  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Systematic Generation of Abstract User Interfaces

  1. 1. 27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 1
  2. 2. • Motivations and related works • AUI generation workflow and its principal components • Conclusion • Demo27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 2
  3. 3. • Today, there exists many ways for generating an Abstract UI (AUI) from different sources such as: • Task model • Domain model (more than a mere data model) • Context model • Consequences • Heterogeneity of techniques • No coverage of all possible AUIs at once27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 3
  4. 4. IKnowU: expert system for deciding AUIs based on rules27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 4
  5. 5. Generating AUIs based on discourse model27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 5
  6. 6. ROAM: Generating AUIs based on task model27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 6
  7. 7. Dygimes: Generating AUIs based on task model27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 7
  8. 8. • Generating the abstract user interfaces for multiple platforms based on: • Task model • and domain model.26/06/2012 8
  9. 9. Principal components27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 9
  10. 10. AUI generation workflow27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 10
  11. 11. Task and domain models Contacts task model Contacts domain model27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 11
  12. 12. AUI generation workflow • Link tasks to domain’s components27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 12
  13. 13. AUI generation workflow • Link tasks to domain’s components An example of linking tasks to domain components27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 13
  14. 14. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 14
  15. 15. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks Tasks in Contact task model are assigned weights based on the task types27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 15
  16. 16. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks • Create task groups27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 16
  17. 17. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks • Create task groups An example of task grouping An example of operator check27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 17
  18. 18. AUI generation workflow• Link tasks to domain’s components• Assign weights for the tasks• Create task groups• Assign weights for the platforms27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 18
  19. 19. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks • Create task groups • Assign weights for the platforms • Generate configurations27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 19
  20. 20. AUI generation workflow • Link tasks to domain’s components • Assign weights for the tasks • Create task groups • Assign weights for the platforms • Generate configurations The configuration is generated for Palm platform27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 20
  21. 21. AUI generation workflow• Link tasks to domain’s components• Assign weights for the tasks• Create task groups• Assign weights for the platforms• Generate configurations• Generate abstract user interface27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 21
  22. 22. AUI generation workflow• Link tasks to domain’s components Rule1: An AbstractSelectionUI is considered when a task derives from an attribute of a domain class which is not the edited class and the relationships between the edited class and another one is ‘1-1’ or• ‘n-1’and . weights for the tasks Assign• Create task groups Rule2: An AbstractInputUI is considered when a task derives from the attributes of the classes that these classes are the edited classes.• Assign weights for the platforms• Rule3: An AbstractOutputUI is considered whenabstract useruser interaction has been created and its Generate name of the task related to this an abstract interaction. label is the task configurations• Rule4: An AbstractDataItemUI is considered when a task derives from the attributes of the classes. Generate abstract user interface Rule5: An AbstractTriggerUI is considered when a task derives from an operation of a class. For example. Once the tasks have been grouped by the developer based on the screen size of devices, the AUIs are generated automatically by system.27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 22
  23. 23. AUI generation workflow• Link tasks to domain’s components• Assign weights for the tasks• Create task groups• Assign weights for the platforms• Generate configurations• Generate abstract user interface AUI is generated from configuration specified above27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 23
  24. 24. AUI generation workflow• Link tasks to domain’s components• Assign weights for the tasks• Create task groups• Assign weights for the platforms• Generate configurations• Generate abstract user interface• Store generated AUIs into a xml file in terms of UsiXML specification27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 24
  25. 25. • Providing a general process for systematically generating abstract user interfaces from the task and the domain models is necessary, but not sufficient • Providing a palette algorithms for specifying abstract user interface types and configurating these abstract user interfaces is definitely a plus • Implementing a software that supports this process is important for maximal usage • Import/export facilities need to be elaborated (for the moment, only UsiXML is supported)27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 25
  26. 26. Demonstration: https://www.youtube.com/watch?v=KoY6KxkVzAU&feature=g-upl27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 26
  27. 27. Thank you very much for your attention! Any question? See more at: www.usixml.org, www.usixml.eu www.lilab.eu, www.lilab.be27/06/2012 EICS2012 (Copenhagen, Denmark, June 25-28, 2012) 27

×