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

More documents

Recommendations

Info

Chapter 9. openETCS Generator Application an option because much more complex and specialised generators in MERL would have to be implemented, which would raise problems already discussed in Chapter 4. On the other hand, it is already assured by the generated tests for the transformation to a CProject object that the GOPPRR C++ abstract syntax model is correct and fully covered / used. Hence, it is sufficient to test if the transformation from CProject object to C++ source code is correct or rather covers the whole model. The executable EVC binary is the end product of the generation process and consists of linked object or rather binary code. This is very difficult to analyse by parsing since object code is always platform specific. Another possibility would be the generation of test methods / functions that are linked with object code of the EVC binary. Since it is quite complicated to identify the C++ object structure by directly analysing the application memory or rather the heap [77, pp. 353-453], the openETCS domain framework objects would have to be accessed for testing. Unfortunately, according to Section 8.3, class instances of the domain framework cannot be easily compared with instances of GOPPRR C++ abstract syntax model because not all model elements are directly transferred to domain framework instances and not all element properties, including the OID, are used. Therefore, a simple identification of elements by their OID is not available. Furthermore, the CCPPGenerator class generates directly the domain framework instantiation in a main-function, which means that for testing the target code would have to be modified. This might influence the validity of the testing results for the real EVC binary. Alternatively, instead of examining the object code, the generated C++ source code could be analysed. Since CCPPGenerator uses the OIDs for generation of object instance names / variable declaration, their GOPPRR equivalence can be found much easier by parsing the generated source code file. It is also questionable if it is necessary to again run tests on openETCS domain framework objects since those are already tested independently from the generators (see Section 8.7). To only test the CCPPGenerator class, the analysis of the generated C++ source code file should be sufficient. This means concretely that the generated C++ source code is checked for the existence of certain C++ statements that instantiate the corresponding domain framework classes. In contrast to the verification of the transformation from a GOPRR model instance to GOPPRR C++ abstract syntax model, not all elements can be tested for existence because the openETCS C++ generator does not use all GOPPRR elements to create a certain openETCS domain framework class instances. For example, the roles “DataOutput” and “DataInput” in a data flow are only used to connect a certain function block object output with a certain input, but their OID is never used. On the other hand, the “DataFlow” relationship is directly used to create CFlow or CBitFlow instances, and accordingly all “DataFlow” relationships in the GOPPRR model must exist in the generated C++ code as object. Thus, currently only the existence of instantiation statements of all function blocks, EVC Mode, and language objects and the objects for the “DataFlow” relationship is tested. 176
9.8. openETCS Tool Chain for Dependable Open Model Software 9.8. openETCS Tool Chain for Dependable Open Model Software The resulting concrete openETCS tool chain for the complete development process is sketched in Figure 9.11. The verification of the transformation from the GOPRR to the GOPPRR instance is done, corresponding to the description in Section 9.7, by the generated “Functional Test Cases”, which are run on the “GOPPRR Abstract Syntax Tree”. The verification of the transformation of the concrete GOPPRR C++ abstract syntax model to the concrete source code for the EVC binary is implemented in the “Functional Testing”, which consumes the generated “Source Code” and “GOPPRR Abstract Syntax Tree” artefact. The validation of the generation process refers here to a valid model, which is checked by the constraints of the static semantics. Also, the final build process of the EVC binary and its execution under a Xen hypervisor were added. Since the extensions or transformations for the PSM cannot be generally foreseen and neither is automatically generated from other artefacts, it is omitted in Figure 9.11. 9.9. Conclusion The openETCS generator application fulfils all initially defined requirements by combining several C++ classes producing the different generator output. To ensure that Req.9 is fulfilled, tests can be generated automatically for both models: First, in a general way, independent from the meta model, for the transformation from the GOPRR meta model instance in MetaEdit+ to the GOPPRR C++ abstract syntax model. Second, for the concrete model-to-text transformation to openETCS domain framework objects. The usage of cmake provides implicitly a platform independent build configuration for compiling and linking the EVC executable binary, which facilitated the implementation of the CBuildGenerator and fulfils Req.11. CVMGenerator provides an implementation for generating configurations for the Xen hypervisor for para-virtualisations, which fulfils Req.12. The separation of independent data flows for parallelisation could be future development work for the openETCS generator application because it is already prepared in the domain framework. Although the checking of the static semantics was only realised by the direct implementation of exemplary constraints in C++, all OCL constraint statements in Section 7.5 could be used in combination with the UML-based Specification Environment (USE) [34] application, which is available as FLOSS, to check the static semantics outside the openETCS tool chain in Figure 9.11. Accordingly, the openETCS tool chain and USE would have to be adapted to allow the export and import of the concrete GOPPRR C++ abstract syntax model instantiation. Hence, an appropriate XMI export must be realised inside the GOPPRR package / name space and the corresponding XMI import mechanism in USE, which neither is currently available. 177
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:
Chapter 8. openETCS Domain Framewor
Page 146 and 147: Chapter 8. openETCS Domain Framewor
Page 180 and 181: Chapter 9. openETCS Generator Appli
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 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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?