Stateflow Chart Considerations

R2026b

Stateflow^® chart names, properties, and architecture

Apply high-integrity guidelines for Stateflow chart names, properties, and architecture.

Modeling Guidelines

Naming Conventions

hisl_0031: Model file names	Use naming conventions for model file names
hisl_0032: Model element names	Naming conventions for model elements that produce valid identifiers in generated code

Chart Properties

hisf_0001: State Machine Type	Use the same state machine type for all Stateflow charts in the model
hisf_0011: Stateflow debugging settings	Protect against unreachable code and indeterminate execution time by configuring Stateflow debugging settings

Chart Architecture

hisf_0004: Protect against recursive function calls to improve code compliance	Avoid recursive function calls to promote bounded call behavior in generated code
hisf_0013: Usage of transition paths (crossing parallel state boundaries)	Avoid creating transitions that cross from one parallel state to another
hisf_0014: Usage of transition paths (passing through states)	Avoid transition paths that pass through states without ending on a substate
hisf_0015: Strong data typing (casting variables and parameters in expressions)	Explicitly type cast variables and parameters of different data types in expressions
hisf_0016: Stateflow port names	Name Stateflow input and output ports the same as the corresponding signal
hisf_0017: Stateflow data object scoping	Define locally scoped Stateflow data objects at the chart level or below