[DSRP Evidence](https://dsrpevidence.org/)

# Database abstractions: aggregation and generalization

## Details

**Authors** Smith, John Miles and Smith, Diane C. P.

**Year** 1977

**Publisher** ACM Transactions on Database Systems

**Kind of work** article

**Discipline** Computer Science & AI

**Secondary disciplines** Information Science

**Applied** false

[Read it at the publisher](https://doi.org/10.1145/320544.320546) 
10.1145/320544.320546

## In authors' words

### Abstract

Two kinds of abstraction that are fundamentally important in database design and usage are defined. Aggregation is an abstraction which turns a relationship between objects into an aggregate object. Generalization is an abstraction which turns a class of objects into a generic object. It is suggested that all objects (individual, aggregate, generic) should be given uniform treatment in models of the real world. A new data type, called generic, is developed as a primitive for defining such models. Models defined with this primitive are structured as a set of aggregation hierarchies intersecting with a set of generalization hierarchies. Abstract objects occur at the points of intersection. This high level structure provides a discipline for the organization of relational databases. In particular this discipline allows: (i) an important class of views to be integrated and maintained; (ii) stability of data and programs under certain evolutionary changes; (iii) easier understanding of complex models and more natural query formulation; (iv) a more systematic approach to database design; (v) more optimization to be performed at lower implementation levels. The generic type is formalized by a set of invariant properties. These properties should be satisfied by all relations in a database if abstractions are to be preserved. A triggering mechanism for automatically maintaining these invariants during update operations is proposed. A simple mapping of aggregation/generalization hierarchies onto owner-coupled set structures is given.

### What they set out to do (purpose)

To define two kinds of abstraction, aggregation and generalization, that the authors hold to be fundamental in database design and usage, and to develop a primitive for modeling the real world that treats individual, aggregate and generic objects uniformly.

### Who or what was studied (sample)

No empirical sample. The work is a formal proposal for the organization of relational databases.

### How they did it (methods)

The authors define aggregation and generalization, introduce a new data type called generic, formalize it through a set of invariant properties that all relations must satisfy for abstractions to be preserved, propose a triggering mechanism to maintain those invariants during updates, and give a mapping of aggregation and generalization hierarchies onto owner-coupled set structures.

### What they found (results)

Models built with the generic primitive are structured as a set of aggregation hierarchies intersecting a set of generalization hierarchies, with abstract objects at the points of intersection. The authors report that this structure allows an important class of views to be integrated and maintained, keeps data and programs stable under certain evolutionary changes, makes complex models easier to understand and queries more natural to formulate, supports a more systematic approach to database design, and permits more optimization at lower implementation levels.

## Commentary

### In short

Two computer scientists proposed that database models be built from two moves: bundling related objects into a larger whole, and grouping similar objects under a general type. Models built this way form two kinds of hierarchy that cross at every abstract object.

### Response

Aggregation, as defined here, takes a relationship among objects and treats it as a single object. That is the move DSRP describes as a relationship becoming a system, and the paper builds part-whole hierarchies out of it. Generalization, turning a class of objects into a generic object, is a category boundary, the D pattern. The finding that both hierarchies intersect at every abstract object fits DSRP's claim that the same element takes part in more than one structure at once. Caveats: this is a design proposal in an engineering field, not a discovery about nature, so it shows that these operations proved useful for modeling, not that they are universal. Relationships enter mainly as the raw material that aggregation consumes, which is a weaker case of R than a causal finding. Views appear only in the list of benefits and carry too little weight to claim P.

**Patterns it shows** D, S, R

Formal proof or model

**Added** 2026-11-19

**How to cite this** Smith, John Miles and Smith, Diane C. P. (1977). Database abstractions: aggregation and generalization. ACM Transactions on Database Systems.
