Guide project in uk

Experiences of Developing and Deploying a Context-Aware Tourist Guide: The GUIDE Project

Keith Cheverst, Nigel Davies, Keith Mitchell and Adrian

Friday Lancaster University,

Lancaster

Presenter: Jim Cai

Overview

GUIDE is Real World vs. prototype Context-based =/= Location-Based

GUIDE involves Requirement Engineering Human Computer Interaction Wireless infrastructure

Application Requirement Flexibility

Passive (following), active (exploring) Context-Aware

Personal (location, preference), environmental (weather, opening time)

Support for Dynamic Information Opening/closing time, special menus

Support for interactive Services bookings

End-System

Fujitsu TeamPad 7600 Large screen size Light Power/performance (166MHZ) Windows!!! In real world?

User Interface

Browser like Notion of following hyperlink Positive transfer

Friendly Personality Good for novice user

Single-modality distraction

Application functionality

Access context-aware information Tap the info button Not all information are based on

current context Keyword search Nearby attractions sorted by

openness/close


Create a Tailored Tour of the City Step 1: Determine a set of attractions

System: historic, recreation, popular Or User customization

Step 2: Determine the order of the tour Is recommended by the system Can be modified, overwritten. Flexibility -- drawbacks: complicated

interface


Access Interactive Services Motivation: avoid going to TIC Hotel bookings Query films / Book ticket Others (not mentioned)


Send or receive messages Motivation: group tour To keep in touch Request info from the TIC staff

Architectural Approach

The cell-based communications infrastructure

Broadband (2Mbps) Cell server broadcasting Small non-overlapping cells

between buildings Provide more accurate positioning

info Disable WaveLAN roaming

Design of Information Model To represent (GOALS):

Context info Raining / outside castle / interest in history

Geographic info Coordinate vs. symbolic

Hypertext info Global vs. local

State info Visitor’s preference

GUIDE information Model Object types

Location objects Attractions with its location, open time etc. GetImmediateNeighbours() ProvideDescription()

Navigation point objects Way points between location objects

Relationship objects Distance between navigations point/location

objects by different mean

GUIDE INFORMATION MODEL (CON’T)

Augment pages with special tags <GUIDETAG INSERT POSITION> <GUIDETAG INSERT ((HISTORY > 50)

AND (ARCHITECTURE > 50)) <GUIDETAG INSERT NEIGBOURS>


Total of 400 objects (400 html) 120 location/navigation objects 280 relationship objects Store all in local clients (300k) Allow off-line calculation of routes

guidance Is scalability a problem?

City Editor application (portable)

The GUIDE Software Architecture

Disconnected Operation Power matters! Interface solution

Metaphor used to provide connectivity (2 level )

Showing the status of location updates

Use the visitor’s assistance

Evaluation

Expert Walk Through 4 experts Talk aloud Interviewed Feedbacks: progress bar while

downloading; button layout need to be consistent as other browsers

Evaluation (Cont’d) Field Trial

Evaluation (Cont’d)

Results: Positive feedbacks on navigation and

information retrievals Happy with the dimension and weight Degree of connectivity is helpful Location-sensitive is helpful

Current & Future work

Current Employ staff to update information Use of bluetooth and GPS

Future increase diversity of interactive

services adaptive vs. predictable

Discussion

Are all the design decisions being justified by the user study? What are the potential bias? What about a controlled experiment?

Discussion

Is a tablet PC reasonable for a tour guide application?

Discussion

Is scalability a problem, if all objects are stored locally?

Discussion

What could be improved in the current system? Interface Infrastructure Information model

Guide project in uk

Education

Transcript of Guide project in uk