Formal Testing using approved system test scripts (after completion of iterative dry runs) of the solution to ensure the migration objectives are achieved. All System Test evidences will be recorded during this phase
This is a SQL minus query-based validation approach which covers 100% in-scope cases and fields as per data migration business rules.
To validate the accuracy of the migration, comparison of E2B/Paper reports will be carried out, or custom comparison reports will be created, to provide details about match status of migrated fields.
To validate the number of records being migrated from source to target.
At each development and dry run iteration, dedicated manual reviews by business and functional SMEs to ensure the migrated data is satisfying regulatory compliance requirements based on customer business practices
SME reviews to be conducted after
Testing of the migrated data and solution by business users to ensure business/ compliance requirements are satisfied
Classification of representative cases will be finalized. A sample for each class will be created using random sampling method. Customer business team will decide the sample size for each class.
New/FU case processing:
New case processing and follow up case processing on migrated case will be performed to uncover any impact of migration on case processing or report scheduling.
Any additional acceptance test scenarios to be determined in discussion with the business
All defects identified during the project will be logged in a defect log.
The defect log will be actively monitored by the Project Manager and track leads to ensure all logged defects are analyzed and tracked to closure.
A weekly review of open defects will be conducted by stakeholders.