If We Refuse the Inheritance

Levels for Conceptual Modeling

“…On the basis of these observations, following [1], the inheritance of attributes of grounded types must be controlled. By default, T 1 T 2 or T 1 T 2 implies that all the attributes of T 2 are inherited by T 1 .…”

“…By default, T 1 T 2 or T 1 T 2 implies that all the attributes of T 2 are inherited by T 1 . T 1 [A 1 1 , ..., A 1 n ] T 2 [A 2 1 , ..., A 2 m ] means that only the T 2 attributes A 2 1 , ..., A 2 m are exported to T 1 while the T 1 attributes A 1 1 , ..., A 1 n are exported to T 2 . Similarly in the case of generic grounding.…”

“…In this way, attribute hiding can be trivially modeled. Attribute overriding can be approached by systematically override the attributes of the grounding type or by localizing all the attributes as in [1]. The case of compositional dependence is interesting.…”

“…The object and its roles form an aggregate and "the dynamic picking up of a role corresponds to the creation of a new instance of the corresponding role type and its integration in a compound, and dropping a role means releasing the role instance from the unit and destroy it" ( [17], p.91). In object-oriented database management systems, by distinguishing specialization, an abstract concept, from inheritance, a mechanism that implements specialization, [1] systematically multiplies the instances in the presence of a subtype relation. If P is a subtype of Q, then the creation of an object p of type P produces the creation of an object q of type Q plus a link between them that allows p to inherit attributes from q.…”

“…An object then is implemented "by multiple instances which represent its many faceted nature. Those instances are linked together through aggregation links in a specialization relation" ( [1], p.561). The attributes are locally defined and stored but additional ones can be inherited via the links between the instances.…”