Skip to Main Content Skip to Search
Product Documentation

Viewing Linked Requirements in Models and Blocks

Overview of Requirements Features in Simulink

If your Simulink model has links to requirements in external documents, you can review these links. To identify which model objects satisfy certain design requirements, use the following requirements features available in Simulink software:

Having a Simulink Verification and Validation license enables you to perform the following additional tasks, using the Requirements Management Interface (RMI):

Highlighting Requirements in a Model

You can highlight a model to identify which objects in the model have links to requirements in external documents. Both the Model Editor and the Model Explorer provide this capability.

Highlighting a Model Using the Model Editor

If you are working in the Model Editor and want to see which model objects in the slvnvdemo_fuelsys_officereq model have requirements, follow these steps:

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. Select Tools > Requirements > Highlight model.

    Two types of highlighting indicate model objects with requirements:

    • Yellow highlighting indicates objects that have requirements links for the object itself.

    • Orange outline indicates objects, such as subsystems, whose child objects have requirements links.

    Objects that do not have requirements are colored gray.

  3. To remove the highlighting from the model, select Tools > Requirements > Unhighlight model. Alternatively, you can right-click anywhere in the model, and select Remove Highlighting.

While a model is highlighted, you can still manage the model and its contents.

Highlighting a Model Using the Model Explorer

If you are working in Model Explorer and want to see which model objects have requirements, follow these steps:

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. Select View > Model Explorer.

  3. To highlight all model objects with requirements, click the Highlight items with requirements on model icon ( ).

    The Model Editor window opens, and all objects in the model with requirements are highlighted.

Viewing Information About a Requirements Link

Using Simulink, you can view detailed information about a requirements link, such as identifying the location and type of document that contains the requirement.

For example, to view information about the requirements link from the MAP Sensor block in the slvnvdemo_fuelsys_officereq demo model, follow these steps:

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. Right-click the MAP sensor block, and select Requirements > Edit/Add Links.

    The Requirements dialog box opens and displays the following information about the requirements link:

    • The description of the link (which is the actual text of the requirement).

    • The Microsoft Excel® workbook named slvnvdemo_FuelSys_TestScenarios.xlsx, which contains the linked requirement.

    • The requirements text, which appears in the named cell Simulink_requirement_item_2 in the workbook.

    • The user tag test, which is associated with this requirement.

Navigating to Requirements from a Model

Navigating from the Model Object

You can navigate directly from a model object to that object's associated requirement. When you take these steps, the external requirements document opens in the application, with the requirements text highlighted.

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. Open the fuel rate controller subsystem.

  3. To open the linked requirement, right-click the Airflow calculation subsystem and select Requirements > 1. "Mass airflow estimation".

    The Microsoft Word document slvnvdemo_FuelSys_DesignDescription.docx, opens with the section 2.1 Mass airflow estimation selected.

Navigating from a System Requirements Block

Sometimes you want to see all the requirements links at a given level of the model hierarchy. In such cases, you can insert a System Requirements block to collect all requirements links in the model or subsystem. The System Requirements block does not list requirements links for any blocks for that model or subsystem.

For example, you can insert the System Requirements block at the top level of the slvnvdemo_fuelsys_officereq model, and navigate to the requirements using the links inside the block.

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. Select Tools > Requirements > Highlight model.

  3. In the slvnvdemo_fuelsys_officereq model, open the fuel rate controller subsystem.

    The Airflow calculation subsystem has a requirements link.

  4. Open the Airflow calculation subsystem.

  5. Select View > Library Browser

  6. On the Libraries pane, click the Simulink Verification and Validation library.

    This library contains only one block—the System Requirements block.

  7. Drag a System Requirements block into the Airflow calculation subsystem.

    The RMI software collects and displays any requirements links for that subsystem.

  8. Double-click 1. "Mass airflow subsystem".

    The Microsoft Word document, slvnvdemo_FuelSys_DesignDescription.docx, opens, with the section 2.1 Mass airflow estimation selected.

Filtering Requirements in a Model

Filtering Requirements Highlighting by User Tag

Some requirements links in your model can have one or more associated user tags. User tags are keywords that you create to categorize a requirement, for example, design or test.

For example, in the slvnvdemo_fuelsys_officereq model, the requirements link from the MAP sensor block has the user tag test.

To highlight only all the blocks that have a requirement with the user tag test:

  1. Open the demo model:

    slvnvdemo_fuelsys_officereq
  2. In the Model Editor, select Tools > Requirements > Settings.

    The Requirements Settings dialog box opens. If you do not have a Simulink Verification and Validation license, the Filters tab is the only option available.

    By default, your model has no requirements filtering enabled.

  3. Select Filter links by user tags when highlighting and reporting requirements.

  4. In the Include links with any of these tags text box, delete design, and enter test.

  5. Press Enter.

  6. Highlight the slvnvdemo_fuelsys_officereq model for requirements. Select Tools > Requirements > Highlight model.

    In the top-level model, only the MAP sensor block and the Test inputs block are highlighted.

  7. To disable the filtering by user tag, select Tools > Requirements > Settings, and clear Filter links by user tags when highlighting and reporting requirements.

    The model highlighting updates immediately.

Filtering Options for Highlighting Requirements

On the Filters tab, you select options that designate which objects with requirements are highlighted. The following table describes these settings, which apply to all requirements in your model for the duration of your MATLAB session.

OptionDescription
Filter links by user tags when highlighting and reporting requirementsEnables filtering for highlighting and reporting, based on specified user tags.
Include links with any of these tagsHighlights all objects whose requirements match at least one of the specified user tags. The tag names must match exactly. Separate multiple user tags with commas or spaces.
Exclude links with any of these tagsExcludes from the highlighting all objects whose requirements match at least one of the specified user tags. The tag names must match exactly. Separate multiple user tags with commas or spaces.
Apply same filters in context menusDisables navigation links in context menus for all objects whose requirements do not match at least one of the specified user tags.
Under Link type filters, Disable DOORS surrogate item links in context menusDisables links to IBM®Rational®DOORS® surrogate items from the context menus when you right-click a model object. This option does not depend on current user tag filters.

  


Related Products & Applications

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

 © 1984-2012- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS