Iteration: MIDAS-CASE - Universidad Rey Juan Carlos

More documents

Recommendations

Info

46 <strong>Juan</strong> M. Vara the approach and technology for each specific task. The result is a framework that integrates a number of existing tools for specific MDE tasks using Eclipse and the Eclipse Modelling Framework as a meeting ground. To that end, each section provides with a discussion on the different methodlogical and technical options to address the common tasks related with deploying model-driven methodologies and reasons out the ones selected to build M2DAT. Chapter 5 addresses the validation of M2DAT specification using M2DAT- DB, the reference implementation for M2DAT, that serves as proof of concept. It serves to introduce the way each specific task is to be implemented in M2DAT according to the methodlogical and technological decisions made on the previous chapter. Thereby, after providing an overview of M2DAT-DB functionality, this chapter deals with the way new DSLs are built on M2DAT (both abstract and concrete syntax). Next, a set of common scenarios that arose when developing model transformations and the way they are addressed in the context of M2DAT is described. Finally, ways of using M2DAT capabilities in a user-friendly manner by extending the Eclipse GUI are presented. Finally, Chapter 6 concludes by summarizing the main contributions of this thesis. To that purpose, it provides an analysis of the results and reviews the publications that serve to contrast them both on national and international forums. Besides, it raises a number of questions for future research and puts forward the directions to follow for further work. In addition, Appendix A provides with a summary of this dissertation in Spanish; Appendixes B and C provide with more detailed discussions on graph-based and model-to-text transformations. Appendix D presents the main Case Study used along this dissertation to show M2DAT-DB‘s capabilities. Finally, Appendix E collects the bibliographical and electronic references used along this dissertation and Appendix F summarizes the acronyms spread over the text.
State of the Art
Page 1: Universidad Rey Juan Carlos Escuela
Page 5: ―In theory, there is no differenc
Page 8 and 9: Likewise, a set of methodological a
Page 10 and 11: susbsistemas y que soportará la in
Page 12 and 13: Finally, when the time to finish th
Page 15 and 16: Index 1. INTRODUCTION .............
Page 17 and 18: 2.3.3.6 MOFLON-FUJABA .............
Page 19 and 20: 3.3.4.1 Code Generation ...........
Page 21 and 22: 4.8.5 Code Generation: model-to-tex
Page 23: B ABOUT GRAPH TRANSFORMATIONS .....
Page 26 and 27: Figure 3-9. UML extension for XML S
Page 28 and 29: Figure 5-33. One-to-One transformat
Page 30 and 31: Figure B-1. UML simple model render
Page 33: Introduction
Page 36 and 37: 32 Juan M. Vara whole system (and n
Page 38 and 39: 34 Juan M. Vara designer the option
Page 40 and 41: 36 Juan M. Vara O2.1. Analysis and
Page 42 and 43: 38 Juan M. Vara Core of the models
Page 44 and 45: 40 Juan M. Vara Figure 1-2. Ph.D. T
Page 46 and 47: 42 Juan M. Vara D O C U M E N T A T
Page 48 and 49: 44 Juan M. Vara process to follow i
Page 53 and 54: 2. State of the Art During the last
Page 55 and 56: 2.1.3 Models and Metamodels State o
Page 57 and 58: 2.1.4 Concrete Syntax, Abstract Syn
Page 59 and 60: State of the Art 55 In the MDE lite
Page 61 and 62: State of the Art 57 illustrate this
Page 63 and 64: State of the Art 59 generator autom
Page 65 and 66: FinancialTransactionBase CreationDa
Page 67 and 68: MOF UML UML Model Instantiation of
Page 69 and 70: Meta-Metamodel MOF UML Metamodel An
Page 71 and 72: State of the Art 67 A Query is an e
Page 73 and 74: State of the Art 69 represented as
Page 75 and 76: State of the Art 71 itroduce EMF ca
Page 77 and 78: State of the Art 73 need to check w
Page 79 and 80: State of the Art 75 will be judged
Page 81 and 82: State of the Art 77 implements the
Page 83 and 84: State of the Art 79 GME supports it
Page 85 and 86: 2.2.10 MetaEdit+ State of the Art 8
Page 87 and 88: State of the Art 83 platform. In fa
Page 89 and 90: IEME State of the Art 85 The Integr
Page 91 and 92: 2.2.18 Summary and Discussion State
Page 93 and 94: State of the Art 89 The first and m
Page 95 and 96: 2.3 Model-Transformation Languages
Page 97 and 98: State of the Art 93 Since these cla
Page 99 and 100: State of the Art 95 2.3.2.1 Evaluat
Page 101 and 102:
2.3.3 Model-to-Model Transformation
Page 103 and 104:
State of the Art 99 models cannot b
Page 105 and 106:
State of the Art 101 conform to QVT
Page 107 and 108:
State of the Art 103 of a graph rew
Page 109 and 110:
State of the Art 105 control struct
Page 111 and 112:
State of the Art 107 Until the fina
Page 113 and 114:
State of the Art 109 MOMENT-QVT pro
Page 115 and 116:
State of the Art 111 invresolve. Re
Page 117 and 118:
State of the Art 113 2.3.3.15 Other
Page 119 and 120:
State of the Art 115 editors for hi
Page 121 and 122:
State of the Art 117 projects Model
Page 123 and 124:
Table 2-6. Model Transformation Lan
Page 125 and 126:
State of the Art 121 best option si
Page 127 and 128:
State of the Art 123 visual notatio
Page 129 and 130:
State of the Art 125 Deployment Pla
Page 131 and 132:
State of the Art 127 summarizing ho
Page 133 and 134:
State of the Art 129 Finally, altho
Page 135 and 136:
State of the Art 131 to check const
Page 137 and 138:
State of the Art 133 To sum up, the
Page 139 and 140:
State of the Art 135 that is define
Page 141 and 142:
State of the Art 137 that, it gener
Page 143 and 144:
State of the Art 139 etc.). Althoug
Page 145 and 146:
State of the Art 141 BENCHMARK DESC
Page 147 and 148:
MT ArgoUWE WebRatio WebTE OOWS Suit
Page 149 and 150:
State of the Art 145 2.4.4.1 On Too
Page 151 and 152:
State of the Art 147 Last, but not
Page 153:
State of the Art 149 using DSLs for
Page 157 and 158:
3. 1 st Iteration: MIDAS-CASE This
Page 159 and 160:
1 st Iteration: MIDAS-CASE 155 On t
Page 161 and 162:
1 st Iteration: MIDAS-CASE 157 the
Page 163 and 164:
1 st Iteration: MIDAS-CASE 159 If t
Page 165 and 166:
WSDL COMPONENT Name SERVICE END POI
Page 167 and 168:
UML SOD-M SOD-M/PIM Actor UseCase
Page 169 and 170:
1 st Iteration: MIDAS-CASE 165 The
Page 171 and 172:
1 st Iteration: MIDAS-CASE 167 We f
Page 173 and 174:
XML Schema «metaclass» Package «
Page 175 and 176:
1 st Iteration: MIDAS-CASE 171 Figu
Page 177 and 178:
1 st Iteration: MIDAS-CASE 173 3.3.
Page 179 and 180:
1 st Iteration: MIDAS-CASE 175 two
Page 181 and 182:
1 st Iteration: MIDAS-CASE 177 impo
Page 183 and 184:
1 st Iteration: MIDAS-CASE 179 In f
Page 185:
3.4.6 Separation of Concerns: Modul
Page 189 and 190:
4. Solution: M2DAT Architecture and
Page 191 and 192:
Solution: M2DAT Architecture and Te
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
.ecore .gmfgraph .gmftool Domain Mo
Page 207 and 208:
no coupling between the arrow and t
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
LEGEND ABSTRACT SYNTAX DEFINITION S
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
MMa Ma c2 Solution: M2DAT Architect
Page 243:
Page 247 and 248:
5. Validation: M2DAT-DB A reference
Page 249 and 250:
Validation: M2DAT-DB 245 To move fr
Page 251 and 252:
Validation: M2DAT-DB 247 As a resul
Page 253 and 254:
Figure 5-2. SQL:2003 ORDB Metamodel
Page 255 and 256:
Validation: M2DAT-DB 251 Figure 5-4
Page 257 and 258:
Validation: M2DAT-DB 253 Figure 5-7
Page 259 and 260:
Validation: M2DAT-DB 255 To support
Page 261 and 262:
5.2.2 Concrete Syntax Definition Va
Page 263 and 264:
Java Model uses Genmodel Ecore Ecor
Page 265 and 266:
Validation: M2DAT-DB 261 instantiat
Page 267 and 268:
1 2 Validation: M2DAT-DB 263 Figure
Page 269 and 270:
Method Name ReturnType Name Type Pa
Page 271 and 272:
1 Figure 5-21. Setting root element
Page 273 and 274:
SQL2003.ecore Validation: M2DAT-DB
Page 275 and 276:
5.3.1 Common Scenarios Validation:
Page 277 and 278:
SOURCE METAMODEL A Figure 5-26. One
Page 279 and 280:
OMDB.uml rule ClassPropertyNotNull2
Page 281 and 282:
SOURCE METAMODEL A Validation: M2DA
Page 283 and 284:
Validation: M2DAT-DB 279 to the Str
Page 285 and 286:
Validation: M2DAT-DB 281 this behav
Page 287 and 288:
Validation: M2DAT-DB 283 5.3.1.7 Ma
Page 289 and 290:
Validation: M2DAT-DB 285 rule Class
Page 291 and 292:
OneLevelHierarchy.sql2003 1 2 OneLe
Page 293 and 294:
Validation: M2DAT-DB 289 Neverthele
Page 295 and 296:
Validation: M2DAT-DB 291 rule Chara
Page 297 and 298:
lazy abstract rule Feature2Feature
Page 299 and 300:
Validation: M2DAT-DB 295 by the nam
Page 301 and 302:
Validation: M2DAT-DB 297 comment ar
Page 303 and 304:
Validation: M2DAT-DB 299 model. Thu
Page 305 and 306:
Validation: M2DAT-DB 301 Rule Class
Page 307 and 308:
Validation: M2DAT-DB 303 All this g
Page 309 and 310:
Validation: M2DAT-DB 305 To conclud
Page 311 and 312:
1 Validation: M2DAT-DB 307 Figure 5
Page 313 and 314:
Validation: M2DAT-DB 309 The availa
Page 315 and 316:
Validation: M2DAT-DB 311 -- @atlcom
Page 317 and 318:
Validation: M2DAT-DB 313 populated
Page 319 and 320:
Figure 5-78. Eclipse’s shortcut t
Page 321 and 322:
Figure 5-81. UML2SQL2003 Run Config
Page 323:
Generate XMLSchema code Generate OR
Page 327 and 328:
6. Conclusion To conclude this diss
Page 329 and 330:
Conclusion 325 On the other hand, M
Page 331 and 332:
Conclusion 327 others have emerged
Page 333 and 334:
Conclusion 329 attaching an annotat
Page 335 and 336:
Conclusion 331 ACM Symposium on App
Page 337 and 338:
Patents Conclusion 333 o Title: M2D
Page 339 and 340:
Conclusion 335 some information for
Page 341 and 342:
6.4.5 Improving the Development of
Page 343:
Conclusion 339 code) and Oracle mod
Page 347 and 348:
A Resumen en Castellano Este apénd
Page 349 and 350:
Resumen en Castellano 345 beneficia
Page 351 and 352:
Resumen en Castellano 347 IDM, y c
Page 353 and 354:
A.3 Metodología Resumen en Castell
Page 355 and 356:
Resumen en Castellano 351 Para vali
Page 357 and 358:
Resumen en Castellano 353 adapte a
Page 359:
Resumen en Castellano 355 transform
Page 363 and 364:
B About Graph Transformations This
Page 365:
About Graph Transformations 361 a f
Page 369 and 370:
C Text-to-Model Transformations Thi
Page 371 and 372:
Text-to-Model Transformations 367 C
Page 373:
Appendix D: Case Study
Page 376 and 377:
372 Juan M. Vara Figure D-1. Concep
Page 378 and 379:
374 Juan M. Vara Figure D-3. OR Mod
Page 381:
Bibliography
Page 384 and 385:
380 Juan M. Vara 19. Arsenault, S.
Page 386 and 387:
382 Juan M. Vara 59. Borland. (2008
Page 388 and 389:
384 Juan M. Vara http://www.eclipse
Page 390 and 391:
386 Juan M. Vara 146. Friese, P., E
Page 392 and 393:
388 Juan M. Vara 194. Klimavicius,
Page 394 and 395:
390 Juan M. Vara 235. Meliá, S. &
Page 396 and 397:
392 Juan M. Vara 284. Paiano, R., &
Page 398 and 399:
394 Juan M. Vara 325. Software AG.
Page 400 and 401:
396 Juan M. Vara 366. Vela, B., Fer
Page 403:
Acronyms
Page 406 and 407:
402 Juan M. Vara ACRONYM DESCRIPTIO
show all

Iteration: MIDAS-CASE - Universidad Rey Juan Carlos

Create successful ePaper yourself

Delete template?

Save as template?