Planning - Templates - Configuration

A data migration project is naturally divided into areas of business or products etc. Examples of business areas taken from our banking demo sample banking could be:

• Account
• Customer
• Internet Banking
• Portfolio
• Etc…

Each Area is divided into sub-areas that in turn are also subdivided. In fact, a data migration project is divided into a hierarchy of Areas. For instance. Looking at a subset of Account this hierarchy could look like so:

• Account
  1. Loan
     • Base data
       • Product
       • Currency
       • Account Number
       • IBAN Number
       • Owners and partial ownership
       • Etc…
     • Conditions
       • Credit Relief
       • Direct debit
       • Etc…
     • Interest
       • Etc…
  2. Etc…

The project manager can compose and maintain a Template containing the global hierarchy of areas relevant to any data migrations. This hierarchy can be as wide and as deep as necessary.

For each Area the project manager can provide:

• A Name to show for this area
• A Description to assist the understanding of what is covered by this area
• A Test Outline to describe how the tenant recommends the customer test this area   

The Planning Extension should provide language support for the Name, Description, and Test Outline.