“Plan your route around the traffic” Team Awesome Ryan Johnson John Su SmartFinder “Plan your route around the traffic” Team Awesome Ryan Johnson John Su The concept of… + the data from… A way to plan a route around traffic conditions =

Operational Concepts Organize a route based on current traffic conditions Alternate routes provided, estimated based on conditions Internet based web application Based largely on the availability of (accurate) traffic data Aimed to help those who don’t know the area/commute a lot Can be expanded to include data from other locations, assuming traffic data is available

System Requirements Allows a user to input addresses and get directions that take in to account local traffic conditions (Should) take in to account road closures Java/C++ design Client: web browser Server: Java/C++ interface Main stakeholders Users dependent on accurate traffic info DOT workers updating data System admins. who maintain the system and provide necessary upgrades/additions

System and Software Architecture Use concept behind MapQuest to implement our own version of it Java/C++ OO design – Web based application Integration between map algorithm and live DOT data May be very hard to do Actual ability to do a “geocoding” type algorithm Need some place to get the geographic data from $$$

Life Cycle Plan Why? What/When? To ease the life of the daily commuter Practical application that will get everyday use What/When? 1) Formulate a “geocoding” algorithm 2) Integrate our geocoding algorithm with DOT data 3) Design a user interface (web page) (BETA) 4) Purchase data licenses (geographical data) 5) Test/Release to web (FINAL)

Life Cycle Plan Who/Where? How? Clients – people who want to plan a route and avoid traffic Least time spent from one place to another Developers Constantly need to keep up with changing geography Third-party developers (DOT/Geographical data providers) Many states a possibility Updating DOT data Output/performance is based on their performance How? Developers will either integrate a way to recognize changing traffic conditions or periodically update it manually Time consuming! Both pieces need to work independent of one another If traffic data goes down, algorithms should still work under “assumed” conditions

Feasibility Rationale Feasible? Data is readily available for independent use Vendors exist to supply geographical data MapQuest solves one case, DOT solves the other… Infeasible? Data is expensive! By adding new conditions, algorithms may be computationally difficult/expensive Avoid extended research Cost – TIME Is this profitable? Can we profit from the use of public data?