Optimized Traffic Routing System for Western Washington Commuters
100 likes | 220 Vues
Our project focuses on developing a dynamic routing system for users commuting in Western Washington, leveraging current and forecasted traffic data. The primary users will be commuters traveling to work and large events. Key features include a live traffic map, the ability to input start/end addresses, traffic forecasting, and route saving capabilities. The system will be built on a server infrastructure with access to WSDOT traffic databases, supporting multiple connections. We will follow an agile development plan with milestones for initial data integration and user testing.
Optimized Traffic Routing System for Western Washington Commuters
E N D
Presentation Transcript
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
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
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