Due to repeated requests, we also would like to share a guide, on how to make a Customization to allow multiple Requirement Verification Methods.
To deal with this issue, you can customize the extended requirement type (the one you currently use) and redefine the verifyMethod property.
For this, do the following:
1. Create a profile and a Profile diagram within this profile.
2. Use the quick find (press Ctrl+Alt+F) to find the extended requirement type. Important: be sure the Apply Filter check box is unselected! Otherwise, you won't be able to select extendedRequirement, because it is stored in SysML Profile, which is by default excluded from search.
3.Drag the extended requirement type to the profile diagram pane.
4. Create a new stereotype and name it 'MyRequirement'.
5. Draw a generalization between these two stereotypes.
6. Select 'MyRequirement', press Enter to open its Specification, and click Tag Definitions on the left.
7. In the list of inherited tags, select 'verifyMethod' and click the Redefine button. The tag is moved to the owned tags list.
8. Click the small button at the end of the 'verifyMethod' tag row to open its Specification.
9. Change the value of the Multiplicity to '0..*' and close the window.
10. Close and re-open the project to apply the customization to your model.
Now you can add more than one verify method to any of your requirements and they won't be marked as invalid.
If you want to specify that requirement is verified by more than one method, you should edit the verifyMethod tag value. For this, open the Specification of this requirement (1), click Tags on the left (2), select the verifyMethod tag (3), and click the Add button (4).
The attached project includes the sample matrix and requirements with multiple verification methods specified. Requirements A, B, C, and D are not customized, thus they are marked as invalid. Requirements E and D are customized, thus they are marked as valid.
No Magic, Inc. Customer Support
You do not have the required permissions to view the files attached to this post.