Simulink Verification and Validation 2.4

Product Description

• Introduction and Key Features
• Working with Simulink Verification and Validation
• Tracing Requirements to Designs, Tests, and Generated Code
• Assigning Verification Blocks to Test Signals
• Analyzing Model Coverage
• Enforcing Modeling Standards

Analyzing Model Coverage

Simulink Verification and Validation produces model coverage reports to indicate untested elements of your design, such as logical conditions, switches, lookup table interpolation intervals, and subsystems. Published as HTML documents, these reports use industry-standard metrics for structural coverage. They also display coverage information on the model, letting you traverse the model for missing coverage and navigate to the associated requirements. You can then determine whether you need to modify the requirements, test cases, or design to meet your coverage goals.

Simulink Verification and Validation provides six model coverage analysis metrics:

Cyclomatic complexity measures the structural complexity of a model, approximating the McCabe complexity measure for code generated from the model.

Decision coverage examines items that represent decision points in a model, such as Simulink Switch blocks and Stateflow states.

Condition coverage examines blocks that output the logical combination of their inputs, such as the Logic block and Stateflow transitions.

MC/DC analyzes safety-critical software (as defined by RTCA DO-178B) and determines whether the logical inputs have independently changed the output.

Lookup table coverage records the frequency of usage for each interpolation interval. (A test case achieves full coverage if it executes each interpolation and extrapolation interval at least once.)

Signal range coverage indicates the minimum and maximum values generated during simulation by each block output and for all Stateflow data objects.

Next