hisl_0309: Configuration Parameters > Diagnostics > Type Conversion

R2026b

Set type conversion diagnostics to detect unsafe conversions and improve design robustness

Usage: High-Integrity System Modeling

Guideline ID: hisl_0309

Rules

hisl_0309: Configuration Parameters > Diagnostics > Type Conversion

In the Configuration Parameters dialog box, on the Diagnostics > Type Conversion pane, set these parameters as follows:

  • Unnecessary type conversion to warning

  • Vector/matrix block input conversion to error

  • 32-bit integer to single precision float conversion to warning

Rationale

Improve robustness of design.

Verification

Check safety-related diagnostic settings for type conversions (Simulink Check)

Industry Standards

  • DO-331, Section MB.6.3.1.g – Algorithms are accurate
    DO-331, Section MB.6.3.2.g – Algorithms are accurate

  • IEC 61508–3, Table A.3 (2) Strongly typed programming language
    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 (1c) Enforcement of strong typing
    ISO 26262-6, Table 1 (1d) Use of defensive implementation techniques

  • EN 50128, Table A.4 (8) Strongly Typed Programming Language
    EN 50128, Table A.3 (1) Defensive Programming

  • EN 50657, Table A.4 (8) Strongly Typed Programming Language
    EN 50657, Table A.3 (1) Defensive Programming

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

Version History

Introduced in R2011b

expand all

See Also