Representing composites in conceptual modeling

Abstract

A conceptual modeling approach used within database literature to represent composites like entity classes, object classes, relationship classes or associations is presented. It is found that when component things are combined into a larger composite thing, the composite always gains at least one property. One role of a conceptual model is to facilitate communication between user and modelers. It is concluded that the conceptual models use relationship classes or associations to represent composites and undermine the database maintainer's ability to understand the database.