Verify Requirements by Using Tests

Run requirements-based tests in MATLAB^® and Simulink^® to verify requirements

Link requirements to tests in MATLAB and Simulink, then verify the requirements by running the tests. Track the verification status of requirements, and justify requirements that cannot or do not need to be verified. Use external results to verify requirements.

Apps

Requirements Editor	Create and edit requirements
Requirements Manager	Manage requirements and links in model

Classes

expand all

Requirement Classes

`slreq.ReqSet`	Work with requirement sets
`slreq.Requirement`	Work with requirement objects
`slreq.Reference`	Work with external requirement proxy objects
`slreq.Justification`	Requirement justifications

External Verification Classes

`slreq.verification.services.JUnit`	Work with external results sources (Since R2020a)
`slreq.verification.services.TAP`	Work with external results sources (Since R2020a)

Methods

expand all

Requirement Set Methods

`runTests`	Run test cases linked to requirement set
`getVerificationStatus`	Query requirement set verification status summary
`updateVerificationStatus`	Update requirement set verification status summary

Requirement Methods

`getVerificationStatus`	Query requirement verification status summary
`isJustifiedFor`	Check if requirement is justified
`justifyImplementation`	Justify requirements for implementation
`justifyVerification`	Justify requirements for verification

Referenced Requirement Methods

`getVerificationStatus`	Query referenced requirement verification status summary
`justifyVerification`	Justify referenced requirements for verification

Justification Methods

Get Justifications and Requirement Sets

`find`	Find children of parent justification
`children`	Find children justifications
`parent`	Find parent item of justification
`reqSet`	Return parent requirement set

Add and Remove Justifications

`add`	Add child justification
`copy`	Copy and paste justification
`remove`	Remove justification items

Move, Promote, and Demote Requirements

`move`	Move justification in hierarchy
`moveDown`	Move justification down in hierarchy
`moveUp`	Move justification up in hierarchy
`promote`	Promote justifications
`demote`	Demote justifications

Add Comments and Customize Justifications

`addComment`	Add comments to justifications
`getAttribute`	Get justification attributes
`setAttribute`	Set justification attributes

Check and Set Hierarchy

`isHierarchical`	Check if justification is hierarchical
`setHierarchical`	Change hierarchical justification status

Topics

Verify and Validate a Model and Code

Define requirements, test models and code, check for design errors and standards compliance, and measure test coverage.
- STEP 1: Test Model Against Requirements and Report Results
- STEP 2: Analyze Models for Standards Compliance and Design Errors
- STEP 3: Perform Functional Testing and Analyze Test Coverage
- STEP 4: Analyze Code and Perform Software-in-the-Loop Testing
Review Requirements Verification Status
Use the requirements verification status to check test and analysis results linked to your requirements.
View Unified Verification Results in Metrics Dashboard and in Requirements Editor
Use the Metrics Dashboard to visualize the requirements verification status of requirements in your projects.
Verify Requirements with MATLAB Tests
Verify requirements by running linked MATLAB tests.
Link Test Cases to Requirements
Associate Simulink Test™ test cases with requirements.
Generate and Export Tests from Requirements Table Blocks
Automate test generation and execution in models that contain Requirements Table blocks.
Justify Requirements
Provide justifications for your requirements.
Include Results from External Sources in Verification Status
Link from external sources and display the results in the requirements verification status.

Featured Examples

Verify a MATLAB Algorithm by Using Requirements-Based Tests

Verify a MATLAB algorithm by using MATLAB unit tests.

Open Live Script

Validate Requirements by Analyzing Model Properties

Validate requirements that are modeled as properties for a control system.

Open Model

Prove Properties with Requirements Table Blocks

Use a Requirements Table block and Simulink Design Verifier™ to prove properties of a model.

Since R2023a
Open Model

Use Specification Models for Requirements-Based Testing

Follow a systematic approach to verify your design model against requirements.

Since R2022b
Open Live Script

Verify Safety Requirements Linked to Test Steps Using Functional Requirements

Verify safety requirements that are linked to test assessment blocks using functional requirements.

Open Live Script

Fix Requirements-Based Testing Issues

Fix model testing quality issues by using the Model Testing Dashboard.

Open Live Script

Linking to a Test Script

Link a requirement to a MATLAB script.

Linking to a Result File

Link a requirement to a test result file.

Integrating Results from a Custom-Authored MATLAB Script as a Test

In this example, you link a requirement to a MATLAB® script. The verification status in the Requirements Editor reflects the test results. This example performs the steps described in Linking to a Test Script. This example uses a requirements set file named counter_req.slreqx, a MATLAB script called runmytests.m that runs a test for the Counter class in Counter.m. The test script contains custom methods that write results a TAP format to a file named results.tap.

Open Live Script

Integrating Results from an External Result File

In this example, you link a requirement to a result file in Excel® Format. The verification status in the Requirements Editor reflects the test results. This example performs the steps described in Linking to a Result File. This example uses a requirement set file named counter_req and a test results file named results.xlsx. This file contains a test case named counterSetsValue.

Open Live Script

Integrating Results from a Custom Authored MUnit Script as a Test

In this example, you integrate the results from a MATLAB® xml Unit test by linking to a test script. The verification status in the Requirements Editor reflects the test results. This example uses a requirement set file named counter_req and an XML unit test file named myMUnitResults.xml. This file contains a test case named testCounterStartsAtZero.

Open Live Script