Skip to main content

M3 Framework Introduction M3 Framework Overview M3 Phase 0 - Assessment M3 Phase 1 - Readiness M3 Phase 2 - Selection M3 Phase 3 - Engagement M3 Phase 4 - Migration M3 Phase 5 - Operations M3 Resources
M3 Playbook > Phase 4: Migration
4.17 Test Systems and Processes
4.16 Conduct Mock Conversions
4.18 Develop and Execute Cutover Plan for Go-Live
Image Map Phase 0: Assessment Phase 1: Readiness Phase 2: Selection Phase 3: Engagement Phase 4: Migration Phase 5: Operations
Objective: Test systems and processes and trace test cases and results in RTM.

Phase 4 GuidanceLegend - Customer, Provider, Shared
Activities
1. Develop Test Plans and Scripts (Integration, System, Regression, Performance/Stress, User Acceptance, 508, Smoke) (S)
2. Plan and develop test data (S)
3. Execute tests for each test cycle (S)
4. Record, correct, and report defects (S)
5. Perform regression test (S)
6. Develop Test Results Report for each test cycle and confirm exit criteria have been met (S)

Inputs
• Requirements Traceability Matrix (RTM)
• Target State Concept of Operations
• Technical Strategy

Outputs
• Test Plan
• Test Scripts
• Test Results Report
• Test Defect Log
• RTM
Stakeholders
• Program Manager (C, P)
• Technical Lead/Solution Architect (C, P)
• Development Team (C, P)
• Functional Lead (C, P)
• Test Lead (C, P)
• Test Team (C, P)

Best Practice
• Sequence System Integration Testing (SIT) and User Acceptance Testing (UAT) testing with mock conversions to be able to test with quality data to validate both system functionality and reports/data
• Implement a consolidated defect tracking tool for use by both provider and customer during test planning; agree upon implementation tools (like requirements management and defect tracking tools) in the Migration Interagency Agreement (IAA)
• Leverage the RTM to map and trace requirement, test cases, and test scripts
• Involve testing team members in requirements sessions to understand requirements better