Migrating Mapped Assets

The migration of mapped assets will migrate each module to DOORS Next Generation based on the mapping. Each module will be migrated in its own changeset enabling individual acceptance and rejection of a migrated module.

To perform a migration, launch the Perform Migration service.

Provide ELM Connection Information.

Provide DOORS Connection Information.

On Migration Configuration page, provide the DOORS Configuration Mapping (the scope configuration).

On Mapping Configuration page, provide the Mapping File (the DOORS Next mapped configuration).

On Output Directory page, provide an Output directory for summaries and migration status files.

On Working Directory page, provide a working directory where temporary files (OLE Extracts) will be created.

The External References Directory can be left blank. It is used to reference previous migrations. (More details can be found in the advanced segment of the user guide)

Click Finish to initiate the migration.

The console log will be giving verbose information that is contained in a log text file. Additionally the pop-up window will give some guidance to current progress.

Once the migration concludes, a tree view that presents the overall results.

Warning flags identify migration events that may need review. For example this warning is related to the inability to find a requirement shape (type) for the DOORS Attribute value, so it uses the default DOORS Next type.

Note this warning would also have been found in the PreChecks.

In the output directory you will find three files:

The Summary Excel File has an overview of the migration:

The Map Excel File has a cross reference index for the IDs of the generated DOORS Next Artifacts to DOORS ids that can be used for other tooling.

The XMI file is the most important artifact. It contains all of the details of the migration and provides references to what was created in DOORS Next to support the migration. It will be used in the next steps of the migration so make sure you retain this file.

This file contains a rich set of data about migrated requirements, links that need to be created and the changesets that were created for the migration. It is used for the next steps as well as can be leveraged for reporting needs.