31.01.2014 Views

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

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

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

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10.2. Data and Control Flows in ETCS Mod<strong>es</strong><br />

The transition matrix holds all transitions that are defined in the ETCS SRS for the subset<br />

of mod<strong>es</strong> and can be therefore easily compared with the transition table [88, p. 40] in the<br />

specification document. It must be noted that only those conditions are part of the modelled<br />

transition matrix that are applicable in ETCS Application Levels 0 and 1 because the selected<br />

subset for the case study in Section 7.1 preclud<strong>es</strong> Application Levels 2 and 3.<br />

10.2. Data and Control Flows in ETCS Mod<strong>es</strong><br />

In contrast to the gEVCStateMachine root graph, a gMainFunctionBlock is modelled for each<br />

ETCS Application Level in each Mode. Thus, this section is divided in subsections for each<br />

ETCS Mode and, where required, in sub-subsections for different Application Levels.<br />

10.2.1. No Power Mode<br />

Although the No Power Mode is not directly related to a certain Application Level, it is<br />

relevant for the model that No Power is modelled for all possible Application Levels. Application<br />

Level 0 is defined as default for No Power because it is the initial mode for a newly<br />

started EVC binary. Anyway, it is possible that No Power is entered during the runtime<br />

from another Mode in Application Level 1. For example, this is the case for the transition<br />

Full Supervision c29−p2<br />

−→ No Power.<br />

Application Level 0<br />

The main functionality in No Power is, according to [88, p. 10], the enforcing of the train stop<br />

via the emergency brake system. Furthermore, the driver should be able to power up the<br />

EVC (via the DMI), which should activate the transition “c4-p2” to the Stand By Mode. The<br />

corr<strong>es</strong>ponding modelled data flow is sketched in Figure 10.2 as gMainFunctionBlock graph. Of<br />

course, in a “real world” implementation of ETCS, powering the system refers to physically<br />

powering, but since this case study is realised as pure software, this functionality bas<strong>es</strong> on a<br />

simple DMI input object.<br />

The DMI is modelled by a separated oSubFunction object “DMI No Power” to be reusable in<br />

other Application Levels. The corr<strong>es</strong>ponding model is shown in Figure 10.3. The DMI displays<br />

the current ETCS Mode and Application Level to the driver. Additionally, the driver is able to<br />

power up the system via the “System On Power” oDMIInput object.<br />

Application Level 1<br />

The only difference between Application Level 0 and 1 in the No Power mode is the assignment<br />

of the “Stored ETCS Level” oVariableStorage object, which is therefore omitted. The DMI<br />

is modelled by the same oSubFunction object as for Application Level 0 and was already<br />

pr<strong>es</strong>ented in Figure 10.3.<br />

181

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!