|
Activity |
Description |
Owner |
|
Assessment |
Determine migration
events along with cost justification. |
Joint Activity |
|
Gather |
Locate application source components
and load into the code control system (CVS). |
Joint Activity |
|
Data Access |
Create test version of application
data. This may not be an exact copy of the all data, but only
sufficient data to validate application. |
Joint Activity |
|
Debug |
Validate application execution and
apply necessary modifications (fixes) to application. |
Joint Activity |
|
Build Exception List |
Review exception list and confirm
additional work products which may or may not be within the scope
of the project. |
Joint Activity |
|
Online (OLTP) Migration |
Migrate and validate to confirm that
target environment functionality is consistent with source
environment. Validate and make note of any inconsistencies on
project exception list. |
Joint Activity |
|
Batch Process Migration |
Migrate and validate all batch
processes are consistent with functionality in source environment.
Specific issues to be validated are "job scheduling" and "print
spooling". Validate and make note of any inconsistency on the
exception list. |
Joint Activity |
|
Infrastructure Issue Resolution |
Data and Teleprocessing configuration
necessary for production volumes are confirmed. Since the migrated
application will run within a new J2EE environment, it is
important to verify that issue relation to migrating from a
proprietary system to a standards base system are addressed. This
step may be addressed with others who have been assigned this
responsibility. DBAs and Network Specialists will take the lead. A
major checkpoint during this step will be to confirm that Data is
accurately reflected in any new data store; it must be 100%
accurate. |
Joint Activity |
|
Exception List Resolution |
Jointly determine a 'action
activities' leading to an agreeable solution. Commonly weekly
conference calls are conducted to accretion progress on
development, testing and acceptance. |
Joint Activity. |
|
Production System Setup |
Test and Production system setup. The
migrated application system is loaded in configured for production
cutover. |
Customer |
|
System Testing |
Application test (Acceptance Test and
User Training and test). This is the final validation that
all systems have been migrated and that each item on the exception
list has been addressed. The conclusion of this phase is a
go or no-go decision. |
Customer |
|
Production Turnover |
This can be a parallel test phase for
a limited period of time and at some point must be made to turn
off the old system and move forward with the application. |
Customer |
