Motor Vehicle Driver Interfaces
Paul Green

1. Introduction
   This chapter is written for professionals familiar with human-computer interaction but not familiar with the issues and considerations particular to motor vehicles. For non-HCI professionals, reading chapters 1-19 of this text should provide the desired background. The emphasis of this chapter is on how the safety-critical nature of driving changes the implementation of standard HCI practice. The design of tradition interfaces (noncomputer interfaces, such as switches for the headlights and windshield wipers) is not covered.
2. What is the driving context? (short)
   • Motor vehicles are not just another mobile internet portal (debunk Scott McNealy)
   • Summarize crash data
     • Split out US, Europe, Japan but give world wide total
     • Include deaths, injuries, property damage only
     • By Driver age and sex
     • By Vehicle types and include pedestrians
     • By Time of day
3. Who are the users? (short), refer to chapters on elderly, gender
   • Comment: Similar to general purpose computing, it is all adults.
   • Give stats on #, ages, MF, give truck drivers special attention
   • trends in world (cohort shifts)
   • vision
   • education, training, & licensing
4. What tasks to they do? (short)
   • Comment: Unlike office work, most tasks are time shared.
   • Control, navigation, and guidance (include steering and map design
   • issues)
   • information systems/telematics (the emphasis)
     • systems available and coming
     • market penetration
   • Use Kantowitz task list, estimate frequency of occurance
   • Include truck drivers hours of service
5. What platforms do they use? (What do people drive) (short)
   • Comment: Unlike office work, the platform is moving and uses a nonstandard OS and UI.
   • Data on # and types of vehicles, SUV/minivan/light truck/heavy truck trends
   • Motorcycles in other parts of the world
   • Std OS (Windows, Linux, Mac) in non mobile vs open, need for high speed bus for collision data/airbag
   • Vehicle packaging limitations (It's not an office desk with a chair.)
     • No QWERTY keyboards, no mice, no 19inch screens
6. What measures of safety and usability are collected? (moderate), link to aerospace chapter
   • Comment: Many are unique to the driving context
   • Primary task performance-lane variability, speed variability
   • Secondary task performance
   • Subjective measures
   • Physiological measures
   • Visual occlusion
7. How are safety and usability evaluations conducted in a mobile context? (short)
   • Comment: We not only have lots of cameras and mirrors (but not 1-way), but we also have tires, and sometimes a world.
   • Driving simulators
   • On road studies
     • Supervised test
     • Field operational test
   • Test tracks
8. How can user performance with in-vehicle devices be predicted? (long)
   • The models borrow concepts from HCI in some cases, but the dual task context of driving requires far more complex models.
   • J2365 variant of GOMS (refer to Kieras chapter)
   • IVIS
9. What safety and usability design criteria exist for in-vehicle devices? (use lots of tables) (long)
   • The criteria are specific to the dual task context of driving.
   • 15 second rule
   • other SAE rules
   • ISO standards
   • Design guidelines-
     • UMTRI,
     • Battelle,
     • JAMA
     • HARDIE
     • EU principles
     • AAM principles
10. Where is technology going and what does it portend for the future? (short)
    • Comment: We are way behind the office world.
    • Carry ins - PDA, cell phones
    • HUDS
    • AutoPC
    • Email and the web, link to web chapter
    • Wearables-link to that chapter
11. Closing Thoughts
12. References