...
1a: Drag and drop a single Simulink requirement (has no child requirements) to a SysML package. This will generate a requirement in SysML (with nested requirements if the Simulink requirement had nested requirements). The SysML package will be connected to the requirement set, and each SysML requirement will be connected to the Simulink requirement.
1b: Drag and drop a single Simulink requirement (with multiple levels of nested child requirements) to a SysML package. This will generate a requirement in SysML with nested requirements The SysML package will be connected to the requirement set, and each SysML requirement will be connected to the Simulink requirement.
1c (Multiple DnD): Drag and drop multiple Simulink requirements in a requirement set to a SysML package. This will generate corresponding requirements in SysML (with nested requirements if Simulink requirement had nested requirements). The SysML package will be connected to the requirement set, and each SysML requirement will be connected to the Simulink requirement.
1d: Drag and drop a Simulink requirement set to a SysML package. This will generate a new SysML package corresponding to the Simulink requirement set. The SysML package will be connected to the requirement set, and each SysML requirement will be connected to the Simulink requirement.
...
1 In Syndeia Dashboard, select Payload Mass from Simulink requirements Requirement_Sim set from the local folder for eg S1c here, and drag and drop this to the S1e package of SysML Rhapsody as shown below. Select Model Transform. Select Yes.
...
1 Continuing with the same Simulink Requirements Requirement_Sim set from the local folder for eg S1c here, we select multiple requirements, and drag and drop them to package S1F in SysML Rhapsody Model.
...