Brad Woodward Ben Higgins LCO for a Location-Aware Item Framework (with sample applications)

Operational Concepts Location-aware item-based Framework Scavenger hunts Tours Real-world adventure games Items are the basic unit Icon Location Visibility requirements Usage requirements Acquisition requirements Transferability settings

Example Usage Scenario Susan is a student at UW A friend made a game called Ghost Hunt Signs up on the web Begins playing

System Requirements Server receives information about client, gives client list of nearby visible Items Client interacts with world using information about Items If the client wants to change the world (e.g., pick up an item, drop an item), then it asks the server to do so. If the client isn't changing the world, then no communication with the server is required Network traffic kept to a minimum

System and Software Architecture Server designed as a Web Service; maintains a database of Items and Users Probably makes use of Microsoft SQL Server HP Pocket PCs for client with Internet connectivity Shows nearby Items as icons Communicates at regular intervals with the server For testing, no GPS is required, but for production some form of location-awareness would be Client software developed with Visual Studio .NET tools.

Lifecycle Plan Wide variety of applications available Different types of end-user depending on application Independent developers can make their own applications

Feasibility Rationale Framework fairly simple Sample applications can be limited in scope Major drawback is lack of GPS units Not enough work? Options for expansion: Items that move around Items with advanced scripted actions Items that react to your presence More ambitious applications