The reverse process from this section, generating requirements in Rhapsody from the Teamcenter repository, is very similar, including the features of comparing and synching. Exchange is complicated by the different approaches to requirements hierarchies in the two tools.

Generating SysML Requirements from Teamcenter

1. The object of this tutorial is to generate a requirement in a Rhapsody SysML model from a requirement in Teamcenter. In this exercise, we can start with any empty SysML package in a Rhapsody model containing the Syndeia profile. We will use the same Teamcenter repository populated in the previous exercise.
   
   Launching the Syndeia dashboard from the empty Tutorial_2_12 package, we see REQ-0002308/A;1-UAV Specification
   
   
   
   
2. Set Connection Type to Model Transform. Drag and drop REQ-0004927/A;1-UAV Specification onto the Tutorial_2_12 package. Click Yes in the confirmation dialog box shown at the bottom of Figure 105.
   
   

   

   
   

3. The final state of the Connection Manager is shown below
   
    

4. The SysML model created from this single action is complex and requires some explanation. Teamcenter, unlike SysML, allows a requirement to be owned by more than one other requirement or requirement specification. Therefore, a Teamcenter requirement can exist as both an independent requirement and as an "owned" requirement. No corresponding structure is available in SysML, so the "owned" Teamcenter requirement is represented by a SysML requirement that is a <<copy>> of an independent requirement. In the figure below, this relationship appears three times, for Engine Specification, Max Power, and Efficiency.
5. The SysML Model also includes the UAC, Engine and Body blocks, and their dependencies on the requirements. These dependencies reflect the <<satisfy>> relationships transferred to Teamcenter, but are created only as dependencies in SysML on the round trip. <<satisfy>> stereotypes can be applied in Rhapsody, if desired.