This material is copyright. You must include this page with any portion of the book. Please refer to book web site for distribution conditions. Please note that as the book has been re-typeset for electronic distribution, page numbers may difer slightly from the original. CONTENTS Preface

Abstract not found

In this paper weinvestigate the appropriateness of formal specification languages for the description of user interface phenomena. Specifically,we are concerned with the distinction between continuously available information, whichwe call status, and atomic, non-persistent information, which we call events. We propose a hybrid model and notation to address status and event phenomena symmetrically.We demonstrate the effectiveness of this model for designing and understanding mixed control interaction, an especially important topic in the design of multi-user systems.

Model Restructured Abstract Model Detection Transformation Generation (Forward Engineering) (Reverse Engineering) Representation Representation Human Analyst Input 2 Several good surveys of representations for designing user interfaces exist [ABO89],[DIX93], [FOL90], [HAR89], [GRE87]. Almost all existing representations were developed for one or more development-oriented purposes: . Designing a new system (communication with implementers) . Analyzing usability or performance of an existing system (communication with interface designers) . Documenting an existing or developmental system (communication with end users) While these representations were developed to give the designer or analyst a framework for developing or improving an interface, they were not intended to support the recovery of a system-level interface specification from a legacy application. Design notations were developed to describe a "perfect world" - to organize the creation of a new system. They were not intended ...

In this paper we investigate a component-based approach to combining formal techniques and prototyping for user interface construction in which a single specification is used for constructing both implementations (prototypes) for experimentation and models for formal reasoning. Using a component-based approach not only allows us to construct realistic prototypes, but also allows us to generate a variety of formal models. Rapid prototyping allows the designs to be tested with end users and modified based on their comments and performance, while formal modeling permits the designer to verify mechanically specific requirements imposed on the user interface such as those found in safety- or security-critical applications. 1 Introduction User interfaces can be difficult and costly to construct; one recent survey estimates that half the development effort for an interactive application is spent on constructing the user interface [MR92]. It is natural to attempt to apply software engineering...

Physical disabled access is something that most museums consider very seriously. Indeed, there are normally legal requirements to do so. However, online disabled access is still a relatively novel field. Most museums have not yet considered the issues in depth. The Human-Computer Interface for their websites is normally tested with major browsers, but not with specialist browsers or against the relevant accessibility and validation standards. We consider the current state of the art in this area and mention an accessibility survey of some museum websites.

Achieving correct user interface software is difficult because such software is complex, highly interactive, modeless, concurrent, graphical, and has user-based real-time requirements. In this paper I propose developing a framework for applying formal methods to testing of user interface software. I survey relevant work in the areas of formal development of user interface software and specification-based testing. I then outline a case study based research plan to extend an existing specification-based testing framework to incorporate multiparadigm user interface specifications. KEYWORDS Human-Computer Interface, HCI, user interface, UI, formal methods, testing 1. INTRODUCTION A user interface (UI) is some boundary between a computer system, comprised of hardware and software, and a human user. UI software is a significant component of contemporary systems and graphical user interfaces (GUIs) are now almost universal. Confidence in the correctness of UI software is usually achieved ...