A Data Warehouse Roadmap for UC Berkeley

1
A Data Warehouse Roadmap for UC Berkeley

• Suggested approach for developing and delivering
• Thom King, June, 2005

2
Developing a Data Warehouse Roadmap
BusinessRequirements and Strategy
Impl. Project 1
Impl. Project 2
. . .
InitiateProject
On-going governance
Business Value Roadmap
Dataapplicationstechnologyorg/process
3
Strategy Phase
IdentifyInterview team
Summarize interview results
traininterviewteam
Conduct business interviews
Opportunity prioritization meeting
Review with stakeholders
Conduct systems interviews
IdentifyInterviewees
Schedule interviews
Business Value Roadmap
4
Resources for Strategy Phase

• Core Team
• Project leader
• Business analysis team
• Business analyst
• Interviewers
• Technical Team
• Systems analyst
• Data modeler
• (part-time project leader and 3 full-time
  equivalent analysts can be staffed by as many as
  5-6 people)

• Other Key Resources
• Executive interviewees(expect 5-8 interviews)
• Business area intervieweesanalysts subj. matter
  experts(expect 5-10 interviews)
• Systems experts
• (expect 6-8 interviews)
• Administrative systems
• Student systems
• Reporting systems

Expected Duration June-September, 2005
5
Architecture Phase
Develop / Revise Query-pres Tech arch
Document Architecture Reqs Volumes, users,
Security, etc.
Summarize Required Changes
Develop Data Architecture
Document Warehouse Scope
Identify Skills / Training Needs
Develop BI/Query Apps Arch
Dev/revisesecurityarchitecture
Develop Fact/Dimension Data Matrix
Assess Existing Whse Capabilities Against Req.
Identify Interdependencies
Develop / Revise DB, ETL, metadatatechnology arc
hitecture
Reconcile wrequirements
Develop Implementation Strategy
SummarizeBI apps requirements
Document Gaps
Review w stakeholders
Scope, Describe, Sequence Projects
6
Resources for Architecture Phase

• Core Team
• Dedicated (f/t or close)
• Data architect / modeler
• Systems analyst (1-1.5)
• Part-time
• Project Leader
• Tech/security architect
• Solutions / apps architect
• DBA
• Business Analyst

• Other Key Resources
• Existing DW teams
• DBA
• Reports
• Portal
• ETL
• IST leaders
• Project planners
• Skills planners
• management

Expected Duration August-December, 2005