Contents

Customize DOORS Synchronization

DOORS Synchronization Settings

When you synchronize your Simulink® model with a DOORS® database, you can:

  • Customize the level of detail for your surrogate module.

  • Update links in the surrogate module or in the model to verify the consistency of requirements links among the model, and the surrogate and formal modules.

The DOORS synchronization settings dialog box provides the following options during synchronization.

DOORS Settings OptionDescription

DOORS surrogate module path and name

Specifies a unique DOORS path to a new or an existing surrogate module.

For information about how the RMI resolves the path to the requirements document, see Document Path Storage.

Extra mapping additionally to objects with links

Determines the completeness of the Simulink model representation in the DOORS surrogate module. None specifies synchronizing only those Simulink objects that have linked requirements, and their parent objects. For more information about these synchronization options, see Customize the Level of Detail in Synchronization.

Update links during synchronization

Specifies updating any unmatched links the RMI encounters during synchronization, as designated in the Copy unmatched links and Delete unmatched links options.

Copy unmatched links

During synchronization, selecting the following options has the following results:

  • from Simulink to DOORS: For links between the model and the formal module, the RMI creates matching links between the DOORS surrogate and formal modules.

  • from DOORS to Simulink: For links between the DOORS surrogate and formal modules, the RMI creates matching links between the model and the DOORS modules.

Delete unmatched links

During synchronization, selecting the following options has the following results:

  • Remove unmatched in DOORS: For links between the formal and surrogate modules, when there is not a corresponding link between the model and the DOORS modules, the RMI deletes the link in DOORS.

    This option is available only if you select the from Simulink to DOORS option.

  • Remove unmatched in Simulink: For links between the model and the DOORS modules, when there is not a corresponding link between the formal and surrogate modules, the RMI deletes the link from the model.

    This option is available only if you select the from DOORS to Simulink option.

Save DOORS surrogate module

After the synchronization, saves changes to the surrogate module and updates the version of the surrogate module in the DOORS database.

Save Simulink model (recommended)

After the synchronization, saves changes to the model. If you use a version control system, selecting this option changes the version of the model.

Resynchronize a Model with a Different Surrogate Module

You can synchronize the same Simulink model with a new DOORS surrogate module. For example, you might want the surrogate module to contain only objects that have requirements to DOORS, rather than all objects in the model. In this case, you can change the synchronization options to reduce the level of detail in the surrogate module:

  1. In the DOORS synchronization settings dialog box, change the DOORS surrogate module path and name to the path and name of the new surrogate module in the DOORS database.

  2. Specify a module with either a relative path (starting with ./) or a full path (starting with /).

    The software appends relative paths to the current DOORS project. Absolute paths must specify a project and a module name.

    When you synchronize a model, the RMI automatically updates the DOORS surrogate module path and name with the actual full path. The RMI saves the unique module ID with the module.

  3. If you select a new module path or if you have renamed the surrogate module, and you click Synchronize, the Requirements: Surrogate Module Mismatch dialog box opens.

  4. Click Continue to create a new surrogate module with the new path or name.

Customize the Level of Detail in Synchronization

You can customize the level of detail in a surrogate module so that the module reflects the full or partial Simulink model hierarchy.

In Synchronize a Simulink Model to Create a Surrogate Module, you synchronized the model with the Extra mapping additionally to objects with links option set to None. As a result, the surrogate module contains only Simulink objects that have requirement links, and their parent objects. Additional synchronization options, described in this section, can increase the level of surrogate detail. Increasing the level of surrogate detail can slow down synchronization.

The Extra mapping additionally to objects with links option can have one of the following values. Each subsequent option adds additional Simulink objects to the surrogate module. You choose None to minimize the surrogate size or Complete to create a full representation of your model. The Complete option adds all Simulink objects to the surrogate module, creating a one-to-one mapping of the Simulink model in the surrogate module. The intermediate options provide more levels of detail.

Drop-Down List OptionDescription
None (Recommended for better performance)

Maps only Simulink objects that have requirements links and their parent objects to the surrogate module.

Minimal - Non-empty unmasked subsystems and Stateflow charts

Adds all nonempty Stateflow® charts and unmasked Simulink subsystems to the surrogate module.

Moderate - Unmasked subsystems, Stateflow charts, and superstates

Adds Stateflow superstates to the surrogate module.

Average - Nontrivial Simulink blocks, Stateflow charts and states

Adds all Stateflow charts and states and Simulink blocks, except for trivial blocks such as ports, bus objects, and data-type converters, to the surrogate module.

Extensive - All unmasked blocks, subsystems, states and transitions

Adds all unmasked blocks, subsystems, states, and transitions to the surrogate module.

Complete - All blocks, subsystems, states and transitions

Copies all blocks, subsystems, states, and transitions to the surrogate module.

Resynchronize to Include All Simulink Objects

This tutorial shows how you can include all Simulink objects in the DOORS surrogate module. Before you start these steps, make sure you have completed the tutorials Synchronize a Simulink Model to Create a Surrogate Module and Create Links Between Surrogate Module and Formal Module in a DOORS Database.

  1. Open the sf_car_doors model that you synchronized in Synchronize a Simulink Model to Create a Surrogate Module and again in Create Links Between Surrogate Module and Formal Module in a DOORS Database.

  2. In the Simulink Editor, select Analysis > Requirements Traceability > Synchronize with DOORS.

    The DOORS synchronization settings dialog box opens.

  3. Resynchronize with the same surrogate module, making sure that the DOORS surrogate module path and name specifies the surrogate module path and name that you used in Synchronize a Simulink Model to Create a Surrogate Module.

    For information about how the RMI resolves the path to the requirements document, see Document Path Storage.

  4. Update the surrogate module to include all objects in your model. To do this, under Extra mapping additionally to objects with links, from the drop-down list, select Complete - All blocks, subsystems, states and transitions.

  5. Click Synchronize.

    After synchronization, the DOORS surrogate module for the sf_car_doors model opens with the updates. All Simulink objects and all Stateflow objects in the sf_car_doors model are now mapped in the surrogate module.

  6. Scroll through the surrogate module. Notice that the objects with requirements (the engine torque block and transmission subsystem) retain their links to the DOORS formal module, as indicated by the red triangles.

  7. Save the surrogate module.

Detailed Information About The Surrogate Module You Created

Notice the following information about the surrogate module that you created in Resynchronize to Include All Simulink Objects:

  • The name of the surrogate module is sf_car_doors, as you specified in the DOORS synchronization settings dialog box.

  • DOORS object headers are the names of the corresponding Simulink objects.

  • The Block Type column identifies each object as a particular block type or a subsystem.

  • If you delete a previously synchronized object from your Simulink model and then resynchronize, the Block Deleted column reads true. Otherwise, it reads false.

    These objects are not deleted from the surrogate module. The DOORS software retains these surrogate module objects so that the RMI can recover these links if you later restore the model object.

  • Each Simulink object has a unique ID in the surrogate module. For example, the ID for the surrogate module object associated with the Mux block in the preceding figure is 11.

  • Before the complete synchronization, the surrogate module contained the transmission subsystem, with an ID of 3. After the complete synchronization, the transmission object retains its ID (3), but is listed farther down in the surrogate module. This order reflects the model hierarchy. The transmission object in the surrogate module retains the red arrow that indicates that it links to a DOORS formal module object.

Was this topic helpful?