scispace - formally typeset
Search or ask a question

Showing papers on "User interface published in 1981"


Book
01 Jan 1981

662 citations


Journal ArticleDOI
Thomas P. Moran1
TL;DR: This article introduces and discusses a specific grammatical structure—the Command Language Grammar (CLG)—as a representational framework for describing the user interface aspects of interactive computer systems.
Abstract: This article introduces and discusses a specific grammatical structure—the Command Language Grammar (CLG)—as a representational framework for describing the user interface aspects of interactive computer systems. CLG partitions a system into a Conceptual Component (tasks and abstract concepts), a Communication Component (command language), and a Physical Component (display, keyboard, etc.), The components are further stratified into distinct Levels—a Task Level, a Semantic Level, a Syntactic Level, and an Interaction Level-each Level being a complete description of the system at its level of abstraction. Each Level's description contains procedures for accomplishing the tasks addressed by the system in terms of the actions available at that Level. That is, the system is described by progressive refinement. An extensive example, a small message-processing system, is described at all Levels in the CLG notation. CLG is discussed from three points of view: the Linguistic View sees CLG as elaborating the structure of the system's user interface and of the communication between the user and the system. The principal goal of CLG in this view is to lay out the space of command language systems. The Psychological View sees CLG as describing the user's mental model of the system. The main concern in this view is with the psychological validity of the CLG description. The Design View sees CLG as a series of representations for specifying the design of a system. CLG proposes a top-down design process in which the conceptual model of the system is first specified and then a command language is created to communicate with it.

542 citations


Journal ArticleDOI
TL;DR: This paper shows how first-order predicate calculus can be used as a language for formally stating modeling knowledge and how knowledge stated in this manner can be subjected to the resolution principle.
Abstract: In view of the growing prominence of corporate modeling, an important area of research concerns techniques for facilitating the design and utilization of models. In this paper we show how first-order predicate calculus can be used as a language for formally stating modeling knowledge. Furthermore, knowledge stated in this manner can be subjected to the resolution principle. The result is that application specific modeling knowledge need not be embedded in a computer program. Rather, it can be stored in a data base and utilized as needed by a problem processing system employing resolution techniques. Advantages of a decision support system taking an approach of this sort are considerable modeling flexibility, capacity for automating the model formulation and execution processes, and compatibility with a high-level user interface language.

115 citations


Journal ArticleDOI
TL;DR: Results indicate that both user and interface characteristics influence the use of the system options and the request for information in the problem-solving task.
Abstract: An exploratory study was conducted to analyze whether interface and user characteristics affect decision effectiveness and subject behavior in an interactive human/computer problem-solving environment. The dependent variables were performance and the use of the systems options. Two of the independent variables examined, experience and cognitive style, were user characteristics; the other three, dialogue, command, and default types, were interface characteristics. Results indicate that both user and interface characteristics influence the use of the system options and the request for information in the problem-solving task.

103 citations


Book
01 Jan 1981

67 citations


Journal ArticleDOI
A. J. Thadhani1
TL;DR: The relationship between computer response time and user performance, and the separation of user cost from system cost are explored, and strategies for effectively managing installations are presented.
Abstract: Interactive user productivity is a measure of effective communication between man and the computer. Explored in this paper is the relationship between computer response time and user performance, and the separation of user cost from system cost. Strategies for effectively managing installations are presented and discussed.

59 citations


Posted Content
TL;DR: In this article, the authors examined the relationship between various characteristics of a computer chargeback system, the quality of the user interface, user involvement and user attitudes about information systems services.
Abstract: Computer chargeback systems are installed to meet various dataprocessing objectives. One objective is to increase user involvementin decisions regarding information systems development and use.Presumably, increasing user involvement will result in more effectiveinformation systems.In a field study we examine the relationship between variouscharacteristics of a computer chargeback system, the quality of thechargeback system's user interface, user involvement and userattitudes about information systems services. Suggestions are givenboth for the practicing information systems manager and for futureinformation systems researchers.

55 citations


Proceedings ArticleDOI
29 Apr 1981
TL;DR: This paper introduces a high level nonprocedural language Form Operation by Example (FOBE) to manipulate forms in office systems and believes that it is user-friendly and sufficiently powerful for office environments.
Abstract: In this paper we introduce a high level nonprocedural language Form Operation by Example (FOBE) to manipulate forms in office systems. The form data model is selected as the basis for the user interface. The idea of query-by-example is applied to forms. A precise semantics definition of the language is given. FOBE has a predetermined structure. It combines the advantages of procedural and nonprocedural languages. We believe that it is user-friendly and sufficiently powerful for office environments.

53 citations


Proceedings ArticleDOI
09 Mar 1981
TL;DR: This paper presents some of principles of user-centered design and shows how they are achieved in the User Software Engineering project, which is intended to provide the applications developer with a development environment that supports the systematic specification and implementation of interactive systems.
Abstract: The successful construction of interactive systems requires the utilization of principles of user-centered design, combined with techniques for software engineering, in order to produce systems that are reliable, easy to use, and well adapted to user needs. This paper presents some of these principles and shows how they are achieved in the User Software Engineering (USE) project, which is intended to provide the applications developer with a development environment that supports the systematic specification and implementation of interactive systems.

45 citations


Proceedings ArticleDOI
TL;DR: The design of a user interface and an implementation for one such editor is described in language-independent terms and the design rationale is given.
Abstract: A language-directed editor combines the text manipulation functions of a general-purpose editor with the syntax-checking functions of a compiler. It allows a user to create and modify a program in terms of its syntactic structure. The design of a user interface and an implementation for one such editor is described in language-independent terms. The design rationale is given. The implementation is outlined in terms of its major data structures.

35 citations


Proceedings ArticleDOI
Steven R. Wood1
TL;DR: This paper describes a text-oriented display editor called Z, which considerably simplifies the design of the editor and presents the user with a simple but powerful model of program structure.
Abstract: Recently much attention has been focused on structure-oriented program editors that have specific knowledge about the syntax and semantics of a particular programming language [1, 4, 5, 18]. These editors provide many desirable features for editing programs. However, the user interface is constrained by the syntax and semantics of the target language, and editing operations that are simple in a text editor can be quite complicated in a structure-oriented editor. In addition, the user has an editor that is limited to a single language and must use a different editor for text editing. Existing implementations of structure-oriented editors use a parse-tree representation for a program along with a supporting lexical analyzer, parser, and pretty-printer; this representation significantly complicates the implementation of an editor.We believe that the most natural representation of programs is text and that the editor should be able to take advantage of the same visual cues that programmers use to understand their programs. With a text-oriented model of program structure, the editor is both a program editor and a document editor. As a program editor it provides features to support many different programming languages, such as LISP, APL, PASCAL, and BLISS. As a document editor it provides basic word-processing functions such as text justification and spelling correction. A text orientation considerably simplifies the design of the editor and presents the user with a simple but powerful model of program structure. This paper describes a text-oriented display editor called Z. Z is the production editor in the Yale Computer Science Department.

Journal ArticleDOI
M. R. DeSousa1
TL;DR: This paper describes an architectural approach that provides information interchange across a broad spectrum of user applications and office automation offerings and utilizes SNA for data transmission and communications control facilities.
Abstract: This paper describes an architectural approach that provides information interchange across a broad spectrum of user applications and office automation offerings. Some of the architectures described herein are currently implemented in existing IBM products. These and other architectures will provide the basis for document interchange capability between products such as the IBM 5520 Administrative System, the IBM System/370 Distributed Ofice Support System (DISOSS), and the IBM Displaywriter System. Specifically described is a document distribution architecture and its associated data streams. Transforms can be utilized to interchange between these data streams and others. A general overview of the architectures as opposed to a detailed technical description is provided. The architectures described are protocols for interchange between application processes; they do not address the specific user interface. The document distribution architectures utilize SNA for data transmission and communications control facilities.

Journal ArticleDOI
TL;DR: A general method for using disk files (instead of a more conventional parameter-passing mechanism) to transfer control information from a user interface to a set of related applications programs is described.
Abstract: A general method for using disk files (instead of a more conventional parameter-passing mechanism) to transfer control information from a user interface to a set of related applications programs is described. This technique effectively moves much of the user interface, including command decoding and limited parameter checking, from the applications programs to a table-driven executive.

Journal ArticleDOI
David K. Gifford1
TL;DR: Violet as mentioned in this paper is an experimental decentralized information system that allows the creation of decentralized applications by hiding the application's decentralized environment, such as a calendar system and a relational database manager.

Book ChapterDOI
01 Jan 1981
TL;DR: New performance-enhancing features of the DADM system include improved user interfaces, improved visibility of processes and data structures, structure sharing, improvements in inference-planning mechanisms, methods for dealing with incomplete information, utilization of semantic advice, and means for controlling recursive premises.
Abstract: A system for applying the theory of logical deduction and proof procedures to the accessing of data stored in conventional data management systems is described and illustrated with several examples. The DADM (Deductively Augmented Data Management) system has been developed along several dimensions of utility and performance to provide a vehicle for research on interactive techniques for reasoning with data, answering questions, and supporting on-line decision making. After illustrating present system operation by means of several examples, new performance-enhancing features of the system are described. These features include improved user interfaces, improved visibility of processes and data structures, structure sharing, improvements in inference-planning mechanisms, methods for dealing with incomplete information, utilization of semantic advice, and means for controlling recursive premises.

Proceedings ArticleDOI
Mark Green1
01 Aug 1981
TL;DR: A methodology for the design of interactive user interfaces and a list of desirable properties for a user interface design methodology, which has all of these properties.
Abstract: We present a methodology for the design of interactive user interfaces. This methodology provides the designer with a number of steps to be followed in the design of a user interface. Examples of a formal notation for describing user interfaces are presented. This methodology also provides the designer with a number of techniques for evaluating his design. We present a list of desirable properties for a user interface design methodology. Our design methodology has all of these properties.

Proceedings ArticleDOI
TL;DR: The primary design goal for Etude is to provide the user with substantial functionality in the editing and formatting of documents in the context of a system that is easy to learn and use.
Abstract: Etude is an experimental text processing system that is being developed in order to formulate and evaluate new approaches to the design of user interfaces for office automation tools. The primary design goal for Etude is to provide the user with substantial functionality in the editing and formatting of documents in the context of a system that is easy to learn and use.

Proceedings ArticleDOI
09 Mar 1981
TL;DR: A software user interface that enables programmers to provide and maintain online aids in an interactive system that display summary information, command descriptions, explanations of error messages, and other online documentation is described.
Abstract: This paper describes a software user interface that enables programmers to provide and maintain online aids in an interactive system. Through the interface, users are given a set of consistent and unobtrusive aids that display summary information, command descriptions, explanations of error messages, and other online documentation. The interface is presented here from the views of both the end-user and the programmer.

Journal ArticleDOI
TL;DR: In this article, a methodology for the design of interactive user interfaces is presented, which provides the designer with a number of steps to be followed in the design process of a user interface.
Abstract: We present a methodology for the design of interactive user interfaces This methodology provides the designer with a number of steps to be followed in the design of a user interface Examples of a


Journal ArticleDOI
TL;DR: Future software development systems will build on the success of Unix and Interlisp, adding central data bases to store in-progress project information accessible through sophisticated user interfaces.
Abstract: Future software development systems will build on the success of Unix and Interlisp, adding central data bases to store in-progress project information accessible through sophisticated user interfaces.

Journal ArticleDOI
TL;DR: The nature of the social research package user is discussed, and features of the conversational package SCSS are examined to point out the important lines of package development.
Abstract: The general purpose data analysis package is characterized by its user-oriented interface. This paper discusses the nature of the social research package user, and examines features of the conversational package SCSS to point out the important lines of package development. A discussion of these developments covers the areas of data structure flexibility, facilities for model manipulation and testing, self-documentation, adaptability to both expert and novice package users, as well as the facilities of table, graphics and statistics generation systems. Not all of these developments are equally feasible, because they put possibly conflicting pressures on the form of the user interface. The continuing number of users of data analysis packages will continue to make this an interesting area of user-interface development.

Journal ArticleDOI
TL;DR: DIALOG offers, with no extra effort from the applications programmer, not only a simple interface for first‐time users which gives complete instruction in using the program, but also a ‘command driven' interface for more experienced users.
Abstract: DIALOG is a collection of routines, including a main ‘driver’ program, which is used by an applications programmer as the user interface to interactive applications programs. The routines handle command analysis, data input and editing, as well as processing standard commands such as HELP. DIALOG offers, with no extra effort from the applications programmer, not only a simple interface for first-time users which gives complete instruction in using the program, but also a ‘command driven’ interface for more experienced users. DIALOG permits the quick and effective production of interactive applications software by programmers with no previous experience of writing such programs. User reaction to the programs so far produced and offered as part of a university computing service has been extremely favourable.

Proceedings ArticleDOI
09 Mar 1981
TL;DR: This paper describes an incremental programming environment (IPE) based on compilation technology, but providing facilities traditionally found only in interpretive systems.
Abstract: This document describes an Incremental Programming Environment (IPE) based on compilation technology, but providing facilities traditionally found only in interpretive systems. IPE provides a comfortable environment for a single programmer working on a single program. In IPE the programmer has a uniform view of the program in terms of the programming language. The program is manipulated through a syntax-directed editor and its execution is controlled by a debugging facility, which is integrated with the editor. Other tools of the traditional tools cycle (translator, linker, loader) are applied automatically and are not visible to the programmer. The only interface to the programmer is the user interface of the editor.

Proceedings Article
01 Jun 1981
TL;DR: This report is an anthology of papers prepared by the investigators which identify and discuss the design, development and implementation of such a user interface, and the development of a demonstrable prototype.
Abstract: : This report documents the three year investigation by the National Bureau of Standards into the technical issues involved in providing a uniform user and program environment for (possibly concurrent) access to multiple heterogeneous remote database management systems. This report is an anthology of papers prepared by the investigators which identify and discuss the design, development and implementation of such a user interface, and the development of a demonstrable prototype. (Author)

Journal ArticleDOI
TL;DR: This paper describes how the appropriate network frame can be found and displayed in response to specific explanation requests from the user, and describes the declarative nature of the aspect description which makes it easy to adapt NB to changes in and extensions to the tool description formalism.
Abstract: This paper is concerned with providing automatically generated on-line explanations to the user of a functional computer subsystem or tool about what the tool can and cannot do, what parameters and options are available or required with a given command, etc.. The explanations are given through the COUSIN interface system which provides a cooperative tool-independent user interface for tools whose objects, operations, input syntax, display formats, etc. are declaratively represented in a tool description data base. The explanations are produced automatically from this data base, with no incremental effort on the part of the tool designer, and in a single uniform style for any tool that uses COUSIN as its interface. The explanation facility takes the form of a fine-grained, tightly linked network of text frames supported by the ZOG menu-selection system. Exactly what information the net building program, NB, extracts from a tool description, and the way in which this information is formatted in the text frames is controlled by a second declarative data base called the aspect description. The declarative nature of the aspect description makes it easy to adapt NB to changes in and extensions to the tool description formalism, and to experiment with the structure of the explanation network. We also describe how the appropriate network frame can be found and displayed in response to specific explanation requests from the user.

Journal ArticleDOI
TL;DR: The major stadardization issues raised by EMS are described: message structure standards; delivery standards; address identification standards; and, user interface standards.

Journal ArticleDOI
TL;DR: Three APL functions to support principal components analysis are presented: a general-purpose function to obtain eigen values and eigen vectors, a more specialized function to convert these into the results commonly given by principal component analysis, and a user interface function that accesses filed data, offers flexibility in data selection, and produces labeled output.
Abstract: APL functions to support principal components analysis are presented: a general-purpose function to obtain eigen values and eigen vectors, a more specialized function to convert these into the results commonly given by principal components analysis, and a user interface function that accesses filed data, offers flexibility in data selection, and produces labeled output. A brief introduction to the logic and uses of principal components analysis is included. General-purpose support functions to simplify file use and to increase the range of options available to the user are also provided.

Book ChapterDOI
01 Jan 1981

Proceedings ArticleDOI
01 Jan 1981
TL;DR: The hardware configuration, software organization, and applications software for the NASA IKONAS color graphics display system are described and ongoing and planned work for image segmentation/generation, specialized graphics procedures, and higher level language user interface are discussed.
Abstract: The hardware configuration, software organization, and applications software for the NASA IKONAS color graphics display system are described. The systems were created at the Langley Research Center Display Device Laboratory to develop, evaluate, and demonstrate advanced generic concepts, technology, and systems integration techniques for electronic crew station systems of future civil aircraft. A minicomputer with 64K core memory acts as a host for a raster scan graphics display generator. The architectures of the hardware system and the graphics display system are provided. The applications software features a FORTRAN-based model of an aircraft, a display system, and the utility program for real-time communications. The model accepts inputs from a two-dimensional joystick and outputs a set of aircraft states. Ongoing and planned work for image segmentation/generation, specialized graphics procedures, and higher level language user interface are discussed.