bat365 Homepage

Verification, Validation, and Test

Verify and validate embedded systems using Model-Based Design

Systematic verification increases confidence that your design accurately implements your requirements and that your tests fully exercise those requirements. Early in development, you can create a high-level system model and link to system requirements. The system model can serve as an executable specification and basis for more detailed models.

Using these bat365^® products to complement Model-Based Design, you can:

Trace requirements to architecture, design, tests, and code.
Confirm that your design meets requirements and is free of critical run-time errors.
Check compliance and measure quality of models and code.
Identify dead logic and generate test cases to resolve missing coverage.
Produce reports and artifacts, and verify that your design meets compliance standards.

You can also guide MATLAB^® software development by:

Authoring and linking requirements to tests and code.
Running dynamic tests to monitor for regressions in code functionality.
Identifying untested code paths using industry-standard code coverage metrics.

Workflow using Model-Based Design: Start by establishing system requirements and architecture, then component requirements and architecture. Continue with unit design, implementation, and testing. Next, perform integration testing at the component level followed by embedded testing. Finish with integration and testing at the system level.

Products for Verification, Validation, and Test

Requirements Toolbox

Author, link, and validate requirements for designs and tests

Simulink Check

Measure design quality, track verification activities, and verify compliance with standards

Simulink Coverage

Measure test coverage in models and generated code

Simulink Design Verifier

Identify design errors, prove requirements compliance, and generate tests

MATLAB Test

Develop, manage, analyze, and test MATLAB applications

Simulink Test

Develop, manage, and execute simulation-based tests

Polyspace Bug Finder

Identify software bugs via static analysis

Polyspace Code Prover

Prove the absence of run-time errors in software

Topics

Define Requirements

Author Requirements in MATLAB or Simulink (Requirements Toolbox)
Create requirements and define the requirement hierarchy with MATLAB or Simulink^®.
Import Requirements from Third-Party Applications (Requirements Toolbox)
Import requirements from external documents and requirements management tools.

Link Requirements to Designs

Test Model Against Requirements and Report Results (Requirements Toolbox)
Associate your model with detailed requirements, demonstrate traceability, test against requirements.
Link Test Cases to Requirements (Requirements Toolbox)
Associate test cases with requirements.
Track Requirement Links with a Traceability Matrix (Requirements Toolbox)
Track and manage links and change issues with the Traceability Matrix.
Validate Requirements by Analyzing Model Properties (Requirements Toolbox)
Validate requirements that are modeled as properties for a control system.

Identify and Eliminate Design Defects

Analyze Models for Design Errors (Simulink Design Verifier)
Run a Design Error Detection Analysis and interpret the results.
Analyze Models for Standards Compliance and Design Errors (Simulink Check)
Detect and resolve design errors, check against standards, analyze functional dependencies, and prove properties.

Perform Requirements-Based Testing

Requirements-Based Testing for Model Development (Simulink Test)
Test an autopilot system against requirements.
Use Specification Models for Requirements-Based Testing (Simulink Design Verifier)
Follow a systematic approach to verify your design model against requirements.
Perform Functional Testing and Analyze Test Coverage (Simulink Coverage)
Analyze functional dependencies, test model components in isolation, create suites of test cases, test models, and code to achieve coverage.
Fix Requirements-Based Testing Issues (Simulink Check)
Fix model testing quality issues by using the Model Testing Dashboard.
Assess Requirements-Based Testing for ISO 26262 (Simulink Check)
Use the Model Testing Dashboard to analyze the completeness and quality of requirements-based testing activities in accordance with the ISO 26262 standard.

Perform Code-Based Model Testing and Verification

Analyze Code and Test Software-in-the-Loop (Simulink Check)
Detect code errors, generate code metrics, test code and model equivalence, test code against requirements.
Integrate Polyspace with MATLAB and Simulink (Polyspace Bug Finder)
Integrate Polyspace^® with MATLAB and Simulink to identify potential bugs, run-time errors, and coding standard violations in your model and code.
Run Polyspace Analysis on Code Generated with Embedded Coder (Polyspace Bug Finder)
Check code generated with Embedded Coder^® for bugs, run-time errors or coding rule violations.

Related Information

Featured Examples

Debug Property Proving Violations by Using Model Slicer

Use Model Slicer to debug your design with assertion blocks.

Debug Enhanced Modified Condition Decision Coverage Using Model Slicer

Find the Simulink Design Verifier generated objectives related to a specific model object using Model Slicer.

Test Coverage for Requirements-Based Testing

Collect test coverage and scope coverage to requirements.

Explore Status and Quality of Testing Activities Using Model Testing Dashboard

Evaluate the status and quality of model testing in your project.