In last month's DataCore Up Close article we discussed the importance of defining and recording requirements for an IT project, and why it's important to use an experienced team. In this month's article we'll take a look at the Design Phase, where we decide how the requirements will be met.

Let's return to the example we used last month regarding the building of a new home. We learned the importance of defining requirements which were unambiguous, complete, and measurable. We learned how an experienced builder can help solicit your input to ensure key requirements are gathered and documented. Instead of just telling a builder you wanted a 4 bedroom, 2 bathroom house, you define room dimensions, whether or not to include a fireplace, size of basement, and other key specifications.

The next step in the building process is to translate your requirements into a detailed design. Based on your requirements, calculations are made regarding the amount and type of lumber to purchase, size and depth of foundation to dig, location and type of support structures, gauge of wire to install, and length and type of pipes to support your plumbing needs. Your requirements are converted into a plan that will be used for construction – in other words, based on what is required the builder determines how it will be built.

In DataCore Technology's Project Delivery Methodology, we follow the same natural progression to building and implementing your IT solution. The Design Phase follows the Define Phase as the next step in the implementation of a successful project. The Design Phase is where we take the requirements that you identified during the Define Phase and convert them into a detailed, technical design.

Technical in focus, the Design Phase is where plans are made for how the system will be coded, configured, and tested. The primary objective of this phase is to provide the necessary details so that a systems analyst can effectively and efficiently code and/or configure your solution.

There are two major deliverables of this phase. The first is the System Design Specification. Typically an internal document, the System Design Specification is specific to the tools, technology, and components that make up your solution. It requires the author to have a thorough understanding of both your functional requirements and the technical environment that will be used. He or she must understand the databases, programming languages, architecture, and applications that will be integrated in building the right solution for you. A well-written System Design Specification will be clear, concise, and allow one, or more, systems analysts to develop and configure the system with minimum ambiguity or confusion.

The second major deliverable is the Data Migration Plan. A Data Migration Plan is commonly prepared when a large amount of legacy data will be moved from the current system(s) into the new system. The process of data migration can be a complex, time-consuming activity, and needs to be carefully planned to ensure success. The purpose of the Data Migration Plan is to ensure a smooth migration. This plan provides the specific details, including field mapping, file and folder naming conventions, migration methods, etc.

In addition to the preparation of the System Design Specification and the Data Migration Plan, a number of other documentation activities may occur. Some of the previously prepared documents, like the project plans and schedules, and the Functional Specification, may be updated to reflect changed requirements. In preparation of subsequent phases, system test plans and scripts, and an implementation plan may be started.

DataCore believes the benefit of properly defining and designing a solution before building is obvious. Just like in our home building example, by deciding first what and how to build, the result is more likely to meet your expectations, and be accurate, complete, on-time, and within budget. The Define Phase provides the necessary preparation for the next phase, the Build Phase, and minimizes the risk of building something that won't meet the users' needs.

To learn about the Build Phase, click here to continue.