Home > Research > Publications & Outputs > A database evolution taxonomy for object-orient...
View graph of relations

A database evolution taxonomy for object-oriented databases.

Research output: Contribution to journalJournal article

<mark>Journal publication date</mark>1/04/2005
<mark>Journal</mark>Journal of Software Maintenance and Evolution: Research and Practice
Issue number2
Number of pages49
Pages (from-to)93-141
Publication statusPublished
Original languageEnglish


Like any other database application, object database applications are subject to evolution. Evolution, however, is a critical requirement in object-oriented databases as it is a fundamental characteristic of complex applications such as computer-aided design and manufacturing (CAD/CAM) and office information systems. Object-oriented databases are inherently suited to supporting such applications. In this paper we present a database evolution taxonomy for object-oriented databases. We describe a conceptual database model and use it to define the taxonomy. We also present the various invariants and rules governing the various evolution operations. The execution sequence of rules is described. An implementation of the database model and the evolution taxonomy in the Semi-Autonomous Database Evolution System (SADES), is discussed. The implementation employs aspect-oriented programming techniques to provide a flexible means of transforming objects upon evolution, and implementing some application-specific evolution primitives. A case study compares the evolution taxonomy with existing evolution approaches. The comparison demonstrates that the taxonomy and its corresponding implementation in SADES provide improved coverage of the fundamental evolution operations to which an object database might be subjected. At the same time, erosion of the database structure is avoided by maintaining a coherent and comprehensible view of historical changes.

Bibliographic note

This paper culminates the body of work conducted at Lancaster on aspect-oriented database systems. It uses object-oriented databases as a case example to highlight the need to support developer-end customisability in database systems. It then presents the vision of aspect-oriented databases ' database systems natively supporting aspect-oriented abstractions ' as a means to develop customisable database systems. The paper was followed up by a book which has in turn triggered other researchers to focus on aspects and persistence. An SME: Object Nirvana (http://www.objectnirvana.com/) is launching an aspect-oriented database product that is inspired by the ideas in the paper and its follow-up book. RAE_import_type : Journal article RAE_uoa_type : Computer Science and Informatics