Chapter 6 - Part III: Process Although there have been...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Part III: Process Although there have been attempts to use traditional software development methodologies from the OLTP arena for data warehouse development, warehousing practitioners generally agree that an iterative development approach is more suited to warehouse development than are traditional waterfall aproaches. This section of the book presents an iterative warehousing approach for enterprises about to embark on a data warehousing initiative. The approach begins with the definition of a data warehouse strategy, then proceeds to define the way to set up warehouse management and support processes. The latter part of the approach focuses on the tasks required to plan and implement one rollout (i.e., one phase) of the warehouse. Repeat these tasks for each phase of the warehouse development.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Chapter 6. Warehousing Strategy Define the data warehouse strategy as part of the information technology strategy of the enterprise. The traditional Information Strategy Plan (ISP) addresses operational computing needs thoroughly but may not give sufficient attention to decisional information requirements. A data warehouse strategy remedies this by focusing on the decisional needs of the enterprise. We start this chapter by presenting the components of a Data Warehousing strategy. We follow with a discussion of the tasks required to define a strategy for your enterprise. Strategy Components At a minimum, the data warehouse strategy should include the following elements. Preliminary data warehouse rollout plan. Not all of the user requirements can be met in one data warehouse project—such a project would necessarily be large, and dangerously unmanageable. It is more realistic to prioritize the different user requirements and assign them to different warehouse rollouts. Doing so allows the enterprise to divide the warehouse development into phased, successive rollouts, where each rollout focuses on meeting an agreed set of requirements. The iterative nature of such an approach allows the warehousing team to extend the functionality of the warehouse in a manageable manner. The phased approach lowers the overall risk of the data warehouse project, while delivering increasing functionality to the users. Preliminary data warehouse architecture. Define the overall data warehouse architecture for the pilot and subsequent warehouse rollouts to ensure the scalability of the warehouse. Whenever possible, define the initial technical architecture of each rollout. By consciously thinking through the data warehouse architecture, warehouse planners can determine the various technology components (e.g., MDDB, RDBMS, tools) that are required for each rollout. Short-listed data warehouse environment and tools. There are a number of tools and warehousing environments from which to choose.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 9

Chapter 6 - Part III: Process Although there have been...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online