...
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 R2016b or later installed correctly on his or her machine with a valid license for use.
In this tutorial, we will use the Simulink requirement model generated in Exercise 10.7 - SysML Requirements -> Simulink Requirements.
1a: Drag and drop a single Simulink requirement
Steps areThe steps for this exercise are as follows
1 Open Syndeia Simulink Examples in SysML Rhapsody.
2 Observe the Requirements Package S1d Locate the package Model Generation:: FromSimR and see package S1d.
3 This appears as shown below.
...
4 Launch Syndeia Dashboard from Model Generation Package.
...
5 In Simulink, we have Requirement_Sim Set which we have obtained from Feature 1c Step 4 of Tutorial Exercise 10.7 - SysML Requirements -> Simulink Requirements.
From the Simulink Requirements folder on the local computer for eg here S1c, from the Requirement_Sim set we drag and drop a single requirement Autonomous Flight requirement to S1d Package in Rhapsody.
...
6 This appears in Syndeia Dashboard as Observe the newly created SysML requirement Autonomous Flight in SysML package S1d in from Simulink Requirements.
...
7 In Connections Search Tab Click the Connection Search tab, click Get ALL, and a new connection for Autonomous Flight is created and can be seen here.
...
8 In SysML Rhapsody this appears as shown below.
...
1b: Drag and drop a single Simulink requirement (with multiple levels of nested child requirements) to a SysML package
...
The steps for this exercise are as follows
1 In Syndeia Dashboard, select Payload Mass from Simulink requirements Requirement_Sim set from local folder for eg S1c here , and drag and drop this to the S1e package S1e in of SysML Rhapsody as shown below. Select Model Transform. Click Select Yes.
...
2 This will appear in Syndeia Dashboard as In the Syndeia Dashboard you can observe the new SysML requirement Payload Mass and the two nested requirements also generated.
...
3 In Connections search new connections createdthe Connection Search tab, click the Get All button. The connections between SysML requirements and Simulink requirements generated in the previous step can be seen.
4 In SysML Rhapsody this requirement Payload Mass and the two nested requirements can be seen. This appears as shown below.
...
1c (Multiple DnD): Drag and drop multiple Simulink requirements in a requirement set to a SysML
The steps for this exercise are as follows
1 Continiuing Continuing with the same Simulink Requirement Set Requirements Requirement_Sim set from the local folder for eg S1c here, we select multiple requirements, drag and drop them to package S1F in SysML Rhapsody ModelDrag and Drop the selected requirements to S1f.
Select Model Transform. Select Yes.
...
2 In Syndeia this shows as the Syndeia Dashboard you can observe the new SysML requirements generated.
...
3 Connections search shows new connections createdIn the Connections Search tab, click the Get All button. The connections between SysML requirements and Simulink requirements generated in the previous step can be seen.
4 In SysML Rhapsody all the requirements generated can be seen. this appears as shown below.
...
1d: Drag and drop a Simulink requirement set to a SysML package.
The steps for this exercise are as follows
1 Here we drop the entire Requirement_Sim set of Simulink Requirement from Simulink Requirements from the local folder for eg here S1c, to the SyML Rhapsody Package S1g as shown below.
...
2 This appears in Syndeia Dashboard as In the Syndeia Dashboard you can observe the new SysML requirements package Requirement_Sim with all requirements.
...
3 In the Connections Search new connections are created tab, click the Get All button. The connections between SysML requirements and Simulink requirements generated in the previous step can be seen.
4 In the SysML Rhapsody model this is shown as below all the requirements and the Requitement_Sim package generated can be seen. This appears as shown below.
...