Defining views in the Binary Relationship Model

https://doi.org/10.1016/0306-4379(87)90006-8Get rights and content

Abstract

The Binary Relationship Model has been praised for the way it not only supports, but practically forces us to model the “deep structures” of the information in the conceptual schema. An adverse effect is that the conceptual schema becomes very large. This, combined with the fact that a Binary Relationship Model schema gives a “flat” representation of the information, makes it very hard to distinguish important concepts of a model from its less important details. Furthermore, the length of DML statements is directly proportional to the size of the schema. What we need for practical applications is a way of keeping the “deep structures” while seeing only the “surface structures”. We need to be able to define views on a conceptual schema. We need to be able to select and derive from the conceptual schema precisely the concepts we are interested in for each application of our model.

We propose two new concepts for view definition in the Binary Relationship Model, DOTs and shortcuts. DOTs are dervied object types and shortcuts are derived roles which are used in the definition of derived binary relationship types.

References (21)

  • J.R Abrial

    Data semantics

  • M.E Senko

    Specification of stored data structures and desired output results in DIAM II with FORAL

  • M.E Senko

    Foral LP: design and implementation

  • P Hall et al.

    Relations and entities

  • Current issues in conceptual schema concepts

  • G.M Nijssen

    One, two or three conceptual schemata

  • G.M Nijssen

    An architecture for knowledge base software

  • W Kent

    Data and Reality

    (1978)
  • J.M Smith et al.

    Database abstractions: aggregation and generalization

    ACM Trans. Database Systems

    (1977)
  • S Ceri et al.

    Structured methodology for designing static and dynamic aspects of data base applications

    Inform. Systems

    (1981)
There are more references available in the full text version of this article.

Cited by (7)

  • Database Design Using Entity-Relationship Diagrams

    2004, Database Design Using Entity-Relationship Diagrams
  • CLASSIC: A structural data model for objects

    1989, Proceedings of the ACM SIGMOD International Conference on Management of Data
View all citing articles on Scopus
View full text