Page Comparison

...

1. Open the SysML project Syndeia_DOORS_NG_Mapping_Tutorial.mdzip, right-click the DOORS_NG package, and launch the Syndeia dashboard
2. Go to the Mappings tab. The first task will be to create a new mapping using existing artifacts.
   1. Right-click SysML-DOORS NG under Mapping Groups in the left column and select Add Mapping
   2. Initially, the window should appear similar to Figure 1.
      
      
       
      
   3. Modify the Mapping
      1. Change Name to Requirement - Collection (no attributes)
      2. Change Description to SysML Requirement - DOORS NG Collection with no attributes
      3. Change Source Artifact Type to Requirement, using pull-down menu
      4. Set Target Artifact Type to Collection, using pull-down menu
      5. Set Structure Level to CHILDREN_RECURSIVE, using pull-down menu
      6. Set Include Attributes to Exclude Attributes, using pull-down menu
      7. The window should look similar to Figure 2.
         
         
         
         
      8. Click Save Mapping at bottom of right side (scroll down if necessary).
3. Use the new Mapping you just created
   1. Go to the Connection Manager tab. Open a DOORS NG repository in the right column.
   2. Drag the Product_Spec requirement in the SysML model into a project or folder in DOORS NG (Tutorial Sandbox in this example).
   3. A small pull-down menu will appear on the Syndeia dashboard, as Figure 3, showing the possible mappings available for a SysML requirement dragged into DOORS NG.
      
      
      
      
   4. Select Requirement – Collection (No attributes) and click OK.
   5. Expand the destination folder (Tutorial Sandbox in our example) on the right side of the Connection Manager. Check that a new DOORS NG collection with child requirements has been created.
4. The second task is to create another new mapping, this one with attributes shared between the SysML and DOORS NG elements. We will use the Clone Mapping command rather Add Mapping. Clone Mapping saves time when not all features of the new mapping need to be modified.
   1. Right-click Requirement - Collection (no attributes) under Mapping Groups/SysML – DOORS NG in the left column and select Clone Mapping
   2. Initially, the window should appear similar to Figure 4.
      
      
      
      
   3. Modify the Mapping
      1. Change Name to Requirement - Collection (attributes)
      2. Change Description to SysML Requirement – DOORS NG Collection with attributes
   4. Keep Source Artifact Type as Requirement and Target Artifact Type as Collection
   5. Set Structure Level to CHILDREN_IMMEDIATE, using pull-down menu
   6. Set Include Attributes to Include Attributes, using pull-down menu
   7. At the bottom of the right side, click the + sign box under the Stereotypes table.
   8. A Select stereotype window will open. The window should look similar to Figure 5.
      
      
      
      
   9. Select DOORS_Requirement. This choice will appear in the Stereotype box on the right.
   10. Scroll up to Attribute Definition Mappings
   11. Click Retrieve Available Attribute Definitions
   12. Click the + box below the Attribute Definition Mappings box.
   13. In the new row, select Identifier on the right (Target) side of the table, using the pull-down menu
   14. In the new row, select Id [owner: Stereotype(Requirement)] on the left (Source) side of the table.
   15. Repeat steps xi through xiii for Primary Text and Created On. The final table should look like Figure 6.
       
       
       
       
   16. Click Save Mapping at bottom of right side (scroll down if necessary).
5. Use the cloned Mapping you just created
   1. Go to the Connection Manager tab. Open the DOORS NG repository you used above in the right column.
   2. Drag the Product_Spec DOORS NG created earlier into the empty SysML DNG4
   3. A small pull-down menu will appear on the Syndeia dashboard, as in Figure 7, showing the possible mappings available for a collection dragged into SysML.
      
      Image Added
      
      
   4. Select Requirement - Collection (attributes) and click OK.
6. A new requirements hierarchy should appear under DNG4 on the SysML side. It will have the <<DOORS_Requirement>> stereotype in addition to <<requirement>> and all the tag values associated with those stereotypes (see Figure 8).
   Image Removed
   Image Added
   
   
7. Delete the Feature_1_Environmental requirement in package DNG4, then return to the Syndeia dashboard, Connection Browser tab, find the connection between DNG4::Product_Spec and the 511 – Product_Spec collection in DOORS. Right-click and select Compare Source and Target. The Comparison Result shows the missing requirement on the SysML side in red (Figure 9).
   Image Removed
   Image Added