For performing a migration, we are focused on the identification of which DOORS Modules to migrate and to which DOORS Next Components and Modules they should target creation.
To simplify migrations, we collect only a small amount of information in a simple Excel document to identify a migration unit. A migration unit has a name (user defined), a DOORS Project Path (using DOORS preceding ‘/’), and a Folder Path(s).
The folder path will be interrogated to include all sub-folders. The folder path can be a comma separated list if multiple sections of a tree should be included.
From this DOORS Configuration:
We can envision the following configuration.
This Configuration is used as an input to our migration tool to extract information out of DOORS on our migration.
Launch the migration tool and execute the Create Configuration for DOORS service.
Provide your DOORS Client and Server information
On next page, select your Configuration File.
On next page, select a target Output File (different than your input)
Click finish and the Utility will interrogate DOORS for the necessary information from the DOORS project and folders.
The extraction utility identifies the DOORS Modules in tabs associated to the Migration Unit. In addition, it creates a ModuleList tab associated with the DOORS Next Modules it expects to create.
In the ModuleList table you can adjust the Component Name and Project Name to control where the DOORS Next Module will be created. By default, it takes the DOORS Folder Name for the Component Name and the DOORS Project Name for the DOORS Next Project Name. Note you must make sure these project and components exist prior to initiating a migration.
If there are modules in the list that you do not want created simply delete the row.
In the ComponentList table you can adjust the stream your module changesets will be targeting. If there is no specification it will search for the default "Initial Stream" of the component.