Automated Deduction and Usability Reasoning

Abstract

Building systems that are correct by design has always been a major challenge of software development. Typical software development approaches (and in particular interactive systems development approaches) are based around the notion of prototyping and testing. However, except for simple systems, testing cannot guarantee absence of errors, and, in the case of interactive systems, testing with real users can become extremely resource intensive and time-consuming. Additionally, when a system reaches a prototype stage that is amenable to testing, many design decisions have already been made and committed to. In fact, in an industrial setting, user testing can become useless if it is done when time or money is no longer available to substantially change the design. To address these issues, a number of discount techniques for usability evaluation of early designs were proposed. Two examples are heuristic evaluation, and cognitive walkthroughs. Although their effectiveness has been subject of debate, reports show that they are being used in practice. These are largely informal approaches that do not scale well as the complexity of the systems (or the complexity of the interaction between system and users) increases. In recent years, researchers have started investigating the applicability of automated reasoning techniques and tools to the analysis of interactive systems models. The hope being that these tools will enable more thorough analysis of the designs. The challenge faced is how to fold human factors’ issues into a formal setting as that created by the use of such tools. This article reviews some of the work in this area and presents some directions for future work.

Considering Context and Users in Interactive Systems Analysis

“…This new approach will be dealt with in the next section. 2 See http://www.di.uminho.pt/ivy 3 To be precise, two versions of SMV are currently being maintained and developed: Cadence SMV, by Cadence labs, and NuSMV. In the current context are using NuSMV.…”

“…We are particularly interested in seeing how we can build on the work developed in [4,2] to take into consideration models/assumptions about the users and the context of usage of the systems.…”

“…The techniques that are developed here are as important in intelligent and mobile systems where action inference (qua mode) is based on preferences, or location, or history or other elements that can be described as context. The example addresses the design of the Mode Control Panel (MCP) of an MD-88 aircraft (see figure 1), and was developed using MAL interactors [4,2]. …”

“…In the approach put forward in [4,2] For a description of the MAL interactors language the reader is directed to [2]. Here the focus is not so much on the particular language being used but in what is being expressed.…”

GUIsurfer: A Reverse Engineering Framework for User Interface Software

“…The term GUI reasoning refers to the process of validating and verifying if interactive applications behave as expected (Berard, 2001;Campos, 1999;d'Ausbourg et al, 1998). Verification is the process of checking whether an application is correct, i.e.…”