The case for mesodata: An empirical investigation of an evolving database system

Vries, Denise de; Roddick, John F.

doi:10.1016/j.infsof.2006.11.001

Cited by 12 publications

(6 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Based on these considerations, de Vries and ; De Vries et al [2004], and de Vries and Roddick [2007] defined an approach for the relational data model by introducing complex data structures, which can be viewed as information on attribute domains, at a level between the data and the metadata. Such structures can also be used to support domain modifications.…”

Section: Attribute Domain Evolution Using Mesodata (Mesev)mentioning

confidence: 99%

Synchronization of Queries and Views Upon Schema Evolutions

Caruccio

Polese

Tortora

2016

ACM Trans. Database Syst.

View full text Add to dashboard Cite

One of the problems arising upon the evolution of a database schema is that some queries and views defined on the previous schema version might no longer work properly. Thus, evolving a database schema entails the redefinition of queries and views to adapt them to the new schema. Although this problem has been mainly raised in the context of traditional information systems, solutions to it are also advocated in other database-related areas, such as Data Integration, Web Data Integration, and Data Warehouses. The problem is a critical one, since industrial organizations often need to adapt their databases and data warehouses to frequent changes in the real world. In this article, we provide a survey of existing approaches and tools to the problem of adapting queries and views upon a database schema evolution; we also propose a classification framework to enable a uniform comparison method among many heterogeneous approaches and tools.

show abstract

Section: Attribute Domain Evolution Using Mesodata (Mesev)mentioning

confidence: 99%

Synchronization of Queries and Views Upon Schema Evolutions

Caruccio

Polese

Tortora

2016

ACM Trans. Database Syst.

View full text Add to dashboard Cite

show abstract

“…Efforts to tackle the problem of coping with design evolution have included design versioning [1], 'active' object models [2], [3], capture and exploitation of so-called mesodata [4], and schema versioning [5]. However, none of these approaches enables the design of an existing running system to be changed responsively and for those changes to be reflected in a new running version of that design.…”

Section: Research Problem and Related Workmentioning

confidence: 99%

CRISTAL: A practical study in designing systems to cope with change

Branson

McClatchey

Goff

et al. 2014

Information Systems

View full text Add to dashboard Cite

Software engineers frequently face the challenge of developing systems whose requirements are likely to change in order to adapt to organizational reconfigurations or other external pressures. Evolving requirements present difficulties, especially in environments in which business agility demands shorter development times and responsive prototyping. This paper uses a study from CERN in Geneva to address these research questions by employing a 'description-driven' approach that is responsive to changes in user requirements and that facilitates dynamic system reconfiguration. The study describes how handling descriptions of objects in practice alongside their instances (making the objects self-describing) can mediate the effects of evolving user requirements on system development. This paper reports on and draws lessons from the practical use of a description-driven system over time. It also identifies lessons that can be learned from adopting such a self-describing description-driven approach in future software development.

show abstract

“…An attribute with more than one associated mesodata domain can take its value from any of the linked domains (which can be of use in cases of changes to domain structure (cf. [12,13]). …”

Section: Mesodata Domain Modellingmentioning

confidence: 99%