hisl_0314: Configuration Parameters > Diagnostics > Data Validity > Signals

R2026b

Set data validity signal diagnostics to error to improve design robustness

Usage: High-Integrity System Modeling

Guideline ID: hisl_0314

Rules

hisl_0314: Configuration Parameters > Diagnostics > Data Validity > Signals

In the Configuration Parameters dialog box, on the Diagnostics > Data Validity pane, set the Signals parameters as follows:

  • Signal resolution to Explicit only

  • Division by singular matrix to error

  • Underspecified data types to error

  • Inf or NaN block output to error

  • "rt" prefix for identifiers to error

  • Wrap on overflow to error

  • Saturate on overflow to error

  • Simulation range checking to error

Rationale

Improve robustness of design.

Verification

Check safety-related diagnostic settings for signal data (Simulink Check)

Industry Standards

  • DO-331, Section MB.6.4.2.2 'Robustness Test Cases'
    DO-331, Section MB.6.4.3 'Requirements-Based Testing Methods'
    DO-331, Section MB.6.3.1.e 'High-level requirements conform to standards'
    DO-331, Section MB.6.3.2.e 'Low-level requirements conform to standards'
    DO-331, Section MB.6.3.1.g 'Algorithms are accurate'
    DO-331, Section MB.6.3.2.g 'Algorithms are accurate'
    DO-331, Section MB.6.3.3.b 'Software architecture is consistent'

  • IEC 61508-3, Table A.3 (3) 'Language subset'
    IEC 61508-3, Table A.4 (3) 'Defensive programming'

  • IEC 62304, 5.5.3 - Software Unit acceptance criteria

  • ISO 26262-6, Table 1 (1b) 'Use of language subsets'
    ISO 26262-6, Table 1 (1d) 'Use of defensive implementation techniques'

  • EN 50128, Table A.4 (11) 'Language Subset'
    EN 50128, Table A.3 (1) 'Defensive Programming'

  • EN 50657, Table A.4 (11) 'Language Subset'
    EN 50657, Table A.3 (1) 'Defensive Programming'

  • EN 50716, Table A.3 (1) 'Defensive Programming'

  • MISRA C:2012, Dir 4.1

  • MISRA C:2023, Dir 4.1

Version History

Introduced in R2018a

expand all

See Also