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

8.5. Deployment Design
DriverMachineInterfaceMOC
PlatformSpecificClientsMOC
Storage
Condition
Transition
Configuration
DBusInterfaces
DBusAdaptors
Holds the implementation of the concrete DMI Qt 4 observer
CDMIQWidget.
Includes all source code for accessing the platform-specific
extensions for COdomoter, CEmergencyBrake, CServiceBrake,
CBaliseDeviceIn, and CBaliseDeviceOut. For testing
purposes without platform-specific adaptations, also a stub 8
implementation is provided for each class.
Source code of the CStorage class. It is provided in a separated
artefact because it is used by several other artefacts like
EVCStateMachine and Language.
Source code of the CCondition class, which is also provided
in a separated class due to multiple dependencies.
Source code of the CCondition class, which is separated for
the same reasons as for CCondition and CStorage.
Provides type definitions and global constants for the whole
domain framework.
Holds the source code for all D-Bus interfaces [31] for platform
specific classes.
Provides the source code for all D-Bus adaptors [31] for platform
specific classes. The usage and integration of D-Bus [31]
will be additionally discussed at a later point of this section.
AdaptorStubsMOC Source code of all stubs classes for D-Bus adaptors. For
concrete platform-specific adaptations, those should be used
or rather implemented by class inheritance [79].
All source artefacts with the postfix “MOC” in their name require the usage of Qt 4’s meta
object compiler (moc) [59].
As each library component is located in another execution environment respectively another
virtual machine, a middleware for IPC communication has to be used (see Req.8), which was
partly discussed in Subsection 6.2.4. For this purpose D-Bus is employed, which was also
introduced in Subsection 6.2.4. The D-Bus daemon [31] is executed directly on the EVC and
therefore enables the communication between both execution environments but only through
defined interfaces (see Chapter 6). Details about this interconnection are shown in Figure 8.15
as UML component diagram [64].
The interfaces required by the libopenETCSPIM component are IEmergencyBrake, IOdomoter,
IServiceBrake, IBaliseDeviceIn, and IBaliseDeviceOut. Those define the interfaces
that have to be implemented by suppliers of hardware components defined in the ETCS SRS.
8 empty
143