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.

2.2. European Train Control System<br />

indirectly published via the source code. This is a problem if the specification is not licensed in<br />

the manner of OSS or FLOSS, which means generally public acc<strong>es</strong>sible and usable. Therefore,<br />

it is only meaningful to develop OSS or FLOSS for train control systems which specification is<br />

adequately licensed. This circumstance directly influenced the choice of train control system<br />

used for the case study in Part III. Further issu<strong>es</strong> related to OSS and FLOSS software for<br />

safety-critical systems are discussed in Chapter 6.<br />

2.2. European Train Control System<br />

The European Train Control System (ETCS) [67, pp. 102-105] is a component of the standardised<br />

European train traffic control system, which should replace the several different used<br />

train safety systems in European countri<strong>es</strong>. The initiative for creating a general train control<br />

system for the European Union was already launched in 1990. Meanwhile, there exist several<br />

revisions of the specification of ETCS, which are now published and maintained by the<br />

European Railways Agency (ERA) [21]. The actual version of the ETCS specification can be<br />

found in [23]. The specification itself is divided in so-called Subsets, which combine a set of<br />

documents for a certain specification issue. The following d<strong>es</strong>cription of ETCS mainly relat<strong>es</strong><br />

to the Subset-026 [83], which is also called System Requirement Specification (SRS). It must<br />

be emphasised that this work refers to the specification version 2.3.0, which was mandatory at<br />

the beginning of this work in 2010.<br />

The SRS 2.3.0 consists of seven documents:<br />

Introduction general introduction to ETCS and the documents in the SRS [86]<br />

System D<strong>es</strong>cription d<strong>es</strong>cription of an ETCS [84]<br />

Principl<strong>es</strong> principl<strong>es</strong> for ETCS [89]<br />

Mod<strong>es</strong> and Transition d<strong>es</strong>cription of possible mod<strong>es</strong> and transition in ETCS [88]<br />

Procedur<strong>es</strong> operation procedur<strong>es</strong> [90]<br />

ERTMS/ETCS Language structur<strong>es</strong> for data transmission [85]<br />

M<strong>es</strong>sag<strong>es</strong> data structur<strong>es</strong> for radio communication in ETCS [87]<br />

This SRS document often refers to another specification element outside the Subset-026, the<br />

Functional Requirement Specification (FRS) [22]. The FRS defin<strong>es</strong> the functionality that is<br />

available in ETCS. It is more abstract because it only d<strong>es</strong>crib<strong>es</strong> required functions, but not<br />

how those are realised. In the development cycle of the ETCS specification, the FRS is used as<br />

input for the SRS, in which the functional requirements are transformed to requirements of the<br />

whole system. Therefore, the FRS is never used directly for system development.<br />

2.2.1. General Purpose<br />

The ETCS introduction defin<strong>es</strong> some general goals and advantag<strong>es</strong> [86, p. 4]:<br />

13

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

Saved successfully!

Ooh no, something went wrong!