UC: verifying the status of the activities imposed by a Requirement

use case description One of the possible use cases for a RRMV knowledge base is the ability to followup the progress of the activities to fullfill a requirement.

use case challenges RRMV encodes legislation and therefore progress monitoring in the context of RRMV is strongly embedded in the legal perspective.
Because any progress monitoring information sheds only a limited view on the real situation, drawing legal consequences from the progress monitoring, even it seems suited, must be done carefully. Without complete knowledge (including policy officers point of view and information that is only available to the invovled actors) the drawn conclusions may be incorrect.

Another aspect in this use case is that sharing monitoring information (e.g. legal compliance) may be sensitive information. There is a difference between a public statement versus an internal followup that leads to the public statement. There are a variety of requirement monitoring processes in place.
Introducing a rigid approach to capture (internal) monitoring followup proposal should be avoided. That will reduce the adoption of RRMV.

use case proposal Given this context our proposal is to capture status information around the actual ActionResult delivery. Where in issue #55 properties are suggested to capture the delivery tools and outcome, one also can formulate a status w.r.t. each of these aspects:

• System condition: This condition ensures the reporting system is fully operational and capable of processing data during the submission period. It verifies that the technological infrastructure required for reporting was active.
• Flow condition: This condition examines the pathways through which data is transmitted within the system, confirming the proper establishment and maintenance of data flows between reporting entities and recipients.
• Individual submission condition: This condition verifies whether a specific agent has submitted the required document, focusing on the actual delivery of mandated reports. In addition to the submission status, one can complement this with a property compliance_assessment for Action Result that would refer to a compliance assessment provided by the Requirement supervising authority performed after the submission has been finalised.

Providing these process execution status information will shed some operational insights in the ActionResult delivery process. Eg. If the flow condition is set to be unavailable, then the policy officer has not yet opened the individual submission possibility. When the system is unavailable, then involved agents may even not progress at all and may therefore submit after the legally described deadline.