Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology

You're reading from   Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology Take your data warehousing and business intelligence to the next level with this practical guide to Oracle Database 11g. Packed with illustrations, tips, and examples, it has over 80 advanced recipes to fine-tune your skills and knowledge.

Arrow left icon
Product type Paperback
Published in Jul 2012
Publisher Packt
ISBN-13 9781849685481
Length 368 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
John Heaton John Heaton
Author Profile Icon John Heaton
John Heaton
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Business Intelligence Cookbook: A Project Lifecycle Approach Using Oracle Technology
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
1. Preface
1. Defining a Program FREE CHAPTER 2. Establishing the Project 3. Controlling the Project 4. Wrapping Up the Project 5. The Blueprint 6. Analyzing the Requirements 7. Architecture and Design 8. Analyzing the Sources 9. Analyzing the Data 10. Constructing the Data Model 11. Defining the ETL/ELT 12. Enhancing the Data 13. Optimizing the Access 14. Security

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

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image