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

More documents

Recommendations

Info

Chapter 1. Introduction Railway Control Investigation Domain-Specific Modelling Investigation Safety Standards Investigation FLOSS Investigation ETCS Specification Evaluation GOPPRR Meta Meta Model Development Hardware Virtualisation Investigation openETCS Meta Model Development openETCS Model Development openETCS Domain Framework Development openETCS Generator Development openETCS Simulation Development Figure 1.1.: Research process of the main objectives 1.2. Main Contributions The following new, scientific contributions were gained by this dissertation: → the introduction of open source software developed under model-driven aspects with the new denomination open model software [26] → the usage of hardware virtualisation as security measure in the railway domain for open source software [26] → the GOPPRR 1 meta meta model as an extension of the existing GOPRR meta meta model that is applicable for the modelling of safety-critical systems [28] → a graphical domain-specific language for a subset of the ETCS specification as case study including a formal specification language as meta model, a domain framework, a code generator, and a model of parts of the ETCS specification [71, 27, 28] → the development of a completely model-driven tool chain for a case study of the European Train Control System (ETCS) for dependable software [27] Each point is discussed in detail in the following paragraphs. Initially, it was necessary to examine, which prerequisites have to be met in order to develop safety-critical control systems as open source software. Since the usage of Domain-Specific Modelling (DSM) [46] and the extension of such models by supplier-specific implementations implies certain security related problems, those were analysed and discussed. The usage of hardware virtualisation [92] has been proposed as solution and is described in [26]. The selection of an appropriate meta meta model is of certain interest since it builds the basis for the syntax definition of the Domain-Specific Language (DSL) [46]. Although the Graphs, Objects, Properties, Roles, and Relationships (GOPRR) [45, app. A] meta meta model fulfils most of the needs, the Graphs, Objects, Ports, Properties, Roles, and Relationships (GOPPRR) 1 It must be noted that this acronym was also claimed by MetaCASE – developer of the MetaEdit+ [56] application – during the development of this work to also reflect the presence of ports in their meta meta model. However, the GOPPRR meta meta model extension developed in this thesis must not be understood as a rival product of the GOPPRR meta meta model used in MetaEdit+ but as an extension for it that is required in the context of safety-critical systems. 2
1.3. Related Work meta meta model extension was developed with the aim to be able to define a more precise concrete syntax and certain model constraints as static semantics in a general way. Parts of these results will be published in a special issue of Science of Computer Programming [28]. A DSL or rather a meta model based on GOPPRR was developed for ETCS [38], which is an excellent choice for a case study, because it is a publicly available (and usable) train control standard. There also exists an initiative of the German Railways (Deutsche Bahn) to develop an open source solution for ETCS. This initiative led to an European project supported by the Information Technology for European Advancement (ITEA2) board [43] and funded in part by the German Federal Ministry of Education and Research (Bundesministerium für Bildung und Forschung). The University of Bremen is a participant within the openETCS consortium. During the ETCS meta model development, several new formalisms, like data and control flow, were integrated, tested, and adapted to certain specialities of the ETCS specification. Also, new formalisms mainly derived from the specification were developed to support later the transfer of the mostly textual specification document to a model of the meta model. Since the meta model had to be developed in several iterative steps to test certain formalisms or rather syntaxes, an initial version of the DSL was published in a book chapter [71] in [29]. A new version of the DSL will be also included in [28] and the latest results can be found in this document. According to the instances of a DSL or a Model-Driven Architecture (MDA) [44], a domain framework was developed, which already integrates the results from the initial security analysis in form of hardware virtualisation and also hardware abstraction. Additionally, a code generator was realised as link between model and domain framework, which also provides methods for verification and validation by dynamic testing and model constraint checking. Parts of these methods and strategies are independent from the meta model for ETCS and are therefore completely re-usable for any DSL using the GOPPRR meta meta model. To test the ETCS model or rather the generated code, a virtual simulation environment was set up, which can be used to trace the specification model behaviour. The developed model-driven tool chain of the case study will be published in [27]. The requirements for verification and validation were investigated for applicable safety standards in the railway domain. Thus, verification mechanisms were integrated into the tool chain for testing all static code and the transformation processes for the code generation. A static semantics was defined by a set of model constraints to ensure the validity of concrete models. 1.3. Related Work Domain-Specific Modelling in the Railway Domain The general applicability of DSM in the railway domain was successfully investigated in [57] and [75]. Especially in [57], the potential of domain-specific modelling for train control applications was investigated, but, in contrast to this thesis, with focus on the control centre perspective. More important, this work adds the aspect of open source software in the railway domain. 3
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 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 80 and 81:
Page 82 and 83:
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?