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

Chapter 8. openETCS Domain Framework
these two libraries alone cannot build executable binaries for the two execution environments.
As already discussed in this chapter and according to Req.6 for the PIM, this is done by the
instantiation of the openETCS domain framework classes by the code generator. For the
execution of the PSM, any kind of adaptor implementation is required even if it only consists
of stub classes. The deployment including these instantiations for PIM and PSM is shown in
Figure 8.19.
Figure 8.19.: UML deployment diagram of the instantiation of PIM and PSM
The openETCS.xml artefact holds the CIM respectively the openETCS model in the GOP-
PRR meta meta model (see Chapter 4). The openETCSGenerator (to be discussed in Chapter 9)
application uses it to generate the C++ source artefact that holds the corresponding instantiations
of domain framework classes and the main() function [79]. The openEVC process
/ binary is manifested by the GeneratedInstantiations artefact and imports or rather links
against the libopenETCSPIM component with the platform independent types. The HWSpecificImplementations
source artefact holds according to its name the concrete platform and/or
hardware specific implementations. Currently, there exists only a simulative implementation,
which will be explained and used in Chapter 11. This specific artefact uses or rather includes
the AdaptorStubsMOC artefact, which holds the before presented D-Bus adaptor stub classes
in Figure 8.18. Obviously, the HardwareServices process / binary must be manifested by the
HWSpecificImplementations artefact and is linked against the libopenETCSPSM component.
148