Ph.D. Thesis - Business Informatics Group

More documents

Recommendations

Info

1.1.4.1 Tool Adapter Chapter 1 Introduction The prerequisite for using the ModelCVS infrastructure is that the models are conform to the Eclipse Modeling Framework 6 (EMF) XMI and that an Ecore-based metamodel is available. We decided to use EMF as model repository infrastructure and Ecore as meta-modeling language, because EMF is currently the most standard conform implementation of the latest MOF version, thus the terms Ecore and MOF are often used as synonyms in this thesis. If the models are expressed in other formats, tool adapters are needed to connect ModelCVS with proprietary tools. Simple tool adapters are used to resolve incompatible XMI files, a issue which can often be solved with the construction of tool adapters based on XSLT, for instance, that finally render XMI files interchangeably. In this thesis, the focus lies not on incompatible XMI files, instead it is focused on problems coming from meta-metamodel heterogeneity. When integrating two modeling tools, it is often the case that modeling languages are not defined with the same meta-language. Although, standardized meta-languages have been proposed in the model engineering world by the OMG, it is currently not the case that all modeling languages are defined with the same meta-language. A collection of currently used meta-languages for language engineering are shown in Figure 1.3. MOF 1.4 OMG IBM Microsoft MOF 2.0 UML UML Profile Ecore DomainModels XML Schema DTD EBNF OWL Markup-Languages Model Engineering PLs RDFS Ontologies Figure 1.3: Meta-Languages Used for Language Engineering For example, even the OMG has proposed two distinct approaches for developing modeling languages: first, the development from scratch by building a completely new metamodel, and second, the extension of standard UML by exploiting the profile mechanism [OMG05e]. For the first approach, dedicated meta-languages are necessary. The OMG has published the standardized meta-language MOF, however, various versions of MOF are available, each endowed with its own model serialization technique, i.e., XMI specifica- © 2007 BIG Vienna University of Technology, TK & IFS University Linz 9 tion. Even within the OMG, an additional meta-language is proposed by the UML-related group called the UML Infrastructure [OMG03b], which represents the core of UML and is 6 www.eclipse.org/emf 8
1.1 Motivation used for defining the UML 2 standard. Moreover, industry use their own implementation of MOF which are not completely conform to the MOF standard, such as in the Eclipse Modeling Framework 7 meta-language called Ecore that can be seen as a slightly modified MOF subset for the Java platform. Since UML 1.4, UML profiles can be created for extending standard UML with domain-specific modeling concepts. This is done by extending classes of the UML metamodel with stereotypes, which contain tagged values for expressing domain-specific values in UML models. One strong point of the profile mechanism is that standard UML tools can be reused, also for domain-specific modelling concerns. The problematic of meta-metamodel heterogeneity is, however, further aggravated, because in practice additional languages are used as meta-languages . In particular, two cases often occur in typical model engineering scenarios. First, pre-MDA modeling tools have not yet adopted OMG standards and therefore use meta-languages from other technical spaces, in particular XML-based languages. Second, mappings between modeling and programming languages defined in EBNF-like grammars or XML-based description languages defined in Document Type Definitions (DTDs) or XML Schemas, are needed for realizing the transformations between platform independent and platform dependent models as requested by the MDA initiative. Requirements for Tool Adapters. First, tool adapters must be capable of converting models into the format supported by ModelCVS (EMF-based models) as well as generating Ecore-based metamodels from the proprietary modeling language descriptions. Second, tool adapters are nowadays mostly manually implemented for each different tool integration scenario, however, what is really needed are generic adapters which are capable of producing metamodels from any language description defined in a particular meta-language (M2-layer) and also the automatic generation of tool adapters which are capable of importing/exporting models on the M1-layer. 1.1.4.2 Metamodel Bridging Framework For achieving interoperability between two modeling tools in terms of transparent model exchange, current best practices (cf. [Tra05]) comprise creating model transformations based on mappings between concepts of different tool metamodels. As mentioned before, the prevalent form of heterogeneity one has to cope with when creating such mappings between different metamodels is structural heterogeneity. Current model transformation languages, e.g., the OMG standard QVT [OMG05b], provide no appropriate abstraction mechanisms or libraries for resolving recurring kinds of structural heterogeneities. Thus, resolving structural heterogeneities requires to manually specify partly tricky model transformations again and again which simply will not scale up having also negative influence on understanding the transformation’s execution and on debugging. Furthermore, having model transforma- 7 www.elcipse.org/emf 9
Page 1: Ph.D. Thesis From Mining to Mapping
Page 5: Abstract Model-Driven Engineering (
Page 9 and 10: Contents 1 Introduction 1 1.1 Motiv
Page 11 and 12: 7 Summary and Related Work 105 7.1
Page 13 and 14: List of Figures 1.1 Meta-layers of
Page 15 and 16: 10.7 Profile Generation Rule 7 - C2
Page 17 and 18: List of Tables 2.1 Transformation R
Page 19 and 20: Listings 3.1 WebML’s Concepts Gro
Page 21 and 22: Chapter 1 Introduction Contents 1.1
Page 23 and 24: 1.1 Motivation 1.1.2 Model-Driven E
Page 25 and 26: 1.1 Motivation data engineering fie
Page 27: 1.1 Motivation the green boxes repr
Page 31 and 32: 1.2 Contribution of This Thesis wit
Page 33 and 34: 1.3 Thesis Outline «exists» OO-H.
Page 35: Part I Mining
Page 38 and 39: M3 M2 M1 ML X L A M 1 ML Y L A ‘
Page 40 and 41: Chapter 2 From DTDs to Ecore-based
Page 48 and 49: Chapter 2 From DTDs to Ecore-bas
Page 52 and 53: EBoolean and no EEnum is generated
Page 54 and 55: Heuristic 6 - Inheritance Identific
Page 56 and 57: M3 «conformsTo» Phase 1 Phase 2 D
Page 58 and 59: Chapter 3 Evaluation of the DTD to
Page 60 and 61: 3.1.2 Package "Structure" Chapter 3
Page 66 and 67: ContentManagement Hypertext:: to 0.
Page 68 and 69: Basic Chapter 3 Evaluation of the D
Page 72 and 73: Chapter 4 Summary and Related Work
Page 78 and 79:
58 Chapter 4 Summary and Related Wo
Page 81 and 82:
Chapter 5 A Framework for Building
Page 83 and 84:
5.2 Metamodel Bridging Framework ba
Page 85 and 86:
5.2 Metamodel Bridging Framework th
Page 87 and 88:
5.2 Metamodel Bridging Framework to
Page 89 and 90:
5.2 Metamodel Bridging Framework tw
Page 91 and 92:
Chapter 6 CAR - A Mapping Language
Page 93 and 94:
6.2 Mapping Operators These mapping
Page 95 and 96:
6.2 Mapping Operators 6.2.3 R2R Map
Page 97 and 98:
6.2 Mapping Operators Black-Box Vie
Page 99 and 100:
6.2 Mapping Operators * LHS Source
Page 101 and 102:
6.3 An Inheritance Mechanism for Ma
Page 103 and 104:
superClasses type Class 0..* 1 abst
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Angestellter_ANr 6.3 An Inheritance
Page 123 and 124:
Page 125 and 126:
Chapter 7 Summary and Related Work
Page 127 and 128:
7.2 Related Work 7.2.2 Ontology Map
Page 129:
Part III Roundtrip Transformations
Page 132 and 133:
8.1 Motivation Chapter 8 Why Roundt
Page 134 and 135:
Chapter 8 Why Roundtrip Transformat
Page 136 and 137:
Chapter 8 Why Roundtrip Transformat
Page 138 and 139:
Chapter 9 AspectCAR - An Aspect-ori
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
124 Chapter 9 AspectCAR - An Aspect
Page 146 and 147:
Page 148 and 149:
Chapter 10 ProfileGen - A Generator
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
X y Y C2C C2C R2C Gen Chapter 10 Pr
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
1 Chapter 10 ProfileGen - A Generat
Page 172 and 173:
Macro-View - DataModel2UMLModel Cha
Page 174 and 175:
Micro-View - EntityType 2 Class Cha
Page 176 and 177:
Page 178 and 179:
158 Chapter 10 ProfileGen - A Gener
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
providing only a restricted profile
Page 186 and 187:
Chapter 12 Conclusion and Outlook p
Page 188 and 189:
Combining Mapping Operators LHS Map
Page 190 and 191:
Automatic establishment of mapping
Page 192 and 193:
Chapter 12 Conclusion and Outlook o
Page 194 and 195:
Bibliography [BD07] Achim D. Brucke
Page 196 and 197:
Bibliography [Haa07] Laura M. Haas.
Page 198 and 199:
Bibliography [LLPM06] Björn Lundel
Page 200 and 201:
Bibliography [Par72] David L. Parna
Page 202 and 203:
Bibliography [W3C04] World Wide Web
Page 204 and 205:
Bibliography Teaching Assistant Mar
Page 206 and 207:
Bibliography International Workshop
show all

Ph.D. Thesis - Business Informatics Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?