Description of service
According to Software Productivity Consortium, "In the IT world, migration is the movement of an application system to a new environment motivated by a need to serve the business of the enterprise more effectively. Migration helps protect the current investment in data and functionality critical to the business and establishes a path for growth. Migration establishes a basis for effectively harnessing modern IT to satisfy current and future needs. This allows for the enterprise to better position itself within a constantly changing business and technological environment. An enterprise can accomplish the migration in one or more steps. The size and number of steps depend on the amount of change the enterprise's systems must undergo and the need to rest and recover along the way." Porting a large scale software application demands strong automation to meet economic and timeframe objectives.
As a sample of migration the IBA-Gomel presents CA-Easytrieve to COBOL migration service based on homegrown mass-conversion tool
Typical migration project assumptions
- Customer provides just source codes but not the access to target platform
- Customer provides code style guide and/or Cobol framework
- Customer provides sequence and terms of source modules to be converted (migrated)
- IBA-Gomel converts Easytrieve modules and delivers source Cobol modules to Customer
- Customer performs the final tests and user-acceptance tests
- Customer updates JCL according to replacement of CA-Easytrieve modules to Cobol programs
- Cobol Report Writer is not in use
Typical migration project schedule
| When | W1 | W2 | W3 | W4 | M2 | M... | |||
| What/task | What/deliverables | Who | |||||||
| Preliminary estimation of the Project |
1. Decision/contract 2. Project manager (PM), team leader assignment 3. Project plan&schedule |
1. Customer's contact person 2. Contractor's contact person 3. Contractor's PM 4. Contractor's teamlead |
|||||||
| Tuning of mass-conversion tool (MCT) according to Customer's coding style guide and/or options of CA-Easytrieve (CA-ET) and COBOL | 1. initial test conversions | 1. Contractor's developers | |||||||
| Mass conversion | 1. Target COBOL modules | 1. Contractor's developers | |||||||
| Procedure of Customer/Contractor interaction (see below) | 1. Target COBOL modules accepted by Customer |
1. Contractor's developers 2. Customer's technicians |
|||||||
| Project closing |
1. Customer's contact person 2. Contractor's contact person 3. Contractor's PM 4. Contractor's teamlead |
Typical procedure of customer-contractor interaction on the migration project
| Customer | Time step(+delay, hours) | Contractor |
| Initial stage | ||
| Sends source codes of CA-Easytrieve (CA-ET) modules | ||
| Receives source codes of CA-Easytrieve modules | ||
| Translates CA-Easytrieve modules to COBOL modules | ||
| for each module | ||
| START | Sends COBOL source codes, corresponding to CA-Easytrieve modules | |
| Receives COBOL source codes | START+1 | |
| Compiles COBOL source codes with own environment | ||
| Case 1: Compilation errors | ||
| Sends compiler's listings to contractor for validation of compiler's options | START+(1..3) | |
| Receives compiler's listing, updates COBOL source codes, sends codes to customer, returns to START | ||
| Case 2: No compilation errors, test(s) disagree to sample (CA-Easytrieve)output | ||
| Runs tests, compares tests (COBOL) output to sample (CA-Easytrieve output) Sends results of test runs (outputs of COBOL-II and outputs of corresponding CA-ET modules) to contractor | START+(1..3) | |
| Receives results of tests runs, updates COBOL modules, sends codes to customer, returns to START | ||
| Case 3: No compilation errors, test(s) agree to sample (CA-Easytrieve) output | ||
| Accepts COBOL module, sends to contractor a list of accepted CA-ET and COBOL modules | START+(1..3) | |
| Stops processing of corresponding CA-ET module | ||
Links: