Showing papers on "User modeling published in 1985"

The University of Alberta user interface management system

Abstract: In this paper the design and implementation of the University of Alberta user interface management system (UIMS) is discussed. This UIMS is based on the Seeheim model of user interfaces, which divides the user interface into three separate components. The Seeheim model of user interfaces is discussed along with its relationship to the design of UIMSs. The techniques used to design the three user interface components are briefly presented. A mixture of interactive and written notations are used in the design of the user interface. Some interesting features of this UIMS are interactive screen and menu layout, support for three dialogue notations, flexible interface to the application program, ability to adapt to different users, and the use of concurrent processes in user interface implementation The techniques used in the implementation of this UIMS are discussed.

UMFE: a user modelling front-end subsystem

Abstract: The paper argues that user models are an essential component of any system which attempts to be “user friendly”, and that expert systems should tailor explanations to their users, be they super-experts or novices. In particular, this paper discusses a data-driven user modelling front-end subsystem, UMFE, which assumes that the user has asked a question of the main system (e.g. an expert system, intelligent tutoring system etc.), and that the system provides a response which is passed to UMFE. UMFE determines the user's level of sophistication by asking as few questions as possible, and then presents a response in terms of concepts which UMFE believes the user understands. Investigator-defined inference rules are then used to suggest additional concepts the user may/may not know, given the concepts the user indicated he or she knew in earlier questioning. Several techniques are discussed for detecting and removing inconsistencies in the user model. Additionally, UMFE modifies its inference rules for individual users when it detects certain types of inconsistencies. UMFE is a portable domain-independent implementation of a system which infers overlay models for users. UMFE has been used in conjunction with NEOMYCIN; and the paper contains several protocols which demonstrate its principal features. The paper concludes with a critique of UMFE and suggestions for enhancing the current system.

The Real Estate Agent: Modeling Users By Uncertain Reasoning

Abstract: Two topics are treated here. First we present a user model patterned after the stereotype approach (Rich, 1979). This model surpasses Rich's model with respect to it's greater flexibility in the construction of user profiles, and it's treatment of positive and negative arguments. Second, we present an inference machine. This machine treats uncertain knowledge in the form of evidence for and against the accuracy of a proposition. Truth values are replaced by the concept of two-dimensional evidence space. We discuss the consequences of the concept, particularly with regard to verification. The connection between these two topics is established by implementation of the user model on the inference machine.

A typology of management information systems users and its implications for user information satisfaction research

Abstract: User Information Satisfaction (UIS) has emerged as the major surrogate for the effectiveness of Management Information Systems (MIS) in organizations. While the concepts of “information” and “satisfaction” have been researched extensively, we argue that our understanding of the MIS user is inadequate. This inadequacy is compounded by the rapidly changing information technology which has tended to blur the traditional distinctions between users and non-users and is rendering obsolete the implicit assumption of the functionally homogeneous user underlying a wide spectrum of studies. Based on a detailed survey of the literature, we propose a typology of users consisting of three categories: direct user, autonomous user, and indirect user. Direct user is someone who interfaces directly with the computer-based information systems, working with one or more systems, largely designed, implemented, and maintained by the MIS/Data Processing (DP) department or receives periodic computer reports. Autonomous user develops and uses simple systems and/or application programs he or she needs, either individually or in small groups of users. This class of users possesses some amount of computing skills and makes use of a variety of tools such as general purpose, commercial software, user-friendly operating systems, personal computers (PCs), workstations and higher level programming languages. The third category of users—indirect users—are typically managers in the higher levels of the organizational hierarchy whose interface with the computer is mediated by staff analysts or assistants. A certain degree of overlap across the categories is to be expected. The implications of the typology for UIS research in particular and MIS research and practice in general are discussed.

User Interface Design: Generative User Engineering Principles

Abstract: Publisher Summary This chapter explains generative user engineering principles as a means to design systems, which are not only internally consistent but which are compatible with user expectations to a greater extent than is normally possible. The intention has been to demonstrate the potential for higher-order guiding principles that can help bridge the gap between designers and users. Generative user-engineering principles are easily understood and used both by user and designer in their respective forms. They can be expressed in such terms that (1) the user interface may be designed top-down, using gueps as guidelines to select appropriate low-level features; (2) the user has a sound basis on which to construct an understanding of the system, even before using it; (3) the user may generalize his knowledge reliably; the user is confident as to what has happened and does not need debugging skills; (4) the user is encouraged to use his skills fully. Gueps can help enhance the view that what the user does is real and not abstract; This is especially motivating; and (5) the designer can use gueps to meet clearly defined user expectations, often with specific techniques. Often the gueps can be strongly formalized. Having once suggested a basis for the user model, the designer is under an obligation to ensure its coherent implementation through careful system design, which should maintain the model as understood by the user—this approach will entail evaluation and retrospective refinement.

The design of graphical user interfaces

Abstract: A new approach to the design of graphical user interfaces is presented. This approach is based on a design methodology and a set of design tools supporting this methodology. The design methodology is motivated by research in both ergonomics and software engineering. It consists of seven orthogonal design tasks. Each of these design tasks has one well defined goal and a document that records the results of the task. The division of the design process into tasks allows the designer to concentrate on one aspect of the design at a time and gives the design manager the ability to establish milestones. A unique feature of this design methodology is its concentration on design evaluation and correctness. A consistent set of tools has been developed to support this design methodology. The most important tools are a user modeling language for describing the user's view of the problem and the user interface, and a specification language for user interfaces. The user modeling language is based on the concepts of objects and operators. The specification language is based on state machines. The combination of these two languages covers all four levels in the language model of user interfaces proposed by Foley. Techniques have been developed for showing the compatibility of different descriptions of the user interface and for calculating important ergonomic measures given a description of the user interface.

VIE-DPM: A User Model in a Natural-Language Dialogue System

Abstract: User modelling is becoming recognized as a key issue in the design of cooperative dialogue systems. Assumptions about the beliefs, goals and plans of the user are seen as necessary prerequisites for a system to be capable of exhibiting user-oriented dialogue behaviour. This paper gives a survey of VIE-DPM, the user model in the natural language dialogue system VIE-LANG. In VIE-DPM, specific kinds of inferences about the user’s beliefs and wants are generated from his natural-1anguage input to the system, as well as from the system’s replies to the user. These assumptions are stored in a comprehensive representation system and can be used for supporting other components of VIE-LANG.

A knowledge-based approach to data management for intelligent user interfaces

Abstract: An intelligent user interface (POISE) is described that provides facilities for defining and supporting higher-level user tasks. Although an object-based data model forms an important part of the POISE system, other types of knowledge such as task descriptions and tool descriptions are required. The management of instantiations of the task and object descriptions is a complex process because POISE both predicts user actions and allows multiple, competing interpretations of user actions. In this paper, we describe how the knowledge base (including the object data model) is defined and used by the intelligent interface. We also describe an implementation of the knowledge base in a frame-based representation language.

Issues Pertaining to the Design of a User Interface Management System

Abstract: We reported at the GIIT Workshop our experiences in designing and implementing a prototype Interaction Handling Package called the Abstract Interaction Handler (AIH) In keeping with the terminology that has evolved since that Workshop, this paper will refer to the AIH as a User Interface Management System (UIMS) This paper reports our experiences and realizations beyond the Seattle Workshop [GIIT83] We have been proceeding in two directions

Knowledge-based user interface design

Abstract: A key problem in user interface design is delivering the design model on which a program is based in terms of the running software that users actually have to deal with. This article presents a methodology for helping programmers to explicitly state a design model and link it to the actual functions and data of the programs. Terms in the model are defined according to their relationship to a set of prebuilt abstract categories. The model so defined forms an explicit conceptual framework that enforces the consistency of the programmers' design, and provides the basis of user understanding of the program. Because the model is linked to actual program software, the connection of user understanding to the running code - the real user interface - is thus defined in terms of the explicit model. The methodology is presented in terms of techniques implemented in the Consul system, a knowledge-based environment for the design of integrated office automation software.

On Models and their Rôle in the Use of Computers

Abstract: When studying systems development projects a lack of consideration for training and education is often observed. A typical reason is that management is unwilling to spend the money required; all they will offer is a short introduction to ''how to push the buttons''. The hypothesis brought forward in this paper is that there is a lack of understanding for the necessity to deal with training and education already during the design process. Some vendors are aware of this situation. Their solution to the problem seems to be to develop computer applications which are easy to learn . The ''easy-to-learn syndrom'' leads to a tendency towards development of computer applications which are not sufficiently powerful to accomplish the tasks they have to deal with. Learnability instead of efficiency becomes the main goal. Instead I will propose this solution to the problem: ''Develop computer applications, which are easy to teach.'' A promising path to follow seems to be to base the development of a computer application on consistent conceptual models, which are based on concepts from the area of application. Such models must be developed during the systems development process to be used both for further design, during teaching and training, and during interaction with the computer application. A model for this purpose is here called a user model. My purpose with this paper is to try to look at user models and their use mainly from the users' point of view, and from that perspective point at some paths, which lead towards a deeper understanding of the subject.

Adaptive staging and advancement of user-computer interaction skills in office environments

Abstract: A research project has been initiated to study the design of powerful user-network interface systems which will facilitate user interaction but not constrain the user. That user is considered to be the office worker who is not a computer specialist. Our general approach is to utilize what is known from computer science and to blend that with relevant knowledge from psychology (especially learning theory) toward tailoring an intelligent, display-based workstation for the special needs of such office workers. More specifically, we are working on a prototype system which will assist and guide the user toward building up increasingly complex intellectual skills. We are not interested in superficial simplicity; instead we want the user to be able to advance his/her understanding of the technology by progressing through carefully structured stages of learning, encompassing the spectrum of very simple to very complex computer-aided tasks. Along the way, the system will provide special forms of adaptation (using expert systems techniques) as well as network-wide context (with supportive, parallel display channels).

Human Factors in Rule-Based Systems.

Abstract: : This report summarizes several experiments investigating the impact of mental models and cognitive consistency on user/expert system interaction. Results indicate that user/expert system combined problem solving performance significantly improves if the user has a good mental model of expert system processes. Furthermore, 'cognitive consistency' between the user and system problem solving procedures only degrades performance in situations where users do not have a good mental model. Some practical implications of this research is discussed. Keywords: Man machine interface. (Author)

Dynamic user profile in information retrieval (abstract only)

Abstract: Recently a model that incorporates user profiles for a priori query improvement has been proposed.* By personalizing the user query, we obtain two immediate and important advantages. It is possible to retrieve broader range of documents, part of which would not be brought to the user's attention if only queries were used. It is also possible to tailor the retrieved information to a particular user's interests and preference. Since a user's interest will probably be changed as time goes, it seems more appropriate that document space should not only change but have different density which reflects the weights of the information in user profile. Dynamic user profile issues and design are considered. Conversion process of a Boolean query into a standardized form for incorporating user profile into the conventional Boolean system is also considered.

The Role of a User’s System Model, and its Relevance to User Interface Management

Abstract: Of the major attributes of an interactive computer system — examples of which range from cash dispensers to engineering design workstations — the command dialogue is recognized as being particularly vital. A good command dialogue is not only easily learned, but is then essentially instinctive to the user, so that conscious thought can be directed instead to the real problem at hand. In contrast, a poor command language is difficult to learn, intrudes — by reason of the need for conscious thought — upon the main task, and may well be unsympathetic in the sense that command errors will often have catastrophic consequences.

Report on the User’s Conceptual Model

Abstract: The members of Working Group Omega originally belonged to Working Group Beta and, therefore, their deliberations ought to be seen in the context of that Working Group. Already at Seillac II (Guedj et al. 1980), the issue of the user’s conceptual model (UCM) received serious attention. We felt that the time was ripe to make an attempt at the formal specification of such user conceptual models. As a starting point we take the following definition of a UCM: A UCM is the set of all concepts and conceptual relations possessed by a (human) user with respect to some set of entities. To each UCM there corresponds a universe of discourse that is the expression of those concepts and conceptual relations. The M-notation, introduced in (Mac an Airchinnigh 1984), may be used as a basis for further development. Specifically, a user u possesses a conceptual model M of some application domain a. This UCM may then be denoted by M(u, a). It must be emphasised that such UCMs exist solely and entirely in the minds of their owners! The next step is to consider how to represent such UCMs. The following section contains the details.

Maintenance Personnel Performance Simulation (MAPPS) model. Users' Manual

Abstract: This report (MAPPS User's Manual) is the last report to be published from this program and provides detailed guidelines for utilization of the MAPPS model Although the model has been developed to be highly user-friendly and provides interactive means for controlling and running of the model, the user's manual is provided as a guide for the user in the event clarification or direction is required The user will find that in general the model requires primarily user input that is self explanatory Once initial familiarization with the model has been achieved by the user, the amount of interaction between the user's manual and the computer model will be minimal It is suggested however that even the experienced user keep the user's manual handy for quick reference 5 refs, 10 figs, 7 tabs

Application Systems Planning

Abstract: The activities of the MIS organization can profoundly influence the effectiveness and efficiency of the user community. Through the development and use of an application systems plan, MIS management can improve user relations while effectively managing the backlog of new user requests. This is accomplished by providing the focus and direction necessary to solve the right problem in the right sequence with the right resources.

Impacts of query specification mode and problem complexity on query specification productivity of novice users of database systems

Abstract: With the increased demand for the utilization of computerized information systems by business users, the need for investigating the impact of various user interfaces has been well recognized. It is usually assumed that providing the user with assistance in the usage o-f a system would significantly increase the user's productivity. There is, however, a dearth of systematic inquiry into this commonly held notion to verify its validity in a scientific fashion. The purpose of this study is to investigate the impact of system-provided user assistance and complexity level of the problem on novice users' productivity in specifying database queries. The study is theoretical in the sense that it presents an approach adopted from research in deductive database systems to attack problems concerning user interface design. It is empirical in that it conducts an experiment in a controlled laboratory setting to collect primary data for the testing of a series of hypotheses. The two independent variables are system-provided user assistance and problem complexity, while the dependent variable is the user's query specification productivity. Three measures are used as separate indicators of query specification productivity: number of syntactic errors, number of semantic errors, and time required for completing a query task. Due to the lack of a well-defined metric for user assistance, the study first presents a generic classification scheme for relational query specification. Based on this classification scheme, two quantitative metrics for measuring the amount of user assistance in terms of prompts and defaults were developed. The user assistance is operationally defined with these two metrics. Four findings emerge as significant results of the study. First, user assistance has a significant main effect on all of the three dependent measures at the 1 percent significance level. Second, problem complexity also has a significant impact on the three productivity measures at the 1 percent significance level. Third, the interaction effect of user assistance and problem complexity on the number of semantic errors and the amount of time for completion is significant at the 1 percent level. Fourth, Although this interaction effect on the number of syntactic errors is not significant at the 5 percent level, it is at the 10 percent level. More research is needed to permit a thorough understanding of the issue of user interface design. A list of topics is suggested for future research to confirm or to modify the findings of this study.

The use of Multi-Level Adaptable user Interfaces in Improving User-Computer Interaction

Abstract: Users of interactive computer systems will typically display a wide range of computing experience, a fact which is rarely taken into account when user interfaces are constructed. The difficulties encountered by users using a rigid user interface are highlighted, and the role of adaptable user interfaces in the process of improving user-computer interaction is outlined. Particular emphasis is placed on multi-level user interfaces, where each level of the interface is intended to satisfy the needs of a specific class of user. Consideration is given to the use of multi-level interfaces in encouraging users to advance to higher experience levels as their knowledge grows. The difficulties presented during implementation of such complex interfaces are highlighted and a methodology for the specification and design of interactive systems and their user interfaces which encourages the use of sophisticated user-computer interaction is described. A prototype Dialogue Development System has been produced which supports the use of this methodology with the Ada* programming language. The appropriateness of this approach to programming interactive systems in Ada and other languages is discussed.