A Structured Approach to Support 3D User Interface Development

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

Outline

Introduction

State of the Art

A structured approach to support 3D User Interface Development

Conclusion

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?

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

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

Outline

Introduction

State of the Art

A structured method for developing 3DUI

Conclusion

State of the art

Methodological diversity

Not user centered approaches

Single entry and single output

Transformations are hidden

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

Outline

Introduction

State of the Art

A structured approach to support 3D User Interface Development

Conclusion

Scope of the Method February 1-7, 2009 - Cancun, Mexico ACHI’09

Pure Reality

Augmented reality

Augmented Virtuality

Virtual 3D GUI

Digital 3D GUI

3D rendering of 2D GUI

2D GUI

Method Outline February 1-7, 2009 - Cancun, Mexico ACHI’09

Task and Domain Model 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

Step1. Consolidation of the task Model February 1-7, 2009 - Cancun, Mexico ACHI’09 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

Step1. Consolidation of the task Model February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Step 2: From task to Abstract User Interface Model February 1-7, 2009 - Cancun, Mexico ACHI’09 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

Step 2: From task to Abstract User Interface Model February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Step 2: From task to Abstract User Interface Model February 1-7, 2009 - Cancun, Mexico ACHI’09 Each leaf task is executed in an abstract individual component. Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Step 2: From task to Abstract User Interface Model February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Step 3: From Abstract User Interface to Concrete User Interface Model February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Step 3: From Abstract User Interface to Concrete User Interface Model Concrete User Interface For each Abstract Container 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

Step 3: From Abstract User Interface to Concrete User Interface Model 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

Step 4: Adding behaviour February 1-7, 2009 - Cancun, Mexico ACHI’09 Concrete User Interface Task & Concepts Abstract User Interface Final User Interface

Final Result February 1-7, 2009 - Cancun, Mexico ACHI’09 Task & Concepts Abstract User Interface Concrete User Interface Final User Interface

Outline

Introduction

State of the Art

Model-based development of 3D user interfaces

Conclusion

Conclusion

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.

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.

Thank you very much for your attention 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!