You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time a function grounding violates a NFR the objective it is solving is added to the function design fd_error_log.
This shouldn't be the case for all violations, in the smart home for example we don't add the FDs to an error log. In addition, it doesn't make sense to block an FD for a violating a non-functional requirement.
Another issue I see is that the relationship order seems to be inverted. I would say that an FD is added to the objective error log and not the opposite.
But anyway, regarding the main issue I suggest:
Making a distinction between non-functional requirements and functional requirements
Only when a functional requirement is violated, the function design should be blocked
We need to keep track of this change in the tomasys metamodel, i.e. values for 'Objective.status'
Have you edited tomasys.owl in some branch @Rezenders ?
Maybe good to indicate it here.
I only modified mros.owl and its SWRL rules. Changes are in the main branch. meta-control/mros_ontology@dd139f0
I didn't change the o_status. I will add that to tomasys.
Every time a function grounding violates a NFR the objective it is solving is added to the function design
fd_error_log
.This shouldn't be the case for all violations, in the smart home for example we don't add the FDs to an error log. In addition, it doesn't make sense to block an FD for a violating a non-functional requirement.
Another issue I see is that the relationship order seems to be inverted. I would say that an FD is added to the objective error log and not the opposite.
But anyway, regarding the main issue I suggest:
A quick solution for this in MROS could be to
IN_ERROR_FR
#143IN_ERROR_FR
orIN_ERROR_NFR
according to the quality attribute that was violated #144IN_ERROR_FR
too_status
The text was updated successfully, but these errors were encountered: