Evaluating Migration Objectives


The output from data gathering should be an inventory of all elements affected by the migration, together with their interdependencies and any issues that you have uncovered. In the light of these issues, you should revisit the objectives of the migration to determine their viability and testability.

Business Objectives

You must determine how the application will meet business needs. Business needs vary, but can include the following examples:

  • The appearance and functionality of the application s UNIX user interface must be retained after the migration.

  • A UNIX-style development environment must be retained after the migration.

  • The application must run on multiple platforms, so coexistence requirements must be examined.

  • Common code must be used across multiple platforms.

  • The application s development is static.

  • The application will be replaced , so minimal changes are required.

  • The development environment will be migrated to Visual Studio.

Technical Objectives

You must establish criteria to ensure that the migration is successful. Consider the following when determining your criteria:

  • Can the integration of Windows-based applications be accomplished through Interix?

  • Is there significant dependence on UNIX APIs?

  • Is there good Interix support for required APIs?

  • Is there reliance on third-party libraries?

  • Are the third-party libraries available with Interix?

  • Are the third-party libraries available with Win32?

  • Does the application conform to ANSI C/C++?

Migration Objectives

You must establish criteria to judge that the resulting application delivers value. These criteria can include the following:

  • What is the ultimate intended use of the software? For example, is one of the objectives to improve usability and worker productivity by integrating the application with other Windows-based personal and workgroup productivity applications, such as Microsoft Word or Microsoft Excel?

  • Will the application behave as a native application in each unique target environment, particularly with regard to software installation, administration, distribution, and user interface?

  • Is the migration time critical?

  • Is the required user interface based on the Windows GUI?




UNIX Application Migration Guide
Unix Application Migration Guide (Patterns & Practices)
ISBN: 0735618380
EAN: 2147483647
Year: 2003
Pages: 134

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net