SYSML — regarding the <> stereotype in the Requirements package

regarding the <<requirementRelated>> stereotype in the Requirements package of the SysML profile. I have two questions:

Why is the “verifies” tag on requirementRelated instead of <<testcase>>?
Why do you allow <<requirementRelated>> to be applied to <<testcase>> items?

It makes more sense to me to put the “verifies” tag on <<testcase>> and have a constraint on <<requirementRelated>> that states it cannot be applied to items stereotyped as <<testcase>>. As I understand it <<requirementRelated>> is basically a placeholder for the derived tags that can’t go anywhere else (e.g. “satisfies”, etc). Since <<testcase>> is already a stereotype there’s no reason why it can’t hold the “verifies” tag.

No Data Available