10.07.2015 Views

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

MAP-01-011 HFI Technical Guide - Human Factors Integration ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Annex 3 – HF Techniques, Methods and Toolsadapted from published best practice and legacy system experience. Theapplication of checklists often relies on direct visual inspection of the HMI, or thetaking of relatively simple measurements. Functional checking may also becarried out. If a checklist is to be used effectively, persons having familiarity withthe type of HMI and the context of is use should apply the checklist.Checklists are commonly used to assess the physical aspects and characteristicsof the HMI, such as dimensions, layout, orientation, labelling, etc. Checklists canalso be used to assess the more subjective aspects, such as HMI usability:those devised by Ravden & Johnson (DTC150 - 1989) ‘HCI Checklist’ andWoodson, Tillman & Tillman (No citation reference - 1992) ‘<strong>Human</strong> EngineeringChecklist’ having prominence in the area of software-based HMIs.• Advantages• Checklists are a very simple technique to use.• Checklists are probably one of the quickest methods available, offering animmediately useful output.• Checklists are based upon established knowledge about humanperformance (DTC168 - Stanton and Young 1999)• The technique requires very little training.• Resource usage is very low.• Checklists are very adaptable and can easily be modified in order to usefor other devices/systems. For example, Stanton and Young (DTC168 -1999) suggest that the Ravden and Johnson checklist (DTC150 - 1989),originally designed for HCI, is easily adapted to cater for the usability ofother devices, such as in-car stereos.• A number of different checklists are available to the <strong>Human</strong> <strong>Factors</strong>practitioner.• Disadvantages• A checklist type analysis does not account for errors or cognitive problemsassociated with the device.• Context is ignored by checklists.• Checklist type analysis is very subjective. What one analyst classes asbad design may be classed as suitable by another.• Low consistency.• Not a very sophisticated approach to system design.May 2006 Page A3-117 Issue 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!