Objectives
In this tutorial, we shall cover the following scenarios
1a: Drag and drop a single SysML requirement to a folder. This should generate a requirement model file with a requirement set with a single requirement. The Simulink requirement set should have the same name and connected to the nearest package of the SysML requirement. Each SysML requirement should be connected to each Simulink requirement.
1b: Drag and drop a single SysML requirement with multiple levels of nested requirements to a folder. This should generate a requirement model file with a requirement set with a single requirement that then has all the multi-level nested requirements. The Simulink requirement set should have the same name and connected to the nearest package of the SysML requirement. Each SysML requirement should be connected to each Simulink requirement.
1c (Multiple DnD): Drag and drop multiple SysML requirements and drop to a folder. This is an extension of the first two scenarios. A single requirement model with a single requirement set should be created. Now, the user may select SysML requirements from multiple packages. This is odd but you can take the nearest package of the first SysML requirement to derive the name of the Simulink requirement set.
1d: Drag and drop a SysML package and drop to a folder. This will collect all the “immediate requirements” in the folder and do the same as S1c. The SysML package should be linked to the resulting requirement set. Note the package may have other elements too but we just collect the immediate requirements
Preparation
This exercise assumes the student has
Rhapsody 8.4 installed correctly on his or her machine with a valid license for use,
Syndeia 3.3 installed as a plugin for Rhapsody 8.4 with a valid license for use,
Syndeia Simulink interface, correctly installed with a valid license for use,
MATLAB/Simulink R2019b or later installed correctly on his or her machine with a valid license for use.
In this tutorial, we will use the Rhapsody SysML model available as Syndeia_Simulink_Examples_Rhapsody.zip
1a. Drag and drop a single SysML requirement to a folder in Simulink.
Steps are
1 Open Syndeia Simulink Examples.
2 Observe the Requirements Package.
3 Launch Syndeia Dashboard from Requirement Package.
5 In Connection Manager of Syndeia Dashboard in SysML Repository and SimulinkReqts folder which is local for this example is displayed. Local Simulink folder of your choice can be chosen as well.
6 Select a Single Requirement Autonomous Flight and drag and drop to folder S1a as shown above. Select Model Transform. Select Yes.
7 Observe the newly created Simulink Requirement and right-click to Launch Simulink Requirements from Syndeia.
8 In Connections Search this connection is generated.
9 Open in Simulink this requirement Autonomous Flight is displayed in the selected folder.
1b: Drag and drop a single SysML requirement with multiple levels of nested requirements to a folder.
Steps are
1 Select the single Payload Mass with two nested requirements.
2 Drag and Drop to Folder S1b in the SimulinkReqts folder on the local machine.
Select Yes.
3 In Connections Manager, it shows connections generated.
4 In Simulink, this appears as below.
1c (Multiple DnD): Drag and drop multiple SysML requirements and drop to a folder
Steps are
1 Select Multiple Requirements from SysML Package Requirements and drag and drop it to S1c package of the local folder. Select Yes.
2 In Syndeia new connections are created and can be seen in the Connections Search tab.
3 In Simulink, this appears as below.
1d: Drag and drop a SysML package and drop to a folder
1 Drag and Drop Requirement_Sim from SysML Rhapsody to S1d folder on local machine in Simulink Requirements as below
2 In Syndeia, new connections are created and can be seen in the Connections Search tab.
3 In Simulink, this creates a new requirement set as below.
