Objectives
...
In this exercise, we will start with the requirements model in the Teamcenter_Tutorial Part 3::Requirements package in Syndeia Tutorial Testbed.mdzip. The UAV Reqts diagram looks like Figure 1.
Figure 1 Modified UAV SysML model
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.
To avoid problems between the auto-numbering functions on MagicDraw and Teamcenter, it may be necessary to turn off MagicDraw's auto-numbering feature.
In the MagicDraw menu bar, select Options→Project and choose General, Numbering, as shown in Figure 2.
Figure 2 MagicDraw Project Options window, with Use Element Auto-numbering unchecked
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 Teamcenter_Tutorial Part 3 package and select a Syndeia project if necessary.
Go to the Settings tab. Make sure that the Use mapping checkbox is unchecked. We will work with custom mappings for SysML-to-Teamcenter in later exercises.
Scroll down to the Teamcenter setting and check the boxes shown in Figure 3. These affect the model transform of Teamcenter trace links, which we will use later in the exercise.
Figure 3 Syndeia dashboard, Connection Manager tab, with SysML requirements on left
Go to the Connection Manager tab. Open the SysML model in the left column and your Teamcenter repository on the right. In Figure 4, we have an empty folder named Demo_1.
Figure 4 Syndeia dashboard, Connection Manager tab, with SysML requirements on left
Set Connection Type to Model Transform. Drag the SysML UAV Specification requirement onto the Demo_1 folder. When the process is complete, the Teamcenter requirements will be visible on the right side, as shown in Figure 5.
Figure 5 Connection Manager after model transform complete
In the Connection Summary tab, check that four new connections have been created, as seen in Figure 6.
Figure 6 Syndeia dashboard, Connection Search tab, showing new connections between SysML and Teamcenter requirements
The MagicDraw requirements diagram should appear similar to Figure 7 at this stage. Note that additional applied stereotypes are assigned to all elements and additional tagged values have been created and given values.
Figure 7 MagicDraw requirements after Teamcenter model transform
Change the text of the Max Power requirement in SysML to read, "The UAV engine shall generate at least 75 horsepower."
In the Syndeia dashboard, Connection Browser, right-click the Requirements package and select Compare Source and Target. The results should appear similar to Figure 8. The first red row indicates that the Max Power requirement (contained within the Engine Specification) is different between SysML and Teamcenter. The second red row specifically identifies a difference in text between the two.
In the Connection Browser tab, right-click the Requirements package again and select Sync Source -> Target. Do a new comparison to see that the differences have been removed.