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 ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
10.5. Model Extensions<br />
10.5. Model Extensions<br />
Model extensions are mainly needed in the case that an existing model 5 has to be extended or<br />
adapted for a newer version of the ETCS SRS. Ideally, th<strong>es</strong>e extensions only have to be done<br />
in the model but not in the meta model because any chang<strong>es</strong> there might require additional<br />
modifications for the code generators and the domain framework.<br />
On the other hand, it seems doubtful that is possible to for<strong>es</strong>ee any potential chang<strong>es</strong> of the<br />
SRS in the future for the d<strong>es</strong>ign of the meta model or rather the openETCS formal specification<br />
Language (in Figure 7.1).<br />
Furthermore, even extensions on the model level should be traceable [78, p. 323][74] because<br />
those are always related to the safety of the modelled system. One possibility is to trace<br />
chang<strong>es</strong> in the model by identifying the difference (of model elements) between two model /<br />
SRS versions. Unfortunately, finding the difference in graphical models is not always trivial<br />
because a modification of the graphical repr<strong>es</strong>entation do<strong>es</strong> not always mean a modification<br />
of the abstract syntax model or the dynamic semantics. A loophole to this situation is a<br />
transformation to a model repr<strong>es</strong>entation that only holds the abstract syntax..<br />
The GOPPRR meta model extension is such a model repr<strong>es</strong>entation, which was introduced<br />
in Chapter 4. Especially, the intermediate XML model in Section 4.3 can be directly used to<br />
identify the syntactical differenc<strong>es</strong> between two models by using standard tools. Additionally,<br />
a custom application could be developed that us<strong>es</strong> the GOPPRR C++ abstract syntax model<br />
in Section 4.2.<br />
In contrast to identifying model extensions between different model versions, it is also possible<br />
to take model extensions directly into account for the d<strong>es</strong>ign of the meta model. In other words,<br />
the openETCS formal specification could offer a syntax to directly expr<strong>es</strong>s extensions due to<br />
new SRS versions in the graphical model. This would have the advantage of a more abstract<br />
repr<strong>es</strong>entation, compared to building the difference of XML fil<strong>es</strong> but also would increase the<br />
complexity of the meta model and the corr<strong>es</strong>ponding model.<br />
10.6. Conclusion<br />
This chapter introduced the concrete model of the openETCS case study for a sub-subset of<br />
the ETCS SRS. Repr<strong>es</strong>entative exampl<strong>es</strong> of the model from all levels r<strong>es</strong>pectively graph typ<strong>es</strong><br />
were pr<strong>es</strong>ented and d<strong>es</strong>cribed. The complete openETCS model can be found in Appendix C.<br />
Furthermore, an important issue of model extensions for new ETCS SRS versions was<br />
illuminated and a possible outlook on how the traceability of model extensions might be<br />
increased in future work was given.<br />
5 in terms of MDA the CIM<br />
209