1 / 21

Interface Redesign of Flight Reservation Systems

Interface Redesign of Flight Reservation Systems. Nicholas R. Jones Chris S. T. Fernandes Computer Science Union College. Human Computer Interaction Usability Analysis Flight Reservation System. Outline. Motivation Existing Solutions Goals Evaluation Process Results Conclusion.

sahkyo
Télécharger la présentation

Interface Redesign of Flight Reservation Systems

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. Interface Redesign of Flight Reservation Systems Nicholas R. Jones Chris S. T. Fernandes Computer Science Union College

  2. Human Computer Interaction • Usability Analysis • Flight Reservation System Nicholas R. Jones

  3. Outline • Motivation • Existing Solutions • Goals • Evaluation Process • Results • Conclusion Nicholas R. Jones

  4. Motivation • Easy for anyone to make an interface • Some are not intended for human consumption • Interfaces that are not tested Nicholas R. Jones

  5. Existing Solutions • Travel Sites: • Travelocity • Orbitz • Expedia • Focusing on Flight Reservations Nicholas R. Jones

  6. Nicholas R. Jones

  7. Nicholas R. Jones

  8. Nicholas R. Jones

  9. Nicholas R. Jones

  10. Goals • 1.) Time to learn • 2.) Speed of performance • 3.) Rate of errors by users • 4.) Retention over time • 5.) Satisfaction • Shneiderman, Ben. Designing the User Interface. Third Edition. Reading, MA: Addison Wesley, 1998. p 15 Nicholas R. Jones

  11. Evaluation Process • Test on Users • Analyze data to find where problems occur • Suggest multiple ways to fix problems • Test for best solutions • Incorporate solutions in redesign • Run user evaluation again Nicholas R. Jones

  12. Methods • Usability Analysis • Scenarios • Timing and Noting • “Thinking-Aloud Protocol” • Surveys • Automated Testing • Collect various information remotely Nicholas R. Jones

  13. User Test 1 • 6 participants tested • Each participant – 3 scenarios • Frustrating Issues • Waiting and re-entering data • Distinguishing between different flight • Date and time inputs Nicholas R. Jones

  14. User Test 2 • Entering in Dates • Calendar Input • Pull-Down Menus • Text in MM/DD/YY format • Re-entering in Data • Left, Right, or Bottom Nicholas R. Jones

  15. Test 2 results • Pull down menus were significantly faster than calendar input • Inputting into the Left and the Bottom was significantly faster and more satisfying than on the Right • N=49 participants Nicholas R. Jones

  16. User Test 3 • Nine students tested several interfaces using three scenarios. • Fictional FlightGuide.com site • Travelocity, and Orbitz used for comparisons Nicholas R. Jones

  17. Input Screen • Round trip /one way needs to be clearer • before/after/around helpful if noticed • A method to see flight duration before results • Results Screen • Sort by flight length, start time, price • Total flight duration • Results kept together and not separated Nicholas R. Jones

  18. User Test 4 • 5 students participated • Used fictional FlightGuide.com site Nicholas R. Jones

  19. Input Screen • missed one way/round trip still, did not like in middle • liked trip duration • Half used before/around/after • Results Screen • Did not notice sort by fields • Would like an overview of results • Easier way to track results. (color code) Nicholas R. Jones

  20. Conclusions • Information Visualization • Search • Overview • Zoom and Filter • Details on Demand • Asking users is not enough Nicholas R. Jones

  21. 5 users is enough http://www.useit.com/alertbox/20000319.html Nicholas R. Jones

More Related