Objecteering Scope DOORS commands

Import operations

When importing a DOORS file or project, the name of the root container and that of the DOORS file to be imported have to be the same.
For instance, if you wish to import the "Car project requirement", the name of your root container will have to be "Car project requirement".

Running the "Import from DOORS" command

To run the DOORS "Import from DOORS" command, simply carry out the steps shown below.

The "Import from DOORS" command

Steps:

1. Right-click on the appropriate container of your model.

2. Select "Scope DOORS/Import from DOORS".

Import settings

A settings window will then appear.

The "Import from DOORS" settings window

Key:

1. In the "DOORS parent item" field, enter the project or folder you wish to import. In our example, the project name is "Car project requirement". Note that the root container's name which appears in the field below is identical.

2. In the "User name" field, indicate the DOORS user name. If you have already defined the MDAC's parameters, this field will be defined automatically. However, it is still possible to modify it.

3. In the "User password" (optional) field, you can type the user's password.

4. In the "DOORS database path or port@server (optional)" field, indicate the DOORS database from which you want to import elements.

Once you have set the parameters, you can launch the import by clicking on the "OK" button at the bottom of the window.

Result of the "Import from DOORS" command

A import results window will appear at the end of the import process. This window details the result of the import using a graphical code:

The icon indicates that the import of the container was successful.

The icon indicates that an element was added during the import.

The icon indicates a description update.

The import results window

Press the "OK" button to close the window. The import tree structure is visible in the Objecteering browser.

If nothing appears in the window, the import failed. This can be due to several problems:

· The Objecteering root container and the project or folder to import have different names. To solve this problem, simply right-click on the root container and select "Modify" from the context menu. Then, in the "Name field", type the correct name.

· The path to the DOORS executable is incorrect. Make sure you have the right path in the "DOORS executable file path" field of the MDAC parameter window.

· The user name is invalid. Make sure you entered a valid user name in the "User name" field of the MDAC parameter window.

· The DOORS database name is incorrect. Make sure you entered the proper name in the "DOORS database path or port@server (optional)" field of the MDAC parameter window.

· You may not have write rights on the DOORS directory. If this is the case, you will have to modify your user rights in DOORS.

Export operations - DOORS marking

To export your Scope models to DOORS, you have to mark the containers using dedicated tagged values, otherwise the export will fail. Only container elements have to be marked.

Associating a tagged value

Steps:

1. Select the container you want to mark.

2. In the Objecteering auxiliary window, click on the "Associate a tag value" icon.

The tagged values available to mark your container are:

· {DoorsObject}

· {DoorsModule}

· {DoorsFolder}

· {DoorsProject}

· {DoorsLink}

The window shown below then appears. Simply select one of the DOORS tagged values in the "Type" field dropdown list and then click on "Create".

Accessible elements

Container elements have to be tagged {DoorsModule}.
The other tagged values, available in the "Accessible elements" windows, are not used when exporting a project to DOORS.

Running the "Export to DOORS" command

The "Export to DOORS" command

Steps:

1. Right-click on the root container of your model.

2. Select "Scope DOORS/Export to DOORS". All the containers previously marked will be exported.

Export settings

The "Export to DOORS" window will then appear.

The "Export to DOORS" settings window

Key:

1. In the "DOORS parent item (full path)" field, indicate the full path to the element you want to export to DOORS.

2. In the "User name" field, indicate the DOORS user name. If you have already set the MDAC's parameters, this field will be automatically defined. However, it is still possible to modify it.

3. In the "User password" (optional) field, you can type the user's password.

4. In the "DOORS database path or port@server (optional)" field, indicate the DOORS database into which you want to export elements.

Once you have set the parameters, you can launch the export by clicking on the "OK" button at the bottom of the window.

Visualizing the result of the export

In Objecteering, a window will then appear to confirm the result of the export process. The result is detailed as a tree structure as shown below:

· Containers created as folders or projects

· Containers created as models

By default, requirements are created as objects in DOORS.

The export results window

Press the "OK" button to close the window.

If none of these elements appear in the window, the export failed. This can be due to several problems:

· The path to the DOORS folder or project into which you want to export your elements is incorrect. Make sure the export path you indicated in the MDAC parameters window corresponds to that of DOORS.

· The path to the DOORS executable is incorrect. Make sure you have the right path in the "DOORS executable file path" field of the MDAC parameter window.

· The user name is invalid. Make sure you entered a valid user name in the "User name" field of the MDAC parameter window.

· The DOORS database name is incorrect. Make sure you entered the proper name in the "DOORS database path or port@server (optional)" field of the MDAC parameter window.

· You may not have write rights on the DOORS directory. If this is the case, you will have to modify your user rights in DOORS.