3. Go to the Mappings tab. The contents of the main area on the right will depend on the element selected on the left. Expand Mapping Groups and select SysML-Jama on the left to see the existing mappings in this area (Figure 2). Check the mapping spec for Requirement - Requirement (attributes).

4. The first task is to drag a hierarchy of Jama requirements into Cameo to create an equivalent requirements structure. An example Jama structure ‘Product Spec’ is shown below in Figure 3.

5. Go to the Connection Manager tab on the Syndeia dashboard, expand the SysML tree on the LHS, and select your Jama repository from the drop-down menu on the RHS as shown in Figure 4.

a. With Model Transform Connection Type selected, drag the Product Spec Jama requirement onto the empty Cameo Package ‘From Jama’.

b. Select the mapping spec ‘Requirement - Requirement (attributes)’ and click OK.

6. We can view the new Cameo requirements created by expanding the left side of the Connection Manager in Figure 5.

7. In the Connection Browser tab on the Syndeia dashboard, select the Product Spec connection created. Right-click and compare across that connection before any changes have been made to see that all is in sync (Figure 6).

8. The Comparison Result tab will open and the results should appear similar to Figure 7.

Image Removed

Image Added

9. Modify the ‘Product_Spec' text field in Cameo/MagicDraw and add a sub-requirement, 'Feature_1_Safety’, as shown in Figure 8.

10. Compare across the same connection as in Step 7 and display the comparison results (Figure 9).

11. Return to the Connection Browser, click Refresh to show the new child requirement, right-click the connection and select Sync Source -> Target as shown in Figure 10.

12. Repeat the comparison as in Step 2 and check that the Comparison Result shows all green, as in Figure 11.

13. View the same requirement in Jama through its web interface to see the modified requirement text and sub-requirement (Figure 12).

14. Now, return to Cameo/Magicdraw and in the containment tree delete a child requirement underneath Product_Spec as shown in Figure 13.

15. Repeat the Comparison Result step for the Product_Spec Connection.  The deleted Requirement should be flagged in Red in Syndeia as shown in Figure 14.

16. In the Connection Browser of Syndeia, Right-click and select ‘Sync Source to Target’ for the connection as shown in Figure 15.

17. After Syndeia is finished syncing, check that the Requirement no longer shows in Jama Connect as shown in Figure 16.

Part 2

1. In Jama, modify the text of ‘Product_Spec’ and add a new Requirement underneath it as shown in Figure 17.

2. From the Syndeia Dashboard, trigger a Comparison of the connection once again.  The changes should be shown in Red as seen in Figure 18.

3. From the Connection Browser tab, right click the connection and select ‘Sync Target to Source’ as shown in Figure 19.

4. Return to Cameo/Magicdraw and verify that the new changes have been made in the containment tree and properties shown in Figure 20.

5. From Jama Connect, delete a requirement underneath Product_Spec Requirements as shown in Figure 21.

6. From the Syndeia dashboard, compare the Product_Spec Requirements connection again and check that the deleted requirement appears in red as shown in Figure 22.

7. Now from the Connection Browser, right click on the connection and select ‘Sync Target to Source’ as shown in Figure 23.

8. Check in Cameo that the Requirement ‘Feature_1_Environmental’ has been moved to the Parent Package level in the Containment Tree as shown in Figure 24.

9. Compare the connection from Syndeia one last time to check that everything is showing green.