< Day Day Up > |
A migration is defined as the transition of an environment's people, processes, or technologies from one implementation to another. In the preceding historical examples, migration occurred when researchers wanted to use the new BINAC computer but needed their programs and data from the older systems. The term adoption is used to refer to instances for which you add or change an implementation without changing the interface. On the other hand, an upgrade implies changes in the underlying technologies or interfaces, which require substantial application changes. These terms are most commonly used to address hardware and software issues. For example, moving from one version of the Solaris Operating System (Solaris OS) to another, such as from the version 7 of the Solaris OS to version 9, is a common use of the term adoption. In this case, developers add features to a component of the environment without changing the core technology or process employed. The phrase "without changing the core technology or process" differentiates an upgrade from a migration. Additional examples of adoptions are provided in Chapter 3, "Migration Strategies." Whether you are attempting a migration, adoption, or upgrade, the goal of your project is to replace or enhance the functionality and service levels of your current solution while moving to a new environment. |
< Day Day Up > |