Ph.D. - geht es zur Homepage der Informatik des Fachbereiches 3 ...

More documents

Recommendations

Info

Chapter 3. Domain-Specific Modelling natural language, which means text. In minor cases other textual formalisms like tables are used but not generally in a normalised or formalised manner. To provide significant abstraction from the ETCS specification documents, a pure textual DSL would fail because pure text is always represented linearly. As in the specification documents themselves, this may lead to a lot of references or even cross-references. Combined with the complexity of the specification, this renders a textual representation confusing. Instead, a graphical DSL provides a lot more representation techniques that are not limited to linear representation methods. For example, references can be represented by sub-graphs. Although the most of the above introduced meta meta models can be used for building models, MOF / Ecore and GOPRR are predestined because they already provide graphical formalisms for meta model definition. Especially, GOPRR was designed for graphical DSLs, which gives it a big advantage compared with the others. 3.3. Domain-Specific Modelling Development Applications Although a modelling application for a certain DSL can always be implemented explicitly, there are already several applications and tools available for designing a DSL / meta model, modelling, and code generation. In the following, some of the most common and most appropriate for the openETCS case study are introduced. 3.3.1. Xtext Xtext is a plug-in for Eclipse [9] that provides functionality for creating textual DSLs and generating code from those. It uses ANTLR, which is a parser for BNFs. Therefore, the grammar for a DSL and the code generator can be freely specified, which makes Xtext completely independent from any concrete implementation. It additionally offers the export to Ecore meta models. Its main disadvantage is the lack of any possibility for creating graphical models. 3.3.2. Graphical Modelling Framework The Graphical Modelling Framework (GMF) is also a plug-in for the Eclipse IDE that combines EMF (see Subsection 3.1.2) and GEF (Graphical Editing Framework) to enable the creation of graphical DSLs. It uses Ecore as meta meta model and its code generation is limited 1 to Java. 3.3.3. Rascal Like GMF, Rascal [17] is also a plug-in for Eclipse with special focus on graphical meta modelling and modelling. It also has the advantage that it is shipped under an OSS license. Although this approach seems to be quite promising, it is currently still under development and is only provided as an alpha release. 1 because of EMF 36
3.4. Conclusion 3.3.4. MetaEdit+ MetaEdit+ [56] is a commercial application for creating DSLs. It uses the GOPRR meta meta model and is very specialised for the development of graphical meta models and models. The code is generated from graphs using the MetaEdit+ Reporting Language (MERL) [56]. MERL does not depend on any certain programming framework, like Ecore, and therefore code for any kind of programming language can be generated. Moreover, it provides easier generator development because it only uses the concrete syntax, as in Figure 3.19 and 3.20, for certain graph types. The abstract syntax from Figure 3.17 and Figure 3.18 is not visible to MERL. Also, generators can be restricted to certain graph types and cannot be used on the project-level. In contrast to all other DSM applications mentioned before, MetaEdit+ is the only one that provides a development standard on an industrial level. Since this work focuses on safety-critical systems, this fact cannot simply be ignored. The main disadvantage of MetaEdit+, related to this work, is that no FLOSS version is available. 3.4. Conclusion Although a full FLOSS tool chain – including the DSM development applications – fits the aim of this work better, MetaEdit+ as commercial software offers several advantages that cannot be simply ignored. Compared to the other applications and their meta meta models, MetaEdit+ is highly specialised for the development of graphical DSLs. Additionally, it provides a script language for generator development that does not depend on certain programming languages. Furthermore, the usage of the introduced FLOSS applications would always cause additional development effort for the tooling because none provides graphical modelling and general generation in one. Due to the fact that a complete tool development should not be in the main scope of this work, MetaEdit+ and the GOPRR meta meta model are employed for this work. To be able to publish all parts work the corresponding case study in Part III, any meta model and model can be exported to an appropriate XML format like XMI [61]. Such files are then free for publication under any license and are not limited to a certain application. 37
Page 1:
Open Source Software for Train Cont
Page 4 and 5:
Datum des Promotionskolloquiums: 21
Page 7 and 8: Acknowledgments I would like to tha
Page 9: Abstract This document describes th
Page 12 and 13: Contents 3.3.3. Rascal . . . . . .
Page 14 and 15: Contents 8.4. Behavioural Design .
Page 16 and 17: Contents D.3. Domain Framework Mode
Page 18 and 19: List of Figures 6.4. Simple CORBA u
Page 20 and 21: List of Figures 10.27. General read
Page 22 and 23: Chapter 1. Introduction Railway Con
Page 24 and 25: Chapter 1. Introduction MontiCore M
Page 26 and 27: Chapter 1. Introduction ERTMS Forma
Page 29: Part I. Background 9
Page 32 and 33: Chapter 2. Concepts for Safe Railwa
Page 42 and 43: Chapter 3. Domain-Specific Modellin
Page 59 and 60: 4The GOPPRR Meta Meta Model - An Ex
Page 61 and 62: 4.1. Concrete Syntax Description Fo
Page 63 and 64: 4.2. GOPPRR C++ Abstract Syntax Mod
Page 65 and 66: 4.2. GOPPRR C++ Abstract Syntax Mod
Page 67 and 68: 4.5. The Object Constraint Language
Page 69 and 70: 4.5. The Object Constraint Language
Page 71 and 72: 4.6. Tool Chain where artefacts are
Page 73 and 74: 4.7. Conclusion External Artefacts
Page 75: Part II. Dependability 55
Page 78 and 79: Chapter 5. Verification and Validat
Page 85 and 86: 6Security in Open Source Software A
Page 87 and 88: 6.1. Memory Management Open Meta Me
Page 89 and 90: 6.2. Hardware Virtualisation a fixe
Page 91 and 92: 6.2. Hardware Virtualisation in a v
Page 93 and 94: 6.2. Hardware Virtualisation Again,
Page 95 and 96: 6.2. Hardware Virtualisation the fa
Page 97: Part III. openETCS Case Study 77
Page 100 and 101: Chapter 7. openETCS Meta Model far
Page 102 and 103: Chapter 7. openETCS Meta Model gEVC
Page 104 and 105: Chapter 7. openETCS Meta Model gEVC
Page 106 and 107:
Chapter 7. openETCS Meta Model gMai
Page 108 and 109:
Chapter 7. openETCS Meta Model Outp
Page 110 and 111:
Chapter 7. openETCS Meta Model thei
Page 112 and 113:
Chapter 7. openETCS Meta Model gSub
Page 114 and 115:
Chapter 7. openETCS Meta Model The
Page 116 and 117:
Chapter 7. openETCS Meta Model can
Page 118 and 119:
Chapter 7. openETCS Meta Model The
Page 120 and 121:
Chapter 7. openETCS Meta Model List
Page 122 and 123:
Chapter 7. openETCS Meta Model 5 s
Page 124 and 125:
Chapter 7. openETCS Meta Model 7.5.
Page 126 and 127:
Chapter 7. openETCS Meta Model 12 )
Page 128 and 129:
Page 130 and 131:
Chapter 7. openETCS Meta Model Thus
Page 132 and 133:
Chapter 7. openETCS Meta Model In t
Page 134 and 135:
Chapter 7. openETCS Meta Model Valu
Page 136 and 137:
Chapter 7. openETCS Meta Model This
Page 138 and 139:
Chapter 7. openETCS Meta Model and
Page 140 and 141:
Page 142 and 143:
Chapter 8. openETCS Domain Framewor
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Chapter 9. openETCS Generator Appli
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Chapter 10. openETCS Model No Power
Page 202 and 203:
Chapter 10. openETCS Model c4 bool
Page 204 and 205:
Chapter 10. openETCS Model c1 c8 c1
Page 206 and 207:
Chapter 10. openETCS Model Applicat
Page 208 and 209:
Chapter 10. openETCS Model c1 c25 c
Page 210 and 211:
Chapter 10. openETCS Model Initiali
Page 212 and 213:
Chapter 10. openETCS Model Reverse
Page 214 and 215:
Chapter 10. openETCS Model 0 (CONST
Page 216 and 217:
Chapter 10. openETCS Model Current
Page 218 and 219:
Chapter 10. openETCS Model c7 bool
Page 220 and 221:
Chapter 10. openETCS Model Current
Page 222 and 223:
Chapter 10. openETCS Model The purp
Page 224 and 225:
Chapter 10. openETCS Model 10.3.3.
Page 226 and 227:
Chapter 10. openETCS Model be expla
Page 228 and 229:
Chapter 10. openETCS Model 10.4.4.
Page 231 and 232:
11 openETCS Simulation Generally, a
Page 233 and 234:
11.2. Platform Specific Model for t
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
11.3. Simulation Model Figure 11.6.
Page 241 and 242:
11.3. Simulation Model 11.3.2. CDMI
Page 243 and 244:
11.3. Simulation Model sets the Boo
Page 245 and 246:
11.3. Simulation Model Entering_Dri
Page 247 and 248:
11.3. Simulation Model The states o
Page 249 and 250:
11.3. Simulation Model Figure 11.13
Page 251 and 252:
Page 253 and 254:
Page 255:
11.6. Conclusion about warnings, fa
Page 258 and 259:
Chapter 12. Conclusion and Outlook
Page 261:
Part IV. Appendix 241
Page 264 and 265:
Appendix A. GOPPRR to MOF Transform
Page 266 and 267:
Appendix B. openETCS Meta Model Con
Page 268 and 269:
Page 270 and 271:
Page 273 and 274:
DopenETCS Domain Framework D.1. Dom
Page 275 and 276:
D.2. Domain Framework Source Code 8
Page 277:
D.3. Domain Framework Model 32 m_pT
Page 280 and 281:
Appendix E. openETCS Generator 39 <
Page 282 and 283:
Appendix E. openETCS Generator 200
Page 284 and 285:
Appendix E. openETCS Generator 46 4
Page 287 and 288:
FMetaEdit+ Generators F.1. GOPPRR X
Page 289:
GopenETCS Unit Testing G.1. Unit Te
Page 292 and 293:
Appendix H. openETCS Simulation 14
Page 294 and 295:
Page 296 and 297:
Page 299 and 300:
Glossary ANTLR ANother Tool for Lan
Page 301 and 302:
Glossary EVC An European Vital Comp
Page 303 and 304:
Glossary OEM An original equipment
Page 305:
Glossary XML The Extensible Markup
Page 308 and 309:
Bibliography [12] “EN 50128 - Rai
Page 310 and 311:
Bibliography [39] ——, ““Ope
Page 312 and 313:
Bibliography [69] T. J. Parr and R.
Page 315 and 316:
Index Artefact, 51 Automatic train
Page 317 and 318:
Index Linux, 149 Memory management,
show all

Ph.D. - geht es zur Homepage der Informatik des Fachbereiches 3 ...

Create successful ePaper yourself

Delete template?

Save as template?