As the project progresses then the requirement scope and therefore the requirement text may change.
Occasionally, a requirement can become a description, or a description can become a requirement. Worst case scenario is that the author can forget to set the Object Type (it happens !).
We need to flag these mismatches so that only the true requirements can then move forward for the completion of the verification and validation attributes.
This DXL script simply applies a filter for :
- all requirements (as defined by the Object Type) that do not have a “shall”
- non-requirement objects that do.