Formalization of Federated Schema Architectural Style Variability

Abstract

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.

From Digital Twins to Digital Twin Prototypes: Concepts, Formalization, and Applications

“…To enhance the clarity around the concepts and relationships between physical twins, digital models, digital shadows, digital threads, digital twin prototypes, digital templates, and digital twins, we formally specify the digital twin concept as follows. Similar to Hasselbring [38], we propose a three-level interleaving of formality in the specification:…”

Continuous Integration Testing of Embedded Software with Digital Twin Prototypes

“…To enhance clarity around the concepts and relationships between physical twins, digital models, digital shadows, digital threads, digital twin prototypes, digital templates, and digital twins, we formally specify the Digital Twin concept as follows. We propose, similar to Hasselbring [35], a three-level interleaving of formality in the specification:…”

Software Architecture: Past, Present, Future

“…Formalization of architectural styles aims to allow formal checks of conformance between architecture and implementation, to predict the impact of changes, and to formally reason about a system's architectural description [2]. Various approaches to formalizing architectural styles have been proposed [9,31,48]. The formal comparison allows for a detailed analysis of similarities and differences among the architectural variations.…”