Documentation

Modeling Style

hisl_0032: Model object names

ID: Title	hisl_0032: Model object names
Description	For the following model object names: Signals Parameters Blocks Named Stateflow^® objects (States, Boxes, Simulink^® Functions, Graphical Functions, Truth Tables) Use: These characters: `a-z`, `A-Z`, `0-9`, and the underscore `(_)`. Strings that are fewer than 32 characters. Do not: Start the name with a number. Use underscores at the beginning or end of a string. Use more than one consecutive underscore. Use reserved identifiers.
Notes	Reserved names: MATLAB^® keywords Reserved keywords for C, C++, and code generation. For complete list, see Reserved Keywords (Simulink Coder). `int8` , `uint8` `int16`, `uint16` `int32`, `uint32` `inf`, `Inf` `NaN`, `nan` `eps` `intmin`, `intmax` `realmin`, `realmax` `pi` `infinity` `Nil`
Rationale	Readability Compiler limitations Model-to-generated code traceability
Model Advisor Checks	By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Naming > Check model object names By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Naming > Check model object names By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Naming > Check model object names By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Naming > Check model object names By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Naming > Check model object names For check details, see Check model object names (Simulink Check).
See Also	MAB guidelines: jc_0201: Usable characters for subsystem namesM jc_0211: Usable characters for Inport blocks and Outport block jc_0231: Usable characters for block names na_0019: Restricted variable names
References	MISRA C:2012, Rule 21.2 ISO 26262-6, Table 1 (1h) 'Use of naming conventions'
Last Changed	R2018b
Example	Recommended Block name: `My_Controller` Signal name: `a_b` Not Recommended Block name: `My Controller` Signal name: `12a__b`

hisl_0061: Unique identifiers for clarity

ID: Title	hisl_0061: Unique identifiers for clarity
Description	When developing a model:
	A	Use unique identifiers for Simulink signals.
	B	Define unique identifiers across multiple scopes within a chart.
Notes	The code generator resolves conflicts between identifiers so that symbols in the generated code are unique. The process is called name mangling.
Rationale	A, B	Improve readability of a graphical model and mapping between identifiers in the model and generated code.
Model Advisor Check	By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Stateflow > Check Stateflow charts for uniquely defined data objects By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Stateflow > Check Stateflow charts for uniquely defined data objects By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Stateflow > Check Stateflow charts for uniquely defined data objects By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Stateflow > Check Stateflow charts for uniquely defined data objects By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Stateflow > Check Stateflow charts for uniquely defined data objects For check details, see Check Stateflow charts for uniquely defined data objects (Simulink Check).
References	DO-331, Section MB.6.3.2.b 'Low-level requirements are accurate and consistent' IEC 61508-3, Table A.3 (2) ‘Strongly typed programming language’ IEC 61508-3, Table A.3 (3) - Language subset IEC 61508-3, Table A.4 (5) - Design and coding standards 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' ISO 26262-6, Table 1 (1e) - 'Use of well-trusted design principles' ISO 26262-6, Table 1 (1f) - 'Use of unambiguous graphical representation' ISO 26262-6, Table 1 (1g) - 'Use of style guides' ISO 26262-6, Table 1 (1h) - 'Use of naming conventions' EN 50128, Table A.3 (1) - Defensive Programming EN 50128, Table A.4 (8) 'Strongly Typed Programming Language' EN 50128, Table A.4 (11) - 'Language Subset' EN 50128, Table A.12 (1) 'Coding Standard' EN 50128, Table A.12 (2) 'Coding Style Guide'
See Also	Code Appearance (Simulink Coder)
Last Changed	R2017b
Examples	Not Recommended In the following example, two states `Scope_1` and `Scope_2` use local identifier `IntCounter`. The identifier `IntCounter` is defined for two states, `Scope_1` and `Scope_2`.
Examples	Recommended To clarify the model, create unique identifiers. In the following example, state `Scope_1` uses local identifier `IntCounter_Scope_1`. State `Scope_2` uses local identifier `IntCounter_Scope_2`. The identifier `IntCounter_Scope_1` is defined for state `Scope_1`. Identifier `IntCounter_Scope_2` is defined for `Scope_2`.

hisl_0062: Global variables in graphical functions

ID: Title	hisl_0062: Global variables in graphical functions
Description	For data with a global scope used in a function, do not use the data in the calling expression if a value is assigned to the data in that function.
Rationale	Enhance readability of a model by removing ambiguity in the values of global variables.
Model Advisor Checks	By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Simulink > Check global variables in graphical functions By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Simulink > Check global variables in graphical functions By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Simulink > Check global variables in graphical functions By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Simulink > Check global variables in graphical functions By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Simulink > Check global variables in graphical functions For check details, see Check global variables in graphical functions (Simulink Check).
References	IEC 61508–3, Table A.3 (3) 'Language subset' IEC 61508–3, Table A.4 (4) 'Modular approach' IEC 61508–3, A.4 (5) 'Design and coding standards' IEC 62304, 5.5.3 - Software Unit acceptance criteria ISO 26262-6, Table 1 (1b) 'Use of language subsets' ISO 26262-6, Table 1 (1f) 'Use of unambiguous graphical representation' ISO 26262-6, Table 1 (1h) 'Use of naming conventions' EN 50128, Table A.4 (11) 'Language Subset' EN 50128, Table A.12 (1) 'Coding Standard' EN 50128, Table A.12 (2) 'Coding Style Guide' DO-331, Section MB.6.3.2.g 'Algorithms are accurate' MISRA C:2012, Rule 13.2 MISRA C:2012, Rule 13.5
Last Changed	R2018b
Examples	Consider a graphical function `graphicalFunction` that modifies the global data `G`. Recommended Not Recommended

hisl_0063: Length of user-defined object names to improve MISRA C:2012 compliance

ID: Title	hisl_0063: Length of user-defined object names to improve MISRA C:2012 compliance
Description	To improve MISRA C:2012 compliance of generated code, use configuration parameter Maximum identifier length (`MaxIdLength`) to limit the length of user defined names. Note The default of Maximum identifier length is `31`.
	A	For Subsystem blocks with parameter Function name options set to `User specified`, limit the length of function names to be equal to or less than the value specified in Maximum identifier length.
	B	Limit the length of data object names to be equal to or less than the value specified in Maximum identifier length: `Simulink.AliasType` `Simulink.NumericType` `Simulink.Variant` `Simulink.Bus` `Simulink.BusElement` `Simulink.IntEnumType`
	C	When using these storage classes, limit the length of signal and parameter names to be equal to or less than the value specified in Maximum identifier length: Exported Global Imported Extern Imported Extern Pointer Custom storage class Note If specified, this includes the length of the Identifier name.
Rationale	Length in the generated code can result in a MISRAC:2012 violation.
Model Advisor Checks	By Task > Modeling Standards for DO-178C/DO-331 > High-Integrity Systems > Simulink > Check for length of user-defined object names By Task > Modeling Standards for IEC 61508 > High-Integrity Systems > Simulink > Check for length of user-defined object names By Task > Modeling Standards for IEC 62304 > High-Integrity Systems > Simulink > Check for length of user-defined object names By Task > Modeling Standards for EN 50128 > High-Integrity Systems > Simulink > Check for length of user-defined object names By Task > Modeling Standards for ISO 26262 > High-Integrity Systems > Simulink > Check for length of user-defined object names For check details, see Check for length of user-defined object names (Simulink Check).
References	MISRA C:2012, Rule 5.1 MISRA C:2012, Rule 5.2 MISRA C:2012, Rule 5.3 MISRA C:2012, Rule 5.4 MISRA C:2012, Rule 5.5
Prerequisites	hisl_0060: Configuration parameters that improve MISRA C:2012 compliance
Last Changed	R2018b

Simulink Documentation

Support