Amir Kouretchian Peter Turschmid Chris Byszeski ARC Amir Kouretchian Peter Turschmid Chris Byszeski

Operational Concepts Calculate and display optimized routes in Western Washington to users that takes current and forecasted traffic data into account Our primary user base will be people who commute to and from work and large events

Operational Concepts 2 Live traffic map Portability Highway Nodes Start/End Addresses or Locations Traffic Forecasting Start/End Time Constraints Force Road Usage Dynamic Manipulation of Traffic Save Routes

Example

System Requirements Access to WSDOT traffic database Server that can support many simultaneous TCP/IP connections at once Server with large storage devices to store WSDOT historic data Clients with enough resources to perform a routing algorithm like Dijkstra’s and to display the route map

System and Software Architecture

Life Cycle Plan Agile Development Plan Milestone 1: Simple client and server with sample WSDOT data. Milestone 2: Display historic traffic data and traffic forecasting Milestone 3: Saving and displaying favorite routes, debugging and user testing Milestone 4: User testing, debugging, documentation and code maintenance

Feasibility Rationale Assumptions Clients utilize Java 1.5 Clients have a dedicated high speed internet connection Clients live in the Seattle area and use the highway system

Feasibility Rationale 2 Risks WSDOT can grant us access to real time traffic data from their servers Reliability of the WSDOT servers, if they go down, we go down Feature creep We don’t have experience interfacing Java with SQL