Check for requirement granularity in an architecture model

R2026b

mathworks.hism.hisc_0002

Since R2026b

Dependencies: Simulink^® Check™, Requirements Toolbox™, and System Composer™

Usage: High-Integrity System Modeling

Guideline: hisc_0002: Establish requirement granularity in an architecture model

Description

This check verifies the requirement granularity in System Composer architecture model components.

It verifies that:

• A component is limited to a configurable number of unique requirement links, as specified by Maximum number of requirement links per component. The default limit is up to 5.

• A component linked to a requirement is limited to a configurable number of immediate child components, as specified by Maximum number of child objects per linked component. The default limit is up to 7.

This check assumes that requirement links are already present.

Elements under review: In this check, these elements are collectively referred to as components.

• Architecture model

  • Component (System Composer) block

  • Reference Component (System Composer) block

  • Variant Component (System Composer) block

  • Variant choices

• Sequence diagram

  • Lifelines (System Composer)

• Activity diagram

  • Action Node (System Composer)

  • Decision or Merge Node (System Composer)

  • Join or Fork Node (System Composer)

Check Parameters

Use the Model Advisor Configuration Editor to define the scope of the analysis by specifying the input parameters.

Parameter	Description
Maximum number of requirement links per component	Specify the maximum number of unique requirement links allowed for each component. 5 (default) | inf (disables the check) | positive integer value
Maximum number of child objects per linked component	Specify the maximum number of immediate child elements allowed for each component that is linked to a requirement. 7 (default) | inf (disables the check) | positive integer value
List of architecture model elements exempt from requirement links	The architecture model elements that can be exempted from requirement links. Add or remove blocks from the list by using the Add, Delete, and Add from buttons. By default, the list includes these blocks: Area Annotations Display Gauge Slider Adapter Initial Node Flow Final Node Activity Final Node

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.

Modeling Condition	Recommended Action
Model component exceeds the maximum allowed number of requirement links.	Decompose the component into more focused components and redistribute requirement links to support single-responsibility design.
Model component linked to a requirement exceeds the allowed number of immediate child elements.	Create more granular child requirements and decompose the component so that each component is associated with a single, well-scoped requirement.

Capabilities and Limitations

• Verifies only components that are linked to requirements

• Does not verify the presence or placement of requirement links. To verify missing requirements, refer Check for architecture components without requirement links.

• Does not support exclusions

• Does not require model compilation

Version History

Introduced in R2026b