Consumer Vehicle Interface Design and Assessment. Paul Green

Size: px

Start display at page:

Download "Consumer Vehicle Interface Design and Assessment. Paul Green"

Blaise Booker
5 years ago
Views:

1 Consumer Vehicle Interface Design and Assessment Paul Green Research Professor UMTRI Driver Interface Group Adjunct Associate Professor Industrial & Operations Engrg. 5th Annual University of Michigan Transportation Research Institute Focus on the Future Automotive Research Conferences The Business of IT: Transforming the Organization and the Vehicle September 12, 2012; Ann Arbor, Michigan

2 Know thy user Who are you? Education level and in what? bachelors / masters / doctorate science / engineering / what else? Job title? Employer? car company / supplier / government / academia / other What do you know about human factors/ergonomics heard the name / self taught / had a class / degree in it / BCPE cert.

3 What systems are of interest? Driver Assistance Adaptive Cruise Control, Forward Collision Warning, Pre-Crash Braking Curve Speed Warning Lane Departure Warning, Lane Keeping Assistance Blind Spot Warning, Side Collision/Merge Warning, Side Collision Avoidance. Backup Warning, Backup Braking Intersection Collision Avoidance, Intersection Collision Braking Expressway Control, Autonomous Driving Drowsy Warning Systems Drunk Driver Interlock Systems

4 What systems are of interest? Information and Entertainment Navigation Music and News Traffic Information Phone Text Message Internet

5 take driver s eyes off the road?? eye fixations take driver s hands off the wheel? task analysis and video analysis reduce their concentration on the road? - most difficult Q What are some of the questions we ask and how do we answer them? Is it easy to use? Do drivers understand what they need to do? time to perform common and important tasks frequency of errors occur and how do drivers correct them time to learn how to use the interface/system Can older driver (most likely to have problems) use it? Is it safe?

6 Our approach is to follow the Gould and Lewis design principles. Principle 1: Early focus on users and tasks. Users: age, gender, technical knowledge, experience with similar devices, etc. statistical data personas Tasks (task = goal + method): frequency, importance, severity of consequence, time frame, duration, scenarios of use statistical data predictions of task times and scenario simulations use cases

7 A high level persona describes a hypothetical user but is based on real data. Typically 5-15 personas are used.

8 Reported Frequency of Destination Entry Method Lo, Green, and Franzblau (2010)

9 Use SAE Recommended Practice J2365 to estimate task time. Assumes Experienced user (longer if inexperienced) Specified method (can t estimate if you don t know what they will do) Task is routine No errors (but they can be included) After obtaining info on the task and user, list the task goals and subgoals Goal: Enter the destination using the street address method. Subgoal 0: Move a hand to the device. Subgoal 1: Select destination entry via street address mode. Subgoal 2: Select a city. Subgoal 3: Select a street. Subgoal 4: Select a street address. Subgoal 5: Select route criteria.

10 Identify the methods used, and write a description of each method as text Method for subgoal of select a city: Scroll through the list of cities until the desired city is found. If the first letter of the city name does not match the first letter for the desired name, use the up and down arrow keys until a matching first letter is found. Then use the right and left arrows to scroll through the list of cities one city at a time. When a match is found, select it. Shortcut: If the city was recently visited, it appears on the recent list at the beginning of the city list. Use the up arrow keys to scroll to a possibly matching name. In all cases, when a match is found, select it.

11 Convert the text to pseudocode. wait for list of streets to appear 1: read highlighted item, decide if 1st character of name of current entry matches desired street 2: if first pass, select method (sequential scrolling or alpha scrolling by first letter of the name) if character not match 1st character then press right arrow key to go to next character go to step 1 (to read the next item) else if matching 1st character then current character = second character compare current character of highlighted item with desired street 2.1 if current character matches and last character confirm correct entry hit enter go to next subgoal if current character matches and not last character increment current character go to 2.1 (compare current character ) if current character does not match displayed character press key to scroll down 1 entry go to 2. exit: next subgoal

12 Look up the time for each operator and add them up to determine total task time. If total>15 s, do not perform while driving. Code Name Operator Description Time (s) Young from steering wheel to other parts of the wheel, stalks or Rn Reach near pods Rf Reach far from steering wheel to center console C1 Cursor once press cursor key once time/keystroke for the 2 nd & each successive cursor C2 Cursor 2 times or more keystroke L1 Letter or space 1 press a letter or space key once L2 Letter or space 2 times or more time/keystroke for the 2 nd &each successive cursor keystroke N1 Number once press the letter or space key once N2 Number 2 times or more time/keystroke for the 2 nd & each successive number key E Enter press the enter key F Function keys or shift press the function keys or shift M Mental time/mental operation S Search search for something on the display Rs Rm Response time of systemscroll time to scroll one line 0 0 Response time of systemnew menu time for new menu to be painted Old

13 Long lists result in long task times. Task # Activity Type 3 Navigation 5 Navigation 17 Media Specific Times (s) Equations Task Young Old Find nearest gas station Rf+7C1+S+5M Set destination Rf+5C1+S+L1+ to DTW 2L2+3M Tune to "Elvis" station Rf+7C1+S+3R m+6m

14 Principle 2: Empirical Measurement (Test) Naturalistic on the road tests with fleets of vehicles (e.g., Safety Pilot) $$$$ Single vehicle tests with an accompanying experimenter Driving simulator experiments Bench tests with working mockups Walkthroughs with paper mockups Different methods for different questions and different phases Methods vary widely in cost and duration No best method

15 Example: Think Aloud Method to Determine User Understanding of a Task (say what your reasoning is for what you are doing) Experimenter IP camera Hypothetical subject Face camera show video clips

16 GEN 3 navigation radio showing time

19 Say how & why tasks were selected

20 Fix the most frequent problems (13 subjects) Freq. Problem Problem Description 12 9 no way for abbreviation input in state name (DC, Washington DC) system freeze no capability of highway intersection search not intuitive method to save radio frequency as preset 9 2 difficult to switch to number keys 9 20 no effective search method for selecting XM channel (channel number, browsing list) 9 24 typing street direction in street name (north/no) 9 35 time-consuming search method for a ipod song 8 4 unclear and uncomfortable guidance voice 8 6 no intuitive method to cancel route/destination on map screen 8 7 confusing to recognize real buttons 8 8 misunderstanding of control maneuver of touch screen (multi-touch, dragging on the map) 8 17 wrong address information (wrong house number range) 7 28 difficult to select the typed-in information (search) 7 29 uncompleted and insufficient text information 7 37 no alphabetical input method for numerical street name (fifth ave)

21 Problem Fix the problems with critical impact (t > 300 s here). Description 24 typing street direction in street name (north/no) 6 no intuitive method to cancel route/destination on map screen 37 no alphabetical input method for numerical street name (fifth ave) 25 not intuitive method to search for a waypoint and add it as a waypoint on the map screen

22 Principle 3: Iterative Design The quality of the design is proportional To the number of design + test iterations. Design/Redesign (include calculations) Test

23 To learn more: Human Factors Engineering Short Course (year 54) July 22 August 2, 2013 Ann Arbor, Michigan

24 To learn more: Industrial and Operations Engineering 437 (Automotive Human Factors) - 3 credits Taught in fall (September December) Ann Arbor, Michigan

25 SAE Safety and Human Factors Committee Current Documents

26 SAE Safety and Human Factors Committee Documents in Development

27 ISO Telematics Standards ISO TC 22/SC 13/WG 8

28 ISO Vehicle Dynamics Standards ISO TC 204

29 For additional info contact: Paul Green umich.edu/~driving

Before Using the Navigation System

Before Using the Navigation System WARNING Read this manual first Read this manual carefully before using the navigation system. We are not liable for accidents or other problems resulting from failure