1 / 9

ARC

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.

carl-james
Download Presentation

ARC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ARC Amir Kouretchian Peter Turschmid Chris Byszeski

  2. 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

  3. 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

  4. Example

  5. 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

  6. System and Software Architecture

  7. 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

  8. 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

  9. 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

More Related