Your SlideShare is downloading. ×
The problem of user actions analysis
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The problem of user actions analysis

660

Published on

Discussion about the problem of gathering data from the system for supporting AtGentive

Discussion about the problem of gathering data from the system for supporting AtGentive

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
660
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion The problem of user actions analysis Damien Clauzel American University of Paris atGentive workshop in Oxford, May 2006
  • 2. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion
  • 3. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion What do we want to do? We want to follow the user activity: • what exactly is doing the user? • why is he doing a precise action? • how is he doing it? We want to be able to manipulate the system: • storing and restoring context • activating functions and widgets
  • 4. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion What do we need to do it? We need to know what the user is doing ⇒ activity tracking: high level (search, writing a letter. . . ) ⇒ action tracking: low level (key press, widgets used. . . ) We need to be able to remotely controlling the plat-form ⇒ communicating software ⇒ common interfaces ⇒ smart applications
  • 5. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion Hosting application requirements 1. the position of the caret in the last selected text area 2. the coordinates of the pointer 3. the coordinates of a click event, and which application, area and widget were having the focus 4. the coordinate, geometry and status (active, inactive, folded, maximized, z-level) of the windows 5. the status of the menus 6. the time spent on the current focus, the overall task and the activity 7. the time schedule of the user 8. . . .
  • 6. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion How do we do it? Two main possibilities: • data gathering from operating system ⇒ not enough (?) ⇒ technical problems & few data • modifying the plat-form & applications ⇒ how far can we go? ⇒ means having atGentive ready software
  • 7. Contents What do we want to do? What do we need to do it? How do we do it? (Not a) conclusion (Not a) conclusion • We need right now to make some decisions • Design will be crucial for future extension

×