Showing papers on "User interface published in 1974"
1 Jul 1974
TL;DR: A comprehensive power system analysis package, PSS/2, is described which has been developed specifically for use with dedicated computers and allows load flow, short-circuit, and dynamic simulation work, data base maintenance, and printed report preparation to be handled in the interactive mode at lower cost than could be possible by alternative batch or time-shared computing methods.
Abstract: The analysis of power system performance has always been enhanced by close interaction between engineer and computation, and recent developments in high-speed displays, minicomputer capacity, and computational technology are encouraging major revisions of computing practices for power system analysis. A comprehensive power system analysis package, PSS/2, is described which has been developed specifically for use with dedicated computers. This dedicated computer approach allows load flow, short-circuit, and dynamic simulation work, data base maintenance, and printed report preparation to be handled in the interactive mode at lower cost than could be possible by alternative batch or time-shared computing methods. The subjects covered are data organization, computational techniques, user interface, and operational experience.
37 citations
IBM1
TL;DR: The language includes many special features which permit quick and precise specification of terminal behavior and is best suited for problems that are currently being described informally by word statements.
Abstract: This correspondence describes a special purpose Asynchronous Circuit Design Language (ACDL) for specifying the terminal behavior of asynchronous sequential circuits. The language is a valuable tool for formalizing and documenting asynchronous designs, as well as providing a user interface to a completely automated synthesis system. The language includes many special features which permit quick and precise specification of terminal behavior and is best suited for problems that are currently being described informally by word statements.
2 citations
TL;DR: This paper describes the incorporation of a graphics facility into an existing interactive system with the importance of an inexpensive system with a simple user interface.
Abstract: This paper describes the incorporation of a graphics facility into an existing interactive system. Emphasis is placed on the importance of an inexpensive system with a simple user interface. Details of some implementation considerations are given.
2 citations
1 Jan 1974
TL;DR: A scheme making terminal recognition almost invisible to the user is described, which recognizes the following terminal types: the IBM 2741, and ASCII terminals operating at 110, 150, and 300 baud.
Abstract: Economy and flexibility provide the motivation for using a single set of computer ports for various terminal types. To do this, the communications controller must adapt to the different terminal characteristics. This, in turn, requires that the controller recognize the type of terminal. Many terminal speed recognition algorithms require the user to type a terminal identification character before entering the first command. Entering an identification character detracts from the user interface to the computer. A scheme making terminal recognition almost invisible to the user is described. The implementation recognizes the following terminal types: the IBM 2741, and ASCII terminals operating at 110, 150, and 300 baud. While the algorithm is programmed on the IBM 3705 Communications Controller, it could be applied to other controllers. To make this easier, the algorithm is described in detail, and the techniques generalized.
TL;DR: It is argued that it is essential to shift the emphasis from an over pre‐occupation with programming languages and program development techniques to the design of a good interface for the occasional user.
Abstract: Summary The emphasis of this paper is upon man and machine engaged in interaction where ‘man’ is the occasional user and ‘machine’ is a terminal. It is argued that it is essential to shift the emphasis from an over pre‐occupation with programming languages and program development techniques to the design of a good interface for the occasional user. The aim of this paper is to encourage all users to make sure that the computer professionals provide an optimum interface for the casual user by the development of appropriate standards and by the full exploitation of the equipment available.