Check Stateflow charts for uniquely defined data objects

R2026b

mathworks.hism.hisl_0061

Dependencies: Simulink^® Check™ and Stateflow^®

Usage: High-Integrity System Modeling

Guideline: hisl_0061: Unique identifiers for clarity

Description

This check searches your model for local data in Stateflow charts that is not uniquely defined.

Elements under review:

• Local data in Stateflow charts

Recommended Actions and Results

Review the violations that are flagged by the check and the recommended action for fixing the issue. After applying the changes, save the model and rerun the check analysis.

If you consider the flagged violation to either not be relevant or not feasible for your design, use the Justify button to provide rationale as to why the violation is either not relevant or not feasible for your design.

You can use the Fix button to allow the Model Advisor to fix all flagged violations. For this check, the Model Advisor configures model code generation settings that can impact safety.

Modeling Condition	Recommended Action
The Stateflow chart contains a data object identifier defined in two or more scopes.	For the identified chart, do one of the following: Create a unique data object identifier within each of the scopes. Create a unique data object identifier within the chart, at the parent level.

Capabilities and Limitations

• Does not look for usage of unique identifiers for Simulink signals

• Does not require model compilation

• Runs on library models

• Does not allow exclusions of blocks or charts

Version History

Introduced in R2020a