The 30-day checklist

Checklist#	Checklist Item
1.	Identify resources (functional and technical) to assist with the Unit Test phase of the migration process. These resources will provide application walkthrough’s and clarifications for the Core testing team.
2.	Identify resources with the required skill set to form the RMA team to support any development and integration activities.
3.	Identify resource(s) with the required skill set to form the RMA team to support any deployment activities related to the new application. This resource will be the interface between Core and the RMA IM/IT organization.
4.	Provide the frozen source code for all components of the release baseline to be used for the application migration.
5.	Identify a preferred order of migration. This will be factored into the project plan and will dictate the order in which RMA Billing system is migrated.
6.	(Optional) Provide a data mapping spreadsheet that identifies any proposed changes required to the legacy data structures in the new environment. This spreadsheet to include legacy data set names, legacy column names, target table names, target columns names, etc.
7.	Provide test data to be used at both the RMA site and the Core Software site; 2 sets, one small for functional testing, one large for conversion testing, performance testing and refresh mechanisms for all environments.
8.	Provide a complete set of sample output including reports and screen recordings (i.e., Blueberry or Camtasia recordings) /screen shots from the existing modules for comparison during unit test. Complete with all input parameters used to create the output as well as a spreadsheet outlining the test cases provided. Note: Drop 1 and 2 are required upon completion of 30 day checklist. Future drops must be delivered prior to the commencement of the next drop. Note2: All test cases should be performed against test data provided in step 6 above.
9.	Provide the Core Software engineers VPN access to the RMA DG QA application instance for the duration of the project. On a 7/24 availability basis.
10.	Provide the Core Software engineers with VPN access to the RMA target acceptance environment for the duration of the project. On a 7/24 availability basis.
11.	Define the target acceptance/production environment for the migrated system Note: Can be identified after 60 day acceptance period.
12.	Aggregate the production data to be migrated to the new database. Core assumes a single data source will be used. Not applicable for RMA.
13.	Define the target acceptance/production environment for the migrated system. 32 Bit or 64 Bit? 64 Bit will be the target acceptance/production environment.
14.	Identify acceptance sign-off authority, and define any special processes in place at RMA governing the acceptance of custom software. Charlotte Duchesne will be the acceptance sign-off authority for all deliverables and final project sign-off.