Gary H. Sockut

Office-by-example: an integrated office system and database manager

Office-by-Example (OBE) is an integrated office information system that has been under development at IBM Research. OBE, an extension of Query-by-Example, supports various office features such as database tables, word processing, electronic mail, graphics, images, and so forth. These seemingly heterogeneous features are integrated through a language feature called example elements. Applications involving example elements are processed by the database manager, an integrated part of the OBE system. In this paper we describe the facilities and architecture of the OBE system and discuss the techniques for integrating heterogeneous objects.

GRAQULA: a graphical query language for entity-relationship or relational databases

Abstract GRAQULA is a graphical language for querying and updating a database. One version of GRAQULA provides a user interface for the entity-relationship data model, and another version (with almost identical syntax) provides a user interface for the relational model. Each version is relationally complete, and each depicts relationships (or expected joins) graphically, GRAQULA provides logical operations (e.g. negation) on graphical objects; these operations have user-specified scopes, allow nesting, and can involve existential or universal quantification. Aggregates (e.g. average) also have user-specified scopes. Queries can invoke other queries, and users and queries can pass parameters to queries. The design reflects a specified set of goals, including expressive power, consistency, and limitation of required memorization.

Two-dimensional specification of universal quantification in a graphical database query language

A technique is proposed for specifying universal quantification and existential quantification (combined with negation) in a two-dimensional (graphical) database query language. Unlike other approaches that provide set operators to simulate universal quantification, this technique allows a direct representation of universal quantification. Syntactic constructs for specifying universal and existential quantifications, two-dimensional translation of universal quantification to existential quantification (with negation), and translation of existentially quantified two-dimensional queries to relational queries are presented. The resulting relational queries can be processed directly by many existing database systems. The authors claim that this technique renders universal quantifications easy to understand. To substantiate this claim, they provide a simple, easy-to-follow guideline for constructing universally quantified queries. >

Supporting universal quantification in a two-dimensional database query language

A technique for specifying universal quantification and existential quantification (combined with negation) in a two-dimensional graphical database query language is proposed. Unlike other approaches that provide set operators to simulate universal quantification, this technique allows a direct representation of universal quantification. The authors present syntactic constructs for specifying universal and existential quantifications, two-dimensional translation of universal quantification to existential quantification (with negation), and translation of existentially quantified two-dimensional queries to relational queries. The resulting relational queries can be processed directly by many existing database systems. Traditionally, universal quantification has been considered a difficult concept for typical database programmers. The authors claim that this technique renders universal quantification easy to understand. To substantiate this claim, they provide a simple, easy-to-follow guideline for constructing universally quantified queries.<<ETX>>

A full-screen facility for defining relational and entity-relationship database schemas

An easy-to-use, interactive facility for defining schemas for a mainframe database system has been developed that is more convenient than a linear language. The facility called Dbdefs, has several features that make it easy to use. It provides similar interfaces for defining schemas for two data models, relational and entity-relationship. An overview of Dbdefs is followed by discussion of the relational and entity-relationship interfaces.<<ETX>>

AERIAL: Ad hoc entity-relationship investigation and learning

A discussion is presented of browsing, an alternate style of working with databases, that facilitates the unplanned exploration of the structure and contents of a database by a novice user. The authors argue that browsing facilitates learning and helps bring the users mental model of the problem space into correspondence with the model stored in the database. Browsing is illustrated through a learning scenario using AERIAL, a facility that allows the user to browse an entity-relationship database. The facilities provided by AERIAL are discussed in detail as is their use in building a correspondence between the users model of the problem space and the model stored in the database.<<ETX>>

AERIAL: ad-hoc entity-relationship investigation and learning

Abstract This paper discusses Browsing, an alternate style of working with databases, that facilitates the unplanned exploration of the structure and contents of a database by a novice user. We argue that Browsing promotes learning and helps bring the users mental model of the problem space into correspondence with the model stored in the database. Browsing is illustrated through a learning scenario using AERIAL, a facility that allows the user to browse an Entity-Relationship database. The facilities provided by AERIAL are discussed in detail as well as their effectiveness in building the above correspondence.

Issues in designing an information model for application development

IBMs object-oriented information model lets a customer share data among various tools for application development. This paper discusses several issues in designing the information model, namely (1) techniques for diagrams (an essential part of communication between an information model designer and other designers or tool writers), (2) organization of the design of the information model (an essential step when many designers design anything large), and (3) technical content. These discussions of the experience of designing the information model should be valuable for further design of the information model and for other design efforts, e.g., involving other models or other integration of tools.