Delivery process of a Data Warehouse

The most important aspect of the delivery process is that the requirements are never static. Business requirements will constantly change during the life of the data warehouse, so it is imperative that the process supports this, and allows these changes to be reflected within the system. This issue can appear to be a very complex one, but in practice, it is addressed by designing the data warehouse around the use of data within business processes, as opposed to the data requirements of existing queries. The architecture is designed to change and grow to match changing business needs. However, it is critical that the changing requirements are captured and managed through an ongoing requirements capture activity.

642-812 and 70-431 are advanced courses where as 640-822 and 640-863 is required to clear the primary certifications like 70-640 and 70-236.

In effect, the process operates as a pseudo joint application development process, where new user requirements are continually fed into the development activities. Partial deliverables are produced, fed back to users, and then reworked, ensuring that the overall system is continually updated to meet the business needs. More often than not, this involves the loading of additional data sources into the data warehouse, although it can just be the introduction of new data marts using the existing information. In either case, the effort and complexity can be substantial, and the phase should be performed as a separate phase.

No Comments