A Structured Approach to Support 3D User Interface Development

Post on 28-Nov-2014

3.243 views 0 download

description

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

Transcript of A Structured Approach to Support 3D User Interface Development

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-ArteagaUniversité 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 February 1-7, 2009 - Cancun, Mexico ACHI’09

Outline

1. Introduction2. State of the Art3. A structured approach to support 3D User

Interface Development4. Conclusion

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 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 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 February 1-7, 2009 - Cancun, Mexico ACHI’09

Outline

1. Introduction2. State of the Art3. A structured method for developing 3DUI4. Conclusion

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 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 February 1-7, 2009 - Cancun, Mexico ACHI’09

Outline

1. Introduction2. State of the Art3. A structured approach to support 3D

User Interface Development4. Conclusion

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 February 1-7, 2009 - Cancun, Mexico ACHI’09

Method Outline

12 February 1-7, 2009 - Cancun, Mexico ACHI’09

Method Outline

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 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

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

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

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

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

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

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

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

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

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

Step 4: Adding behaviour

24 February 1-7, 2009 - Cancun, Mexico ACHI’09

1 0 C a lc Va lue ( x ,y ) 1 0 0

< x ,y > < x ,y >

< x .y >

T r a in er s

T r a ie rS a lar y

S tu d en tS a lar y

S tu d en ts

T r a in er W o r -k in g D ay s

An n u alW o r -k in g D ay s

Upda te A n n u a lW ork in gD ays

S tu d en tsP erT r a in er

Upda te S tu de n ts Pe rTra in e r

0 C a lc Va lue ( x y ) 3 0 0

< x ,y >

0 C a lc Va lue ( x ,y ) 1 0 0

1 0 C a lc Va lue ( x ) 1 0 0

1 0 C a lc Va lue ( x ,y ) 3 0 0

< x ,y >

2 0 0 C a lc Va lue ( x ,y ) 3 0 0

< a>

< a>

< b >

< b >< c >

< c >

< d >

< e>

< d >

< e>

< f >

< f >

< g >

Upda te Tra in e rs

Upda te S tu de n tS a la ry

Upda te Tra in e rS a la ray Upda te Tra in e rW ork in gD ays

Upda te S tu de n ts

a = C a lc Va lue ( x y )

d= C a lc Va lue ( x y )

e = C a lc Va lue ( x y )

b= C a lc Va lue ( x y )

c = C a lc Va lue ( x y )

f = C a lc Va lue ( x y )

g= C a lc Va lue ( a b,c ,d,e , f )

< x ,y >

Concrete User Interface

Task & Concepts

Abstract User Interface

Final User Interface

Final Result

25 February 1-7, 2009 - Cancun, Mexico ACHI’09

Task & Concepts

Abstract User Interface

Concrete User Interface

Final User Interface

26 February 1-7, 2009 - Cancun, Mexico ACHI’09

Outline

1. Introduction2. State of the Art3. Model-based development of 3D user

interfaces4. Conclusion

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.

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

For more information and downloading,http://www.isys.ucl.ac.be/bchi

http://www.usixml.orgUser Interface eXtensible Markup Language

http://www.similar.ccEuropean network on Multimodal UIs

Special thanks to all members of the team!

Thank you very much for your attention