1 / 24

Human-Centered Technologies Analysis Tool

A tool designed to evaluate complex systems for human factors issues, including errors and inconsistencies in controls, displays, and automation. It aims to assist safety regulators in identifying potential problems early on. The beta version allows analysis of graphical user interfaces, with the final version expanding to assess function keys, dual interfaces, and conflicting functions.

tcarlton
Download Presentation

Human-Centered Technologies Analysis Tool

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. Human Centered Technologies Analysis Tool Victor Riley June 29, 2005 User Interaction Research and Design, Inc. Point Roberts, WA

  2. Project team • Dr. Tom Raslear, FRA • Stephen Reinach, Foster-Miller • Kurt Bruck, Foster-Miller • Dr. Victor Riley, UIR&D

  3. Background • Technology and systems becoming more complex • HF issues coming to the fore • FRA: new rule on processor-based control systems • FAA: new rule on design-related human error • Too many problems, not enough regulators with HF expertise

  4. FRA Human Centered Technologies Tool • FRA wants tool to help Office of Safety personnel evaluate systems and UIs for potential human factors problems • Current status: beta version

  5. Design related error • Fitts and Jones (1947): • Substitution errors • Adjustment errors • Forgetting errors • Reversal errors • Unintentional activation errors • Inability to reach a control

  6. Design related error • Fitts and Jones (1947): • Substitution errors • Adjustment errors • Forgetting errors • Reversal errors • Unintentional activation errors • Inability to reach a control

  7. More specifically: • Controls: • Violation of cultural expectations • Inconsistencies within the interface • Adjacent controls with conflicting functions • Protections • Hidden functions • Mode errors • Separation • Appropriate placement for importance • Appropriate selection for number and type of functions • Color

  8. More specifically: • Displays: • Violation of cultural expectations • Inconsistencies within the design • Adjacent displays with conflicting functions • Color (appropriateness, contrast) • Appropriate placement for importance • Control/display relationships • Feedback • Labels • Function keys

  9. More specifically: • Automation: • Potential situation awareness gaps due to combinations of automation SA parameters controls functions operator displays SA parameters

  10. More specifically: • Automation: • Potential situation awareness gaps due to combinations of automation SA parameters controls automation functions operator displays SA parameters

  11. More specifically: • Multiple interfaces: • Compare two systems/interfaces for inconsistencies (interface and automation) • Interoperability • Mixed-fleet flying • Differences training • System 1 • type • location • appearance • motion • logic • System 2 • type • location • appearance • motion • logic Function

  12. Tool role • Inform, not replace, regulator decision-making • Plan to make tool available to industry after FRA acceptance

  13. Tool input • Upload picture of interface for guide • Designate types and positions of controls and displays • Define appearance of controls and displays • Define control and display functions • Identify SA parameters associated with controls and displays • Define automation

  14. Beta version • Will also be able to analyze some aspects of graphical user interfaces

  15. Final version • Will also be able to analyze graphical user interfaces and function keys, dual interfaces, automation • conflicting function types assigned to same key on different screens • same function assigned to different keys on different screens

  16. New rule support

  17. New rule support

  18. Schedule • Alpha test in November of last year • Beta test in July • Final version in 4Q 2005

More Related