1. AccuFlight CSE 403

2. AccuFlight Imagine you are a limousine driver and you are waiting to pick up a particular passenger from the airport. If your passenger’s flight is delayed, then the extra wait time is lost income for you because during that time you could’ve given someone else a ride home. Or Imagine your manager gave you the task of picking up an important customer from the airport. You go there just to discover that his plane is one hour delayed. If only you knew exactly what time the plane would land…

3. Operational Concepts Bring to the customer real-time data about any domestic commercial flight. Customer base:  Business people with tight schedules.  Concerned relatives waiting for their loved ones.  Transferring passengers.  Rental car companies  Limousine drivers

4. Operational Concepts We will provide the following information:  Estimated time of arrival  Latitude and longitude  Altitude  Speed  Distance traveled  Time traveled since departure  Time remaining  Distance remaining

5. System Requirements Unlike existing products, our system doesn’t simply present the user with the data about the flight. The information gathered is used to determine the time of arrival to the highest precision possible. In order to achieve that, the system accounts for route changes as well as weather fluctuations.  Flexibility  Portability  User friendliness  Accurate  Accessibility

6. System Requirements The user can specify:  Flight id number  City of destination / arrival  Departure and arrival times User is then presented with a webpage which displays:  Estimated arrival time,  A satellite map with a detailed flight route of the plane,  Brief description of weather conditions at both arrival and departure locations.

7. System Architecture

8. Lifecycle Plan  A prototype of the simulator to be completed in ~ 3 weeks  A prototype of the data processing module: ~ 3 weeks  Initial testing on the 4 th week  DB created and integrated with existing components by the end of the 4 th week  Integration testing and beta release by the end of 5 th week  More testing / changes and final release by the end of 8 th week

9. Feasibility Rationale Assumptions:  The functionality of our GPS simulator will be the same as for the real simulator.  Our system will work in the real world. This assumption is due to the fact that we are using a GPS simulator that does not take into account the possible inaccuracy of the real GPS.  The plane is going to preserve its current course between two consecutive samplings of the GPS.