The object of this tutorial is to generate requirements in Teamcenter from requirements in a MagicDraw SysML model. In this exercise, we will start from the Tutorial_2_11 package in the Syndeia Tutorial Testbed.mdzip 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.
Figure 94 SysML Requirements diagram
- The initial requirements structure in MagicDraw looks like Figure 94below. We will add two new stereotypes from the Syndeia profile to identify the top two requirements as special Teamcenter requirements elements.
- In the MagicDraw containment browser, right-click on UAV Specification, select Stereotype, check the box next to TC_RequirementSpec _Revision, and click Apply.
- Similarly right-click on Engine Specification, select Stereotype, check the box next to TC_Paragraph _Revision, and click Apply.
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.
Figure 95 MagicDraw Project Options Menu
- To avoid problems between the auto-numbering functions on MagicDraw and Teamcenter, it may be necessary to turn off MagicDraw's auto-numbering feature, as shown in Figure 95.
- In the MagicDraw menu bar, select Option→Project and choose General Project Options.
- Scroll down to the Numbering section and uncheck Use Element Auto-numbering.
- MagicDraw requires that this setting be made for each individual project. It cannot be set as default for all projects.
- Without this setting, MagicDraw will tend to renumber the Teamcenter requirements whenever the two models are connected, which may not be desirable for the user.
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 Figure 95, the The tc-newuav Teamcenter repository contains an empty folder Demo3.
Figure 94Connection Manager showing SysML Tutorial 2_11 package and empty Demo3 folder in Teamcenter- Drag the UAV Specification requirement from SysML onto the Demo3 folder. Confirm the generation of Teamcenter requirements as in Figure 96. The dashboard shows the final requirements structure in Teamcenter at completion in Figure 97. The connections created are shown in Figure 98.
Figure 96 Confirmation window
Connection Manager showing final Teamcenter requirements structure
Figure 98 Connection Summary showing connections between SysML and Teamcenter requirements
