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

Creating a cyclical build and test process


Defects and enhancements are required to be placed into releases and environments. To enable this, a cyclical build and test process is required.

Getting ready

Before starting, it is important to determine how often you require builds. The builds should be frequent enough to show progress, but not so frequent that they add unnecessary overhead to the project. To start with, a frequency of once a week should be sufficient. You can increase or decrease your build cycle as required. It is important to get into the build cycle directly from the start of the project. Releases into the test environment can be more frequent than releases into production. This enables components, defects, and enhancements to be reviewed more regularly. Production releases are a culmination of test releases, and should be on a scheduled basis so that stakeholders are aware and expecting releases.

How to do it...

  1. 1. Open the Project Control Register.

  2. 2. Go to the RTM tab and...