Business Requirements Gathering Techniques For Data Warehouse & Business Intelligence

Business Requirements Gathering Techniques for
Data Warehouse & Business Intelligence

Portland DAMA Presentation
July 22, 2005
Michael J. Lampa
mlampa@coreintegration.com
1
Course Outline
Introduction
Business Requirements Defined
Scoping the Data Warehouse Program Initiative
Planning & Coordinating Resources
“Facili-Modeling” Techniques & Tools
Designing & Executing Requirements Gathering Workshops
Open Discussion
2
Session Objectives
How to scope data warehouse program initiatives using Lay-

of-the-Land interviewing techniques
How to plan and coordinate involvement of representatives
from your DW team and business communities.
How to use group facilitation techniques, process modeling
disciplines and data modeling disciplines to get the right
information as input to your data warehouse project
deliverables.
How to build and execute requirements gathering
workshops
How to know when you have enough input to move on.
3
What do we mean by Business
Requirements?
4
Each Data Warehouse Process has Requirements…

Source
Databases
Day-to-Day
Data Delivery Business
Source System Screens, forms,
Method Source System Operations
Data BI Binaries
Structures
Data
Correction
Data Extraction Data Structures & Relational Database
Data Transport
Cleansing Edits Erwin Repository Data Analysis, Data End-User
Services Mining & Drilling
Data Client Access
Stewardship Rule
Correction Meta Data
Audit Management Statistics
Exception
Load Definitions Business
Raw Source Exceptions Load & Views Intelligence
System Data Statistics Data Software Executive
Extraction of Staging Data Transformation & Structures Dashboards
To the PSA, MDA, Subscription
Or a Target System Rules
Business Intelligence
Data Delivery Operational
Extraction, Reporting
Cleansing & Translation, & Aggregated
Audit Source ETL Routines that Time
Loading Multi-Dimensional
System Data cleanse Staging Series
Rules
Data Analytics
Aggregation
Staging Database & Summarization
Relational Rules
Insertion of Source Database, Data Marts
System Data into ETL Software
Staging Database
Relational Database Integrated Operational Report
OS Scripted Routines Current Relational Database Services
Published Integrated Operational Drill-Down
Data Data Data
Subscribed Aggregated
Integrated Multi-dimensional
Target System Data Historical
data Reporting
Details
Tool
Target Multi-Dimensional
Databases
Aggregated,
Aggregates
Persistent Storage Area Summarized
Atomic Data
Relational
History Database Current
Relational Database Details
5
…and Each Requirement has 6 Architectural Contexts
Each Architecture has

requirements
Data Warehouse
projects touch ALL
architectures
Data Warehouse
programs define what
requirements are
needed
Data Warehouse
increments capture
the requirement
details
6
Each Architectural Context has Engineering Blueprints or Specifications
Business Architecture Facilities Architecture

Goals & Objectives Decomposition Facilities Blueprints
Business Process Model Air Handling
Enterprise Data Model Power Specifications
Application Architecture Practice Architecture

Application Interface Diagram Guides & Procedures
Application Deployment Diagram Intuitive Helps & Hints
Technology Architecture People Architecture

Server Topology Diagram Organization Charts
Network Topology Diagram Skills Inventory
End User Device Inventory Training Programs
7
Scoping the Data Warehouse
Initiative
8
Scoping the Data Warehouse Initiative
Focus is on Business Architecture
What is the Business

Opportunity you are
trying to achieve?
What is the Business
Pain you are trying to
eliminate?
What Business
Functional Areas are
involved?
Which Organizational
Units are affected?
What Applications are
implicated?
9
The Lay of the Land: Technique
1-on-1 Interviews with Key

Business Sponsors
1-on-1 Interviews with KEY
IT Sponsors
Prepare a detailed Interview
Script
Take Copious Interview
Notes
Request review of Interview
Notes for accuracy
Compile Notes and form a
Recommendation
10
The Lay of the Land: Interview Questions
What is the mission of your team/group/division/department?

What is the most significant shift in the way you are doing
business?
What are your competitors doing that you don’t?
How do you measure success in your department?
How does your boss measure your success?
What are your Functional Goals?
How do your Functional Goals relate to the Corporate Goals?
What MUST go right for you to be successful?
How much of the Business Process Value Chain is your concern?
What questions do you answer/need to answer?
Who do you rely upon to get the right answers?
From where does the information come?
What are the critical “systems” used by your department?
11
The Lay of the Land: Scope Recommendation
DOCUMENT THE BUSINESS OPPORTUNITY/PROBLEM TO

ADDRESS
Identify & Recommend scope based on Business Priority.
Define the Organizations that should sponsor the initial efforts
Define the functional scope of the initial efforts
Name the key people from appropriate Business Operations Units
Define the Operational Systems that will be involved
Name the key people from the appropriate IT Units
12
“Facili-Modeling”
Techniques & Tools
13
Premise: To deliver a useful Data Warehouse, we must

know WHAT the business does!
We need to:
Document the Business Process Model
Document the Enterprise Data Model
Document the Corporate & Functional Goals
Document Key Performance Metrics
Document Key Business Information Needs
14
Business Context Diagram

USED AT: x WORKING READER DATE CONTEXT:
PROJECT: Created: 12/11/1998
Class Location Process Modeling Practical Approach DRAFT Top
Rev Date: 3/23/1999
Captures: Facilitators: Business Architecture Group, Inc.

File Name: Process Modeling Example
Rev Version: Version 1.0
RECOMMENDED
PUBLICATION
Explicit Functional Scope Legal and

Regulatory
Data Subjects 1 Jurisdiction
Corporate Goals & Metrics Bellcore

8
Customers
Techniques: 2
Group Facilitation LEC

Telecom
7
Scripted Interviews
Documentation Dissection
Administration
3
A0
Sales
Force P. 2 Service
Tools: Providers
Process Modeling Tool Inputs

Outputs
6
------------------------------------
Database or Spreadsheet ------------------------------------
Request for Service - 2, 3, 12, 13, 14
Provision Notice - 1, 2, 4, 15, 7, 8
Publishing Tool Service Readiness Confirmation - 2, 15, 7, 1

Customer Correspondence - 2, 12,
13, 14, 8, 3, 15
Usage - 7
Word Processor Remittance - 7 Network
Equipment
Banks/Credit
Info Provider
Bill - 13, 2, 7, 15
Disbursements - 1, 2, 3, 4, 5, 6, 7, 8
Customer Response - 7 Provider
Financial Reports - 5
Jurisdiction Data - 8 4 5
Marketing Campaign - ALL
NODE: A-0 TITLE: Process Modeling Example NUMBER: P. 1
15
Business Process Model
Captures:
Process Definitions
Information Flow
product fit SOR customer
Process Controls customer
SOR industry
customercharacteristics data transactions
Process Mechanisms discovery

data
data
customer
profile
Functional Goals & Metrics Develop
Customer
Profile
2.1
advice data
Techniques: follow up activity
Provide
Customer
Group Facilitation Advocacy

2.2
proposition
acceptance
Scripted Interviews activity
request
"what if" data
Documentation Dissection Provide
Fulfillment
CRUD Analysis 2.3
customer profile updates customer Maintain Customer

product Portfolio
data 2.4
Tools:
Process Modeling Tool customer transaction request
Generate
Intelligent
SOR transaction
Triggers
Database or Spreadsheet 2.5
SOR customer data
Publishing Tool Collect Customer

Experience
Word Processor Feedback

2.6
customer
feedback
Order Mgmt
System
CRM System
16
Enterprise Data Model
Captures:
Entity Definitions
Entity Relationships
Functional Subject Areas
Data Quality Rules
Techniques:
Group Facilitation
Scripted Interviews
Documentation Dissection
CRUD Analysis
Tools:
Data Modeling Tool
Database or Spreadsheet
Publishing Tool
Word Processor
17
Business Model Relationship to Data Warehouse Design
Enterprise
Enterprise Business
Business
Business
Business Process
Process Model
Model
CCR
RUU
Decomposition
Decomposition
DD
Specification
Input/Output
Specification
Input/Output
Mechanism
BBA
Mechanism
Diagram
Controls
ALL
Process
Diagram
Context
Controls
Process
Context
AAN
NCC
EE
Business
Business
Architecture
Architecture
Data
Data
Model
Model
“HUB”
“HUB” ENTITY
ENTITY VIEW
VIEWFUNCTIONAL
FUNCTIONAL VIEW
VIEW
STATE
STATE
S/T MAPS SUBJECT AREA
TRANSITIONS
TRANSITIONS
Business
Business
Strategy
CONTENT
Strategy
CONTENT
SOURCE
MODELS
TRAGET
TRAGET
MODEL
MODEL
DATA WAREHOUSE
DATA ARCHITECTURE Plan
Plan
ANALYSIS
ANALYSIS
CONFORMITY
CONFORMITY ACCESS
ACCESS MODELS
MODELS DIMENSIONS
DIMENSIONS
18
Business Information Needs
Captures:
The information needs of the target users
How the users want to use the information
Insight for building business intelligence solutions
Techniques:
Group Facilitation
Cross Reference to the Process model Functions
Cross Reference to the Corporate and Functional Goals
Ask for Information Needs
Ask for Supporting Questions to the Information Need
Make sure the Questions include/reference
Analysis dimensions
Time Periods
Refresh Frequency & Latency Considerations
Tools:
Publishing Tool
Word Processor
19
Business Information Needs (an Example)
Karolyn’s Kritters™
Cost of Inventory
This need describes understanding the cost associated with holding items in our
warehouse inventory for any length of time. We need to know the rate of inventory
turnover by location, product, and time of year. The sales price of the item is not important
in this need.
Business Questions:
1. What is the average number of days products sit in the warehouse by location,
product group, and month?
2. Which products do we produce without buyer demand? Show this by product.
3. What has been the average inventory, at the start of each month, by product, by
location?
4. What has been the average inventory at the end of each month, by product, by
location?
Adapted from Information Strategies, Inc
20
Business Information Needs (another Example)
Karolyn’s Kritters™
Owner Satisfaction
This need is designed to help us better understand owner satisfaction through orders
filled, return of products, and owner complaints. The overall value of the owner is not a
factor in understanding owner satisfaction at large.
Business Questions:
1. What is the number of owner complaints due to late or inaccurate credits?
2. Show the percent of returns by owner, by product, by reason code.
3. What is the number of calls, per month, received by our 800 service lodging a
complaint? Show by complaint code.
4. What percentage of orders are completely fillable at the time they are placed? Show
this by location, month, and product.
Adapted from Information Strategies, Inc
21
Business Information Needs & KPI’s
Business Info Analysis Refresh Analysis

Business Question KPI
Need Period Frequency Dimension
How long does

product sit in the Location,
Cost of Inventory Inventory Days Month daily
warehouse Product Cat
locations?
Which Products
Inventory turn ? ? Product
have low demand?
Owner compliants
Owner Satisfaction Cust Sat Index ? ? Owner
due to billing errors
Owner,
What is the %
Product Returns ? ? Product,Return
Returns?
Reason Code
22
Business Activity Model & KPI Defs

Data Warehouse Catalog Metric_Class
Metric Dimension Business_Unit
DW Catalog ID metric_class_id
Metric Dimension ID bus_unit_id
DW Catalog Name metric_class_name
Metric Dimension Name bus_unit_name
DW Schema Name metric_gl_class_code
Public Ind parent_bus_unit_id (FK)
Data Warehouse Table Performance_Metric

DW Table ID performance_metric_id
DW Table Name performance_metric_name Business_Process
DW Catalog ID (FK) performance_metric_measure_type bus_process_id
parent_performance_metric_id (FK)
metric_class_id (FK) bus_unit_id (FK)
Performance Metric Period Grain bus_process_name
Metric Dimension Hierarchy parent_process_id (FK)
Data Warehouse Column
Metric Dimension Hierarchy ID
DW Column ID
hierarchy sequence
DW Column Name
performance_metric_id (FK)
DW Table ID (FK)
Metric Dimension ID (FK)
DW Column ID (FK)
Process_Performance_Target
Performance Metric Component process_performance_target_id
Perf metric Component ID performance_metric_id (FK) Process Performance Trigger Business Activity
function_name bus_process_id (FK) process_performance_target_id (FK) bus activity ID
concatenation sequence Performance_target_goal bus activity ID (FK)
bus activity name
performance_metric_id (FK) performance_target_ceiling_threshold
Trigger Reason bus activity enabling module
concat target column (FK) performance_target_floor_threshold
bus_process_id (FK)
concat source column (FK) ceiling_escalation_rule
bus activity protocol
floor_escalation_rule
trending_rule
trending_series_type
series_duration
series_function_rule
23
Designing & Executing
Requirements Gathering Workshops
24
The Iterative Nature of Facili-Modeling Workshops
EXTENDED
SUBJECT
MATTER
EXPERTS
INTERVIEW
MINUTES
BE ISS
IN
NE UE
FIT S
TE
S/ &
RV
PA
IN
I
EW
S
S
STRAWMAN
MODELS WORK
CORE ISSUES & IN
TEAM DEFINITIONS PROCESS
DATABASE
IO IN G
&
S
S NS
SS EL
N
E IO
SU IT
SE OD
IS IN
M
F
DE
CORE
SUBJECT MODEL
MATTER REPOSITORY
EXPERTS
25
The Three Phases of Facilitated Workshops

Workshop
Agenda Template
C1
Project Annotated
Charter Prepare for
Agenda
I1
Workshop
O2
A41
Conduct
Workshop
Agenda Sessions
Completion A42 Workshop
Status Session Notes
Review & Workshop

Distribute Deliverables
Deliverable Workshop O1
Completion
Results
Status A43
26
The Key to Success – Preparing Annotated Agendas

Workshop
Agenda Template
C1
Purpose,
Objectives &
Project Identify Where Deliverables
Charter Project Needs to
I1 go
A411
Identify Where
Project Came
From
A412
Agenda Known
Completion Information Identify How to
Status Get There
I2
Draft Steps
A413
Filter Approach
to be User-
Freindly
Revised
A414
Steps
Annotated
Walkthru Agenda
Approach
O1
Changesto
Steps A415
27
A Business Modeling Facilitated Workshop Flow
Context
Diagram
Documentation Workshop
Session Notes
Annotated Conduct Context O1

Agenda Diagram Agenda
I1
A421
Process
Flow
Diagram
Documentation
Agenda
Conduct Process
Completion
Flow Diagram Status
Agenda O2
A422 Entity
Relationship
Diagram
Documentation
Conduct Entity
Relationship
Diagram Agenda
A423
28
Business Modeling Facilitated Workshop Agendas
The CONTEXT DIAGRAM Agenda
INTRODUCTION
DEFINE PURPOSE OF BUSINESS
IDENTIFY WHO INTERACTS WITH THE BUSINESS
IDENTIFY WHAT COMES INTO THE BUSINESS
IDENTIFY WHAT GOES OUT OF THE BUSINESS
MODEL AND VALIDATE
DESCRIBE SCOPE OF THE BUSINESS
WRAP-UP
ASSIGN OPEN ITEMS
ASSIGN HOMEWORK
REVIEW/FEEDBACK
29
The PROCESS FLOW DIAGRAM Agenda
INTRODUCTION
DEFINE BUSINESS FUNCTION
DEFINE PROCESS ACTIVITIES
ORDER PROCESS ACTIVITIES
IDENTIFY INPUTS, OUTPUTS, CONTROLS,
MECHANISMS
WRAP-UP
ASSIGN OPEN ITEMS
ASSIGN HOMEWORK
REVIEW/FEEDBACK
30
The ENTITY-RELATIONSHIP DIAGRAM Agenda
INTRODUCTION
DEFINE BUSINESS FUNCTION
DEFINE CANDIDATE BUSINESS INFORMATION
ENTITIES
DESCRIBE ENTITIES
DEFINE RELATIONSHIPS BETWEEN ENTITIES
DEFINE RELATIONSHIP RULES
WRAP-UP
ASSIGN OPEN ITEMS
ASSIGN HOMEWORK
REVIEW/FEEDBACK
31
Facili-Modeling Tips for Success
Defined Roles & Adherence to Ground Rules

Don’t EVER, EVER leave your Agenda!
Generous use of Brainstorming Technique
You own the process, the group owns the
content
Build models in the workshop early to set stage
Build majority of models off-line as “strawman”
Review Strawman models with group
Strive for 1-workshop per Functional Area
Don’t model Process lower than 3-4 levels
Focus on Subject Areas and Entities.
Use attributes to reinforce concepts
32
Open Discussion
Group Discussion
33

Business Requirements Gathering Techniques For Data Warehouse & Business Intelligence

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Business Requirements Gathering Techniques For Data Warehouse & Business Intelligence

Diunggah oleh

Hak Cipta:

Format Tersedia

Business Requirements Gathering Techniques for

Data Warehouse & Business Intelligence

 How to scope data warehouse program initiatives using Lay-

Each Data Warehouse Process has Requirements…

…and Each Requirement has 6 Architectural Contexts

 Each Architecture has

Each Architectural Context has Engineering Blueprints or Specifications

Business Architecture Facilities Architecture

Application Architecture Practice Architecture

Technology Architecture People Architecture

Focus is on Business Architecture

 What is the Business

The Lay of the Land: Technique

 1-on-1 Interviews with Key

The Lay of the Land: Interview Questions

 What is the mission of your team/group/division/department?

The Lay of the Land: Scope Recommendation

 DOCUMENT THE BUSINESS OPPORTUNITY/PROBLEM TO

Premise: To deliver a useful Data Warehouse, we must

Business Context Diagram

Captures: Facilitators: Business Architecture Group, Inc.

 Explicit Functional Scope Legal and

 Corporate Goals & Metrics Bellcore

 Group Facilitation LEC

 Process Modeling Tool Inputs

 Publishing Tool Service Readiness Confirmation - 2, 15, 7, 1

Business Process Model

 Process Mechanisms discovery

 Group Facilitation Advocacy

 CRUD Analysis 2.3

customer profile updates customer Maintain Customer

 Publishing Tool Collect Customer

 Word Processor Feedback

Enterprise Data Model

Business Information Needs

Business Information Needs (an Example)

Business Information Needs (another Example)

Business Information Needs & KPI’s

Business Info Analysis Refresh Analysis

How long does

Business Activity Model & KPI Defs

Data Warehouse Table Performance_Metric

The Iterative Nature of Facili-Modeling Workshops

The Three Phases of Facilitated Workshops

Review & Workshop

The Key to Success – Preparing Annotated Agendas

A Business Modeling Facilitated Workshop Flow

Annotated Conduct Context O1

Business Modeling Facilitated Workshop Agendas

The CONTEXT DIAGRAM Agenda

Business Modeling Facilitated Workshop Agendas

The PROCESS FLOW DIAGRAM Agenda

Business Modeling Facilitated Workshop Agendas

The ENTITY-RELATIONSHIP DIAGRAM Agenda

Facili-Modeling Tips for Success

 Defined Roles & Adherence to Ground Rules

Anda mungkin juga menyukai

How to scope data warehouse program initiatives using Lay-

Each Architecture has

What is the Business

1-on-1 Interviews with Key

What is the mission of your team/group/division/department?

DOCUMENT THE BUSINESS OPPORTUNITY/PROBLEM TO

Explicit Functional Scope Legal and

Corporate Goals & Metrics Bellcore

Group Facilitation LEC

Process Modeling Tool Inputs

Publishing Tool Service Readiness Confirmation - 2, 15, 7, 1

Process Mechanisms discovery

Group Facilitation Advocacy

CRUD Analysis 2.3

Publishing Tool Collect Customer

Word Processor Feedback

Defined Roles & Adherence to Ground Rules