A user-centred design and evaluation of IR interfaces

Abstract

This paper presents a user-centred design and evaluation methodology for ensuring the usability of IR interfaces. The methodology is based on sequentially performing: a competitive analysis, user task analysis, heuristic evaluation, formative evaluation and a summative comparative evaluation. These techniques are described, and their application to iteratively design a prototype IR interface, which was then evaluated, is described. After each round of testing, the prototype was modified as needed. The usercentred methodology had a major impact in improving the interface. Results from the summative comparative evaluation suggest that users' performance improved significantly in our prototype interface compared with a similar competitive system. They were also more satisfied with the prototype design. This methodology provides a starting point for techniques that let IR researchers and practitioners design better IR interfaces that are both easy to learn to use and remember. The paper concludes with some principles of interface design for IR systems.

Seeking Serendipity

“…Instead of concentrating on IR evaluation with users, the present study focuses on one of the preceeding phases in technology development, namely ideation. In line with user-centered design cases in IR, which indicate that co-developing with users helps refine search goals, problems, and interface design [2,20], this paper focuses on both identifying user needs as well as understanding factors that constrain user-technology interaction.…”

Help with health information on the web

“…Next, is a summary of user requests and general best practice design guidelines from the HCI design community which are relevant to the development of quality help features in online information resources (Kerchner, 2006;Mueller, 2003;Aberg and Shahmehri, 2003;Aberg and Shahmehri, 2001;Aberg and Shahmehri, 2003;Ahmed et al, 2006;Trenner, 1989;Hughes, 1987):…”

Evaluation of University Websites as Communication Tools: An Iranian Report

“…Since it is not here intended to review related studies comprehensively and in detailed, evaluation criteria applied by some previous researchers are compacted and included in Table 1. [5] Usability, functionality, reliability, efficiency, portability, and maintainability Nielsen (1993) [6] Easy to learn, efficient to use, easy to remember, few errors, pleasant to use Nielsen (1994) [7] Visibility of system status, match between system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency of use, aesthetic and minimalist design, help users recognize, diagnose and recover from errors, and help and documentation Scholz-Crane (1998) [8] Authority, accuracy, objectivity, currency, and scope Olsina et al (1999) [9] Usability, functionality, reliability, efficiency, and derived subcharacteristics Alexander and Tate (1999) [10] Authority, accuracy, objectivity, currency, and coverage Accessibility, speed, navigability, and content Lee and Teh (2001) [12] Objectivity, reliability, authority, content, design (structure), marketing, accuracy, currency, and instructional support Grimes and Boening (2001) [13] Authority, content, design, coverage, objectivity, currency, recommendations, and stability Tillotson (2002) [14] Currency, content, design (appearance), authority (author and references), and other Yates (2005) [15] Accessibility and usability Yoo and Jin (2005) [16] Design and content Wulf et al (2006) [17] Relevance, credibility (authority), currentness (currency), sufficiency, design, interactivity, speed, navigation, readability, reliability, progressiveness, pleasure, satisfaction, commitment, and trust Davarpanah and Khaleghi (2006) [18] Authority, coverage (scope), language (multilingualism), availability, currency, links, domain type, and services and facilities Ahmed et al (2006) [19] Consistency, user support, visibility, refining the search query, informative feedback, simple error handling, easy reversal of actions, navigation, and reduction of short-term memory load Schumaker (2007) [20] Navigation, design Kasli and Avcikurt (2008) …”