1. Driving Implementation Through a Methodology Chapter 4

2. “Big Bang” Approach Analyze enterprise requirements Build enterprise data warehouse Report in subsets or store in data marts

3. “Big Bang” Approach: Advantages and Disadvantages zAdvantages: - The only real advantage is where the warehouse is being built as part of another major project or program such as reengineering and they are dependent on each other - Having a “big picture” of the data warehouse before starting the data warehousing project zDisadvantages: - Involves a high risk, takes a longer time - Runs the risk of needing to change requirements

4. Incremental Approach to Warehouse Development zMultiple iterations zShorter implementations zValidation of each phase Strategy Definition Analysis Design Build Production Strategy Definition Analysis Design Build Production Strategy Definition Analysis Design Build Production

5. Benefits of an Incremental Approach zDelivers a strategic data warehouse solution through incremental development efforts zProvides extensible, scalable architecture zSupports the information needs of the enterprise organization zQuickly provides business benefits and ensures a much earlier return of investment zAllows a data warehouse to be built based on a subject or application area at a time zAllows the construction of integrated data mart environment

6. Top-Down Approach Sales Marketing Legacy data Operational data External data source Data warehouse Data marts Users

7. Top-Down Approach: Advantages and Disadvantages zAdvantages: - Provides a relatively quick implementation and payback - Offers significantly lower risk - Emphasizes high-level business needs - Achieves synergy among subject areas zDisadvantages: - Requires an increase in up-front costs - Difficult to define the boundaries - May not be suitable unless the client needs cross-functional reporting

8. Bottom-Up Approach Sales Marketing Legacy data Operational data External data source Data warehouse Data marts

9. Bottom-Up Approach: Advantages and Disadvantages zAdvantages: - Appealing to IT - Easier to get buy-in from IT zDisadvantages: - Requires source systems to encapsulate the current business processes - Design may be out-of-date before delivery - Requires reengineering for each increment - Solutions may be rejected by the next line of business to be involved - Overall benefit to the business may be minimized

10. Oracle Method zConsists of: - Online guidelines and manuals - Workplan templates - Deliverable templates zCreated by experienced and field-based practitioner for estimated, managing, developing, and delivering business solutions.

11. Oracle Data Warehouse Method zGuides through development: - Business functions - Processes - Tasks zModeled on the Custom Development Method

12. Method Materials zWorkplan templates* zDeliverable templates* zOnline handbooks zEstimating software Software Tools Handbooks zMethod handbook zProcess and task reference* zDeliverable reference*

13. Oracle Data Warehouse Method zFocuses on scoping zManages risk zRelies on user involvement throughout zDelivers an extensible, scalable solution zUses a variety of technologies zIdentifies tasks with clear objectives and deliverables zEmploys common techniques, skills, and dependencies zAssigns tasks to processes and processes to phases

14. Benefits Experience and best practices Flexibility Risk avoidance Productivity Consistency

15. DWM Fundamental Elements zApproaches zPhases zProcesses zTasks and deliverables zRoles Phase 1Phase 2Phase 3 Process 1 Process 2 Phase 1 Task1 Phase 1 Task2 Phase 1 Task3 Phase 2 Task1 Phase 2 Task2 Phase 2 Task3 Phase 3 Task1 Phase 3 Task2 Phase 3 Task3

16. Approaches Increment I Proof of Concept Warehouse Business infrastructure application implementation Increment II Through N Increment II Data mart Warehouse Packaged data mart

17. Incremental Approach Warehouse Strategy Phase Scoping Services Technical Architecture Services Increment 1 Increment A Proof of Concept Increment 2 Increment 3 Increment n Increment B Increment C Increment z Warehouse Infrastructure Services Warehouse Business Solution Services Requirements Capture Business Strategy IT Strategy

18. Incremental Development zFocus on business functionality zDeliver business benefit zSuited to warehouse evolution zOnce an increment is complete the selection and scope of the next increment is defined zEach increment follows the same phase sequence Strategy PGMPJM Project and Program Management Definition ETA Enterprise Technical Architecture Analysis Design Build Transition to Prod. Discovery Incremental Development

19. The Strategy Phase Strategy Analysis Design Build Transition Discovery Definition Business requirements Data acquisition Architecture Data quality Administration Strategy

20. The Strategy Phase Strategy Analysis Design Build Transition Discovery Definition Metadata Data access Documentation Testing Training Strategy

21. The Definition Phase Strategy Analysis Design Build Transition Discovery Definition Business requirements Data acquisition Architecture Data quality Definition

22. The Definition Phase Strategy Analysis Design Build Transition Discovery Definition Administration Metadata management Data access Documentation Training Definition

23. The Analysis Phase Strategy Analysis Design Build Transition Discovery Definition Business requirements Data acquisition Architecture Data quality Administration Analysis

24. The Analysis Phase Strategy Analysis Design Build Transition Discovery Definition Metadata Data access Documentation Testing Training Analysis

25. The Design Phase Strategy Analysis Design Build Transition Discovery Definition Data acquisition Metadata management Architecture Data quality Administration Design

26. The Design Phase Strategy Analysis Design Build Transition Discovery Definition Data access Database design & build Documentation Testing Training Design Transition

27. The Build Phase Strategy Analysis Design Build Transition Discovery Definition Data acquisition Metadata management Architecture Data quality Administration Build

28. The Build Phase Strategy Analysis Design Build Transition Discovery Definition Data access Database design & build Documentation Testing Training Build Transition

29. Transition to Production Phase Strategy Analysis Design Build Transition Discovery Definition Data acquisition Post-implementation support Testing Training Transition Transition to production

30. Discovery Phase Strategy Analysis Design Build Transition Discovery Definition Post-implementation support Discovery

31. Processes zCohesive set of tasks that meet objectives zCommon skill set zProject deliverables Most overlap and interrelate; others are strict predecessors

32. Processes Business Requirements Definition Data Acquisition Architecture Data Quality Warehouse Administration Metadata Management Data Access Database Design and Build Documentation Testing Training Transition Post-Implementation Support

33. Business Requirements Definition zDefines requirements zClarifies scope zEstablishes implementation road map zProvides initial focus on enterprise implementation zIdentifies information needs zModels the requirements

34. Data Acquisition zIdentify, extract, transform, and transport source data zConsider internal and external data zMove data between sources and target zPerform gap analysis between source data and target database objects zDefine first-time load and refresh strategy zDefine tool requirements zBuild, test, and execute data acquisition modules

35. Architecture zSpecify technical foundation zCreate warehouse architectural design zIntegrate products of architecture components for scalability and flexibility zDetermine database environment--distributed or centralized zDefine development, testing, training, and production environments zConfigure the platform zPerform database sizing zConsider disk striping

36. Data Quality zEnsure data consistency, reliability, accuracy zDevelop a strategy for: - Cleansing - Integrity functions - Quality management procedures zIdentify business rules for: - Cleansing - Error handling - Audit and control zDefine data quality tool requirements zBuild, test, and execute data quality modules

37. Warehouse Administration zSpecify maintenance strategy for: - Configuration management - Warehouse management - Data governing zDefine warehouse management workflow and tool requirements zBuild, test, and execute modules zProve data access management and monitoring zAutomate warehouse management tasks

38. Metadata Management zDefine metadata strategy zDefine metadata types zSpecify requirements for the metadata repository, integration, and access zEstablish technical and business views of metadata zDevelop modules for capturing, bridging, and accessing metadata

39. Data Access zIdentify, select, and design user access tools zDefine user profiles zDetermine requirements for interface style, queries, reports, and the end user layer zEvaluate, acquire, and install access objects - Queries and reports - Catalogs - Hierarchies and dimensions

40. Database Design and Build zSupport data requirements zProvide efficient access zCreate and validate logical and physical models zCreate relational and multidimensional database objects zEvaluate partitioning, segmentation, and placement zIdentifying indexes and keys zGenerate DDL zBuild and implement database objects

41. Documentation Produce textual deliverables: zGlossary zUser and technical documentation zOnline help zMetadata reference guide zWarehouse management reference zNew features guide

42. Testing zDevelop a test strategy zCreate test plans, scripts, and scenarios zTest all components: - Data acquisition - Data Access - Ad hoc access - Regression - Volume - Backup - Recovery zSupport acceptance testing

43. Training zDefine requirements: - Technical - End user - Business zIdentify staff to be trained zEstablish time frames zDesign and develop materials zFocus on tool training and use of the warehouse

44. Transition zDefine tasks for transitioning to the production warehouse zMigrate modules and procedures zDevelop the installation plan zPrepare the maintenance environment zPrepare the production environment

45. Post-Implementation Support zEvaluate and review warehouse use zMonitor warehouse use zRefresh the warehouse zMonitor and respond to problems zConduct performance testing and tuning zTransfer responsibility zEvaluate and review the implemented solution

46. Tasks and Deliverables zOutlined in Work Breakdown Structure zOrganized by process and phase Task ID Task Name A Strategy A. RD.EXEC Business Requirements Definition A.RD.001 Obtain Existing Reference Material A.RD.002 Obtain Reference Data Models A.RD.003 Define Strategic Goals, Vision of the Enterprise A.RD.004 Establish Business initiatives A.RD.005 Define Objectives and Purpose of Enterprise Data Warehouse A.RD.015 Collect Enterprise Business Information Requirements

47. Roles zThe project team: roles and responsibilities zCommon roles Analyst, database administrator, programmer, tester zWarehouse specific roles DW architect, metadata architect, data quality administrator, DW administrator

48. Warehouse Technology Initiative zCustomer driven - Warehouse products only - Quality, not quantity - High-value partnerships zRequires - Oracle certified solution partner level - Product certification - Reference

49. WTI Partners by Categories zDesign and administration zSource zManage zAccess zData content provider

50. Summary This lesson discussed the following topics: zExplaining the different approaches to warehouse development and the benefits of an incremental approach zIdentifying the purpose of the Oracle Method zDiscussing the purpose and fundamental elements of Data Warehouse Method zDiscussing the objectives of the Oracle Warehouse Technology Initiative