Business Information Requirements
What data should you keep in a Data Warehouse and why? This form helps you identify the needed data and its associated characteristics in relation to your business requirements.
What data should you keep in a Data Warehouse and why? This form helps you identify the needed data and its associated characteristics in relation to your business requirements.
Here's a template, with attached examples, for testing your Data Warehouse canned queries (analytical reports).
What is the best way to get data from the legacy system(s) into the new system? Design your conversion routines to organize the process.
Map the transformation of the data elements from source system tables to data warehouse target tables.
This example will help you put in place logical as well as physical database design standards for building data warehouses using Business Objects.
An evaluation of relational database systems determines the most suitable engine for a data warehouse. This report is an example of a comparative analysis of data warehouse database tools.
How do you select the best data extraction/transformation toolset for your data warehouse? Evaluate features, functionality, vendor reputation... the works. Follow the example set by this robust tool evaluation.
A handy spreadsheet for recording Data Warehouse QA issues, from data transformation to report generation problems.
What's the password? Do the right and only the right people know how to get into the system? Document the procedures and access priveleges and restrictions for keeping your application package system secure.
Need help selecting a Data Warehouse toolset? You must consider many factors regarding vendor service and reputation, tool functionality and tool quality against your technical and business requirements when selecting Data Warehouse construction and implementation tools. Let this matrix guide your selection.
"The reason why worry kills more people than hard work is that more people worry than work." - Robert Frost |