Book Image

Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology

By : John Heaton
Book Image

Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology

By: John Heaton

Overview of this book

Oracle Database 11g is a comprehensive database platform for data warehousing and business intelligence that combines industry-leading scalability and performance, deeply-integrated analytics, and embedded integration and data-quality all in a single platform running on a reliable, low-cost grid infrastructure. This book steps through the lifecycle of building a data warehouse with key tips and techniques along the way. Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology outlines the key ways to effectively use Oracle technology to deliver your business intelligence solution. This is a practical guide starting with key recipes for project management then moving onto project delivery. Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology is a practical guide for performing key steps and functions on your project. This book starts with setting the foundation for a highly repeatable efficient project management approach by assessing your current methodology to see how suitable it is for a business intelligence program. We also learn to set up the project delivery phases to consistently estimate the effort for a project. Along the way we learn to create blueprints for the business intelligence solution that help to connect and map out the destination of the solution. We then move on to analyze requirements, sources, and data. Finally we learn to secure the data as it is an important asset within the organization and needs to be secured efficiently and effectively.
Table of Contents (21 chapters)
Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface

Introduction


Business intelligence and data warehouse projects have a lot of information and artifacts, once the project wraps up. It is important to identify which of these need to be transferred to production support and which can be archived. Most of the documentation that was used and useful during the project should not be transferred. The key documents and information that should be transferred are as follows:

  1. 1. Business information, such as:

    • Project Charter

    • Metadata and Conceptual Data Model

    • Frequently asked questions (derived from defect and enhancement register)

  2. 2. Technical information, such as:

    • Technical architecture overview and design

    • Design standards

    • Security overview

    • Runbook for ETL

    • Data lineage from report to source data

    • Software support manual

    • Code repository