Generating Teamcenter Requirements from SysML.
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.
Â- The initial requirements structure in Rhapsody looks like the figure above. We will add two new stereotypes from the Syndeia profile to identify the top two requirements as special Teamcenter requirements elements.
- In the Rhapsody model view browser, right-click on UAV Specification, select Set Stereotype, and TC_RequirementSpec_Revision.
- Similarly right-click on Engine Specification, select Set Stereotype, and TC_Paragraph_Revision.
- 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.
Â
- 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.
Â
- Drag the UAV Specification requirement from SysML onto the Demo3 folder. Confirm the generation of Teamcenter requirements. The dashboard shows the final requirements structure in Teamcenter at completion. The connections created are shown in the figure below.
Â
Â
Â