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

...