Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a sample requirements module in DOORS NG. For this tutorial, we have created a module, UAV Requirement Module, consisting of three levels of requirements, 1531 at the top level, 1532 and 1534 at the second level and 1533 below 1532 at the third level. It is outside the scope of this tutorial to describe how to create modules in DOORs NG, but review the IBM documentation if this Syndeia feature is of importance to you.

    Figure 1  DOORS NG web interface, showing UAV Requirement Module structure

  2. Assuming the model Syndeia_DNG_Mapping_Tutorial (Get it here - SysML Models, Profiles and Mappings.) and Syndeia dashboard are still open from the last exercise, expand the SysML model in the Connection Manager tab to show the DOORS NG Tutorial::DNG Module to SysML package. On the right side, choose a project containing a DOORS requirement module. Figure 2 shows the 2083 – UAV Requirement Module under the Unmanned Aerial Vehicle project.

    Figure 2  Syndeia dashboard, Connection Manager tab, showing module in DOORS NG

  3. To create a SysML multi-level requirement structure with Model Transform connections back to the original DOORS NG requirements module,

    1. Set Connection Type to Model Transform in center section

    2. Drag-and-drop the module (2083 – UAV Requirements Module) in this example from the right side on top of the DNG Module to SysML package on the left.

    3. Click Yes to confirm.

    4. Expand and refresh left side to show the multi-level requirements structure within the DNG Module to SysML package, as shown in Figure 3.

      Figure 3  Syndeia dashboard, Connection Manager tab, showing module in DOORS NG and SysML

  4. The new requirements structure created in Rhapsody has been shown in a requirement diagram in Figure 4. Note that the elements have special stereotypes reflecting their generation from DOORS NG. For example, 2083 – UAV Requirement Module is a requirement with the <<DOORS-NG_Module>> stereotype.

    Figure 4  Rhapsody Requirements Diagram

  5. Comparison and synch from DOORS NG to Rhapsody is available, similar to the behavior of Collections as shown in the previous exercise.

  6. The reverse process, creating or updating a Module in DOORS NG from a multi-level requirements structure in SysML is not currently supported by Syndeia (because it is not supported by the DOORS NG APIs).

...