Syndeia allows requirements to be generated, compared and synchronized bi-directionally between Rhapsody and Teamcenter. Exchange is complicated by the different approaches to requirements hierarchies in the two tools, which are described in Section 2.11.2.

Generating Teamcenter Requirements from SysML

1. The object of this tutorial is to generate requirements in Teamcenter from requirements in a Rhapsody SysML model. In this exercise, we will start from the Tutorial_2_11 package in the Syndeia Tutorial Testbed model provided with this tutorial. The user also needs an active repository link to Teamcenter, which can be the same as that used in Section 2.4, plus at least one empty folder within the Teamcenter repository in which the new requirements structure can be created.
   
    

2. The initial requirements structure in Rhapsody looks like Figure 93. We will add two new stereotypes from the Syndeia profile to identify the top two requirements as special Teamcenter requirements elements.
   1. In the Rhapsody model view browser, right-click on UAV Specification, select Set Stereotype, and TC_RequirementSpec_Revision.
   2. Similarly right-click on Engine Specification, select Set Stereotype, and TC_Paragraph_Revision.
   3. The additional stereotypes on these two elements will appear on the requirements diagram. It is beyond the scope of this tutorial to describe the significance of Paragraphs and Requirement Specifications in Teamcenter repositories, but these elements obey certain rules in building requirements hierarchies and applying the stereotypes at the SysML level is necessary for Syndeia to recognize the need to create these elements in the next step.
       
3. Launch the Syndeia dashboard from the Tutorial_2_11 package. In the Connection Manager tab, select the appropriate Teamcenter link for access to the empty Teamcenter folder. In this figure, the tc-newuav Teamcenter repository contains an empty folder Demo3.
   

   

    
4. Drag the UAV Specification requirement from SysML onto the Demo3 folder. Confirm the generation of Teamcenter requirements as in Figure 95. The dashboard shows the final requirements structure in Teamcenter at completion in Figure 96. The connections created are shown in the figure below.
   
    
   
    
   
    
   

Syncing Requirements from SysML to Teamcenter

Syndeia is able to compare and sync requirements across existing connections. 

1. Change the text of the Max Power requirement in Rhapsody to "The UAV engine shall generate at least 75 horsepower."
2. In the Syndeia dashboard, Connection Browser, right-click on the Requirements folder and select Compare SysML & Target.

   
   

   

    
3. The above figure shows the results of the comparison. The Max Power requirement is identified as having changed in Name, ID or Description, although the specific change is not identified.
4. The requirements may be synchronized in either direction, by choosing Sync SysML → Target or Sync Target → SysML, as shown in Figure 98.

Dependencies from SysML to Teamcenter

Syndeia is able to generate, compare and sync dependencies between SysML and Teamcenter. In SysML, dependencies include <<satisfy>>, <<trace>>, <<verify>>, <<allocate>> and other relationships that are dependencies with additional stereotypes attached. In Teamcenter, dependencies take the form of Trace Links, which do not differentiate between different types of SysML dependencies.

1. The SysML model in Tutorial 2_11 contains both requirements and blocks, with <<satisfy>> relationships between them.
    
2. Launch the Syndeia dashboard from the Tutorial 2_11 package in Rhapsody.
   

   

    

3. Set Syndeia options so dependencies are carried across the connectors. In the Syndeia dashboard, Settings tab, check the three boxes marked "Generate SysML Dependencies and Trace Links", "Generate SysML Dependencies and Trace Links Recursively", and "Generate Other End of SysML Dependencies and Trace Links". Click Apply (settings will not be updated with clicking Apply).
    
4. The Connection Browser should appear.
   
   

   

    

   

    
5. Set Connection Type to Model Transform. Drag the UAV block from the SysML model onto the Demo3 folder on the Teamcenter side. The final state of the Teamcenter model, partially expanded. The trace links corresponding to the <<satisfy>> relationship between UAV and UAV specification are shown as associated with both elements in Teamcenter. The two <<satisfy>> relationships originating from the Engine block appear next to the Engine item version, as well as the Efficiency and Max Power requirements. 
    
6. Other SysML dependencies, including <<allocate>>, <<verify>> and <<trace>>, can be created as trace links in Teamcenter in the same way.|