Modeling-Centered Data Warehousing Learning: Methods, Concepts and Resources

Modeling-Centered Data Warehousing Learning: Methods, Concepts and Resources

Nenad Jukic, Boris Jukic
Copyright: © 2012 |Pages: 22
DOI: 10.4018/jbir.2012100104
(Individual Articles)
No Current Special Offers


Though data warehousing is widely recognized in the industry as the principal decision support system architecture and an integral part of the corporate information system, the majority of academic institutions in the US and world-wide have been slow in developing curriculums that reflect this. The authors examine the issues that have contributed to the lag in the coverage of data warehousing topics at universities and introduce methods, concepts and resources that can enable business educators to deal with these issues and conduct comprehensive, detailed, and meaningful coverage of data warehouse related topics.
Article Preview

Background Overview-Data Warehousing

A typical organization maintains and utilizes a number of operational databases. These operational databases are used to support the organization’s day-to-day operations. A data warehouse is created within an organization as a separate database, (using its own DBMS), whose primary purpose is data analysis for the support of management's decision making processes (Inmon, 2005). The data stored in the data warehouse captures many different aspects of the business process, such as production, supply-chain management, marketing, sales and customer service. This data reflects strategically important information such as customer behavior patterns, sales trends, outcomes of marketing strategies, and other characteristics. Therefore, this data is of vital importance to the success of the business whose state it captures. That is the reason why companies choose to engage in the relatively expensive and lengthy undertaking of creating and maintaining the data warehouse, often containing multiple terabytes of data. For example, one study (Gray, 2006) reports a typical cost of $3 million for creating a 1-terabyte data warehouse, with a typical implementation time of 2 years.

Often the same data can have both operational and analytical purposes, and subsequently can be stored in both an operational database and the data warehouse. For example, data describing that product A was bought by customer B in store C can be stored in an operational data store for business-process support purposes, such as financial transaction record keeping or inventory monitoring. That same piece of information can also be stored in a data warehouse where, combined with vast amounts of similar data accumulated over a time period, it is used to analyze important trends, such as sales patterns or customer behavior.

Complete Article List

Search this Journal:
Volume 15: 1 Issue (2024)
Volume 14: 1 Issue (2023)
Volume 13: 1 Issue (2022)
Volume 12: 2 Issues (2021)
Volume 11: 2 Issues (2020)
Volume 10: 2 Issues (2019)
Volume 9: 2 Issues (2018)
Volume 8: 2 Issues (2017)
Volume 7: 2 Issues (2016)
Volume 6: 2 Issues (2015)
Volume 5: 4 Issues (2014)
Volume 4: 4 Issues (2013)
Volume 3: 4 Issues (2012)
Volume 2: 4 Issues (2011)
Volume 1: 4 Issues (2010)
View Complete Journal Contents Listing