A survey of schema versioning issues for database systems

Roddick, John F.

doi:10.1016/0950-5849(95)91494-k

Cited by 228 publications

(125 citation statements)

References 53 publications

Supporting

Mentioning

117

Contrasting

Unclassified

Order By: Relevance

“…As a consequence, all system dependent components must be changed to reflect the changes in the database schema. Roddick (1995) suggests schema modification for database systems should require the minimal changes to the existing database schema and applications (Roddick, 1995).…”

Section: Schema Evolutionmentioning

confidence: 99%

Designing a Framework for End User Applications

Deng

Churcher

Abell

et al. 2011

End-User Development

View full text Add to dashboard Cite

of a thesis submitted in partial fulfilment of the requirements for the Degree of Doctor of Philosophy in Software and Information Technology Designing a Framework for End User Applications by Yanbo DengEnd user developers (i.e. non-professional developers) often create database applications to meet their immediate needs. However, these applications can often be difficult to generalise or adapt when requirements inevitably change. As part of this thesis, we visited several research institutions to investigate the issues of end user developed databases. We found that different user groups in the same organisation might require similar, but different, data management applications. However, the very specific designs used in most of these systems meant it was difficult to adapt them for other similar uses.In this thesis we propose a set of guidelines for supporting end user developers to create more flexible and adaptable data management applications. Our approach involves professional and end user developers working together to find a "middle way" between very specific and very generic designs. We propose a framework solution that allows the data model to have several co-existing variations which can satisfy the requirements of different user groups in a common domain. A "framework provider" (IT professional) will create the initial framework and data model. Configuration tools are then provided for a "framework manager" to easily customise the model to the specific needs of various user groups. The system also provides client toolkits and application generators to help end user developers (EUDs) to quickly create and customise applications based on the framework.The framework approach was applied to a case study involving a Laboratory Information Management System (LIMS) for data on research experiments. We demonstrated that the framework developed could be successfully applied to several groups working in the same domain and could be extended to include new or changed requirements.We also evaluated the framework through software trials at several research organisations. All participants successfully used the configuration tools to extend the LIMS framework within an average of 40 minutes. EUDs were also able to easily create basic applications within an average of 25 minutes. The overall feedback was that the framework approach was a useful and efficient way to create adaptable data management applications. More importantly, ii participants were able to immediately see how the framework could be applied to their own laboratory data.

show abstract

Section: Schema Evolutionmentioning

confidence: 99%

Designing a Framework for End User Applications

Deng

Churcher

Abell

et al. 2011

End-User Development

View full text Add to dashboard Cite

show abstract

“…Schema versioning is based on a view mechanism and all changes, i.e., in particular deletes, are recorded in view changes. Schema versioning [27] is combined with an adaptional mechanism in the O2 [12] system. O2 minimizes needed application reconstructions.…”

Section: Related Workmentioning

confidence: 99%

Integrated Model-Based Software Development, Data Access, and Data Migration

Bordbar

Draheim

Horn³

et al. 2005

Model Driven Engineering Languages and Systems

View full text Add to dashboard Cite

Abstract. In this paper we describe a framework for robust system maintenance that addresses specific challenges of data-centric applications. We show that for data-centric applications, classical simultaneous roundtrip engineering approaches are not sufficient. Instead we propose an architecture that is an integrated model-based approach for software development, database access and data migration. We explain the canonical development process to exploit its features. We explain how the approach fits into the model-driven architecture vision. We report on experiences with the approach in the IMIS environmental mass database project.

show abstract

“…As far as the interaction between the temporal dimensions involved in intensional and extensional versioning, we follow here a Synchronous Management approach [16], according to which temporal data are always stored, retrieved and updated through the schema version having the same temporal pertinence. Notice that the synchronous management is the usual choice for schema versioning support in object-oriented databases, where data objects are normally only visible (and updatable) through the schema version they belong to, that is the one in which they were created [17]. We will consider, at intensional level: transaction-time (tS), valid-time (vS) and bitemporal schema versioning (tvS), and, at extensional level: snapshot (D), transaction-time (tD), valid-time (vD) and bitemporal databases (tvD).…”

Section: Definition Of Legal Databasesmentioning

confidence: 99%

“…In this context, if the adoption of a temporal database allows one to represent and manage the history of data objects (extensional properties), the introduction of temporal schema versioning enables one to represent and manage the history of the structure of data objects (intensional properties). Whereas a great deal of research work was done on temporal OODBs [11][12][13][14][15], temporal schema versioning has been deeply investigated so far only for the relational model [16,17].…”

Section: Introductionmentioning

confidence: 99%

A formal model for temporal schema versioning in object-oriented databases

Grandi

Mandreoli

2003

Data & Knowledge Engineering

View full text Add to dashboard Cite

In this paper we present a formal model for the support of temporal schema versions in object-oriented databases. Its definition is partially based on a generic (ODMG compatible) object model and partially introduces new concepts. The proposed model supports all the schema changes which are usually considered in the OODB literature, for which an operational semantics and a formal analysis of their correct behaviour is provided. Semantic issues arising from the introduction of temporal schema versioning in a conventional or temporal database (concerning the interaction between the intensional and extensional levels of versioning and the management of data in the presence of multiple schema versions) are also considered.

show abstract

A survey of schema versioning issues for database systems

Cited by 228 publications

References 53 publications

Designing a Framework for End User Applications

Designing a Framework for End User Applications

Integrated Model-Based Software Development, Data Access, and Data Migration

A formal model for temporal schema versioning in object-oriented databases

Contact Info

Product

Resources

About