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

<strong>Solution</strong> <strong>Guide</strong> <strong>for</strong> <strong>Migrating</strong> <strong>Oracle</strong> on UNIX to SQL Server on Windows 393Planning PhaseIntroduction and GoalsIn the Planning Phase, the team defines the solution in detail — what to build, how tobuild it, who will build it, and when it will be built. During this phase, the initial vision andsolution concept defined in the Envisioning Phase is translated into practicalimplementation designs and plans <strong>for</strong> how to achieve it. Team members draw upon theirexpertise to create individual plans and designs in all areas of the project, ranging fromsecurity to budget to deployment. Likewise, individual team schedules and associateddependencies are identified. These plans and schedules are rolled into a master projectplan by the Program Management Role.The phase concludes when the project team agrees that the plans are sufficiently welldefinedto proceed with development, and the team, business sponsor, and keystakeholders approve the functional specification and the master project plan andschedule, usually at a milestone meeting. The <strong>for</strong>mal conclusion is marked by the secondmajor project milestone, Project Plans Approved.The key deliverables <strong>for</strong> the project team <strong>for</strong> the Planning Phase are:● Functional specification. The functional specification is the virtual repository ofproject and design related artifacts that are created in the Planning Phase. Theartifacts are primarily a result of design activities during the conceptual design,logical design, and physical design processes of the Planning Phase. The artifactscan include models such as case diagrams, usage scenarios, feature list, userinterface screen shots, database design, and so on.The key goals of the functional specification are to consolidate a commonunderstanding of the business, design, and user requirements; break down theproblem and modularize the solution logically; provide a framework to plan,schedule, and build the solution; and to serve as a contract between the team andthe customer and stakeholders.● Master project plan. The master project plan is a collection of individual plans thataddress tasks per<strong>for</strong>med by each of the six team roles to achieve the functionalitydefined in the functional specification. The master project plan documents thestrategies the team roles will use to complete their work. The solution concept thatthe team developed in the Envisioning Phase provides high-level approaches thatare developed into detailed plans in the Planning Phase. See Chapter 2,"Envisioning Phase," <strong>for</strong> the discussion of team roles.● Master project schedule. The individual team schedules apply a time frame to themaster plan. The master project schedule synchronizes project schedules across