The myui project focuses on improving accessibility in ICT applications through a user interface adaptation engine that utilizes self-learning and adaptive interfaces. It aims to enable developers to create individualized user experiences without significant configuration efforts by leveraging user profiles and real-time adaptations. The project emphasizes a modular and extensible design for various user needs and contexts while fostering collaboration between developers and users.

1. Integration of a Regular
Application into a User Interface
Adaptation Engine in the MyUI
Project
Vctor Sánchez (ISOIN); vsanchez@ isoin.es
í ICCHP 201 2, Linz

2. MyUI project overview
• Funding within the FP7 Programme.
• Mainstreaming accessibility through the Synergistic User Modelling
and adaptability
• MyUI aims to improve support to developers and designers in
producing accessible ICT applications.
• 30 months proj life time.
ect
•About to finish.
2

3. Accessibility through S elf-learning and self-adaptive interfaces …
• Composition of multimodal
UI patterns
• No or minimal initial
configuration
• System is learning to
increasingly adapt to a
specific user and relevant
contexts or situations.
3

4. MyUI: »Eight Treasures«
(5) User profile initialization
(4) User profile •Games for user profiling
•Diagnostic vs. design-oriented •Intuitive personalization dialogues
•Simple and pragmatic
(3) Runtime adaptations
(8) Control over the resulting UI •Self learning user profiles
•Preview •Interaction monitoring
•Customization and simulation •Live adaptations
(6) Mixed Initiative
Adaptations
•Transparent
•User control
(7) Intuitive application modelling
(1) Extensive adaptations for accessibility
• user: physical, perceptual, cognitive
• context
(2) Adaptation rules/
mechanisms • device
•modular
•transparent
•open and extensible
4

5. Framework for MyUI Adaptive User Interfaces
Design Patterns Repository
Transition patterns
describe how to switch
Transition from one pattern to
another within a bundle
design of related generic or
patterns interaction patterns.
Common patterns define Generic patterns set Interaction patterns
stable (not adapted) global variables to fit define variants of UI
Common features of a UI for a Generic specific user Interaction elements and controls
specific device. requirements and other for specific interaction
design design features of the session
design situations and UI profiles.
patterns patterns profile. patterns
Selection of best-fitting design patterns
UI Generation
UI Parameterization
Session Profile User Interface Profile Individual UI
Device / client General UI features set Best-fitting UI solution
by global UI variables, • Current device
e.g. font size, contrast, • Current user state
updates interaction mechanisms, …
• Current context
User and context
User and context profile • Current application state
m odel and interaction situation
Sensors
e.g. light, noise, …
Application Model Application:
and Content interaction situation,
content
User profile refinem ents on the basis of:
sensors and analysis of actual user interaction
Current interaction situation from
Interaction
dialogue m anager
5

6. Universal Design – Design for All
O n e d e s ig n
f it s a ll?
6

7. Individualization
• Different users will require
different user interfaces
• Vision
individualized user
interfaces for every user
7

8. Individualization
Developer
8

9. Individualization
• But
Developing individualized
user interfaces would
mean enormous effort
Developer
9

10. Individualization
• But
Developing individualized
user interfaces would
mean enormous effort
• And
many users
will have difficulties in
personalizing their user
interface on their owns.
10

11. Vision: Adaptive User Interfaces
• No or only minimal
configuration effort for the
user
• Increasingly better
individualization
• Dynamic adaptations to
context changes
•A daptations to changing
individual needs
11

12. The developer‘s role in MyUI:
Create an Abstract Application Interaction Model
Abstract Application
Interaction Model
•… describes the
interaction between user
and system
•… in an abstract format
which is independent of
the concrete appearance
on the user interface
Developer
12

13. Abstract Application Interaction Model
Extended UML 2 S tate Machine Diagram
Maj concepts:
or
•S t e
at
condition of the application which
defines accepted user behaviour
and system actions
•Interact sit ion
ion uat
represents the user interaction
options in a given state,
e.g. perceiving information,
providing input, selecting options, etc.
•Transition
changing from one state
to another
•Functions
reference to dat acquisit funct
a ion ions
or appl ion funct
icat ions (triggered on
transition or state entry)
13

14. Abstract Application Interaction Model
• The only necessary UI-related
artefact provided by the
developer of a MyUI application
• Basis for UI generation and
adaptation
• Interface between UI and
application functions (e.g. The Development
manipulate the application data Toolkit
base and perform transactions)
• Interface between UI and
application databases
14

15. The Development Toolkit
• Transforming the A IM into real
A
CakePHP code
• Use of patterns browser for
choosing among the application
functions available
•Auto-generated code structure
The Development
• Completing the code
Toolkit
15

16. The Development Toolkit – S tate Viewer
• Eclipse worksapce
•Application A IM
A
• Patterns browser
16

17. 17

18. Detailed architecture
18

19. THANK YOU FOR
YOUR ATTENTION
Vctor Sánchez, vsanchez@ isoin.es
í
19