The Kimball Lifecycle

From Wikipedia, the free encyclopedia
Jump to: navigation, search

The Kimball Lifecycle is a methodology for developing data warehouses, and has been developed over many years by Ralph Kimball and a variety of colleagues.

Program/Project planning[edit]

According to Kimball et al., this phase is the start of the Lifecycle. It is a planning-phase in which project is a single iteration of the Lifecycle while program is the broader coordination of resources. When launching a project/program Kimball et al. suggests following three focus areas:

  • Define and Scope project
  • Plan project
  • Manage project

Program/Project Management[edit]

This is an ongoing discipline in the project. The purpose is to keep the project/program on course, develop a communication plan and manage expectations.

Business Requirements Definition[edit]

This phase/milestone of the project is about making the project team understand the business requirements. Its purpose is to establish a foundation for all the following activities in the Lifecycle. Kimball et al. makes it very clear that it is extremely important for the project team to talk with the business users. It is important to be prepared, to focus on listening and to document the interview with the business users.

Technology Track[edit]

This is the top track in the diagram. It holds two milestones:

Technical Architecture Design is supposed to create a framework for the DW/BI system. The main focus in this phase is to create a plan for the application architecture, while considering business requirements, technical environment and the planned strategic technical directions.

Product Selection & Installation use the architecture plan to identify what components are needed to complete the DW/BI project. This phase then selects, installs and tests the products.

Data Track[edit]

Dimensional Modeling is a process in which the business requirements are used to design dimensional models for the system.

Physical Design is the phase where the database is designed. It involves the database environment as well as security.

ETL Design & Development is the design of some of the heavy procedures in the DW/BI-system. Kimball et al. suggests four parts to this process, which are further divided into 34 subsystems (Kimball et al., 2008):

  • Extracting data
  • Cleaning and conforming data
  • Delivering data for Presentation
  • Managing the ETL system

Business Intelligence Application Track[edit]

BI Application Design deals with designing and selecting some applications to support the business requirements. BI Application Development use the design to develop and validate applications to support the business requirements.

Deployment[edit]

When the three tracks are complete they all end up in the final deployment. This phase requires planning and should include pre-deployment testing, documentation, training and maintenance and support.

Maintenance[edit]

When the deployment has finished the system will need proper maintenance to stay alive. This includes data reconciliation, execution and monitoring and performance tuning.

Growth[edit]

As the project can be seen as part of the larger iterative program, it is very likely that the system will want to expand. There will be projects to add new data as well as reaching new segments of the business areas. The Lifecycle then starts over again.

References[edit]

Kimball, R., Ross, M., Thornthwaite, W., Mundy, J., & Becker, B. (2008). The data warehouse lifecycle toolkit (2nd ed.). Wiley Publishing, Inc.