Objectives
The new learning objectives of this exercise are to transform a requirement or set in Jama into a Rhapsody SysML model using the default Jama -> SysML mappings.
Preparation
This exercise assumes the student has
IBM Rational Rhapsody 8.2 installed correctly on his or her machine with a valid license for use, and
Syndeia 3.3 installed as a plugin for Rhapsody with a valid license for use
Syndeia Jama interface, correctly installed with a valid license for user.
A Jama repository network connection in the Syndeia Repository Manager
A Jama requirement structure, typically the one created in the previous exercise.
Unchecked the Use mapping checkbox on the Syndeia dashboard Settings tab.
The user can use any Jama repository they have available. It is generally advisable to carry out these exercises in a non-production repository, a "sandbox", set up for training and practice purposes.
Exercise
Open the Syndeia_Jama_Mapping_Tutorial model and launch Syndeia from the Jama Connections folder, if not already open from the previous exercise. Go to the Connection Manager tab on the Syndeia dashboard, expand the SysML tree on the LHS, and select your Jama repository from the drop-down menu on the RHS (Figure 1).
Figure 1 Drag and drop Jama requirement onto SysML package
With Model Transform Connection Type selected, drag and drop either a set or a requirement from Jama to a SysML package, and click 'Yes' when prompted. We are using the requirement structure System Requirement Spec generated in Jama in the previous exercise and the empty SysML package From Jama, but any similar structures could be used.
Figure 2 Syndeia dashboard showing new SysML requirements
Expand and view new SysML requirements both in the Syndeia Connection Manager's SysML tree (Figure 2) as well as in the Rhapsody model view tree (Figure 3).
Figure 3 Rhapsody model view browser showing new SysML requirements