Ph.D. Thesis - Business Informatics Group

More documents

Recommendations

Info

Chapter 2 From DTDs to Ecore-based Metamodels To illustrate the transformation approach, a small sub-set of the WebML DTD is used to show the effects of applying transformation rules, heuristics and refactoring steps in terms of the resulting WebML metamodel (M2). In particular, this small sub-set consists of part of the concepts provided by WebML to represent a web application’s content layer which in fact resembles the well-known ER-model [Che76]. It has to be emphasized that the focus in this section is on the illustration of the transformation approach, i.e., the consecutive application of (some) transformation rules, heuristics, and refactoring steps. As a consequence, using an example requiring concepts for modeling a web application’s hypertext has been avoided, since the concepts are too numerous and often relate to concepts defined for the content layer. In this respect, the WebML content layer serves as a self-contained and small example. For those rules and heuristics that cannot be illustrated in the context of WebML’s content model, an abstract example is provided in this section as well as a reference to an illustration of their concrete application in the context of WebML’s hypertext model in Section 3.1. 2.3.1 Transformation Rules A couple of rules for transforming concepts of DTDs into Ecore concepts have been designed. Table 2.1 summarizes these rules by differentiating between rules for XMLElement- Types, XMLAttributes and XOR-Constraints, denoting DTD concepts on the left-hand side and their Ecore counterparts on the right-hand side. Rules are marked using a decimal numbering schema and may contain sub-rules, further specializing the correspondences between DTD concepts and Ecore concepts. Finally, alternative correspondences depending on the concrete DTD concept are depicted by a distinction of cases. Following, the application of some of these rules are illustrated using the running example introduced above. Rule 1 - Element Type For each XMLElemType, an EClass is created and the name of the EClass is set to the element type’s name. Depending on the particular sub-class of XMLElemType, additional metamodel elements have to be created in the transformation process, which is outlined in Table 2.1. Example. In Figure 2.7(a), the WebML DTD specifies amongst others element types for ENTITY and RELATIONSHIP, since WebML’s content model is based on the ER-model. According to Rule 1, two EClasses are generated and named after the element types (cf. Figure 2.7(b)). In addition, the ENTITY XMLCompositeETElemContent contains the RE- LATIONSHIP XMLEmptyET, and with respect to case (4) in Table 2.1 an EReference is produced, specifying RELATIONSHIP as the contained EClass. 26
2.3 A DTD to Ecore Transformation Framework XML Element Type XML Attribute XOR Table 2.1: Transformation Rules from DTD to Ecore Rule DTD Concept Ecore Concept R 1 XMLElemType (ET) EClass XMLElemType. Name EClass.name (1) XMLEmptyET no additional elements required (2) XMLAnyET no additional elements required (3) XMLAtomicET add EAttribute EAttribute.name=”PCDATA”, EAttribute.eAttributeType=EString, EAttribute.defaultValue=XMLAtomicET.value (4) XMLCompositeET ElemContent If XMLSequence with cardinality=1 and nested=false If XMLChoice with cardinality=1 and nested=false If XMLContentParticle with cardinality>1 or nested=true add EReference for each XMLElementType in XMLSequence EReference.name=XMLElementType.name, EReference.containment=true add EReference for each XMLElementType in XMLChoice EReference.name=XMLElementType.name, EReference.containment=true add OCL constraints restricting the alternative EReferences add helper EClasses for each XMLSequence or XMLChoice serving as containers for nested XMLContentParticles (5) XMLCompositeETMixedContent add EReference for each XMLElementType EReference.name=XMLElementType.name, EReference.containment=true add EAttribute EAttribute.name=”PCDATA”, EAttribute.eAttributeType=EString, EAttribute.defaultValue= XMLCompositeETMixedContent.value R1.1 XMLContentParticle.cardinality EReference.multiplicity (1) ? (Zero-or-one) EReference.lowerBound=0, EReference.upperBound=1 (2) * (Zero-or-more) EReference.lowerBound=0, EReference.upperBound=-1 (3) + (One-or-more) EReference.lowerBound=1, EReference.upperBound=-1 (4) no symbol EReference.lowerBound=1, EReference.upperBound=1 R2 XMLAttribute EAttribute XMLAttribute.name EAttribute.name (1) XMLStringAtt, NMTOKEN(S), IDREF(S) EAttribute.eAttributeType=EString (2) ID EAttribute.eAttributeType=EString, EAttribute.id=true (3) XMLEnumAtt add EEnum EEnum.name= XMLEnumAtt.name+”_ENUM” for each XMLEnumLiteral add EEnumLiteral EAttribute.eAttributeType=EEnum R2.1 XMLAttribute.cardinality EAttribute.multiplicity R3 (1) default_value (2) #FIXED (3) #REQUIRED (4) #IMPLIED If XMLElemType is part of several XMLCompositeETElemContent Single-valued Multi-valued Single-valued Multi-valued EAttribute.lowerBound=1, EAttribute.upperBound=1, EAttribute.defaultValue=XMLAttribute.default_value EAttribute.lowerBound=1, EAttribute.upperBound=-1, EAttribute.defaultValue=XMLAttribute.default_value EAttribute.lowerBound=1, EAttribute.upperBound=1, EAttribute.defaultValue=default_value, EAttribute.unchangeable=true EAttribute.lowerBound=1, EAttribute.upperBound=-1, EAttribute.defaultValue=default_value, EAttribute.unchangeable=true Single-valued EAttribute.lowerBound=1, EAttribute.upperBound=1 Multi-valued EAttribute.lowerBound=1, EAttribute.upperBound=-1 Single-valued EAttribute.lowerBound=0, EAttribute.upperBound=1 Multi-valued EAttribute.lowerBound=0, EAttribute.upperBound=1 then add OCL constraint to contained EClass specifying that the produced EReferences are exclusive 27
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 and 28: 1.1 Motivation the green boxes repr
Page 29 and 30: 1.1 Motivation used for defining th
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?