SYSMLR — Satisfy, Verify and DeriveReqt could be used with non-requirement elements

SysML specification constraints the usage of Satisfy, Verify and DeriveReqt relationships to requirement model elements.
When in MBSE approach, textual requirements are most likely to be left aside and non-textual requirements start commonly being used. For example, an Activity can represent a functional requirement, as it has inputs, outputs and a processing that shows how inputs are transformed into outputs.
When using non-textual requirements, other model elements will start representing requirements. Therefore, those relationships should accept elements that are not SysML::Requirement model elements.

Requirement Relationship Constraints are Appropriate

Requirement relationships need to be contained to have at least one end be identified as a "requirement" in the model. The resolution to SYSMLR-155 has clarified the scope of requirement properties, which may help address the originator's concern.