6 Designing Conventional Data Warehouses
6 Designing Conventional Data Warehouses The development of a data warehouse is a complex and costly endeavor. A data warehouse project is similar in many aspects to any software develop- ment project and requires definition of the various activities that must be performed, which are related to requirements gathering, design, and imple- mentation into an operational platform, among other things. Even though there is an abundant literature in the area of software development (e.g., [48, 248, 282]), few publications have been devoted to the development of data warehouses. Some of these publications [15, 114, 119, 146, 242] have been written by practitioners and are based on their experience in building data warehouses. On the other hand, the scientific community has proposed a variety of approaches for developing data warehouses [28, 29, 35, 42, 47, 79, 82, 114, 167, 203, 221, 237, 246]. Nevertheless, many of these approaches target a specific conceptual model and are often too complex to be used in real-world environments. As a consequence, there is still a lack of a method- ological framework that could guide developers in the various stages of the data warehouse development process. This situation results from the fact that the need to build data warehouse systems arose before the definition of formal approaches to data warehouse development, as was the case for operational databases [166]. In this chapter, we propose a general method for conventional-data- warehouse design that unifies existing approaches. This method allows de- signers and developers to better understand the alternative approaches that can be used for data warehouse design, helping them to choose the one that best fits their needs.
[Show full text]