Main Content

Review Requirements Verification Status

You can view the verification status of your requirements in the Requirements Browser and Requirements Editor. The verification status reflects results from simulation testing using Simulink® Test™ or property proving using Simulink Design Verifier™. Use Verified by links from requirements to simulation assessments or proof objectives.

  • Simulation testing: Requirement verification status reflects the result of the following linkable Simulink Test items after they are run in the Test Manager:

    • Test files

    • Test suites

    • Test cases

    • Iterations

    • Assessments

    To learn how to verify requirements with Simulink Test items, see Test Model Against Requirements and Report Results.

    Run tests from the Simulink Test Manager, or using (Simulink Test). For a brief tutorial on creating and running a test case, follow the first part of Create and Run a Baseline Test (Simulink Test).

    Run-time assessments from verify (Simulink Test) statements or Model Verification Blocks (Simulink Test) can be captured by monitoring those assessments through test cases in the Test Manager.


    To view the verification status of a requirement that is linked to a test authored in MATLAB®, you must use a MATLAB-based Simulink test. See Test Models Using MATLAB-Based Simulink Tests (Simulink Test).

  • Property proving: Verification status reflects the analysis result of properties modeled using:

    • Simulink Design Verifier Proof Objective blocks.

    • Model Verification blocks.

    Link blocks to requirements, then analyze the properties. For more information, see Requirement Links.

To learn how to include results from external sources in the verification status, see Include Results from External Sources in Verification Status.

Display Verification Status

The verification status is summarized in the Verified column of the Requirements Browser and Requirements Editor. To display the column:

  • In the Requirements Editor, select Columns > Verification Status

  • In the Requirements Browser pane of the model window, right-click a requirement and select Verification Status.

For example, the Verified column shows partial verification links for this requirement set, with one failed result:

The fullness of the bar indicates how many requirements in a group (parent + children) are linked to verification items. Color indicates the test or analysis results:

  • Passed (green): The linked test(s) passed, or the analysis proved the objective(s).

  • Failed (red): The linked test(s) failed, or the analysis falsified the objective(s).

  • Justified (light blue): The requirement is excluded from the status with a justification. For more information, see Justify Requirements.

  • Unexecuted: (yellow): The linked test(s) or objective(s):

    • Have not run or executed

    • Have been updated more recently than the most recent result

  • None (colorless): The requirement does not have Verified by link(s).

Update Verification Status by Running Tests or Analyses

You can update the verification status by running tests or analyses linked to your requirements:

  1. In the Requirements Editor, right click the requirement and select Run Tests.

  2. In the Run Tests dialog box, select the tests.

  3. Click Run Tests.

You can also update verification status by running tests or analysis outside of the Requirements Editor:

  • In Simulink Test, run the tests in the Test Manager.

  • In Simulink Design Verifier, run property proving analysis.

  • In Simulink, run the model that contains the Model Verification blocks.


If you have linked requirements to Simulink Design Verifier Proof Objective blocks in multiple models, the Run Tests dialog box runs a Simulink Design Verifier analysis when the corresponding models are open.

Include Verification Status in Report

You can include verification status in your requirements report:

  1. In the Requirements Editor menu, select Report > Generate Report.

  2. Select Verification Status.

  3. Click Generate Report.

For more information, see Report Requirements Information

See Also