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

More documents

Recommendations

Info

Chapter 12. Conclusion and Outlook static semantics can have an erroneous impact to all lower instances. Accordingly, the concrete syntax – especially the graph bindings – and the static semantic were extensively documented. Furthermore, mathematical models were developed and introduced to also formalise the dynamic semantics of the openETCS meta model. All static source code that does not have to be generated from a concrete model was designed and implemented as domain framework for the openETCS meta model. An object-oriented design was chosen because this could be aligned to the object-oriented meta model syntax, which simplified the later generator development. Hence, the openETCS domain framework provides classes, which only have to be instantiated from the concrete openETCS model by the generator. All implementations of the dynamic semantics were transferred accordingly to the domain framework libraries. Additionally, functional tests were provided to verify the correctness of the openETCS domain framework implementation. The openETCS generator, as link between the concrete openETCS model as formal specification and the source code, was developed and its software design was discussed. Additionally, the developed strategies for the verification of the used model transformation for the generation of the openETCS source code for the EVC were described: Assert statements are generated from the GOPRR instance, which can be executed on the transformed GOPPRR model to ensure that all model elements for the model-to-model transformation from GOPRR to GOPPRR model are correctly converted. The final model-to-text transformation from GOPPRR model to the instantiation of the openETCS domain framework is verified by tests for the existence of certain domain framework objects in the generated source code. Furthermore, the openETCS generator provides the possibility to generate the build configuration needed for creating the EVC binary from the generated source code and the configuration for executing the PIM and PSM of the openETCS model in separated virtual machines under a Xen hypervisor. The ETCS SRS or rather Subset-026 [83] was partly 1 modelled and discussed by exemplary diagrams of the corresponding openETCS model for all developed graph types. Additionally, the possibility of tracing the modification of safety properties due to model extensions was illuminated. A simulation for the model or rather the generated openETCS EVC binary was developed under the MDA principle to validate the complete openETCS case study. Hence, a special simulative PSM had to be realised to provide the interconnection between EVC binary and simulation. The successful execution of the simulation shows that the proposed and developed concepts for developing safety-critical software for train control applications as open model software can be seen as a proof-of-concept. The reduction of model size and complexity is no limitation to this statement because the influence of further model extensions was also illuminated and the case study is a valid sub-subset of the ETCS SRS. The concepts for dependability were only exemplary realised by generating configurations for VMs, which was also applied in the simulation execution. The certification of the developed openETCS case study software for the EN 50128 and SWSIL 4 is obviously out of the scope of this work because this always has to be done by an external party. Since neither a concrete hardware target platform was available during this work nor the proposed minimal host operating system, all tests (including the simulation) are pure software tests and no system 1 according to the scope of the openETCS case study 238
integration tests. Future work would primary focus on the extension of the openETCS meta model and model to completely cover the ETCS SRS, which also would render extensions of the domain framework and the generator necessary. The direct integration of the simulation models and the Subset-076-6-3 [82] in the openETCS model and meta model seems promising to enhance the modelling process related to safety properties of the system. Furthermore, it might be necessary to investigate if the tracing of model extensions and safety properties by the identification of differences in model instances is sufficient for SWSIL 4 conformance or if model extensions must also be added to the meta model capabilities. Currently, not all parts of the developed tool chain conform to the Open Proofs concept, which requires all elements to be FLOSS. Primary, this is related to meta modelling and modelling application because with MetaEdit+ only a closed source application is available for the GOPRR meta meta model. Thus, it would be necessary to develop the openETCS meta model under a different meta meta model that has FLOSS tool support. Alternatively, the openETCS meta model could be simply transformed to avoid a complete redevelopment, which was developed and discussed for the MOF meta meta model. While this transformation only have to be proceeded, the main future work would have to focus on the development of the modelling tool because related Eclipse plug-ins currently do not provide a stable performance. Furthermore, the openETCS model or rather the formal specification has to be remodelled in the new meta model or an appropriate model-to-model transformation has to be found. Neither, the simulation generation by the RT-Tester application is aligned to the idea of open proofs and could accordingly be extended in further work. In contrast to the development of new FLOSS generators for the simulation model, it seems more promising to directly integrate the simulation specification in the openETCS meta model, which means another extension of the openETCS specification language. 239
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 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Chapter 3. Domain-Specific Modellin
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
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 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 255: 11.6. Conclusion about warnings, fa
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 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 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?