1 / 10

User Interface Design and Evaluation

Explore the case study on user requirements gathering in the oil industry logistics domain for improving the system used by tanker drivers at Tokairo. Learn about the process, benefits, and communication strategies involved in this UI design and evaluation project.

martinjames
Download Presentation

User Interface Design and Evaluation

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. User Interface Design and Evaluation Chapter 7 Case study on requirements: Tokairo, part 1

  2. The System • UI for a kiosk and worksheet for oil tanker drivers • Original system- Paper worksheet • New system- Kiosk + Worksheet

  3. Excel plc Business unit of Shell Tankfreight Tokairo Subcontracts developments of lorry driver’s system to… Subcontracts Logistics to… Background info • Companies involved • Tokairo • Tankfreight • Shell

  4. User requirements gathering • Domain • Logistics in oil industry • Drivers • Nonacademic • Motivated • Unions

  5. User requirements gathering • Tasks • Safety checks • Load tanker • Drive tanker • Make deliveries • Make record of deliveries

  6. User requirements gathering • Environment • Noise • Dirt • Poor writing instruments

  7. How Tokairo gathered user requirements • Tokairo had prior knowledge about users • Looked for “pockets” a.k.a. groups • Identify common characteristics • Conducted Site and System Audit • Analyze function and link to documents involved

  8. Communicating user requirements • Spec passed to programmer • Tokairo did not write down the user requirements

  9. Benefits of conscientious requirement gathering • Saves: • Time • Money

  10. ¿Questions or Comments?

More Related