Object‐oriented specification of user interfaces

Abstract

This paper presents an object‐oriented approach for the specification of graphical user interfaces. Specification starts with the analysis of the end user's operations. The user interface is then designed on the basis of this analysis. Operation analysis is followed by structure and component specification which presents the dialogue structure of the application and the contents of each dialogue. Visualization produces the final screen layouts, and task specification documents the usage of the user interface for the purpose of creating user's guides. The method presented in this paper makes it easier for a designer to take the end user's needs into account. Still, it does not automatically guarantee good quality user interfaces. The top‐down nature of the method allows the designer to concentrate on the most important aspects of the user interface and split the design procedure into manageable pieces. Also, the visibility of the process allows the designer to communicate with other people while specifying the user interface. This paper connects the method with the object‐oriented specification of entire applications. It briefly explains the connections with object‐oriented analysis and design, and demonstrates how to implement the specified user interface in an object oriented fashion. The approach presented in this paper is being applied in the development of a large network management system with about two million lines of C++ code running in the XII environment. Still, the method does not require the specification being implemented with any specific windowing system. The only requirement is that the user interface is based on graphical elements, such as dialogues, push‐buttons and text fields.

Refining temporal criteria to classify collaborative systems

“…A user interacts with the objects through a graphic interface. The users do not feel that they interact with a user interface but with the objects themselves, due to the fact that they use mental models to describe, explain, and predict the application behaviour (Jaaksi, 1995). These mental models are representations of reality that give meaning to the objects and explain the associations that exist among them.…”

Integrating use-case analysis and task analysis for interactive systems

“…Thus, the dialog model can be used to identify user-interface components and the structure between the components. The rest of this section describes how to derive a dialog model from the task model (this is a contrast to [9] which identifies dialogs first and then allocates tasks to the dialogs).…”