Define Requirements Hierarchy

Using Requirements Toolbox™, you can derive lower-level requirements from higher-level requirements to establish and manage parent-child relationships.

The requirement set is the top level of hierarchy for all requirements. All requirements in Requirements Toolbox are contained in requirement sets. Every top-level parent requirement in a requirement set is the first-level hierarchy for that set. Referenced requirements (slreq.Reference objects) and requirements (slreq.Requirement objects) cannot share a parent requirement.

Within a requirement set, you can change the level of individual requirements by clicking Promote Requirement or Demote Requirement in the Requirements Editor, or the icons in the Requirements Perspective. When you promote or demote a requirement with children, the parent-child hierarchical relationship is preserved. You can also move requirements up and down the same level of hierarchy by right-clicking the requirement and selecting Move up or Move down.

The Implementation and Verification Status metrics for a requirement set are cumulatively aggregated over all the requirements in the set. Each parent requirement in a requirement set derives its metrics from all its child requirements. For more information on the Implementation and Verification Status metrics, see Track Requirement Links by Using Implementation Status and Review Requirements Verification Status.

Requirement Sets

You can create requirement sets from the Requirements Editor and from the Requirements Browser. Requirement set files (.slreqx) are not inherently associated with your Simulink^® models.

Requirement sets have built-in properties such as the Filepath and the Revision number associated with them as metadata. Except for the Description, properties of the requirement set are read-only and are updated as you work with the requirement set.

Custom Attributes of Requirement Sets

Define custom attributes for your requirement sets that apply to the requirements they contain. Custom attributes extend the set of properties associated with your requirements. Define custom attributes for a requirement set from the Custom Attribute Registries pane of the Requirements Editor.

To define custom attributes:

1. Open the Requirements Editor. In the Apps tab, click Requirements Manager. In the Requirements tab, click Requirements Editor.

2. Select the requirement set and click Add in the Custom Attribute Registries pane.

3. The Custom Attribute Registration dialog box opens. Select the type of custom attribute you want to set for your requirements by using the Type drop-down list. You can specify custom attributes as text fields, check boxes, and combo boxes and date time entries.

To view the custom attributes for your requirements in the spreadsheet, right-click the requirement set and click Select Attributes.

When you define a custom attribute as a combobox, the first entry is preset to Unset and it cannot be renamed or deleted. Custom attributes that are imported as referenced requirements from an external document become read-only custom attributes after they are imported. The custom attributes of a requirement set are associated with every individual requirement in the set and removing the custom attributes for a requirement set removes it from all the requirements in the set.

See Add Custom Attributes to Requirements for more information about creating custom attributes for requirements.