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

More documents

Recommendations

Info

Chapter 8. openETCS Domain Framework objects that are not used in the current data flow. This modification of a currently unused object can lead to undefined and/or undesired behaviour not corresponding to the concrete model. The concrete syntax of data flows between function block objects in the openETCS meta model in Subsection 7.3.2 defines DataFlow relationships as the related interconnection. Although function block objects can be reused in any graph of a model 4 , this DataFlow relationship is unique. Therefore, an obvious and direct solution is to additionally design a class representing a data flow or rather an interconnection between two function block objects. This class should be instantiated 5 for each relationship in the openETCS model. The classes for the data flow interconnection are shown in Figure 8.4. Figure 8.4.: Class diagram of the function block classes for the data flow As data flows can be of different types (double, integer, string, etc.), CFlow, the additional class for interconnections, is a template class [79]. Its first template parameter INPUT_TYPE_T 4 instance of the openETCS meta model 5 generated by openETCS generator 130
8.3. Structural Design defines the corresponding implementation or rather C++ type [79], like bool, double, int, etc. The second template parameter FLOW_TYPE_T defines the type of the related CInput object. This parameter has the default value CInput< INPUT_TYPE_T > and normally does not have to be set explicitly. It is used to define the attribute m_pInput of CFlow that is the connected CInput instance. m_pInput is not modelled as composition in Figure 8.4 because the usage of template parameters in UML class diagrams is limited. The CInput template class, which is nested in the CFunctionBlock base class, is used to encapsulate each data flow input as property. Its template parameter INPUT_TYPE_T defines, as for the CFlow class, the concrete implementation data type. This means each input of a certain function block type or rather class is defined as attribute of the type CInput with the corresponding template parameter for the concrete data flow type corresponding to the meta model. Compared with the direct usage of an implementation data type, this has the advantage that the modification state of each input can be made available or visible to its possessing function block object. Furthermore, the access of inputs can be made thread-safe [7] by using a mutable exclusion (mutex) [7] object via the m_ValueMutex composition. It must be noted that the mutex class is located within the std:: name space of the standard C++ library [7], which is not explicitly modelled in Figure 8.4. Unfortunately, the bit data flow type between oVariableStorage objects in the openETCS meta model (see Subsection 7.3.2) cannot be directly mapped to a data type in the implementation. Hence, the CFlow template class cannot be used for those data flows and the additional CBitFlow class was added, which is not a template class and is especially designed for data flows between CStorage instances. Correspondingly, the aggregation between those two classes has the two ends m_pInput and m_BitValue. The first is the input storage object, from the view of CFlow while the latter holds all outputs to other CStorage objects. It should be remarked that m_pInput is modelled as aggregation compared to the m_pInput because CBitFlow is not a template class. Since all interconnections or rather all flows are assigned to a certain parent CEVCStateMachine object via the m_Flows composition, CAbstractFlow is used as base class for the both concrete flow types. Finally, to solve the initial problem of the general usage or rather execution of all existing interconnection / data flows, each CAbstractFlow instance requests via the m_pStateMachine aggregation if it is part of the currently executed data flow, which means an element of the m_Flows aggregation. If not, any message from a connected function block object using operator=() is ignored. Otherwise, the value is marshalled to the related input. Since the flows between function block objects that are part of an embedded state machine respectively a CControlFlow instance should only be executed if the related CState object is currently active, also CState posses an aggregation m_Flows to CAbstractFlow. 8.3.2. Driver Machine Interface Details All classes especially related to the DMI are presented in a separated class diagram in Figure 8.5. CDMIObserver is the abstract observer [32, pp. 293-303], from which each concrete observer implementation must be derived and methods called by the CEVCStateMachine class must be implemented by overriding [79]. The parent CEVCStateMachine instance holds pointers to all registered, concrete observers in the aggregation m_Observers via the abstract base type to be 131
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 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 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 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?