Solution Guide for Migrating Oracle on UNIX to SQL Server - Willy .Net

30Envisioning PhaseOptimal StrategyThe factors that need to be considered while deciding a migration strategy are:●●●●Business needs. The migration strategy should meet the present and futureneeds of the organization.For example, an organization may need to open its existing application to externalusers. Security needs to be implemented <strong>for</strong> the external users. The organizationmay select the rewrite strategy.Technical feasibility. <strong>Migrating</strong> <strong>Oracle</strong> Forms to the Windows plat<strong>for</strong>m may not betechnically feasible. If the new features warrant a lot of change to the currentapplication, the organization may opt to select rewriting as a strategy.Time. The time frame within which the migration has to be planned, developed,tested, and deployed needs to be decided. In addition, the actual time taken in themigration needs to be minimized to reduce the business risk.For example, an organization may plan to provide access to its application to theexternal users within three months. A quick port to the Windows Services <strong>for</strong> UNIXplat<strong>for</strong>m may be the best option.Budget. The budget available needs to be planned. According to the moneyavailable, the infrastructure, human resources, and cost need to be planned.For example, the direct cost of porting may be lower than the cost of a rewrite.Also, porting an application minimizes the cost of training, as the same applicationis used in the new environment. The indirect cost; such as cost of maintenance,testing, and retraining, will also be lower.Set Up a TeamTo trans<strong>for</strong>m overall business and design goals into a clear vision <strong>for</strong> the project, anorganization needs to assemble a multidisciplinary team, based on MSF roles, and withdefined skill sets appropriate to the project. These roles are Product Management,Program Management, Development, Test, User Experience, and Release Management.Once assembled, this team defines the vision and scope that together provide a cleardirection <strong>for</strong> the project and set expectations within the organization. During theEnvisioning Phase, it is likely that only the lead person or persons <strong>for</strong> each team role willbe determined. During the Planning Phase, the entire team should be assembled if it isnecessary <strong>for</strong> your organization to staff each role with more than one person. Morein<strong>for</strong>mation about the MSF Team Model is available in the UMPG.Table 2.6 lists each role with its goal and identifies its key functional areas and projectresponsibilities <strong>for</strong> an <strong>Oracle</strong> on UNIX to SQL Server on Windows migration project.Table 2.6: Project Requirements and Responsibilities by TaskRole Project responsibilities and tasks Knowledge and skillrequirementsProductManagementRole* Ensure that the team addressesbusiness goals and customerrequirements* Manage communications, launchplanning, and feedback with customers(both internal and external)Understanding of theorganization's businesspriorities and goalsProgram * Drive solution design * Project management skills