FunctionModeling::LocalDeviceManager

Header Image
Content:
LocalDeviceManager : Public Class FunctionModeling
The LocalDeviceManager represents a DesignFunction that act as a manager or functional interface to Sensors, Actuators and other devices. It is responsible for translating between the electrical/logical interface of the device, as provided by a BasicSoftwareFunction, and the physical interface of the device. For example, consider a temperature sensor with voltage output. The HardwareFunctionType defines the transfer from temperature to voltage. A BasicSoftwareFunction relays the voltage from the microcontroller's I/O. The role of the LocalDeviceManager is now to translate from voltage to temperature value, taking into account the sensor's characteristics such as nonlinearities, calibration, etc. The resulting temperature is available to the other DesignFunctions. By separating the device specific part from the middleware and ECU specific parts, it is possible to systematically change interface function together with the device.<br/><br/>The role of the LocalDeviceManager is to act as an interface between the electrical output of Sensors or electrical input of Actuators and the physical quantity of those devices.<br/><br/><br/>Semantics:<br/>The LocalDeviceManager encapsulates the device-specific or functional parts of a Sensor or Actuator, device, etc. interface.<br/><br/><br/>Constraints:<br/>[1] A DesignFunctionPrototype typed by a LocalDeviceManager shall be allocated to the same ECU node as the device that it manages is connected to.<br/>[2] A LocalDeviceManager shall be connected with BasicSoftwareFunction(s) and DesignFunction(s).<br/><br/><br/>Extension: Class, specialization of SysML::Block<br/>
  • Advanced
  • Other Links
Property Value
isFinalSpecialization: 0
Object Type Connection Direction Notes
DesignFunctionType Class Generalization To