Which user interaction for cross-language information retrieval? Design issues and reflections

A novel and complex form of information access is cross-language information retrieval: searching for texts written in foreign languages based on native language queries. Although the underlying technology for achieving such a search is relatively well understood, the appropriate interface design is not. The authors present three user evaluations undertaken during the iterative design of Clarity, a cross-language retrieval system for low-density languages, and shows how the user-interaction design evolved depending on the results of usability tests. The first test was instrumental to identify weaknesses in both functionalities and interface; the second was run to determine if query translation should be shown or not; the final was a global assessment and focused on user satisfaction criteria. Lessons were learned at every stage of the process leading to a much more informed view of what a cross-language retrieval system should offer to users

Which User Interaction for Cross-Language Information Retrieval? Design Issues and Reflections

A novel and complex form of information access is cross-language information retrieval: searching for texts written in foreign languages based on native language queries. Although the underlying technology for achieving such a search is relatively well understood, the appropriate interface design is not. This paper presents three user evaluations undertaken during the iterative design of Clarity, a cross-language retrieval system for rare languages, and shows how the user interaction design evolved depending on the results of usability tests. The first test was instrumental to identify weaknesses in both functionalities and interface; the second was run to determine if query translation should be shown or not; the final was a global assessment and focussed on user satisfaction criteria. Lessons were learned at every stage of the process leading to a much more informed view of what a cross-language retrieval system should offer to users

Which User Interaction for Cross-Language Information Retrieval? Design Issues and Reflections

A novel and complex form of information access is cross-language information retrieval: searching for texts written in foreign languages based on native language queries. Although the underlying technology for achieving such a search is relatively well understood, the appropriate interface design is not. This paper presents three user evaluations undertaken during the iterative design of Clarity, a cross-language retrieval system for rare languages, and shows how the user interaction design evolved depending on the results of usability tests. The first test was instrumental to identify weaknesses in both functionalities and interface; the second was run to determine if query translation should be shown or not; the final was a global assessment and focussed on user satisfaction criteria. Lessons were learned at every stage of the process leading to a much more informed view of what a cross-language retrieval system should offer to users

Usability testing for improving interactive geovisualization techniques

Usability describes a product’s fitness for use according to a set of predefined criteria. Whatever the aim of the product, it should facilitate users’ tasks or enhance their performance by providing appropriate analysis tools. In both cases, the main interest is to satisfy users in terms of providing relevant functionality which they find fit for purpose. “Testing usability means making sure that people can find and work with [a product’s] functions to meet their needs” (Dumas and Redish, 1999: 4). It is therefore concerned with establishing whether people can use a product to complete their tasks with ease and at the same time help them complete their jobs more effectively. This document describes the findings of a usability study carried out on DecisionSite Map Interaction Services (Map IS). DecisionSite, a product of Spotfire, Inc.,1 is an interactive system for the visual and dynamic exploration of data designed for supporting decisionmaking. The system was coupled to ArcExplorer (forming DecisionSite Map IS) to provide limited GIS functionality (simple user interface, basic tools, and data management) and support users of spatial data. Hence, this study set out to test the suitability of the coupling between the two software components (DecisionSite and ArcExplorer) for the purpose of exploring spatial data. The first section briefly discusses DecisionSite’s visualization functionality. The second section describes the test goals, its design, the participants and data used. The following section concentrates on the analysis of results, while the final section discusses future areas of research and possible development

Current Practices for Product Usability Testing in Web and Mobile Applications

Software usability testing is a key methodology that ensures applications are intuitive and easy to use for the target audience. Usability testing has direct benefits for companies as usability improvements often are fundamental to the success of a product. A standard usability test study includes the following five steps: obtain suitable participants, design test scripts, conduct usability sessions, interpret test outcomes, and produce recommendations. Due to the increasing importance for more usable applications, effective techniques to develop usable products, as well as technologies to improve usability testing, have been widely utilized. However, as companies are developing more cross-platform web and mobile apps, traditional single-platform usability testing has shortcomings with respect to ensuring a uniform user experience. In this report, a new strategy is proposed to promote a consistent user experience across all application versions and platforms. This method integrates the testing of different application versions, e.g., the website, mobile app, mobile website. Participants are recruited with a better-defined criterion according to their preferred devices. The usability session is conducted iteratively on several different devices, and the test results of individual application versions are compared on a per-device basis to improve the test outcomes. This strategy is expected to extend on current practices for usability testing by incorporating cross-platform consistency of software versions on most devices

A tale of two studies

Running user evaluation studies is a useful way of getting feedback on partially or fully implemented software systems. Unlike hypothesis-based testing (where specific design decisions can be tested or comparisons made between design choices) the aim is to find as many problems (both usability and functional) as possible prior to implementation or release. It is particularly useful in small-scale development projects that may lack the resources and expertise for other types of usability testing. Developing a user-study that successfully and efficiently performs this task is not always straightforward however. It may not be obvious how to decide what the participants should be asked to do in order to explore as many parts of the system’s interface as possible. In addition, ad hoc approaches to such study development may mean the testing is not easily repeatable on subsequent implementations or updates, and also that particular areas of the software may not be evaluated at all. In this paper we describe two (very different) approaches to designing an evaluation study for the same piece of software and discuss both the approaches taken, the differing results found and our comments on both of these

Usability study of the iACTwithPain platform: an online acceptance and commitment therapy and compassion-based intervention for chronic pain

Background: This pilot study aims to test the usability of the iACTwithPain platform, an online ACT-based intervention for people with chronic pain, to obtain information on which intervention and usability aspects need improvement and on expected retention rates. Methods: Seventy-three Portuguese women with chronic pain were invited to complete the first three sessions of the iACTwithPain intervention assess their quality, usefulness and the platform’s usability. Twenty-one accepted the invitation. Additionally, eight healthcare professionals working with chronic medical conditions assessed the platform and the intervention from a practitioner’s point of view. Results: This study presented a considerable attrition rate (71.43%) among chronic pain participants, with six completers. There were no significant differences in demographic or clinical variables between dropouts and completers except for completed education (participants who dropped out presented less education than completers). Reasons for dropout were related to difficult personal events occurring during the time of the intervention, lack of time, or having forgotten. There seemed to be an overall satisfaction with both the intervention, its contents and form of presentation of information, and the platform, concerning its design, appearance, and usability. Real image videos were preferred over animations or audio by chronic pain participants. Healthcare professionals emphasized the appealing and dynamic aspects of the animation format. Conclusion: This study informs the ongoing improvement of the iACTwithPain platform and provides valuable information on aspects researchers should consider while developing online psychological interventions for chronic pain. Further implications are discussed