Verifica dei requisiti utilizzando i test
Collegare i requisiti ai test in MATLAB e Simulink, quindi verificare i requisiti eseguendo i test. Monitorare lo stato della verifica dei requisiti e giustificare i requisiti che non possono o non necessitano di essere verificati. Utilizzare risultati esterni per verificare i requisiti.
App
| Requirements Editor | Create and edit requirements |
| Requirements Manager | Manage requirements and links in model |
Classi
Metodi
Argomenti
- Verify and Validate a Model and Code
Define requirements, test models and code, check for design errors and standards compliance, and measure test coverage.
- PASSAGGIO 1: Test Model Against Requirements and Report Results
- PASSAGGIO 2: Analyze Models for Standards Compliance and Design Errors
- PASSAGGIO 3: Perform Functional Testing and Analyze Test Coverage
- PASSAGGIO 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 Model Testing Dashboard and in Requirements Editor
Use the Model Testing Dashboard to visualize the requirements verification status of requirements in your projects. (Da R2024a)
- Verify Requirements with MATLAB Tests
Verify requirements by running linked MATLAB tests. (Da R2022a)
- Collegamento dei casi di test ai requisiti
Associare i casi di test Simulink Test™ con i requisiti.
- 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.
Esempi in primo piano
Verifica di un algoritmo di MATLAB utilizzando test basati sui requisiti
Verificare un algoritmo di MATLAB utilizzando test unitari di MATLAB.
Validate Requirements by Analyzing Model Properties
Validate requirements that are modeled as properties for a control system.
Prove Properties with Requirements Table Blocks
Use a Requirements Table block and Simulink Design Verifier™ to prove properties of a model.
Use Specification Models for Requirements-Based Testing
Follow a systematic approach to verify your design model against requirements.
Verify Safety Requirements Linked to Test Steps Using Functional Requirements
Verify safety requirements that are linked to test assessment blocks using functional requirements.
Fix Requirements-Based Testing Issues
Fix model testing quality issues by using the Model Testing Dashboard.
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.
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.
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.
