1. The document proposes a model-driven development approach for 3D user interfaces that is user-centered rather than content-centric. 2. It involves separating design into abstract, concrete, and final models through a multi-step process using tools like UsiXML, UML class diagrams, and graph transformations. 3. A case study demonstrates applying the method to design a virtual polling system, generating interfaces in tools like Alice, Maya, and VUIToolkit from the abstract and concrete models.

1. A model-based development for 3D User Interfaces Juan Manuel Gonzalez Calleros Université catholique de Louvain, School of Management (IAG) Information Systems Unit (ISYS) Louvain-la-Neuve, 13th June , 2006

7. Related work – Programmatic Approach, VRML

8. Related work – Toolkit Approach, Anark

9. Related work – Render Engines, 3DNA

16. Method Outline

17. Development paths

18. Graph transformation tool support AGG

19. Method Step1 – Task and concepts description

20. Method Step1 - User Action Task Extension The action of identifying any user action Perceive The action of mediate user actions Mediate The action to communicate the user to the system or vice versa Communicate The existence of two different states of an item Toggle An action of modifying an item Modify Specifies the creation an item Create Specifies some sort of indication Indicate Specifies the end to an action Terminate Specifies the triggers of an action Trigger Definition actionType

25. Method Step1– Domain Model

26. Method Step1 – Software tool

28. Method Step2 – Tool support

29. Method Step3 –To obtain a Concrete specification

30. Method Step3 –Taxonomy of 3D UIs

33. Method Step3 - Tool support - Alice

34. Method Step3 - Tool support - Maya

35. Method Step3 - Tool support - VUIToolkit

38. Case Study – Task and domain definition

39. Case Study – Concrete Definition

40. Case Study – Concrete Model B

41. Case Study – From Abstract to concrete Model x>2 RHS := LHS NAC NAC

42. Case Study – From Abstract to concrete Model A trigger Feedback Navigation “ Navigation” A trigger Feedback Control “ Send Questionnaire” A dropdown list, a group of option buttons Data type, domain characteristics Select attribute value + repetitive (selection values not known) “ Select Answer” An output text Attribute, data type, domain characteristics Output (value unknown) “ Show Questionnaire”

43. Mock-up of the Concrete User Interface

45. Case Study – Editing the FUI in Maya

46. Case Study – Editing the FUI in Alice

47. Case Study – FUI generated with Alice

48. Case Study – FUI generated with the VUIToolkit

49. Case Study – FUI generated with the Maya

50. Case Study – FUI generated with the Maya

51. Use of the virtual polling system Case Study in a virtual world

53. Conclusion –Model-based approaches Java, XHTML, Flash, HTML, Voice XML* Java 3D*, X3D*, VRML*. T  Do, T  AUI, AUI  CUI, CUI  AUI, T  CUI, (T, Do,AUI,CUI)  C, CUI ≈ -> FUI T, Do, C, AUI, CUI Our methodology X3D, Behavior3D, Audio3D (CUI, Di) -> FUI CUI, Di Contigra T ≈-> ( Di, CUI), ( Di, CUI) ≈ -> FUI Di, CUI InTML C++ ( T, Di, CUI )  FUI T, Di, CUI CoGenIVE VRML, X3D CUI -> FUI CUI VR-Wise FUI target languages *Indicates that it is done manually Inter Model Transformation  Bidirectional derivation -> Derivation link ≈-> Manual Derivation ≈  Manual Bidirectional der. FUI = Final User Interface Models t= task, Do = Domain Di = dialog AUI=abstract presentation CUI=concrete user interface U = user, C = context.