1. Travel Companion – Life Cycle Architecture Milestone Jordan HomEric Kochhar Abhinav JainChris Baker Justin QuanBen Higgins

2. Operational Concepts  Real-time directions.  Point-of-interest (POI) list for use with directions.  Ability to expose POI list with others.  Other users’ POI lists can be combined with yours.  Optional reminders when close to a POI.

3. Operational Concepts – User Community  Users will be people who often find themselves in need of directions on the go. City residents who want to conveniently store addresses of friends, restaurants, movie theaters. Travelers who want to explore a city.

4. Operational Concepts – Environment  On the go, using an Internet- connected PocketPC with or without a GPS.  At home, through the web, managing your POI list and viewing lists of other users.

5. Operational Concepts – Benefits Provided  When “in the field”: Get directions (either to a POI or enter an address). See what points-of-interest are nearby. Be reminded when you are close to a POI.  Through the web: Explore other POI lists and discover places you might want to visit.

6. Operational Concepts – Does Not Do  Friend tracking.  Complex route planning (i.e., multiple destinations).  Service in areas without Internet access.  World-wide coverage.  Availability for anything other than PocketPC.

7. System Requirements  PocketPC Application Wireless Internet connection. Global Positioning System (GPS).  Website Internet connection.

8. System Specification – PocketPC Application  Get directions Select POI, or enter address. Starting location based on GPS coordinates, or enter address. Directions update themselves if you stray from path.  Reminders User is alerted with a reminder they set if they get close to a POI.

9. System Specification – Website  Manage basic account details.  Add/Update/Delete POI list: Make a POI public or private. Categorize a POI. Add reminders for a POI.  Manage friends Add friends to your account to view their POI list.

10. System and Software Architecture  Products used: Microsoft MapPoint Web Service Microsoft Visual Studio.NET Microsoft SQL Server PocketPC Handheld  Languages/Technologies used: SQL, C#, ASP Web Service: XML, UDDI, SOAP, WSDL

11. Architecture – System Overview

12. Architecture – Database

13. Architecture – Handheld UI

14. Architecture – Data Flow

15. Specification – PocketPC Application

16.  Splash Screen Travel Companion logo Developers  Login Screen Initial screen (post- splash) Authenticate

17. Specification – Pocket PC Application  General Settings Application preferences Store user/pass Default screen (post- login) Server synchronization

18. Specification – Pocket PC Application  Reminder Settings Default action after viewing reminder Distance before triggering reminder Reminder behavior

19. Specification – Pocket PC Application  Map View Map of area Current location Points of Interest Route to destination Next direction

20. Specification – Pocket PC Application  Directions View Full location-aware directions New destination

21. Specification – Pocket PC Application  Points of Interest Personal and friends’ POIs Comments Directions

22. Specification – Website

23. Lifecycle Plan  Who will want it: Travelers for sight seeing Those often out-and-about Tour guides/agencies  Support For now, the 6 member team Later, we don’t know

24. Feasibility Rationale  Website can be done without problems, group has experience  Little difficultly creating database  Group experience is lacking: High-load server (not a problem now) Making a PocketPC application Using Microsoft’s MapPoint Web Service  Biggest obstacles: wireless Internet connection and GPS

25. Expansion options  Blogging service on website  Create extensive POI lists available for everyone Restaurants Landmarks All businesses