Showing papers on "User interface published in 1975"

Implementation of integrity constraints and views by query modification

Abstract: Because the user interface in a relatonal data base management system may be decoupled from the storage representation of data, novel, powerful and efficient integrity control schemes are possible. This paper indicates the mechanism being implemented in one relational system to prevent integrity violations which can result from improper updates by a process. Basically each interaction with the data is immediately modified at the query language level to one guaranteed to have no integrity violations. Also, a similar modification technique is indicated to support the use of "views," i.e. relations which are not physically present in the data base but are defined in terms of ones that are.

Abstract readability as a factor in information systems

Abstract: Documents may be accessed by increasingly efficient retrieval of abstracts, but information will not be transferred unless the abstracts are read. It is suggested that the measurement of the readability of abstracts can provide an assessment of one phase of an information system: the system/user interface. Controlled reading levels for abstracts could result in more rapid processing of abstracts and a wider use of the information system. It was hypothesized that the use of readability principles in guidelines for abstracting would result in abstracts of lower reading levels than the source documents upon which they were based. Abstracts and their source documents were selected randomly from the information system supported by the Educational Resources Information Center (ERIC); readability scores were calculated using the Flesch Reading Ease formula. Comparisons among reading levels were made using analysis of variance for correlated data and Tukey's Honestly Significant Difference (HSD) test for post hoc comparisons. Results indicated that the reading level of abstracts was significantly higher than the reading level of source documents, but not higher than the reading ability of the intended audience. It was concluded that readability measurement provides one useful techinque for hte evaluation of abstracts.

RISS: a generalized minicomputer relational data base management system

Abstract: With the recent growth in popularity of low cost, relatively powerful minicomputers, it is clear that associated data base management systems are required. Nearly all of the minicomputer systems that are currently available commercially have at most rudimentary data base management capabilities. Consequently, in this paper we discuss the design and implementation of a minicomputer relational data base management system: the Relational Inquiry and Storage System (RISS). RISS provides a "naive" user interface, to allow nonprogrammers to deal routinely with a data base without the aid of a programmer, as well as an applications program interface. These interfaces facilitate data base access, modification, and restructure. RISS is a generalized and context-adaptable system, but it maintains a degree of efficiency guaranteeing cost-effective operation.

Partitions and principles for secure operating systems

Abstract: As part of the general goal of providing secure computer systems, the design of verifiably secure operating systems is one of the most important tasks. This paper addresses the problem by defining security in terms of a model and proposing a set of principles which should be satisfied. Four key operating system partitions are identified: user interface functions, user invoked services, background services, and the security kernel. Principles are then defined to insure that interface functions provide a safe initial environment for executing user programs, user called services are confined, background services have no access to user information, and the security kernel adequately protects stored information.

Search strategies and user interface.

Abstract: This paper discusses what in The Mead Corporation have found to be certain aspects of search strategy with respect to searching large data bases and certain problem areas that remain. The paper defines some problem areas, especially problem areas in the freeing-up of the interface language between the user and the search process. Four specific areas in the interface language are defined, and a recommendation is made concerning basic research into some linguistic meanings for the four areas.

Data Base User Languages for the Non-Programmer

Abstract: In light of the necessary investments, commercially available data base systems usually offer comparatively general-purpose interfaces These are suitable only for the data base specialist In order for a data base system to attract non-programmer users, interfaces must be provided that approximate the special user terminology and conceptualizations If, in particular, these users form a heterogeneous group, a variety of interfaces will be required Questions of interest are then the extent to which user interfaces should be standardized, the techniques which allow rapid implementation of new more specialized interfaces, or the procedure for selecting the most suitable interface for a given problem Based on the concept of hierarchy of abstract machines, the paper presents a possible approach to the solution of these questions Three examples will be introduced to critically examine the concept and demonstrate some of its merits and shortcomings

On the design of a user interface to large Fortran subroutine packages under IBM 360/370 OS

Abstract: An often encountered inconvenience when one uses a large subroutine package (e.g. IBMSSP) is that one faces the problem of selecting the proper subroutines in the proper sequence to execute the proper computation. This at times is difficult if not prohibitive because the algorithms employed by the subroutines are sophisticated and beyond the comprehension of the user. When this happens, the subroutine package becomes a frustration as much as a useful tool to the user. It is therefore desirable to split up such large subroutine packages into chapters of subroutines according to their functions and create control routines for each chapter. The purpose of these control routines is to interpret the arguments supplied by the user and then invoke the proper subroutines in the proper sequence for the computational solution.

An Approach to Providing a User Interface for Military Computer-Aided- Instruction in 1980

Abstract: : A recent needs study determined that most of the terminal requirements for military CAI applications can be satisfied with mainstream commercial terminals. Additional development, however, is likely to be required to satisfy two of the capabilities (limited graphics and prerecorded visuals). The expected architecture of commercial terminals will make it easy to modify and customize them to meet all the identified CAI needs. The military community is also expected to use computer networks to satisfy an appreciable portion of its requirements. Commercial terminals and available computer networks provide the basis for an effective and economical user interface to military CAI systems.