Type evolution in an object-oriented database
Research directions in object-oriented programming
An axiomatic model of dynamic schema evolution in objectbase systems
ACM Transactions on Database Systems (TODS)
Schema and Database Evolution in the O2 Object Database System
VLDB '95 Proceedings of the 21th International Conference on Very Large Data Bases
Evolution Features of the F2 OODBMS
Proceedings of the 4th International Conference on Database Systems for Advanced Applications (DASFAA)
Object Migration in ISA Hierarchies
Proceedings of the 4th International Conference on Database Systems for Advanced Applications (DASFAA)
Object Deputy Model and Its Applications
Proceedings of the 4th International Conference on Database Systems for Advanced Applications (DASFAA)
Multiobjects to Ease Schema Evolution in an OODBMS
ER '98 Proceedings of the 17th International Conference on Conceptual Modeling
A Generic Role Model for Dynamic Objects
CAiSE '02 Proceedings of the 14th International Conference on Advanced Information Systems Engineering
From Object-Oriented to Aspect-Oriented Databases
DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Levels for conceptual modeling
ER'11 Proceedings of the 30th international conference on Advances in conceptual modeling: recent developments and new directions
| Hi-index | 0.00 |
Specialization is an abstract concept which expresses the IS-A relationship while inheritance is a mechanism which implements specialization. Our experiences in extended entity-relationship DBMSs and object-oriented DBMSs have shown that specialization can be implemented by several mechanisms. We propose in this paper a mechanism which is more flexible than inheritance with respect to object dynamics and schema evolution. In our "hologram" approach, an object is implemented by multiple instances which represent its many faceted nature. Those instances are linked together through aggregation links in a specialization hierarchy. Objects are dynamic since they can migrate between the classes of a hierarchy. Attributes and methods are not inherited but reached by navigating in a specialization hierarchy. Class views provide customized interfaces of classes. Our approach makes schema changes more pertinent and easier to understand.