Drag-n-drop operations for DOORS-NG Repositories

#	Drag This	To This	With This Connection Type	And This Will Happen
D1	Anything from the System Model Panel (or Repository Panel)	Anything in the Repository Panel (or System Model Panel)	Reference	Reference Connection will be created but nothing will be generated.
D2	SysML requirement	DOORS-NG repository or folder	Model Transform	If the SysML requirement has a DOORS-NG Requirement Collection stereotype applied, a requirement collection will be generated in DOORSNG with child requirements based on the nested requirements in SysML. If the SysML requirement has a DOORS-NG Module stereotype applied, the same function will be executed as above. DOORS-NG modules cannot be generated programmatically, and hence a DOORS-NG requirement collection will be generated. If the SysML requirement does not have any DOORS-NG related stereotypes applied, then a DOORS-NG requirement will be generated if the SysML requirement doesn’t have nested requirements, or a DOORSNG requirement collection will be generated if the SysML requirement has nested requirements. Model transform connections will be created between the SysML requirements and DOORS-NG requirements and collections.
D3	SysML requirement	DOORS-NG repository or folder	Data Map	Same behavior as D2 except that a requirement structure will not be generated. So, the DOORS-NG requirement collection (if generated) will not have any child requirements even if the source SysML requirement had nested requirements. A data map connection will be created between the SysML requirement and DOORS-NG requirement or requirement collection.
D4	DOORS-NG Module	SysML Package	Model Transform	SysML requirement structure (multi-level) will be generated based on the DOORS-NG module structure. Model transform connections will be created between SysML requirements and DOORS-NG module and requirements.
D5	DOORS-NG Module	SysML Package	Data Map	A SysML requirement will be generated based on the DOORS-NG module. Requirement structure will not be generated on the SysML side. Data map connection will be created between the SysML requirement and the DOORS-NG module.
D6	DOORS-NG Requirement Collection	SysML Package	Model Transform	SysML requirement will be generated based on the DOORS-NG requirement. Model transform connections will be created between SysML requirement and DOORS-NG requirement.
D7	DOORS-NG Requirement	SysML Package	Data Map	SysML requirement will be generated based on the DOORS-NG requirement. Data map connections will be created between SysML requirement and DOORS-NG requirement.

In DOORS-NG, requirement and requirement collection are the base resource types. Different types of artifacts are defined in a DOORS-NG project based on these basic resource types. For example, System Requirement, Hardware Requirement, and Software Requirement may be three artifact types which have the same base type as requirement. When generating requirements or collections in DOORS-NG from SysML (operations D2 and D3 in the table above), you can set the specific type of artifact that needs to be generated in DOORS-NG, e.g. generate a System Requirement versus a basic requirement in DOORS-NG. Follow the steps below to do this:

Go to Syndeia > Utils > DOORS-NG Utils menu by right clicking on any SysML element in the model tree. This will launch the DOORS-NG Utils window as shown below. Select your DOORS-NG repository, project, resource type, and press OK. Syndeia will query the DOORS-NG server and output all artifact types available for the given resource type in the specified DOORS-NG project.
For a given SysML requirement, apply the DOORS-NG module, requirement collection, or requirement stereotype, and set the value of the _artifact_type tag to one of the artifact type values obtained in the previous step, as shown below.