Answer Happy

Obiect: 1. Drivers: (a) Attributes: driver ID, name, bank account #, active (Y/N), current location (GPS coordinates), date created; (b) Methods (processes): Driver Maintenance (create/modify/inquire/delete). 2. Customers: (a) Attributes: customer ID, name, address (street name & number, city, state, zip code), visa card , date created; (b) Methods (processes): Customer Maintenance (create/modify/inquire/delete). 3. Maps: (a) Attributes: street name, street number, city, state, zip code, GPS coordinates; (b) Methods (processes): Map Maintenance (create/modify/inquire/delete). 4. Fare Rates: (a) Attributes: time of day, fares/mile; (b) Methods (processes): Fare Rate Maintenance (create/modify/inquire/delete). 5. Call Estimates: (a) Attributes: customer ID date, time, from location (GPS coordinates), to location (GPS coordinates), distance, fare$/mile, estimated fare; (b) Methods (processes): Call Estimate Entry (create/delete) 6. Ride Transactions: (a) Attributes: driver ID, customer ID, date, time, from location (GPS coordinates), to location (GPS coordinates), distance, fare$/mile; actual fare; (b) Methods (processes): Ride Transaction Entry (create/modify/inquire/delete). 7. Customer History: (a) Attributes: customer ID, last ride date, last ride time, last ride-from location (GPS coordinates), last ride to location (GPS coordinates), last ride amounts last ride driver ID, total # of rides taken, total $ paid; (b) Methods (processes): Update Customer History (create/inquire/delete). 8. Driver History: (a) Attributes: driver ID, last ride date, last ride time, last ride from location (GPS coordinates), last ride-to location (GPS coordinates), last ride amounts, last ride customer ID, total # of rides given, total $ received; (b) Methods (processes): Update Driver History (create/inquire/delete). 4) Requirements Engineering: (a) Create a Functional Decomposition Diagram (FDD) of QuickTime Ride Share Services Company-including at Level 2 its various possible departments and, at Levels 3 & 4, a detailed analysis of its information system and its associated processes. (b) Create a Use Case Description and a Use Case Diagram of the 'Ride Estimate/Transaction process. In your Use Case description, consider and list the steps (min. of 25) that constitute a successful ride transaction' (from beginning to end) and the steps that constitute other possible alternative outcomes that could take place (e.g., user cancels ride; driver cancels ride; driver goes to wrong location, etc.). See appendix A for a list of possible steps. Steps should include user actions, driver actions, and system responses/actions to both user and driver actions.