Models of interactive systems: a case study on programmable user modelling

Abstract

Models of interactive systems can be used to answer focused questions about those systems. Making the appropriate choice of modelling technique depends on what questions are being asked. We present two styles of interactive system model and associated verification method. We show how they contrast in terms of tractability, inspectability of assumptions, level of abstraction and reusability of model fragments. These tradeoffs are discussed. We discuss how they can be used as part of an integrated formal approach to the analysis of interactive systems where the different formal techniques focus on specific problems raised by empirical investigations. Explanations resulting from the formal analyses can be validated with respect to the empirical data.The first modelling style, which we term 'operational', is derived directly from principles of rationality that constrain which user behaviours are modelled. Modelling involves laying out user knowledge of the system and task, and their goals, then applying the principles to reason about the space of rational behaviours. This style supports reasoning about user knowledge and the consequences of particular knowledge in terms of likely behaviours. It is well suited to reasoning about interactions where user knowledge is a key to successful interaction. Such models can readily be implemented as computer programs; one such implementation is presented here.Models of the second style, 'abstract', are derived from the operational models and thus retain important aspects of rationality. As a result of the simplification, mathematical proof about selected properties of the interactive system, such as safety properties, can be tractably applied to these models. This style is well suited to cases where the user adopts particular strategies that can be represented succinctly within the model.We demonstrate the application of the two styles for understanding a reported phenomenon, using a case study on electronic diaries.

A model-based framework for classifying and diagnosing usability problems

“…2, a conceptual framework needs to be firstly developed, from which classification schemes can be systematically developed. Blandford et al (2004) made a distinction between a particular model and the underlying framework in the development of programmable user model. They stated that the framework encapsulates a generalized collection of guidelines for construction a model.…”

Automatic evaluation of assistive interfaces

“…al. [1] implement the Programmable User Model (PUM) using the Soar architecture. They developed a program, STILE (Soar Translation from Instruction Language made Easy), to convert the PUM Instruction Language into Soar productions.…”

Formal models for user interface design artefacts

“…One way to achieve this might be to take an existing approach to user modelling, such as PUM, and find ways to integrate this into our work. Developed initially as an evaluation tool for UIs, PUMs [42] have been subsequently adapted and used extensively by Blandford et al (see for example [2,3,7]) in approaches to integrating user models with design models and usability evaluation at early stages of the design process. It may be possible to integrate semi-formal PUMs with our presentation models and PIMs in a way that enables us to do things such as examine the correspondence between expected userbehaviours (from the PUM) and behavioural possibilities of the UI (from the presentation model and PIM) leading to a more thorough investigation of early design options.…”