search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
9.3 Human sciences-based usability testing methods Task, user and environment analysis


In task analysis, the objective is to focus on the users’ goals – what they want to achieve by using the interface, for example using a web interface to locate a particular service local to them. In order to understand how they approach this, it is necessary to understand the personal, social, and cultural characteristics the users bring to the goal. Task analysis also involves working out the specific tasks that users must complete in order to achieve their goal while using the interface. Depending on the results of the user analysis, the interface may need to be modified to take user characteristics into account, for example by using larger fonts for those with poor vision. A third type of analysis, which is often (but not always) carried out alongside the other two, is environment analysis, which involves understanding users’ physical, social, cultural and technological environments. For example, one aspect of this might be examining the physical location in which a system is to be placed, to determine the type of light levels available for the visual display.


Focus groups


Although the focus group has its origins in marketing, it has become a useful tool for obtaining feedback on an interface at an early stage of development. Usually, a small group of around six users is asked to work with an interface. Under the guidance of a trained facilitator, they give their reactions to the interface. Depending on the stage of development of the interface, this may be a mock-up or a paper prototype (where the prototype has not been built, but exists on paper only). Occasionally, focus groups are used with working prototypes, for example where a device is very high profile and is expected to have a very wide appeal. Video recordings of the discussions are usually made so that exact quotations can be obtained, and key clips are sometimes put together to provide a summary of the session.


Cognitive walkthrough


Cognitive walkthrough is a method of testing the design of an interface at a relatively early stage of development. Expert evaluators use the specification of a prototype to create scenarios for various tasks and goals on the system. They then role-play the part of a user, ‘walking through’ the different tasks to determine whether there are any blocks which prevent the user from reaching their goal. If the sequence required to achieve a goal is very long and complicated, it can indicate that there is a need to review the action sequence and replace it with a simpler approach.


Thinking aloud


Thinking aloud is way of obtaining feedback from the user over the course of their interaction with an interface. A user is given various tasks to perform using the system interface. They are instructed to talk out loud as they perform the task, explaining what they are thinking about and the problems they encounter. The type of data gathered from this type of test can include:


l the users’ feelings generally about the look and feel of the interface l whether they like the colours


l how easy they find it to carry out the task they have been assigned l what problems they encounter


This can provide very detailed in-depth data, but it is not always clear what users are talking about. By combining system logging and a record of the user’s comments, this difficulty can be overcome.


107


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140