Manage Project Artifacts for Analysis in Dashboard

When you develop and test software units using Model-Based Design, use the Model Testing Dashboard to assess the status and quality of your unit testing activities. Requirements-based testing is a central element of model verification. By establishing traceability links between your requirements, model design elements, and tests, you can measure the extent to which the requirements are implemented and verified. The Model Testing Dashboard analyzes this traceability information and provides detailed metric measurements on the traceability, status, and results of these testing artifacts.

Each metric in the dashboard measures a different aspect of the quality of your unit testing and reflects guidelines in industry-recognized software development standards, such as ISO 26262 and DO-178C. To monitor the requirements-based testing quality of your models in the Model Testing Dashboard, maintain your artifacts in a project and follow these considerations. For more information on using the Model Testing Dashboard, see Explore Status and Quality of Testing Activities Using Model Testing Dashboard.

Manage Artifact Files in a Project

To analyze your requirements-based testing activities in the Model Testing Dashboard, store your design and testing artifacts in a MATLAB^® project. The artifacts that the testing metrics analyze include:

• Models

• Libraries that the models use

• Requirements that you create in Requirements Toolbox™

• Tests that you create in Simulink^® Test™

• Test results from the executed tests

For information on how the dashboard traces dependencies between project files, see Digital Thread.

When your project contains many models and model reference hierarchies, you can track your unit testing activities by configuring the dashboard to recognize the different testing levels of your models. You can specify which entities in your software architecture are units or higher-level components by labeling them in your project and configuring the Model Testing Dashboard to recognize the labels. The dashboard organizes your models in the Artifacts panel according to their testing levels and the model reference hierarchy. For more information, see Categorize Models in a Hierarchy as Components or Units.

Trace Artifacts to Units and Components

To determine which artifacts are in the scope of a unit or component, the dashboard analyzes the traceability links between the artifacts, software unit models, and component models in the project. The Project panel lists the units, organized by the components that reference them.

When you select a unit or component in the Project panel, the Artifacts panel shows the artifacts that trace to the selected unit or component. Traced artifacts include:

• Functional Requirements

• Design Artifacts

• Tests

• Test Results

To see the traceability path that the dashboard found between a unit or component and its artifacts, click Trace View in the toolstrip. Trace views are interactive diagrams that you can use to see how artifacts trace to units and components in your design and to view the traceability information for requirements, tests, and test results in the project. For more information, see Explore Traceability Information for Units and Components.

In the Artifacts panel, the folder Trace Issues contains unexpected requirement links, requirements links which are broken or not supported by the dashboard, and artifacts that the dashboard cannot trace to a unit or component. To help identify the type of tracing issue, the folder Trace Issues contains subfolders for Unexpected Implementation Links, Unresolved and Unsupported Links, Untraced Tests, and Untraced Results. For more information, see Fix Requirements-Based Testing Issues.

If an artifact returns an error during traceability analysis, the panel includes the artifact in an Errors folder. Use the traceability information in these sections to check if the artifacts trace to the units or components that you expect. To see details about the warnings and errors that the dashboard finds during artifact analysis, click Artifact Issues in the toolstrip.

Functional Requirements

The folder Functional Requirements shows requirements of Type Functional that are either implemented by or upstream of the unit or component.

When you collect metric results, the dashboard analyzes only the functional requirements that the unit or component directly implements. The folder Functional Requirements contains two subfolders to help identify which requirements are implemented by the unit or component, or are upstream of the unit or component:

• Implemented — Functional requirements that are directly linked to the unit or component with a link Type of Implements. The dashboard uses these requirements in the metrics for the unit or component.

• Upstream — Functional requirements that are indirectly or transitively linked to the implemented requirements. The dashboard does not use these requirements in the metrics for the unit or component.

Use the Requirements Toolbox to create or import the requirements in a requirements file (.slreqx). If a requirement does not trace to a unit or component, it appears in the Trace Issues folder. If a requirement does not appear in the Artifacts panel when you expect it to, see Requirement Missing from Artifacts Panel.

For more information on how the dashboard traces dependencies between project files, see Digital Thread.

Design Artifacts

The folder Design shows project artifacts that trace to the current unit or component, including:

• The model file that contains the block diagram for the unit or component.

• Models that the unit or component references.

• Libraries that are partially or fully used by the model.

• Data dictionaries that are linked to the model.

• External MATLAB code that traces to the model. If you expect external MATLAB code to appear in the dashboard and it does not, see External MATLAB Code Missing from Artifacts Panel.

If an artifact does not appear in the Design folder when you expect it to, see Resolve Missing Artifacts, Links, and Results. For more information on how the dashboard traces dependencies between project files, see Digital Thread.

Tests

The folder Tests shows tests and test harnesses that trace to the selected unit. A test can be either:

• A test iteration

• A test case without iterations

When you collect metric results for a unit, the dashboard analyzes only the unit tests. The folder Tests contains subfolders to help identify whether a test is considered a unit test and which test harnesses trace to the unit:

• Unit Tests — Tests that the dashboard considers as unit tests. A unit test directly tests either the entire unit or lower-level elements in the unit, like subsystems. The dashboard uses these tests in the metrics for the unit.

• Others — Tests that trace to the unit but that the dashboard does not consider as unit tests. For example, the dashboard does not consider tests on a library or tests on a virtual subsystem to be unit tests. The dashboard does not use these tests in the metrics for the unit.

• Test Harnesses — Test harnesses that trace to the unit or lower-level elements in the unit. Double-click a test harness to open it.

Create tests by using Simulink Test. If a test does not trace to a unit, it appears in the Trace Issues folder. If a test does not appear in the Artifacts panel when you expect it to, see Test Missing from Artifacts Panel. For troubleshooting tests in metric results, see Fix a test that does not produce metric results.

For more information on how the dashboard traces dependencies between project files, see Digital Thread.

Test Results

When you collect metric results for a unit, the dashboard analyzes only the test results from unit tests. The folder Test Results contains subfolders to help identify which test results are from unit tests.

• The subfolders for Model, SIL, and PIL contain simulation results from normal, software-in-the-loop (SIL), and processor-in-the-loop (PIL) unit tests, respectively. The dashboard uses these results in the metrics for the unit.

  The following types of test results are shown:

  • Saved test results — results that you have collected in the Test Manager and have exported to a results file.

  • Temporary test results — results that you have collected in the Test Manager but have not exported to a results file. When you export the results from the Test Manager the dashboard analyzes the saved results instead of the temporary results. Additionally, the dashboard stops recognizing the temporary results when you close the project or close the result set in the Simulink Test Result Explorer. If you want to analyze the results in a subsequent test session or project session, export the results to a results file.

• Others — Results that are not simulation results, are not from unit tests, or are only reports. For example, SIL results are not simulation results. The dashboard does not use these results in the metrics for the unit.

If a test result does not trace to a unit, it appears in the Trace Issues folder. If a test result does not appear in the Artifacts panel when you expect it to, see Test Result Missing from Artifacts Panel. For troubleshooting test results in dashboard metric results, see Fix a test result that does not produce metric results.

For more information on how the dashboard traces dependencies between project files, see Digital Thread.

Trace Issues

The folder Trace Issues shows artifacts that the dashboard has not traced to any units or components. Use the folder Trace Issues to check if artifacts are missing traceability to the units or components. The folder Trace Issues contains subfolders to help identify the type of tracing issue:

• Unexpected Implementation Links — Requirement links of Type Implements for a requirement of Type Container or Type Informational. The dashboard does not expect these links to be of Type Implements because container requirements and informational requirements do not contribute to the Implementation and Verification status of the requirement set that they are in. If a requirement is not meant to be implemented, you can change the link type. For example, you can change a requirement of Type Informational to have a link of Type Related to.

• Unresolved and Unsupported Links — Requirements links that are either broken in the project or not supported by the dashboard. For example, if a model block implements a requirement, but you delete the model block, the requirement link is now unresolved. The dashboard does not support traceability analysis for some artifacts and some links. If you expect a link to trace to a unit or component and it does not, see the troubleshooting solutions in Resolve Missing Artifacts, Links, and Results.

• Untraced Tests — Tests that execute on models or lower-level elements, like subsystems, that are not on the project path.

• Untraced Results — Results that the dashboard cannot trace to a test. For example, if a test produces a result, but you delete the test, the dashboard cannot trace the results to the test.

The dashboard does not support traceability analysis for some artifacts and some links. If an artifact is untraced when you expect it to trace to a unit or component, see the troubleshooting solutions in Trace Issues.

Artifact Errors

The folder Errors appears if artifacts returned errors when the dashboard performed artifact analysis. These are some errors that artifacts might return during traceability analysis:

• An artifact returns an error if it has unsaved changes when traceability analysis starts.

• A test results file returns an error if it was saved in a previous version of Simulink.

Open these artifacts and fix the errors. The dashboard shows a banner at the top of the dashboard to indicate that the artifact traceability shown in the Project and Artifacts panels is outdated. Click the Trace Artifacts button on the banner to refresh the data in the Project and Artifacts panels.

Artifact Issues

To see details about artifacts that cause errors, warnings, and informational messages during analysis, click Artifact Issues in the toolstrip. The issues persist between MATLAB sessions and you can sort the messages by their severity, message, source, or message ID.

The messages show:

• Modeling constructs that the dashboard does not support

• Links that the dashboard does not trace

• Test harnesses or cases that the dashboard does not support

• Test results missing coverage or simulation results

• Artifacts that return errors when the dashboard loads them

• Information about model callbacks that the dashboard deactivates

• Artifacts that are not on the path and are not considered during tracing

Collect Metric Results

The Model Testing Dashboard can collect metric results for each unit listed in the Project panel. Each metric in the dashboard measures a different aspect of the quality of your model testing and reflects guidelines in industry-recognized software development standards, such as ISO 26262 and DO-178. For more information about the available metrics and the results that they return, see Model Testing Metrics.

As you edit and save the artifacts in your project, the dashboard detects changes to the artifacts. If the metric results might be affected by your artifact changes, the dashboard shows a warning banner at the top of the dashboard to indicate that the metric results are stale. Affected widgets have a gray staleness icon . To update the results, click the Collect button on the warning banner to re-collect the metric data and to update the stale widgets with data from the current artifacts. If you want to collect metrics for each of the units and components in the project, click Collect > Collect All.

When you change a coverage filter file that your test results use, the coverage metrics in the dashboard do not indicate stale data or include the changes. After you save the changes to the filter file, re-run the tests and use the filter file for the new results.