Prsentation PowerPoint

Agile method in the support of UI Context-Aware Adaptation

Nesrine Mezhoudi, Jorge Luis Perez Medina and Jean Vanderdonckt

1

11 fvrier 2010Nathalie Delobbe1

Adaptation is an end-user/customer needAdaptation consist on building a degree of flexibility for UIs to better accommodate the diverse needs of users.

Lack of flexibility

Lack of predictabilitybest adaptation rule could not be predicted

2

Definir adaptation Advantages ShortcomingRegidety of poutr cooncepter et utilisateur

Commonly Adaptive user interface are based on a set of predefined and even static adaptation rules defined regarding standards, ergonomic guidelines, esthetic metricsAccordingly it is hard to readapt the UI neither to update the existing adaptation rules wish supposed to evolve across time.and even it it is possible in what costs ?this lack of dynamic adaptability among systems has several consequences:user dissatisfaction because these systems do not fit the users needs, limitations, and preferences,user demotivation to use the systemand finally user withdrawalThereby the dynamicity and the interactivity od adaptation began a crucial requirement to keep the user and ensure their satisfaction.

15/01/15

2

Need for Context-awareness3

Current problems of UIs4Lack of usabilityToo high functionalityPainful AdaptabilityLack of user-centerednessLack of flexibilityFrustrating adaptivityComplex UIOverloaded UIDifficult to useRigid interactionAmbiguous interactionOne size do not fill allUser Dissatisfaction

This is causes/effects as in lack of usability poor performances, dissatisfaction, frustration.15/01/15

4

Challenge

Enhance systems capability to learn over time from experience with end-users

How to involve end-users in adaptation decisions?

How can UI be presented more effectively regarding end-users needs?

5[1]N.Mezhoudi, User Interface Evolution: Machine learning for GUI at runtime contextualisation, BENEVOL 2013, 46[2]N Mezhoudi, User interface adaptation based on user feedback and machine learning, Proceedings of the companion publication of the 2013 international conference on Intelligent user interfaces companion.[3]V.Genaro motti, N Mezhoudi, J Vanderdonckt, A Theoretical Framework for Specifying and Analyzing Context-Aware Adaptation, Workshop on Context-Aware Adaptation of Service Front-Ends CASFE'2012

15/01/15

5

Solution: Interaction-based adaptation

Objective:Enhancing the end-user role in the UI design at runtime.

6

AgendaMain concepts :Adaptation dimentions, AgileState of the artAgile AdaptationAgile Adaptation in the support of methodological prototyping

7

Agile method in Software development

To be agile:

you must go through this full four-step loop continuously and at lightning speed

you must close the gap between the time a change occurs in the real world and when you take action.8

The need for adaptation is a need to reduce the gap between user needs and expectation and systems services, tasks and adaptation , interaction .This tasks depend on time since overcoming interaction shortcoming during runtime provide user a better interaction and enhance the usability of interfac However within the changed context delayed adaptation doesnt make sens Since neww requirement with dynamic context of use .

8

Adaptation Decomposition

To what?

When?

How?

What?

Why?

-Tracking adaptation-triggers

-Support the decisions of adaptationAssigns adaptation constituents to specific adaptation determinantsStrategies:-Rules repository, -Selection trees,-Decision matrixinformation analysis-inferences

Where?

Recognize the Final UI.9

Here we identify adaptation dimention wia a formal analysis methods (the 5 ws) queqtion , this deconposation allow to identifu adaptation t-reletaed , causes, forms ciscomstances Accodingly ana adaptation is identified by the To what ???, the when , that identify the adaptation trigger recognizing the moment where an event requiring adaptation occure The how : this function asssign adaptation it consist on a reasonning treatment definig hox such requirement could be accomplich and wich adaptationshould be made .

9

State-of-the-art10

State-of-the-art11

State-of-the-art12

State-of-the-art13

14

To what?When?How?What?WhereAgile methodology loop for adaptation support

To what?When?How?What?Where

To what?When?How?What?Where

InteractionsessionContext of use

15/01/15

14

15

Agile Adaptation

Agile Adaptation in the support of Runtime context-awareness

16

Walkaware webservices

17

Agile Adaptation in the support of Runtime context-awarenessWetheraware webservices

Agile Adaptation in the support of Runtime context-awareness18

recognizes functionality that concern interface e.g: changing appearance and interaction style

19

prototyping abstract models e.g: allowing users to update explicitly their profiles in order to accommodate the appropriate adaptation regarding their preferencesAgile Adaptation in the support of Runtime context-awareness

20

combines both above stated strategies... Agile Adaptation in the support of Runtime context-awareness

Demo

21

Conclusion and Future WorksA theoretical framework for Agile Adaptation at runtime: Adaptive, Iterative, Incremental, Evolutionary

A case study, and a preliminary analysis of Agile Adaptation for prototyping UIs

Integrating the framework within typical Agile method for SEPlatform Support for the proposal

22

Thank you ! Visit (YouTube): UsiXML Playlist https://www.youtube.com/playlist?list=PLn_SfKW8yXZAVuESKWEKUqwRQa16ORCi6

Slidesharehttp://fr.slideshare.net/jeanvdd?utm_campaign=profiletracking&utm_medium=sssite&utm_source=ssslideview

Nesrine Mezhoudi, Jorge Luis Perez Medina, Iyad Khaddam and Jean Vanderdonckt

JouNum23

24ContactsJorge.Luis.PerezMedina@uclouvain.beJean.Vanderdonkt@uclouvain.be

Nesrine.Mezhoudi@uclouvain.be

AM basisDescriptionHCI Design practicesHCI runtime practices

Feature DrivenThe system is segmented into sets of client-valued functionality, and development work is organized around producing these features.Modelling tasks, ScenarioModelling adaptation rules, Context models, Context tracking,Decision models, knowledge models

Iterative, incrementalDevelopment is performed in repeated cycles (iterative) and in portions at a time (incremental)Prototyping, user testsContexts evolution, Runtime adaptation, user tests, Prototyping UIs, Learning Knowledge

Customer involvementThe Customer Involvement gene means accepting changing requirements and including the user and/or customer feedbacks in the developmentUser test, User-centred design, user experienceUser involvement, User centeredness, user implicit and explicit feedbacks, User commitments, personalization, controllable adaptability

Team DynamicsThe collection of soft factors and effects related to unique practices that influence the development teams performanceDesign rooms, styles guides, collaborative designMixed-initiative adaptations, predictions, user controllable adaptability, System learnability

Continuous IntegrationContinuous Integration involves methods of maintaining updated software.Evaluation, Usability InspectionsAdaptability support, controllability, Iterative prototyping

AM basisDescriptionHCI Design practicesHCI runtime practices

Feature DrivenThe system is segmented into sets of client-valued functionality, and development work is organized around producing these features.Modelling tasks, ScenarioModelling adaptation rules, Context models, Context tracking,Decision models, knowledge models

Iterative, incrementalDevelopment is performed in repeated cycles (iterative) and in portions at a time (incremental)Prototyping, user testsContexts evolution, Runtime adaptation, user tests, Prototyping UIs, Learning Knowledge

Customer involvementThe Customer Involvement gene means accepting changing requirements and including the user and/or customer feedbacks in the developmentUser test, User-centred design, user experienceUser involvement, User centeredness, user implicit and explicit feedbacks, User commitments, personalization, controllable adaptability

Team DynamicsThe collection of soft factors and effects related to unique practices that influence the development teams performanceDesign rooms, styles guides, collaborative designMixed-initiative adaptations, predictions, user controllable adaptability, System learnability

Continuous IntegrationContinuous Integration involves methods of maintaining updated software.Evaluation, Usability InspectionsAdaptability support, controllability, Iterative prototyping

AM basisDescriptionHCI Design practicesHCI runtime practices

Feature DrivenThe system is segmented into sets of client-valued functionality, and development work is organized around producing these features.Modelling tasks, ScenarioModelling adaptation rules, Context models, Context tracking,Decision models, knowledge models

Iterative, incrementalDevelopment is performed in repeated cycles (iterative) and in portions at a time (incremental)Prototyping, user testsContexts evolution, Runtime adaptation, user tests, Prototyping UIs, Learning Knowledge

Customer involvementThe Customer Involvement gene means accepting changing requirements and including the user and/or customer feedbacks in the developmentUser test, User-centred design, user experienceUser involvement, User centeredness, user implicit and explicit feedbacks, User commitments, personalization, controllable adaptability

Team DynamicsThe collection of soft factors and effects related to unique practices that influence the development teams performanceDesign rooms, styles guides, collaborative designMixed-initiative adaptations, predictions, user controllable adaptability, System learnability

Continuous IntegrationContinuous Integration involves methods of maintaining updated software.Evaluation, Usability InspectionsAdaptability support, controllability, Iterative prototyping

AM basisDescriptionHCI Design practicesHCI runtime practices

Feature DrivenThe system is segmented into sets of client-valued functionality, and development work is organized around producing these features.Modelling tasks, ScenarioModelling adaptation rules, Context models, Context tracking,Decision models, knowledge models

Iterative, incrementalDevelopment is performed in repeated cycles (iterative) and in portions at a time (incremental)Prototyping, user testsContexts evolution, Runtime adaptation, user tests, Prototyping UIs, Learning Knowledge

Customer involvementThe Customer Involvement gene means accepting changing requirements and including the user and/or customer feedbacks in the developmentUser test, User-centred design, user experienceUser involvement, User centeredness, user implicit and explicit feedbacks, User commitments, personalization, controllable adaptability

Team DynamicsThe collection of soft factors and effects related to unique practices that influence the development teams performanceDesign rooms, styles guides, collaborative designMixed-initiative adaptations, predictions, user controllable adaptability, System learnability

Continuous IntegrationContinuous Integration involves methods of maintaining updated software.Evaluation, Usability InspectionsAdaptability support, controllability, Iterative prototyping