...
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 be 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 be connected to the nearest package of the SysML requirement. Each SysML requirement should be connected to each Simulink requirement.
1c (Multiple drag and drop): Drag and drop multiple SysML requirements and drop them 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.
1d: Drag and drop a SysML package and drop it to a folder. This will collect all the “immediate requirements” in the folder and do the same as S1c. The SysML package should be connected to the resulting requirement set. Note that the package may have other elements too but we just collect the immediate requirements
...
Steps are for this exercise are as follows
1 Open Syndeia_Simulink_Examples.mdzip (get it here -SysML Models, Profiles and Mappings)in MagicDraw/Cameo.
2 Locate the Model Generation Package::Requirements Package
...
6 Open the Simulink requirements model in Simulink, as shown below.
...
1c (Multiple DnD): Drag and drop multiple SysML requirements and drop them to a folder
The steps for this exercise are as follows.
...
2 This will generate a Simulink requirements file with a requirement set containing the four requirements that were generated. This is seen as below in Syndeia Dashboard on RHS.
...