scispace - formally typeset
Search or ask a question

Showing papers on "User interface published in 1980"


Journal ArticleDOI
TL;DR: There are ~eg:N ms:poets of aser~emt,xu{er ~rforma~ce tha~ sys*em designers sh~d sys~emarka{~ ~ e r.

945 citations


Book
14 Apr 1980
TL;DR: Interacting with Visual Interfaces on Mobile Devices, Investigating Entertainment and Learning in a Multi-User 3D Virtual Environment and more.
Abstract: Interacting with Visual Interfaces on Mobile Devices.- Identification Criteria in Task Modeling.- HCI-Task Models and Smart Environments.- Themes in Human Work Interaction Design.- Evaluating User Experience in Technology Pilots.- Interface Model Elicitation from Textual Scenarios.- Virtual Fixtures for Secondary Tasks.- How 'learnable' are CASE tools in diverse user communities?.- A Prospect of Websites Evaluation Tools Based on Event Logs.- Habbo Hotel - Academic Studies in Mixed Feelings.- Improving Accessibility to Governmental Forms1.- Communicability in multicultural contexts: A study with the International Children's Digital Library.- Facing the digital divide in a participatory way - an exploratory study.- User Interface Input by Device Movement.- An End User Development Model to Augment Usability of Rule Association Mining Systems.- Investigating Entertainment and Learning in a Multi-User 3D Virtual Environment.- Openphone User Engagement and Requirements Solicitation in Low Literacy Users.- Complex and Dynamic Data Representation by Sonification.- Collaborative Knowledge Building for Decision Support System Development.- Multitouch Sensing for Collaborative Interactive Walls.- Visualization of Personalized Faceted Browsing.

647 citations


Patent
22 Sep 1980
TL;DR: In this paper, a user interface device (UI device) for machine control is described, consisting of a video display capable of presenting desired images to the machine operator and a touch sensitive device capable of detecting operator requests by means of the operator touching the surface of the video display.
Abstract: This patent describes a user interface device (UI device) used for machine control. The UI device is comprised of a video display capable of presenting desired images to the machine operator and a touch sensitive device capable of detecting operator requests by means of the operator touching the surface of the video display. A standard keyboard may also be employed when typed responses are required of the operator or for infrequent use a QWERTY keyboard may be displayed on the Display. The UI device is controlled by a general purpose computer, which also controls the on-line machine. Visual elements presented to the user on the UI device's display include instructions in text (orthographic display), and images (imaginal display). Displayed images may include and log status indicators (E.g., meters, thermometers) and buttons which the operator can touch to signal control requests. The displayed images change dynamically so that only relevant indicators and valid control buttons are presented to the user at any given time (termed "conditional disclosure"), and the display format can be changed completely upon operator request, to allow for control of infrequently used or complex features (termed "progressive disclosure"). A set of schematics and flow charts are included to complete the disclosure of the system. The resultant interactive display enables a relatively untrained operator to a control a feature-rich or complex machine system.

186 citations


Journal ArticleDOI
TL;DR: A knowledge-based interactive sequential diagnostic system is introduced which provides for diagnosis of multiple disorders in several body systems and is capable of explaining to the user the reasoning process for its decisions.
Abstract: A knowledge-based interactive sequential diagnostic system is introduced which provides for diagnosis of multiple disorders in several body systems. The knowledge base consists of disorder patterns in a hierarchical structure that constitute the background medical information required for diagnosis in the domain under consideration (emergency and critical care medicine, in our case). Utilizing this knowledge base, the diagnostic process is driven by a multimembership classification algorithm for diagnostic assessment as well as for information acquisition [1]. A key characteristic of the system is congenial man-machine interface which comes to expression in, for instance, the flexibility it offers to the user in controlling its operation. At any stage of the diagnostic process the user may decide on an operation strategy that varies from full user control, through mixed initiative to full system control. Likewise, the system is capable of explaining to the user the reasoning process for its decisions. The model is independent of the knowledge base, thereby permitting continuous update of the knowledge base, as well as expansions to include disorders from other disciplines. The information structure lends itself to compact storage and provides for efflcient computation. Presently, the system contains 53 high-level disorders which are diagnosed by means of 587 medical findings.

110 citations


01 Sep 1980
TL;DR: This document discusses some aspects of the design of DEPAC and explains why the design is appropriate to the authors' computing environment.
Abstract: DEPAC is a user interface to a package of codes for the solution of the initial value problem for a system of ordinary differential equations. It is intended to make the codes in the package as easy as possible to use and, at the same time, to take full advantage of the underlying algorithms. A major objective of the design is to facilitate switching codes. The prologs for the three methods at present represented in DEPAC are given. This document discusses some aspects of the design of DEPAC. It explains why the design is appropriate to the authors' computing environment. It provides ideas, experience, and a discussion of issues which will assist researchers faced with a similar task in other environments.

91 citations


Proceedings ArticleDOI
01 Jul 1980
TL;DR: A set of prototyping and simulation tools has been developed to be used as an integral part of the specification and design process, including an interactive display building utility and a syntax-driven interactive dialogue controller.
Abstract: The design and development of user interfaces to interactive computer systems is enhanced by permitting designers to easily express their design concepts in concrete, comprehensive, and comprehensible working models.A set of prototyping and simulation tools has been developed to be used as an integral part of the specification and design process. These include an interactive display building utility and a syntax-driven interactive dialogue controller. The display builder is used to develop initial conceptual snapshots of system display appearance at selected points in the user/system dialogue. The dialogue controller interprets a grammatical description of input tools and system logic, using predrawn and dynamically constructed displays to simulate the external appearance of the desired end system.

54 citations


Proceedings ArticleDOI
R. G. G. Cattell1
14 May 1980
TL;DR: A user interface to a database designed for casual, interactive use is presented and it is proposed that such an interface could be used to supplement a query language or other interface to allow users both kinds of views of the data.
Abstract: A user interface to a database designed for casual, interactive use is presented. The interface is entity-based: the data display to the user is based upon entities (e.g., persons, documents, organizations) that participate in relationships, rather than upon relations alone as in the relational data model. Examples from an implementation of the system are shown, for a prototype personal database (PDB), developed in connection with the ZOG system at Carnegie-Mellon University (Robertson et al[1977]). Some details of the interface and associated issues concerning data display, data models, views, and knowledge-based assistance are presented. Experience with the prototype system suggests that the entity-based presentation is appropriate for types of casual interactive use that existing database interfaces do not address, such as browsing. It is proposed that such an interface could be used to supplement a query language or other interface to allow users both kinds of views of the data.

50 citations


Journal ArticleDOI

38 citations


Journal ArticleDOI
TL;DR: The authors report on their successful experience in using a virtual operating system that disentangles computing environments from their underlying operating systems and achieving inter-system uniformity at all three levels of user interface: virtual machine, utilities, and command language.
Abstract: Moving to a new system is costly and error-prone. The problem can be reduced through use of a virtual operating system that disentangles computing environments from their underlying operating systems. The authors report on their successful experience in doing this and achieving inter-system uniformity at all three levels of user interface: virtual machine, utilities, and command language.

35 citations


Journal ArticleDOI
TL;DR: A generalized editor that edits text, directories, binary core images, and certain operating system data with a single user interface is described.
Abstract: Text is not the only data that needs editing; for example, file deletion utilities edit directories. If all “editors” used the same command language, they would be easier to learn, remember, and code. This paper describes a generalized editor that edits text, directories, binary core images, and certain operating system data with a single user interface.

33 citations


01 Jan 1980
TL;DR: The purpose of this thesis is to present certain mechanisms and paradigms for building distributed systems with uniform interfaces and mechanisms for resource management which are well suited to a distributed environment.
Abstract: At the University of Rochester we have had five years of experience in the design and implementation of a multiple machine, multiple network system called RIG. It has been useful to distinguish two types of system service: The first is provided directly to the user through a user interface, or user-system interface. The user obtains these services by typing commands or requests which are satisfied by actions initiated by the user interface. The user interface should provide a common viewpoint for the user of distributed resources. The second type of system service is provided by programs or processes executing on behalf of the user. The user's program obtains these services by executing "system calls." The system software that interprets and satisfies these calls implements the system interface or program execution environment. In RIG, equal emphasis was given to user and system interfaces. Each was made as uniform and coherent as possible across all available resources. It is the purpose of this thesis to present certain mechanisms and paradigms for building distributed systems with uniform interfaces. Building on a base of processes communicating solely via messages, four key contributions to research in distributed systems are described: (1) Virtual Terminals are presented as the means for managing a large number of application programs per user. The Virtual Terminal Management System provides extensive facilities for editing text, the ability to save all output in disk-based data structures, and sophisticated mechanisms for the management of screen space. (2) Principles of command interaction are outlined which facilitate the use of distributed resources. Together with the Virtual Terminal Management System, the command interface serves to present an elegant, robust, and consistent interface between RIG and the user. (3) Mechanisms for resource management are presented which are well suited to a distributed environment. In particular, resource management is viewed fundamentally as a problem of process management. Processes may be created "by name" and registration facilities enable any process to register its interest in, for example, the death of any other process. (4) Paradigms are presented for how processes should be written and communicate. Of particular importance are the simple yet powerful mechanisms for error and exceptional conditional handling. Registration facilities are provided which enable any process to register its interest in exceptional events which occur with regard to any other process.

Patent
03 Dec 1980
TL;DR: In this paper, a user interface device (UI device) used for machine control is described, which consists of a video display (124) capable of presenting desired images to the machine operator and a touch-sensitive device (125), capable of detecting operator requests by means of the operator touching the surface of the video display.
Abstract: This invention relates to a user interface device (UI device) used for machine control. The UI device is comprised a video display (124) capable of presenting desired images to the machine operator and a touch-sensitive device (125) capable of detecting operator requests by means of the operator touching the surface of the video display (124). A standard keyboard (126) may also be employed when typed responses are required of the operator, or a QWERTY keyboard may be displayed on the display 124. The UI device is controlled by a general purpose computer (101) which also controls the on-line machine (102). Visual elements presented tothe user on the UI device's display (124) include instructions in text (orthographic display), and images (imaginal display). Displayed images may include and log status indicators (eg, meters, thermometers) and buttons which the operator can touch to signal control requests. The displayed images change dynamically, so that only relevant indicators and valid control buttons are presented to the user at any given time (termed "conditional disclosure"), and the display format can be changed completely upon operator request, to allow for control of infrequently used or complex features (termed "progressive disclosure"). A set of schematics and flowcharts are included to complete the disclosure of the system. The resultant interactive display enables a relatively untrained operator to control a feature-rich or complex system.

Journal ArticleDOI
TL;DR: The design of an interactive system, viewed as a set of constrained decisions based on data structure, control language, user interface, sytem versatility, extensibility, and portability is discussed.
Abstract: Among the most important criteria in the design and implementation of an interactive system for data analysis are: data structure, control language, user interface, sytem versatility, extensibility, and portability. The design of an interactive system, viewed as a set of constrained decisions based on these criteria, will be discussed. The concepts and considerations discussed in this article about the design of interactive systems are general in nature and are neither problem-specific nor discipline-specific. Specific examples from statistical packages and their designs are cited for illustration purposes only.

Proceedings Article
01 Oct 1980
TL;DR: A high-level graphical interface to databases which employs specialized knowledge about graphical symbols, the underlying database, and the database user's context in order to provide pictorial representations of data which is of concern to the user.
Abstract: This paper describes a high-level graphical interface to databases which employs specialized knowledge about graphical symbols, the underlying database, and the database user's context in order to provide pictorial representations of data which is of concern to the user. The approach combines techniques of graphics and knowledge representation to provide more complete and more perspicuously organized answers to user queries. Techniques are presented for the representation and use of the semantic knowledge about the database contained in the data model. The knowledge of the data model allows the system to augment the response to a query with information which is relevant but not specifically requested. It also enables the data to be organized in a manner which reflects the relative importance of each of the entities and attributes within the context of the user's question. Thus the answer to the user's question is broadened in a meaningful way to provide the user with a more complete perspective of the information in the database.

Proceedings Article
18 Aug 1980
TL;DR: This work discusses how schemas for each operation that the tool can perform, and for each kind of object known to the system, can be used by the tool-independent interface to provide a graceful interface to the tool they describe.
Abstract: Command interfaces to current interactive systems often appear inflexible and unfriendly to casual and expert users alike. We are constructing an interface that will behave more cooperatively (by correcting spelling and grammatical errors, asking the user to resolve ambiguities in subparts of commands, etc.). Given that present-day interfaces often absorb a major portion of implementation effort, such a gracefully interacting interface can only be practical if it is independent of the specific tool or functional subsystem with which it is used. Our interface is tool-independent in the sense that all its information about a particular tool is expressed in a declarative tool description. This tool description contains schemas for each operation that the tool can perform, and for each kind of object known to the system. The operation schemas describe the relevant parameters, their types and defaults, and the object schemas give corresponding structural descriptions in terms of defining and derived subcomponents. The schemas also include input syntax, display formats, and explanatory text. We discuss how these schemas can be used by the tool-independent interface to provide a graceful interface to the tool they describe.

Journal ArticleDOI
TL;DR: A description is given of MM/1, a family of user interfaces which can be used as a basis for interactive dialogues, and the thinking behind the interface is given, together with experience of its use in three different systems.
Abstract: This paper discusses the software interface between a computer system and its users, and how it can be made convenient and practical for both the users and implementors of systems. Consistency of interaction is essential, though it is argued that it is too early to define true standards. Standards must be based on experience of actual systems, and must meet specifications that can be justified from the performance of the best of such systems. As one contribution to such a specification, a description is given of MM/1, a family of user interfaces which can be used as a basis for interactive dialogues. MM/1 is suitable for both large and small computers. The thinking behind the interface is given, together with experience of its use in three different systems.

Proceedings ArticleDOI
23 Jun 1980
TL;DR: An effort is underway to improve the process of man-machine dialogue design and implementation by developing prototyping and simulation tools to be used as an integral part of the specification and design process.
Abstract: The design and development of user interfaces to interactive computer systems has suffered from the inability of designers to easily express their design concepts in concrete, comprehensive, and comprehensible working models. An effort is underway to improve the process of man-machine dialogue design and implementation by developing prototyping and simulation tools to be used as an integral part of the specification and design process. These include an interactive display building utility and a syntax-driven interactive dialogue controller.

Proceedings ArticleDOI
01 Jul 1980
TL;DR: The design concepts and languages of a geographic information system ATLAS, which contains semantic structure, topological structure and location structure, and GDDL, which constructs and maintains the database, are proposed.
Abstract: The design concepts and languages of a geographic information system ATLAS (Administration and Total Landuse Analysis Support system) are proposed.The database structure is designed based on the geographic information structure concepts which contain semantic structure, topological structure and location structure. For a flexible user interface, the system provides two languages) IGL (Interactive Geographic Language) and GDDL (Geographic Data Definition Language), whose functions are designed based on the geographic information structure concepts. IGL is an interactive end user language, which facilitates information retrieval under geographic and/or statistic conditions and thematic map production. GDDL is a language for a system manager who constructs and maintains the database.

Book ChapterDOI
01 Jan 1980
TL;DR: This paper surveys the state-of-the-art in the design and implementation of human-computer interactive systems and concludes with severalulations of principles for the design of user interfaces to such systems.
Abstract: This paper surveys the state-of-the-art in the design and implementation of human-computer interactive systems. Such systems are based on the technologies of computer processing and storage, of information display, and of interactive input to a computer. Examples of the use of display and input devices in person-machine dialogues are presented as well as examples of human-computer interactive systems that are dynamic media for human creativity and problem solving. The paper concludes with severalformulations of principlesfor the design of user interfaces to such systems.

Journal ArticleDOI
TL;DR: This research presents new insights, based on the way people learn to use computer graphics, which are leading to better designs for the user interface.
Abstract: New insights, based on the way people learn to use computer graphics, are leading to better designs for the user interface.

01 Oct 1980
TL;DR: Several suggestions for data base design are presented to improve system performance and response time, and thus to improve the user interface.
Abstract: : A satisfactory user interface is essential for a decision support system to gain acceptance, and system performance is an important component of the user interface Several suggestions for data base design are presented to improve system performance and response time, and thus to improve the user interface (Author)

Journal ArticleDOI
TL;DR: The paper describes the STATUS retrieval system, concentrating on the recent developments and improvements to the system, in particular, the use of pre‐and post‐processors that give much greater flexibility to the user interface and allow STATUS to be integrated into existing information systems.
Abstract: This paper shows how a free text, Boolean‐type retrieval system can be used to provide a wide range of information processes. The paper describes the STATUS retrieval system, concentrating on the recent developments and improvements to the system. In particular, the use of pre‐and post‐processors is discussed. These give much greater flexibility to the user interface and allow STATUS to be integrated into existing information systems. This is illustrated with examples from a library loans system.

Proceedings ArticleDOI
R. G.G. Cattell1
23 Jun 1980
TL;DR: The goal of the database subproject of Cedar is to provide a uniform prepackaged way to perform access to data structures, as contrasted to the current state of affairs in which Mesa programmers repeatedly re-invent the facilities the authors intend to provide to type, structure, index, link, robustly store, concurrently access, and cache data.
Abstract: Vast differences in terminology aside, there is considerable overlap between work in knowledge representation, programming language data types, and database models. Our current work on the Cedar programming environment has necessitated integrating a number of ideas in these areas.As part of the Cedar project in the Computer Science Lab at Xerox PARC, we have been constructing a database management system. The goal of the Cedar environment is to greatly increase our productivity by combining the best currently known principles from programming languages, programming tools, and user interfaces into a single integrated system. Cedar is based on the Mesa programming language [1]. The goal of our database subproject of Cedar is to provide a uniform prepackaged way to perform access to data structures, as contrasted to the current state of affairs in which Mesa programmers repeatedly re-invent the facilities we intend to provide to type, structure, index, link, robustly store, concurrently access, and cache data stored in the primary or secondary memory of one or more computers on a network.

01 Sep 1980
TL;DR: An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented, a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems.
Abstract: An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented. IPIP is a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems. It also significantly advances a number of capabilities that are offered commercially. IPIP capabilities range from support for multiple schemas and data models to support for distributed processing, configuration control, and data inventory management. IPIP exploits semantic commonality in features offered in various forms at different user interfaces in today's commercial systems. An integrated software architecture supports all user interfaces: programming languages, interactive data manipulation, and schema languages. This approach promotes simplicity and compactness in software and permits features to be offered symmetrically across all appropriate user interfaces.

Proceedings ArticleDOI
26 Jun 1980
TL;DR: Four different perspectives of the user interface are examined: (1) user motivation, (2) user-developer differences, (3) organization structure, and (4) the political perspective, which highlights certain legitimate system development issues and narrows the view of theuser interface.
Abstract: It has become increasingly popular for researchers to study management information system users and their relationships with system developers. Motivated by numerous reports of system failure, which were not technical in nature, investigators have sought a better understanding of the user interface. The ultimate objective of much of this research is to guide methodologies for user-oriented system development and design of systems which meet user needs more readily. In other words, the intent is to design systems which are behaviorally valid as well as technically valid.Such a quest necessarily requires us to draw upon concepts from the behavioral sciences. To study user behavior, interpersonal relationships and organizational settings, one must either invent new theories or use existing ones. The latter strategy is strongly recommended for many reasons not reiterated here. But within the behavioral sciences there are fundamental choices among perspectives, and these choices influence our view of the user interface quite profoundly.Adopting any one approach allows the investigator to see and understand certain phenomena but to ignore others. Like the blind man examining the elephant, each observer develops a “trained incapacity” to see the object from other viewpoints. As a result, alternative explanations of research findings are rarely considered, much less reported.The purpose of this paper is to examine four different perspectives of the user interface: (1) user motivation, (2) user-developer differences, (3) organization structure, and (4) the political perspective. Each highlights certain legitimate system development issues. However, each also narrows our view of the user interface. Awareness of these perspectives accomplishes two purposes. First, researchers will be more receptive to the alternative perspectives and aware of the consequences of their choices. Second, investigators will treat the user interface less naively, especially through increased sensitivity to the political factors in system development.

Journal ArticleDOI
TL;DR: A design exercise for the ECDIN ADABAS data base has been completed and parts of the existing ECDIn data base have been converted to the new system and the first tentative steps in this direction are described.
Abstract: The ECDIN (Environmental Chemicals Data and Information Network) project started in 1973. During the pilot phase of operation the feasibility of the system was demonstrated using a data base of 4000 compounds and the SIMAS information retrieval system. It was quickly realised that for ECDIN data management was as important as information retrieval and in November 1977, after a study of available software, the ADABAS data base management system was installed at JRC Ispra for ECDIN and other JRC data banks. A design exercise for the ECDIN ADABAS data base has been completed and parts of the existing ECDIN data base have been converted to the new system. The problems encountered and the solutions adopted are discussed. The user interface to ECDIN is still under development. When fully operational ECDIN will be available through EURONET to both casual and specialist users and, in consequence, at least two levels of user interface will be required: (a) a user friendly conversational language designed for the casual user and capable of dealing with the more common types of question, (b) a sophisticated query language capable of answering the more difficult questions, producing ''one-off'' reports and probably requiring both a specialist knowledge of the data base and a programmer oriented background. The first tentative steps in this direction are described.

Journal ArticleDOI
TL;DR: A review of the tools available for easing the tasks of constructing and modifying the user interface of CAD application programs.
Abstract: A review of the tools available for easing the tasks of constructing and modifying the user interface of CAD application programs.


Proceedings ArticleDOI
01 Jul 1980
TL;DR: A hidden surface algorithm similar to Myers' approach which combines the simplicity of a Z buffer with the efficiency of a Watkin's algorithm is implemented to satisfy the basic GCS design goal of device independence.
Abstract: Raster scanned graphics terminals provide several features not found in standard line drawing displays. Among them are area fill and an extensive color palette. Hardware support for such functions is becoming cost effective and available in a variety of forms. What is now needed is high level, device independent software that assists in the generation of and interaction with these terminals. To accomplish this, a project has been undertaken jointly by Sandia Laboratories, Purdue University, and MEGATEK Corporation to integrate solid image capabilities into the Graphics Compatibility System, GCS. GCS is a widely used, general purpose calligraphic graphics package. Due to the similarity of the GCS model to that of the GSPC Core System, GCS provides a timely test bed for solid image extensions to a line drawing package. This paper will summarize the capabilities being implemented, the method and motivation behind each function, and suggestions for further work.The heart of the extensions is a hidden surface algorithm similar to Myers' approach which combines the simplicity of a Z buffer with the efficiency of a Watkin's algorithm. Facilities will be provided for hidden line removal as well as hidden surface processing in order to satisfy the basic GCS design goal of device independence. In this way, random vector terminals as well as raster devices will benefit.If a user does not require hidden object processing then very little additional overhead will remain in those routines which have been called. Hidden surface processing may also be intermixed with wire frame drawings and text.Two remaining issues are the user interface for 3D object definition and the specification of lighting models. Since the Myers algorithm requires N sided polygons as input, a basic call has been provided for such definitions. Higher level constructs, called “shells” and “faces”, which facilitate creation of complex 3D bodies, have been implemented.The specification of lighting models is an area of considerable debate. It has been concluded that a choice of a few common models will be made available to the user. These include interpolated and noninterpolated shading (smooth and flat). Objects may be color-shaded or black-and-white. A hook is provided for user definition of more exotic lighting models.

Book
01 Jan 1980
TL;DR: Recent work performed to prepare the Vulnerability Model for operational use is described, including development of the user Interface Module (UIM), and easy-to-use conversational program which enables inexperienced or occasional users to set up and run VM simulations easily and reliably with little or no training.
Abstract: The Vulnerability Model (VM) is a computer model which simulates hazardous materials spills and computes the consequences to people and property from resulting fires, explosions, or toxic vapors. This report describes recent work performed to prepare the VM for operational use. Four specific tasks or developments are described: (1) development of the user Interface Module (UIM), and easy-to-use conversational program which enables inexperienced or occasional users to set up and run VM simulations easily and reliably with little or no training; (2) development of a series of VM output display routines which display the results of VM simulations on CRT terminals or hard copy plotters; (3) development of ready-to-use Geographical/Demographic files for Los Angeles and New York Harbors (a file for New Orleans already exists); and (4) performance of a number of VM spill simulations for selected chemicals in Los Angeles and New York Harbors to operationally test the UIM/VM system and to provide a hazard ranking of the selected chemicals.