The document presents a structured model-driven approach for developing 3D user interfaces. It begins with an introduction describing limitations of current methods and the goals of the presented approach. A review of the state of the art finds a lack of user-centered design and separate models. The presented approach includes 4 steps: 1) consolidating task models, 2) creating abstract user interface models from tasks, 3) deriving concrete interface models from abstract models, and 4) adding behavior. The approach uses models and transformations defined in UsiXML to support design, implementation and reasoning about 3D user interfaces in a model-driven way.

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

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

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 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Final Result
25 February 1-7, 2009 - Cancun, Mexico ACHI’09
Task &
Concepts
Abstract User
Interface
Concrete
User Interface
Final User
Interface

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