Modelling QoC criteria |
At design time, developers use the graphical editor to define primitive or composite QoC criteria. |
|
With the editor, defining the refresh rate, precision, spatial resolution, uncertainty and accuracy QoC indicators separately. Then, configure the relations between the accuracy definition and the uncertainty and precision. |
|
Qualifying context information |
At programming time, developers use the editor to generate and complete the source code corresponding to the QoC criteria they choose for their applications. |
|
Fill-in the method getQoCMetricValue() with the algorithm described in Section 5.1 and 5.2. (Class QoCMetricDefinition in the Maven module named qocim-common) |
|
Processing QoC meta-data |
Because all the QoC criteria are based on the same meta-model, QoCIM eases the implementation of generic QoC transformation functions. |
|
Implementing the algorithm described in Section 6.2 with the functions available in the Maven module named qocim-functions. |
|
Expressing QoC guarantees |
The QoCIM framework provides methods to transform instances of QoC indicators into constraints that reflect the capabilities of a producer in terms of QoC. |
|
In the Maven module qocim-routing-filter, using instances of the QoC indicators as parameters of the methods addQoCCriterionConstraints and addQoCValueConstraints in the class IQoCIMRoutingFilterGenerator |
|
Expressing QoC requirements |
The QoCIM framework provides methods to transform instances of QoC indicators into constraints that reflect the needs of a consumer in terms of QoC. |
|
In the Maven module qocim-routing-filter, using instances of the QoC indicators as parameters of the methods addQoCCriterionConstraints and addQoCValueConstraints in the class IQoCIMRoutingFilterGenerator |