A ModelDriven Architecture for Logging Navigation

1
A Model-Driven Architecture for Logging Navigation

• Marco Winckler, Florence Pontico

LIIHS-IRIT Logiciels Interactifs et Interaction
Homme-Système (LIIHS) Institut de Recherche en
Informatique de Toulouse (IRIT) Université Paul
Sabatier, Toulouse, France winckler,
pontico_at_irit.fr
2
Strategies for logging traces

• Tool support on the Web client
• Web server log files
• Modifying the Web applications
• Model-Driven Architectures

3
Need for model-based approach for Web development

• Make complex applications manageable
• Increase communication between multidisciplinary
  teams
• Clear definition of user requirements
• Provide unambiguous models
• Predict problems before implementation
• Cope explicitly with modifiability
• Separate abstract modelling from implementation

4
What kind of models for Web Applications
Modelling layers
Presentation (Look Feel)
Hypertext (navigation)
Application domain (content)
Structure
Development process
Requirement engineering
Conceptual modelling
Design
Implementation
Behaviour
Modelling aspect
5
Modelling Layers
6
Navigation modelling case study with SWC
notation
Storyboard
7
Model-based dialog architecture a proposal
Activatea link
Navigation
Presentation
Contents
1
IF the page belongs to the website MERGING
3
Pagerequested
4
NAVIGATION CONTROLLER
3bis
Sends the page todisplay (no-cache)
2
Redirection to the requested website
Interaction recording
LOG
USER
SERVER
8
Running out the case study
9
Running a scenario
CAPES
SpiderWeb workshop
IHC2002Workshop
3
COFECUB
SpiderWeb intro
2
SpiderWeb schedule
1
II-UFRGS
4
7
SpiderWeb publications
6
LIIHS-IRIT
5
10
Empirical results
11
Discussion

• Efficient way to collect user traces
• Full control of user navigation
• The approach can go beyond navigation
• Cost are reduced since models also used during
  the design process