Basic Rules/Expectations of a Migration

The migration tooling is targeted to address specific needs of users looking to leverage DOORS Next to its full intention. To this regard, it attempts to populate requirements in DOORS Next as if an end user had created it. The migration toolkit values the following:

• No need to modify the source or target while doing the migration
  • Remapping to DOORS Next is done as part of the migration effort
  • Refactor OLEs to the target formats that we expect in DOORS Next
• Minimize the overhead of migrations
  • Migrations are direct from DOORS to DOORS Next without Migration Packages/ReqIF
• Migrations have natural units for migration and review
  • Migrations occur as a collection of modules (to varied projects and components)
  • Migrations create changesets for each Module for review
  • (Outbound) Linking comes from the unit of a component
• Migrations occur over time so support incremental migrations
  • Migrations can occur as units from DOORS
  • Links can be recreated to artifacts later migrated
• Leverage of DOORS Next Configurations
  • Links can cross component boundaries with no extra effort
  • Migrations always into Changeset to allow review without impact
• The Migration Tooling is considered a tool for the Organization
  • Flexibility in application
  • Intended for Enterprise migrations

In all cases the migrations are incremental (collections of DOORS modules). When effectively planned, a team can do a series of incremental migrations that enable teams to be active in DOORS Next quickly.

The following guide supports everything you need for your first migration experience. Further guides provide advanced features that may be leveraged in your enterprise migration.