This guide is describing a roundtrip import-export procedure from DOORS^© Classic > ReqEdit > DOORS^©Classic then to use Merge package

Configuration of DOORS© Classic

Before you begin you must have the power to partition data, and modify access to the project.

1. In the database explorer, select the project where you want to create a definition, and then click File> Properties.
2. Click the ReqIF Definitions tab, and then click New.
3. Type a name and optionally a description for the definition, and click OK.
4. In the file explorer, select the first module to add to the definition. The Add ReqIF Definition window opens.
5. In the Options pane, select the version of the module to include from the Module Version list.
6. Select the data to lock locally when the definition is exported. The user in the remote database can edit that data, and can send their updates back to you.

To be able to use the DOORS^© Classic ReqIF Definition Merge functionality the data in the DOORS^© Classic local database must be locked at export time.

Lock all data

• All the data in the module in the local database is locked.
• Users in the remote database can edit all the data in the module. Any updates in the remote database can be imported and merged with the local module.

Lock objects

• The selected objects in the module in the local database are locked.
• Users in the remote database can modify the specified objects and add new objects.
• Updates to the specified objects in the remote database can be imported and merged with the local module.
• Updates to any other objects are not merged with the local module.

Lock attributes

• The selected attributes in the module in the local database are locked.
• Users in the remote database can modify the specified attributes.
• Updates to the specified attributes in the remote database can be imported and merged with the local module.
• Updates to any other attributes are not merged with the local module.
• If you soft-delete or purge objects in the remote database, the deletions and purges are ignored when you merge with the local module.

No locks

None of the data in the module in the local database is locked.
Users in the remote database can edit all the data in the module. However, any updates to the data in the remote database cannot be merged with the local module.

DOORS© Classic – export

1. Click Add or Update Module to add the module to the ReqIF definition. Continue adding modules until your definition is complete.
2. Click OK.
3. In the ReqIF Definitions tab, select the definition, and click Export.
4. Enter a package file name and location and click OK.

Open in ReqEdit

Before the file can be used in ReqEdit client, it has to be imported.

Simply just open the file, the application checks it and immediately prompts the user if he wants to start the importer.

Or by selecting File > Import… and selecting the IBM Rational DOORS^© importer and following the wizard steps,

After import all the data present in the ReqIF file can be edited and imported back to DOORS^© Classic, but based on what type of lock was selected in the ReqIF Definition in DOORS^© Classic, only that data can be merged with the original module.

Edit and modify the document.

After all modifications are done the file must be exported by selecting File > Export and selecting the IBM Rational DOORS^© exporter then follow the wizard steps.

Import back to DOORS© Classic

1. In the database explorer, select the project or folder where you want to import the package, and then click File > Import ReqIF Package. The Import ReqIF Package File window is displayed.
2. Browse to the package that you want to import.
3. Click OK. The Import ReqIF Package window is displayed.
4. In the Import ReqIF Package window, complete the required fields. The fields that are available depend on whether IBM Rational DOORS^© recognizes the package as being associated with a definition that exists in the project.
   • In the case of a DOORS^© Classic -> ReqEdit -> DOORS^© Classic roundtrip, the package will be recognized, and only a new folder name for the import must be set.
5. Click Import.

The modules that are contained in the file are created in your database, ready to be merged with your local data.

DOORS© Classic – Merge

• When you merge a package, the following updates are made to local modules:
• New objects are added to the local module.
• New attribute definitions are added to local module.
• All attribute value differences are copied to the local module.
• Deleted objects are soft-deleted in the local module.
• Purged objects are not updated in the local module. If an object no longer exists in an imported module, it is ignored during the merge and the original object is unchanged in the local module.
• New view definitions are added to the local module.
• A view that already exists in the local module is not updated if it has been changed in the imported module.
• New links are created in the local module.
• The history information for the local module history is updated with every change. The user who performed the merge and the time the merge is made are recorded. History information is generated only for attributes that are set up to update history.

Merging procedure

1. In the database explorer, select the project containing the package you want to merge, click File> Properties, and then click the ReqIF Definitions tab.
2. Select the definition that is associated with the imported package that you want to merge, and click Imports. The ReqIF Definition Imports window opens.
3. Select the imported package that you want to merge, and click Merge.