Implement Phase Defined

 <  Day Day Up  >  

The implement phase of a migration project is the active development of a new environment during which the following types of tasks occur:

  • Porting applications to the new operating system, which includes the following types of tasks:

    • Creating a target build environment

    • Building a new application for the target platform

    • Deciding whether to support backward compatibility

  • Migrating data to the new environment by transferring or converting it. This step includes the following types of tasks:

    • Transferring data

    • Transforming data

  • Creating the production environment, including the following types of tasks:

    • Building the production facilities environment

    • Building the production platform

    • Building the application infrastructure

  • Testing the migrated environment, which includes the following types of tasks:

    • Building the test environment

    • Creating the test plan

    • Performing unit testing

    • Performing regression testing

    • Performing integration testing

    • Testing performance

  • Refining the migrated solution

  • Training end users and staff

The key deliverables of the implement phase include working components and documentation. In addition, the implement phase might possess an iterative structure and might include prototyping. In particular, prototyping is useful for data migration and difficult or risky conversion techniques. If changes are made as a result of the prototyping that occurs during the implement phase, be sure to maintain the outputs from the architect phase.

Developing Projects Iteratively

The implement phase can be iterated to allow incremental development. This allows a number of drivers to influence staging. You might develop a migration solution incrementally because different management environments are being migrated in different stages, with training done before the quality assurance installation; or it could be that the solution's architecture permits a component-based delivery or that the phasing might be based on project or business resource constraints. You should include phasing in the project plan to allow more effort and testing to be undertaken for the riskier elements of the project. The trial of both conversion and transition process on a training, quality assurance, or user acceptance instance of the application enhances the likelihood of success on a production instance.

An additional architect phase should include a business case review and review of the outputs from the previous architect phase. Implementation should be designed to permit this activity to occur. In particular, data migration timings should be available to validate the transition planning, and the transition plan should be revised in the light of improved knowledge.

 <  Day Day Up  >  

Migrating to the Solaris Operating System
Migrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX Migrations
ISBN: 0131502638
EAN: 2147483647
Year: 2003
Pages: 70 © 2008-2017.
If you may any questions please contact us: