Toward Modeling Language-Independent Integration of Dynamic Schemata

Towards the Automation of Modeling Language Independent Schema Integration

“…• Preparation of source schemata • Recognition of conflicts and commonalties between source schemata • Resolution of conflicts and commonalties between source schemata • Merging the source schemata and restructuring the global schema Furthermore, in [6] we mapped our proposed guidelines to those sub-steps. Our approach of using domain repositories and ontologies for gaining semantic information about domain concepts and their relationships and utilizing this knowledge for the integration process was inspired by [7] [14] and discussed first in [20].…”

“…• Performing schema integration on the predesign level • Standardizing concept notions and utilizing them during integration • Using domain repositories for supporting the integration process • Neighborhood based conflict recognition • Pattern based resolution of integration conflicts • Computer supported integration with utilizing user feedback In [6] we focused on the integration of dynamic schemata describing system behavior and processes and proposed the following four sub-steps:…”

“…In [5] we proposed the following six guidelines for modeling language independent integration strategies:…”

“…"Modeling language independent" means that we are not dealing with formal modeling languages but instead with concepts and relationships on a high level of abstraction. This has the advantage that our approach is applicable on source schemata from arbitrary modeling languages [5]. We also use additional repository information (e.g.…”

“…Our previous research on integration of both static and dynamic schemata gave us valuable insights into integration on a high level of abstraction and its advantages compared to integration on a level closer to implementation [4] [5] [6].…”