Objectives
The new learning objectives of this exercise are to create a multi-level requirements structure in MagicDraw from a Module in DOORS NG, and keep them connected using the Syndeia Model Transform connection. This exercise uses the default SysML-DOORS NG mapping. Custom mappings are demonstrated in Exercises 5.6 and above.
Preparation
This exercise assumes the student has
Cameo System Modeler 18.0 - 19.0 (or MagicDraw with SysML plug-in) installed correctly on his or her machine with a valid license for use, and
Syndeia 3.3 installed as a plugin for Cameo/MagicDraw with a valid license for use
Syndeia DOORS NG interface, correctly installed with a valid license for user.
The user can use any DOORS NG repository network connection 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
Create a sample requirements module in DOORS NG. For this tutorial, we have created a module, UAV Requirement Module, consisting of three levels of requirements, 1531 at the top level, 1532 and 1534 at the second level and 1533 below 1532 at the third level. It is outside the scope of this tutorial to describe how to create modules in DOORs NG, but review the IBM documentation if this Syndeia feature is of importance to you.
Figure 1 DOORS NG web interface, showing UAV Requirement Module structure
Assuming the model Syndeia_DNG_Mapping_Tutorial (get it here - SysML Models, Profiles and Mappings) and Syndeia dashboard still open from the last exercise, expand the SysML model in the Connection Manager tab to show the DOORS NG Tutorial::DNG Module to SysML package. On the right side, choose a project containing a DOORS requirement module. Figure 2 shows the 1530 – UAV Requirement Module under the Unmanned Aerial Vehicle project.
Figure 2 Syndeia dashboard, Connection Manager tab, showing module in DOORS NG
To create a SysML multi-level requirement structure with Model Transform connections back to the original DOORS NG requirements module,
Set Connection Type to Model Transform in center section
Drag-and-drop the module (1530 – UAV Requirements Module) in this example from the right side on top of the DNG Module to SysML package on the left.
Click Yes to confirm.
Expand and refresh left side to show the multi-level requirements structure within the DNG Module to SysML package, as shown in Figure 3.
Figure 3 Syndeia dashboard, Connection Manager tab, showing module in DOORS NG and SysML
The new requirements structure created in MagicDraw has been shown in a requirement diagram in Figure 4. Note that the elements have special stereotypes reflecting their generation from DOORS NG. For example, 1530 – UAV Requirement Module has both <<requirement>> and <<DOORS-NG_Module>>.
Figure 4 MagicDraw Requirements Diagram
Comparison and synch from DOORS NG to MagicDraw is available, similar to the behavior of Collections as shown in the previous exercise.
The reverse process, creating or updating a Module in DOORS NG from a multi-level requirements structure in SysML is not currently supported by Syndeia (because it is not supported by the DOORS NG APIs).