A Structured Approach to Support 3D User Interface Development

1,610 views

Published on

Given its current state of the art, Model-Based UI Development (MBDUI) is able to fulfill the major requirements of desktop and mobile applications, such as form-based user interfaces that adapt to the actual context of use. More recent research deals with the development of 3D interactive multimodal environments. Though user-centered design is more and more driving the design of these environments, less attention is devoted to the development processes than to interactive tools supporting isolated phases in the realization process. In this paper we present an attempt to structure an approach to support 3DUIs development by introducing a MBDUI compliant method. The development method is articulated on three axes: models and their specification language, approach, and tools that support the method based on the underlying models

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,610
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
48
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • So, why are virtual worlds appealing to so many people now? It is not new that nowadays the web has change from a passive static content to a dynamic interactive one. In recent years, the Web has become a more collaborative platform through the increased use of social networking and new technologies associated to the web (sometimes called Web 2.0). In that light, some efforts are towards 3D interaction, maybe 3D will not be the only way of interact in the future but for sure it will be one of the options.
  • Modifiability: If there is a change in a model then the 3DUI changes accordingly;
    Complexity: As it provides ways to address complexity, huge quantity of code, as well as the reliability;
    Safety Critical: to warranty and investigate 3DUI’s behavior, models are needed.
    The use of a formal specification technique is extremely valuable, because it provides non-ambiguous, complete and concise ways of describing the behavior of the systems;
    Rigorous: The development life cycle of the 3DUI involves the same level of rigor that is typically used in software engineering;
    Reasoning: Because from the models describing the 3DUI some reasoning is possible, such as: Automatic. Computer based system might analyze data related to the 3DUI automatically and might be able to predict pilots behavior; Production of errors; Processable. Models can be processed and studied by devoted systems; Checking properties. Analysis of the different effects produced in the 3DUI by modifying properties of the components, for instance, changing background color, fonts of labels, etc; Human readable. This is not necessarily always achieved but model are expected to be understandable for humans.
  • A Structured Approach to Support 3D User Interface Development

    1. 1. 1 February 1-7, 2009 - Cancun, Mexico ACHI’09 A structured approach to support 3D User Interface Development Juan Manuel Gonzalez-Calleros, Jean Vanderdonckt and Jaime Muñoz-Arteaga Université catholique de Louvain (UCL), Louvain School of Management (LSM) Information Systems Unit (ISYS) juan.m.gonzalez@uclouvain.be jean.vanderdonckt@uclouvain.be Sistemas de Información Universidad Autónoma de Aguascalientes jmunozar@correo.uaa.mx
    2. 2. 2 February 1-7, 2009 - Cancun, Mexico ACHI’09 Outline 1. Introduction 2. State of the Art 3. A structured approach to support 3D User Interface Development 4. Conclusion
    3. 3. 3 February 1-7, 2009 - Cancun, Mexico ACHI’09 Introduction – Web more collaborative – Increase use of social networks – Web 2.0 It will be the future landscape of the internet places, not pages?
    4. 4. 4 February 1-7, 2009 - Cancun, Mexico ACHI’09 Introduction – Current methods: • rarely provide the design knowledge • are more focusing on the implementation – Available tools for 3D UIs are: Toolkits, interface builders, rendering engines
    5. 5. 5 February 1-7, 2009 - Cancun, Mexico ACHI’09 Introduction – Our goal: “to demonstrate the feasibility of a MDE- compliant method that is user-centered as opposed to contents-centric for developing 3D UIs” – We propose: • a user-centered approach • model-driven architecture • separation of concerns
    6. 6. 6 February 1-7, 2009 - Cancun, Mexico ACHI’09 Outline 1. Introduction 2. State of the Art 3. A structured method for developing 3DUI 4. Conclusion
    7. 7. 7 February 1-7, 2009 - Cancun, Mexico ACHI’09 State of the art – Methodological diversity – Not user centered approaches – Single entry and single output – Transformations are hidden
    8. 8. 8 February 1-7, 2009 - Cancun, Mexico ACHI’09 State of the art – Lack of a methodology for developing 3D UIs – Lack of user task models – Lack of models independent to the final implementations – Lack of a toolkit for such work – Lack of genuine 3D UIs
    9. 9. 9 February 1-7, 2009 - Cancun, Mexico ACHI’09 Outline 1. Introduction 2. State of the Art 3. A structured approach to support 3D User Interface Development 4. Conclusion
    10. 10. 10 February 1-7, 2009 - Cancun, Mexico ACHI’09 Scope of the Method – Pure Reality – Augmented reality – Augmented Virtuality – Virtual 3D GUI – Digital 3D GUI – 3D rendering of 2D GUI – 2D GUI
    11. 11. 11 February 1-7, 2009 - Cancun, Mexico ACHI’09 Method Outline
    12. 12. 12 February 1-7, 2009 - Cancun, Mexico ACHI’09 Method Outline
    13. 13. Task and Domain Model 13 February 1-7, 2009 - Cancun, Mexico ACHI’09 Rule: A task manipulates a domain class Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    14. 14. 14 February 1-7, 2009 - Cancun, Mexico ACHI’09 Step1. Consolidation of the task Model NAC LHS RHS ::= NAC LHS RHS ::= Each of the new sub-tasks will be mapped on the corresponding attribute of the class Rule: For each task that manipulates a domain class, a new subtask is created for each attribute. Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    15. 15. Step1. Consolidation of the task Model 15 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    16. 16. Step 2: From task to Abstract User Interface Model 16 February 1-7, 2009 - Cancun, Mexico ACHI’09 NAC LHS RHS ::= NAC LHS RHS ::= Each task is executed in an abstract container if the task is decomposed into subtasks Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    17. 17. Step 2: From task to Abstract User Interface Model 17 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    18. 18. Step 2: From task to Abstract User Interface Model 18 February 1-7, 2009 - Cancun, Mexico ACHI’09 NAC LHS RHS ::= NAC LHS RHS ::= Each leaf task is executed in an abstract individual component. Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    19. 19. Step 2: From task to Abstract User Interface Model 19 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    20. 20. Step 2: From task to Abstract User Interface Model 20 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    21. 21. Step 3: From Abstract User Interface to Concrete User Interface Model 21 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    22. 22. Concrete User Interface For each Abstract Container Step 3: From Abstract User Interface to Concrete User Interface Model 22 February 1-7, 2009 - Cancun, Mexico ACHI’09 That contains an abstract individual component (AIC) And the AIC is composed of an input facet And the facet has an action type select Task & Concepts Abstract User Interface Final User Interface
    23. 23. Step 3: From Abstract User Interface to Concrete User Interface Model 23 February 1-7, 2009 - Cancun, Mexico ACHI’09 And the domain of the data is continuous Then concretize the AIC into a Slider contained in a graphical container (Box) The rule is applied to 6 AIC Concrete User Interface Task & Concepts Abstract User Interface Final User Interface
    24. 24. Step 4: Adding behaviour 24 February 1-7, 2009 - Cancun, Mexico ACHI’09 1 0 ≤ C a l c V a l u e ( x , y ) ≤ 1 0 0 < x , y > < x , y > < x . y > T r a in e r s T r a ie r S a la r y S t u d e n t S a la r y S t u d e n t s T r a in e r W o r - k in g D a y s A n n u a lW o r - k in g D a y s U p d a t e A n n u a l W o r k i n g D a y s S t u d e n t s P e r T r a in e r U p d a t e S t u d e n t s P e r T r a i n e r 0 ≤ C a l c V a l u e ( x ,y ) ≤ 3 0 0 < x , y > 0 ≤ C a l c V a l u e ( x , y ) ≤ 1 0 0 1 0 ≤ C a l c V a l u e ( x ) ≤ 1 0 0 1 0 ≤ C a l c V a l u e ( x , y ) ≤ 3 0 0 < x , y > 2 0 0 ≤ C a l c V a l u e ( x , y ) ≤ 3 0 0 < a > < a > < b > < b > < c > < c > < d > < e > < d > < e > < f > < f > < g > U p d a t e T r a i n e r s U p d a t e S t u d e n t S a l a r y U p d a t e T r a i n e r S a l a r a y U p d a t e T r a i n e r W o r k i n g D a y s U p d a t e S t u d e n t s a = C a l c V a l u e ( x ,y ) d = C a l c V a l u e ( x ,y ) e = C a l c V a l u e ( x ,y ) b = C a l c V a l u e ( x ,y ) c = C a l c V a l u e ( x ,y ) f = C a l c V a l u e ( x ,y ) g = C a l c V a l u e ( a ,b , c , d , e , f ) < x , y > Concrete User Interface Task & Concepts Abstract User Interface Final User Interface
    25. 25. Final Result 25 February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface
    26. 26. 26 February 1-7, 2009 - Cancun, Mexico ACHI’09 Outline 1. Introduction 2. State of the Art 3. Model-based development of 3D user interfaces 4. Conclusion
    27. 27. Conclusion 27 February 1-7, 2009 - Cancun, Mexico ACHI’09 • We introduced a 3DUI Engineering methodology articulated on three axes: models and their specification language, method, and tools that support the method based on the underlying models. • All aspects are stored in UsiXML (www.usixml.org) files that can be exchanged, shared, and communicated between stakeholders (designers, developers, and end users). • It has been demonstrated that the global methodology adheres to the principles of MDA and is therefore compliant, except for the standardization process which is ongoing.
    28. 28. Conclusion • Advantages – Modifiability – Complexity – Rigorous. – Reasoning. – Processable. • Model transformations of bigger systems will be more complex to discover and to apply, so it is not clear if the solution is computationally feasible considering the amount of operations needed to perform graph transformations. 28 February 1-7, 2009 - Cancun, Mexico ACHI’09
    29. 29. For more information and downloading, http://www.isys.ucl.ac.be/bchi http://www.usixml.org User Interface eXtensible Markup Language http://www.similar.cc European network on Multimodal UIs Special thanks to all members of the team! Thank you very much for your attention

    ×