Title:
|
CO-CONSTRUCTED TASKS FOR WEB USABILITY TESTING |
Author(s):
|
Kimmo Tarkkanen, Pekka Reijonen, Ville Harkke, Janne Koski |
ISBN:
|
978-972-8939-90-8 |
Editors:
|
Katherine Blashki |
Year:
|
2013 |
Edition:
|
Single |
Keywords:
|
Usability testing, Test task, Test procedure, Web usability, Requirements elicitation |
Type:
|
Full Paper |
First Page:
|
79 |
Last Page:
|
86 |
Language:
|
English |
Cover:
|
|
Full Contents:
|
click to dowload
|
Paper Abstract:
|
Usability testing is one the most widely utilized usability evaluation technique and it typically is an integral part of a user-centered design (UCD) process. There is a lot of literature on how to perform usability testing but one of the key factors affecting the test results, the test tasks, has received relatively little attention. According to the general usability testing guidelines, the test tasks should be based on the real goals and tasks of the users, be reasonable short, and have a clear ending or a correct answer. Rather often, however, the tasks are based solely on the functionalities of the tested software. This means that the designed and/or implemented software is considered as an accurate representation of the user needs but the test does not reveal if this is actually the case. In this paper, we propose a modified task type, co-constructed tasks, as a means to allow user needs to come forth also in a usability test. Co-constructed tasks support maintaining of appropriate user influence also during the usability testing phase, dispute the interpretations of the user needs made in an earlier design phase, and enhance the evaluation in environments where users, goals, and context of use are less exactly defined. The results from a pilot study show that the co-construction is a feasible procedure to create high-level usability test tasks for web users with heterogeneous profiles and variety of usage incentives. It can be concluded that the co-constructed high-level tasks complement the more structured tasks and shift the focus of evaluation to new requirements elicitation. Applicability of the approach as well as its restrictions and future development needs are discussed. |
|
|
|
|