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

More documents

Recommendations

Info

Chapter 7. openETCS Meta Model can be only used at the beginning of a telegram to define a telegram header [85]. Therefore, they only can be modelled in the order between the oRootNode object and the first oPacket or oAnyPacket instance. The VariableOrder relationship is used between the connection between two oVariableInstance objects. PacketOrder is valid between oAnyPacket and/or oPacket types, and between the last oVariableInstace and the two packet types. The oAnyPacket object type is different from the others because it cannot be directly found in SRS [85]. It can be used to model that at a certain point in the variable-packet order several oPacket objects are possible. The concrete set of oPacket objects is specified in the decomposition of the oAnyPacket instance. In that way, ETCS telegrams only differing from each other in a certain packet can be easier and faster modelled. 7.3.7. gPacket Graph Type Similar to the gTelegram graph type, the gPacket graph type is used to specify the order of oVariableInstance objects in a certain ETCS packet [85]. Three object types are provided: oRootNode defines the start point of a packet order. oVariableInstance defines a certain ETCS variable of a certain type [85]. Therefore, the oVariableInstance object type holds an oVariableType object as property. The oVariableType type is not graphically used (only as property) and specifies the type of an oVariableInstance object, which is similar to a template-mechanism [79] in object-oriented programming languages. The oVariableType type holds several properties for defining the attributes of an oVariableInstance object: 1. size in bits 2. the variable’s resolution [85] 3. the variable’s physical unit oLeafNode determines the last gPacket object in an order. The advantage of defining a property of oVariableType object type is that the concrete oVariableType objects can be reused for several oVariableInstance objects. Apart from enabling the specification of variable orders according to the ETCS specifications [85], also a possibility to model the scaling of certain variables is needed. Scaling means that a value of a certain variable can scale (by multiplication) the value of another. This is modelled by the additional Scaling relationship while the VariableOrder is used for specifying the oVariableInstance object order. The full syntax is illustrated in Figure 7.12. Moreover, the ETCS language specification [85] defines so-called iterating variables. This concept is similar to arrays in C/C++ [79] or other high-level programming languages. A certain variable holds the size of an array and the following variables are components of an array of the specified size. An iterating variable is not modelled by a relationship but by graphical containment, as introduced in Chapter 4. Therefore, oVariableInstance objects that are iterated by another oVariableInstance object are drawn within the iterating instance. In this way, it is also possible to specify nested iterations. A specialisation of iterating variables are so-called conditional iterator variables. In contrast to the normal iteration concept, conditional iterators do not iterate the graphically contained 96
7.4. Concrete Syntax for Type Properties gPacket VariableOrder oVariableInstance 0...* Scaling PreviousVariable 1...1 NextVariable 1...1 oVariableInstance 1...* ScalingValue 1...1 ScaledValue 1...1 oRootNode 1...1 oVariableInstance 1...1 oLeafeNode 1...1 oVariableInstance 1...* oVariableInstance 1...1 Figure 7.12.: gPacket binding syntax objects corresponding to their numerical value. A (numerical) conditional value can be defined, for which all iterated variables (by graphically containment) are exactly iterated once. Otherwise, they will not exits. In this manner, it is possible to define the existence of certain oVariableInstace objects only for certain (numerical) conditions. 7.3.8. gAnyPacket Graph Type The gAnyPacket type is only used to specify a set of oPacket objects for oAnyPacket objects. Hence, it has no binding syntax at all. 7.4. Concrete Syntax for Type Properties As stated in Chapter 4, for a complete meta model syntax definition, besides sub-graphs and graph-binding, the full definition for all types 10 is needed. For the most important properties, this was already done in Section 7.2 and Section 7.3. As the definition of all types is not necessary for understanding the case study and for further reading of this document, this can be found in Appendix B. 7.5. Static Semantics for Models Section 7.3 defined all bindings as concrete syntax for each graph type by means of the GOPPRR meta meta model. However, it is additionally necessary to define constraints for some graph types as static semantics to reduce or refine the allowed syntax for models in special situations. The use of constrains avoids models that do not have a semantic meaning with respect to the SRS and is also an issue related to the safety properties of the generated software. According to Section 4.5, constraints are defined by OCL. 10 graphs, objects, ports, roles, and relationships 97
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 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 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 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 142 and 143: Chapter 8. openETCS Domain Framewor
Page 166 and 167:
Chapter 8. openETCS Domain Framewor
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 ...

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

Delete template?

Save as template?