Aktuelles

Reakkreditierung der Studienrichtung Wirtschaftsinformatik


Alle Neuigkeiten ansehen.


Campusplan

campusplan_image

Unser Standort befindet sich hier.




Extending Object-Oriented Systems with Roles

Autoren: G. Gottlob, M. Schrefl, B. Röck
Paper: Gott96a (1996)
Zitat: ACM Transactions on Information Systems (ACM TOIS), Vol. 14, No. 3 (July 1996), ACM Press, ISSN 1046-8188, pp. 268-296, 1996.
Ressourcen: Kopie  (Senden Sie ein Email mit  Gott96a  als Betreff an dke.win@jku.at um diese Kopie zu erhalten)
BibTeX


Kurzfassung:

In many class-based object-oriented systems the association between an instance and a class is exclusive and permanent. Therefore these systems have serious difficulties in representing evolving objects which may take on different roles over time. Entities must be reclassified any time they evolve, e.g., if a person becomes a student and later an employee. Class hierarchies must be planned carefully and may grow exponentially if entities may take on several independent roles. The problem is even more severe for object-oriented database programming languages than for common object-oriented programming. Databases store objects over longer periods during which the represented entities evolve.

This article shows how class-based object-oriented systems can be extended to handle evolving objects well. Class hierarchies are complemented by role hierarchies, whose nodes represent types an object classified in the root may evolve. At any point in time, an entity is represented by an instance of the root and an instance of every role type whose role it currently plays. The approach extends traditional object-oriented concepts, such as classification, object identity, specialization, inheritance and polymorphism in a natural way.

The practicability of the approach is demonstrated by an implementation in Smalltalk. Smalltalk has been chosen, because it is widely known, which is not true for any particular class-based object-oriented database programming language. Roles can be made available in Smalltalk by adding a few classes. There is no need to modify the semantics of Smalltalk itself. Role hierarchies are mapped transparently to ordinary classes. The presented implementation can be easily ported to object-oriented database programing languages based on Smalltalk, such as OPAL of Gemstone.