1. Lost No More: Driving Directions & Traffic Conditions For Your Cell Phone David Kasprzyk Karl Yerkes

2. Concepts: What we’re proposing Driving Directions: Get driving directions on your phone using the MapQuest service. Highway Conditions: Get current Puget Sound highway traffic conditions. Smart Route Finding: Use the current traffic conditions to find the fastest route available, avoiding highway backups if it means a shorter travel time.

3. LifeCycle: Consumers & Support Who Wants This?: Seattle Area Drivers Can quickly get directions on the go. Makes it easy to deal with last minute change in plans. Can check traffic conditions on the go instead of having to rely on checking before they leave or waiting for radio updates which don't give full conditions. Can find alternative routes from point A to point B. Who’ll Support This?: Use of existing websites for data will reduce the amount of upkeep needed. Minor updates could be provided by a small team or an individual programmer.

4. Driving Directions: How It Works Midlet requests driving directions from Servlet Servlet gets data from MapQuest.com Servlet parses data and sends it back to the Midlet Sends directions to the Midlet in easily readable format. Image data is converted to PNG and sent to the Midlet. Midlet can save locations to the Servlet Servlet stores locations for future use by the Midlet

5. Highway Conditions: How It Works Midlet requests highway conditions from the Servlet Servlet gets data from WSDOT Servlet parses data and sends it back to the Midlet Sends current travelling times to the Midlet in easily readable format. Image data is converted to PNG and sent to the Midlet.

6. Smart Route Finding: How It Works Servlet stores locations of several bypass points. When calculating an alternate route, uses these bypass points to find other possible ways to reach the final destination. Uses current traffic conditions to estimate the speed of using the highways. Returns the shortest route, the fastest estimated route, and if available, a route that avoids the highways. Users can add bypass points to provide known shortcuts.

7. System Requirements: What’s Needed Driving Directions: Mapping and directions are already provided. MapQuest already provides map images and direction information. Servlet only needs to clean up the data and pass it to the Midlet. Highway Conditions: Conditions are already provided. WSDOT already provides map images and travelling times. Servlet only needs to clean up the data and pass it to the Midlet.

8. System Requirements: What’s Needed Smart Route Finding: Largest portion of development. Need algorithms to find best routes using bypass points. Need algorithms to estimate traveling times using data on the current highway conditions. Need system for incorporating sub-paths using bypass points into a final path from the start point to the finish.

9. Feasibility: Can We Do It? Driving Directions: Image sizes vs. phone data rates. Large image sizes would be heavy downloads. Possible solutions: Don’t download the image unless the user asks for it. Transmit smaller image chunks as needed. Highway Conditions: Image sizes vs. phone data rates. Same issues as with Driving Directions.

10. Feasibility: Can We Do It? (Part 2) Smart Route Finding: Requires knowledge of possible bypass points. Good bypass routes would require a large number of bypass points. Possible solutions: Allow users to add their own bypass points along their most common routes.

11. Conclusions: What To Take Away Lost No More: Provides drivers with a powerful multi-tool. Takes advantage of existing web resources. Feasible design for today’s cell phones. Allows users to choose what they want to view so we don’t overload the bandwidth. Allows for user customization and easy expansion. Simple maintenance.