Overview of a Migration

We consider migrations as modular entities. This is to support how users transition from DOORS to DOORS Next. We propose that the toolkit be leveraged in an incremental fashion for ease of execution and supporting the timeline in which uses can migrate. In this sense it is expected that there will only incremental units used.

In this manner there are the local increments of a migration which can be classified as:

  1. Scoping – Identify DOORS Artifacts to migrate to which DOORS Next Artifacts
  2. Mapping – Identify the Mapping of DOORS Classic data to DOORS Next Schema
  3. Migrate Assets – Execute a migration with the Scope and Mapping as inputs
  4. Review Migration Changesets – Users can evaluate changesets to identify the correct migration of assets (or discard and repeat the migration)
  5. Commit Changes – Deliver manually or automated the changesets
  6. Link Assets – Create the links identified during the migration.

These are logical steps and can be executed rather quickly. For your first migration you should be able to do a simple configuration and execution in less than an hour. After your first experience the efforts will be on creating strong mapping configurations that put data in DOORS Next exactly the way your team needs it.