Figure 111 : Domain model of MUNICH platform5.6.4.7 Specification of functional view
The realisation of the use-case according to the IoT ARM a Functional View is
tailored to the use-case needs to be specified. The Functional View for the
MUNICH platform is depicted in Figure 112. No IoT Service Resolution is
required, because all needed services are already known to the system at
design time. A VE Resolution FC is included in the FV. This FC is able to
resolve particular towels to the IoT Service they are currently associated with.
The ̳VE & IoT Service Monitoring‘ FC is used to update the current state of
towels whenever these VEs change their position in the operating theatre.
Whenever VEs change their positions their associations between the VEs and
the IoT Services reading the RFID tags change too. No Service Organisation
functions are required in this use case since the binding of services is static and
can therefore be hardwired. To accommodate IoT Business Process
Management functionality that is required in the MUNICH platform the
respective FG is included in the FV. The process model diagram depicted in
Figure 110 was created by the ̳Process Modelling‘ FC and this model is
executed by the ̳Process Execution‘ FC. The Functional View of the MUNICH
platform includes IoT Services for the RFID readers and for Event Storage