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

48Planning PhaseExamining the conceptual design of the client application will provide an understanding ofhow it operates and is structured. This in<strong>for</strong>mation is used to create the physical designof the solution. Two additional design studies that may assist in creating the physicaldesign are discussed in the following section.High Level User Interface and Database DesignUsing the objects, services, attributes, and relationships identified in the logical design ofthe system, the team might decide to create a high-level user interface and databasedesign.The list of objects and services gives the team an idea about the kind of functionalityexpected by the users. The team can use this in<strong>for</strong>mation to design user interfaceelements such as buttons, text fields, and menu items.Similarly, the object and attribute in<strong>for</strong>mation of the logical design can be used to developan initial database design equivalent to the <strong>Oracle</strong> database being migrated.Build the Physical DesignPhysical design is the process of describing the components, services, and technologiesof the solution from the perspective of the development team. The goal of the design is toprovide clarity and detail <strong>for</strong> each of the development teams to develop their components,be it the user interface, business logic, database, or infrastructure.The physical design should include:● Class definition of applications.● Database schema <strong>for</strong> the solution.● Baseline deployment model that provides:● The network topology, showing hardware locations and interconnections.● The data and component technology, which indicates the locations of thesolution components, services, and data storage in relation to the networktopology.●●Component specifications that include internal structure of components andcomponent interfaces.Programming models that identify implementation guidelines <strong>for</strong> threading, errorhandling, security, and code documentation.A detailed discussion of physical design is out of scope of this solution. For detailedguidance on designing the data layer, designing the presentation layer, and designing thesecurity specifications, refer to chapters 7 through 9 of Analyzing Requirements andDefining Microsoft .NET <strong>Solution</strong> Architectures (Microsoft Press 2003).The physical design diagram allows you to see how all the components connect together.For completeness, it may include infrastructure elements outside of the scope of theproject such as firewalls or network connections that are not directly related to thesolution. It will help prove the security of the system, and may show potential throughputbottlenecks, or highlight single points of failure.