A Model of Data Warehousing ProcessMaturity

A Model of Data Warehousing ProcessMaturity

1. IS

   • A data warehouse is a subject-oriented, integrated, time-variant, and nonvolatile collection of data that supports managerial decision making. The data in a data warehouse are typically extracted and loaded from multiple online transaction processing (OLTP) systems and other data sources using an extract, transform, and load (ETL) process.

2. MOTIVATION FOR A DWP MATURITY MODEL

   • More specifically, it is a set of activities, methods, practices, and transformations that people use to develop, maintain, and operate data warehouse and its associated products. Many DWP tasks can be categorized as development tasks, which revolve around the design, development, and implementation of the data warehouse.
   • Development tasks in DWP include business requirements analysis, data design, architecture design, data mapping, ETL design, end-user application design, end-user cube design, implementation, and deployment.

3. EXTANT LITERATURE ON MATURITY MODELS

   • The concept of maturity implies progress from some initial state to a more advanced state. The notion of evolution is implicit in the stages of growth, suggesting that the progress transitions through a number of intermediate states on the way to higher maturity levels
   • Features
     • Maturity levels.
       • The idea of levels originated from Crosby’s work. The number of levels in a model typically ranges from three to six. Each level usually has a descriptor that serves as a name for the level.
     • Key process areas.
       • Each level in the maturity model indicates a level of process capability. A level is decomposed into a set of key process areas (KPAs) that an organization should focus on to improve its process.
     • Activities in key process areas.
       • The objective of each process area can be summarized by its key practices, also known as activities. Each activity must have goals and commitments. Key practices, according to Paulk et al. [50, p. 39], “describe ‘what’ is to be done, but they should not be interpreted as mandating ‘how’ the process should be implemented.

4. DESIGNING A DWP MATURITY MODEL

   • work in this area has been limited to a simple specification of the levels and mapping of some of the activities from CMM, without much serious theory-based development.
     • Design-Science Research
     • Initial Model
     • Knowledge Acquisition
     • Evolution of the DWP-M Model
     • Design Evaluation
       • Relationships among Process Areas
       • Validation of the Final DWP-M Model