Building The Vision of a Data Warehouse

Building the vision is the stage where the first production deliverable is produced. This is typically the smallest component of the data warehouse. that adds business benefit. For example, this stage will probably build the major infrastructure components for extracting and loading data, but limit them to the extraction and load of one or two data sources, with minimal history. To a very large extent, the purpose of minimizing the scope of this phase is to reduce project risk, and to timebox the deliverable into a 4-6-month exercise. We recommend that the deliverable satisfies your most pressing business requirement for data analysis. If the time-scales for this activity are significantly.

The remaining phases within a data warehouse delivery can occur in any sequence; that is, they are driven by the specific business drivers. As we have discussed, the purpose of breaking the delivery up into phases is to reduce project and delivery risk. This is achieved by reducing the scope of each phase so that it lasts 3 to 4 months elapsed. If the projected phase is much bigger than this, it indicates that the scope is probably too large. In most cases, the next phase is one where the remainder of the required history is loaded into the data warehouse. This means that new entities would not be added to the data warehouse, but additional physical tables would probably be created to store the increased data volumes. For example, let us consider a case where the building the vision phase has delivered a retail sales analysis data warehouse with 3 months’ worth of history. This information is probably ample to allow the business user to analyze recent trends and address short-term sales issues. It does not provide sufficient data to identify annual or seasonal sales trends.

No Comments