Page 1 of 1

Multiple Verify Methods

PostPosted: Mon Apr 25, 2016 10:17 am
I have some requirements have more than one verification method (e.g. both inspection and test). Is there a way to have more than one 'verify method' for a requirement?

Re: Multiple Verify Methods

PostPosted: Tue Apr 26, 2016 2:52 am

Thank you for the question.

SysML Specification specifies only one of the standard Verification Methods: Inspection, Analysis, Demonstration, or Test.

The easiest workaround would be to specify in the Documentation for the Requirement that multiple Verification Methods are required.
Another option is to create a Customization by modifying or extending the extendedRequirement Stereotype. Or to extend the requirement Stereotype and add a Custom Property to it. But this requires a substantial amount of effort and may not bet the best solution in your case.

Kind regards,
No Magic Inc., Customer Support

Re: Multiple Verify Methods

PostPosted: Thu May 19, 2016 1:56 am

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.


Best Regards,
No Magic, Inc. Customer Support

Re: Multiple Verify Methods

PostPosted: Fri Apr 28, 2017 10:55 am
Thank you for providing the sample project that allows for multiple verification methods. I have a couple questions regarding the sample project.

1. Presently, the Verification Matrix included in the sample project doesn’t allow the user to assign more than one Verification Method (If one tries, the latest Verification Method overwrites the older one). Is there a way to fix this?

2. How would one go about importing tag values for the ‘verifyMethod’ field? According to the previous post, the method to add a verification type is done in the element specification. Is there a more efficient way, such as a CSV mapping or excel import? This could be more advantageous for a large set of requirements that need multiple verification method tag values.