Scribd
Upload
246 views24 pages

03a - PPT3 - Kimball Lifecycle - R0

The document discusses the Kimball Lifecycle, which provides a framework for developing a data warehouse. It involves the following key stages: project planning, business requirements definition, dimensional modeling, physical design, ETL design, BI application design, deployment, maintenance, and growth. The lifecycle illustrates the general flow and ensures tasks are sequenced properly with activities occurring concurrently when needed.

Uploaded by

Budiutama Lawas Lawu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
246 views24 pages

03a - PPT3 - Kimball Lifecycle - R0

The document discusses the Kimball Lifecycle, which provides a framework for developing a data warehouse. It involves the following key stages: project planning, business requirements definition, dimensional modeling, physical design, ETL design, BI application design, deployment, maintenance, and growth. The lifecycle illustrates the general flow and ensures tasks are sequenced properly with activities occurring concurrently when needed.

Uploaded by

Budiutama Lawas Lawu
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 24

7023T

Advanced Database Systems


Session 03
Introduction to Kimball’s Lifecycle

This presentation is based on Michael A. Fudge, Jr.


Two Main Data Warehouse Development
Methodologies

Top-down Approach Bottom-up Approach


• The Inmon’s approach • The Kimball’s approach
• DW is developed based on the • Starts with one data mart (ex.
Enterprise wide data model sales); later on additional data
• DW as a single repository feeds marts are added (ex. collection,
data into data marts marketing, etc.)
• Longer to implement • Data flows from source into data
• May fail due to the lack of marts, then into the data
patience and commitment warehouse
• Faster to implement
• Implementation in stages
• Need to ensure consistency of
metadata

Bina Nusantara
The Kimball Lifecycle
Diagram

Bina Nusantara
The Kimball Lifecycle
• Illustrates the general flow of a DW implementation
• Identifies task sequencing and highlights activities that
should happen concurrently
• May need to be customized to address the unique needs of
your organization
• Not every detail of every Lifecycle task will be performed on
every project

Bina Nusantara
The Kimball Lifecycle
Diagram

Bina Nusantara
Program/Project Planning
Project planning
• Scope definition understanding business requirements
• Tasks’ identification
• Scheduling
• Resource planning
• Workload assignment
• The end document represents a blueprint of the project

Bina Nusantara
Program/Project Management
Enforces the project plan
Activities:
• Status monitoring
• Issue tracking
• Development of a comprehensive communication plan that
addresses both the business and IT units

Bina Nusantara
The Kimball Lifecycle
Diagram

Bina Nusantara
Business Requirements Definition
• Success of the project depends on a solid understanding of
the business requirements!!!
• Understanding the key factors driving the business is crucial
for successful translation of the business requirements into
design considerations
• Three tracks following tracks follows this step:
– Technology
– Data
– Bussiness intelligence Applications
The Kimball Lifecycle Diagram
Technology Track

Bina Nusantara
Technology Track
• Technical Architecture Design
• Overall architectural framework and vision
• Considerations:
– The business requirements
– Current technical environment
– Planned strategic technical directions

Bina Nusantara
The Kimball Lifecycle Diagram
Data Track

Bina Nusantara
Dimensional Modeling
• Detailed data analysis of a single business process is
performed to identify the fact table granularity, associated
dimensions and attributes, and numeric facts.
• Dimensional models contain the same data content and
relationships as models normalized into third normal form,
but structured differently.
– Improve understandability and query performance required by
DW/BI
• Primary constructs of a dimensional model
– Fact tables
– Dimension tables

Bina Nusantara
Physical Design
Defining the physical structures
• Setting up the database environment
• Setting up appropriate security
• Preliminary performance tuning strategies, from indexing to
partitioning and aggregations.
• If appropriate, OLAP databases are also designed during this
process.

Bina Nusantara
ETL Design and Development
• The MOST important stage
• 70% of the risk and effort in the DW project is attributed to
this stage
• ETL system capabilities:
– Extraction
– Cleansing and conforming
– Delivery and management

Bina Nusantara
The Kimball Lifecycle Diagram
Bussiness Intelligence Application Track

Bina Nusantara
Business Intelligence
Application Track
• Applications that query, analyze, and present information
from the dimensional model.
• BI applications deliver business value from the DW/BI
solution, rather than just delivering the data
• The goal is to deliver capabilities that are accepted by the
business to support and enhance their decision making.

Bina Nusantara
BI Application Design &
Development
BI Application Design
• Identify the candidate BI applications and appropriate navigation
interfaces to address the users’ needs and needed capabilities.
• Produce BI application specification
BI Application Development
• Configuration of the business metadata and tool infrastructure
• Construction and validation of the specified analytic and operational
BI applications and the navigational portal

Bina Nusantara
The Kimball Lifecycle Diagram
Bussiness Intelligence Application Track

Bina Nusantara
Deployment
• It is crucial that adequate planning was performed to make
sure that:
– The results of technology, data, and BI application tracks are
tested and fit together properly
– Appropriate education and support infrastructure is in place.
• It is critical that deployment be well orchestrated
• Deployment should be deferred if all the pieces, such as
training, documentation, and validated data, are not ready
for production release.

Bina Nusantara
The Kimball Lifecycle Diagram
Maintenance

Bina Nusantara
Maintenance
• Occurs when the system is in production
• Includes:
– Technical operational tasks that are necessary to keep the system
performing optimally
– Usage monitoring
– Performance tuning
– Index maintenance
– System backup
• Ongoing support, education, and communication
with business users

Bina Nusantara
The Kimball Lifecycle Diagram
Growth

Bina Nusantara
Growth
DW systems tend to expand (if they were successful)
• Is considered as a sign of success
• New requests need to be prioritized
• Starting the cycle again
– Building upon the foundation that has already been established
– Focusing on the new requirements

Bina Nusantara

You might also like