Research issues in federated database systems

Conrad, Stefan; Eaglestone, Barry; Hasselbring, Wilhelm; Roantree, Mark; Schöhoff, M.; Strässler, Markus; Vermeer, Mark W. W.; Saltor, Fèlix

doi:10.1145/271074.271089

Cited by 21 publications

(5 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As reported in [31], this reference schema architecture of [22] is generally accepted as the basic structure in federated database systems or at least for comparison with other specific architectures. However, several modifications have been proposed, as shall be discussed in Section 5.…”

Section: The Five-level Reference Schema Architecture For Federated Dmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

View full text Add to dashboard Cite

Data integration requires managing heterogeneous schema information. A federated database system integrates heterogeneous, autonomous database systems on the schema level, whereby both local applications and global applications accessing multiple component database systems are supported. Such a federated database system is a complex system of systems which requires a well-designed organization at the system and software architecture level. A specific challenge that federated database systems face is the organization of schemas into a schema architecture. This paper provides a detailed, formal investigation of variability in the family of schema architectures, which are central components in the architecture of federated database systems. It is shown how the variability of specific architectures can be compared to the reference architecture and to each other. To achieve this, we combine the semi-formal object-oriented modeling language UML with the formal object-oriented specification language Object-Z. Appropriate use of inheritance in the formal specification, as enabled by Object-Z, greatly supports specifying and analyzing the variability among the studied schema architectures. The investigation also serves to illustrate the employed specification techniques for analyzing and comparing software architecture specifications.

show abstract

Section: The Five-level Reference Schema Architecture For Federated Dmentioning

confidence: 99%

Formalization of Federated Schema Architectural Style Variability

Hasselbring¹

2015

JSEA

View full text Add to dashboard Cite

show abstract

“…16 The problems legacy systems present in the multidatabase context, 27 are, first the reverse engineering problem of determining the integrity constraints built into the legacy systems, and second, how to derive a global mechanism within which the constraints of the component systems are reconciled and maintained.…”

Section: Vv and I Of Legacy And Multidatabase Systemsmentioning

confidence: 99%

Verification, validation, and integrity issues in expert and database systems: Two perspectives

Coenen

Eaglestone

Ridley

2001

Int. J. Intell. Syst.

View full text Add to dashboard Cite

“…The ODMG group has proposed a standard object model in an attempt to address the incompatability problem of each object-oriented database using its own object model. As a result of this standard, many multidatabase groups [7,8] have chosen to adopt the ODMG model as their canonical data model. As the ODMG object model was originally designed for object-oriented database systems, part of our research focused on identifying enhancements required for multidatabase systems [16].…”

Section: Evaluation Of Odmg and Oqlmentioning

confidence: 99%