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

54Planning PhaseOverall Delivery StrategyThis describes the overall approach to delivering the solution. Examples of deliverystrategy include staged delivery, depth-first, breadth-first, and features-then-per<strong>for</strong>mance.In migrations, the solution already exists and the delivery strategy consists of deployingthe replacement solution.Tradeoff ApproachThis defines the approach <strong>for</strong> making design and implementation tradeoff decisions. Forexample, you might agree to trade features <strong>for</strong> schedule improvements, or to tradefeatures <strong>for</strong> per<strong>for</strong>mance.Key Design GoalsThese identify the key design goals and the priority of each goal. Examples of designgoals in a migration include interoperability between a UNIX application and theSQL Server database or rewriting the application using the .NET framework.Development and Build EnvironmentThis describes the development and build environment and how it will be managed.Include in<strong>for</strong>mation on items such as source code control tools, design tool requirements,operating systems, or other software installed. If a development environment <strong>for</strong> theexisting application does not exist, it will need to be created. This situation is commonwhen the development of the applications to be migrated was originally outsourced.Development ToolsThese tools are used to assist in the development and test environments. For a detaileddiscussion of tools, see the "Set Up the Development and Test Environment" sectionlater in this chapter.<strong>Guide</strong>lines and StandardsThese list and provide references to all standards and guidelines to be used <strong>for</strong> theproject. Standards and best practices could differ substantially from the current<strong>Oracle</strong>/UNIX environment. However, applying new standards will require a tremendousrewrite, which could greatly affect the migration timeline. It is recommended that suchstandards be applied only to the components that are being rewritten or modified.Versioning and Source ControlThis describes how versioning and source control will be managed. This section includesidentification of the specific tools that will be used and how developers are expected touse them. Most source control tools work with code irrespective of plat<strong>for</strong>m. Due to thechange in operating systems, new software may need to be acquired. For instance, ifCVS or any other source control software is currently used in the UNIX environment,consideration should be given to migrating these functions to a Windows-basedalternative, such as Visual Source Safe.Build ProcessThis describes the incremental and iterative approach <strong>for</strong> developing code and <strong>for</strong> buildsof hardware and software components. It also describes how the build process will beimplemented and how often it will be implemented.