https://github.com/nmsa/tma-framework-p
Component P - Trustworthiness Monitoring & Assessment Framework
https://github.com/nmsa/tma-framework-p
Last synced: about 1 year ago
JSON representation
Component P - Trustworthiness Monitoring & Assessment Framework
- Host: GitHub
- URL: https://github.com/nmsa/tma-framework-p
- Owner: nmsa
- License: apache-2.0
- Created: 2018-04-09T17:01:10.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2022-12-16T00:37:52.000Z (over 3 years ago)
- Last Synced: 2025-04-04T01:32:12.262Z (over 1 year ago)
- Language: Java
- Size: 57.6 KB
- Stars: 1
- Watchers: 5
- Forks: 5
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Planning Component @ TMA Framework
* ER diagram used by the planning component.*
The `TMA_Planning` is responsible for analyzing the measurements calculated by `TMA_Analyze`.
All the scores that need to be consumed by `TMA_Planning` and will be enqueued by `TMA_Analyze` on the `planning` topic.
The `TMA_Planning` is responsible for executing the verification of the predefined rules.
For each rule that is not respected, one or more adaptations will be generated, which will be gathererd in a set of adaptations.
The next step is to consolidate this set of adaptations in a "adaptation plan" by dealing with conflicting rules and priorities. In practice, this consolidated "adaptation plan" is optimized to allow the system to recover the desired levels of trustworthiness.
The resulting "adaptation plan", containing the adaptations that need to be performed, will be added to a queue to be executed by `TMA_Execute`, and will also be stored in the `TMA_Knowledge` for future reference.
Each adaptation action is added as a message to the `execute` queue. Each message should contain the following attributes:
* `resourceId` -- identifies the resource to which the adaptation is targeted
* `actionName` -- identifies the adaptation to be promoted by the actuator
* `actuatorId` -- identifies the responsible actuator by the action
* `configuration` -- configuration data for the action, which can be included in the form of key/value format