The significant classes in the service are shown in the UML class diagram below. This is a static view of the Saturimeter Service class in relation to other classes. The SaturimeterDevice is the class that plays the role of the servicemanager found in the ontology.
The significant communication related to the service is shown in the UML sequence diagrams below. The first figure shows how the scheduler triggers the SaturimeterService to ask for a new value on the SerialLine.It is the Saturimeter, that sends the data as a characterstream through the SerialLine, and they are return parameters to the saturimeterservice. The SaturimeterService then forwards the data in the way it is expected by the assemblymanager, which is then in turn able to propagate them on in the assembly.
In the sequence diagram below the assembly communication is shown. The HeartrateInspectionService is interested in knowing the heart rate. The redundancy of this value from the SaturimeterService and the RespiratorService is used in the assembly to provide that. If there is an inconsistency, that triggers an alarm in a given policy about the values, the AlarmService is asked to invoke an alarm.