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 an effective risk register


Project risks are a fact of life on any software development project. The key is to identify and quantify the risks in a way that is easy to understand and communicate. A method to achieve this is FMEA—Failure Mode and Effect Analysis. A derivative of this is RFMEA—Risk Failure Mode and Effect Analysis.

Getting ready

Before starting, it is important to have a list of all the potential risks related to your project. An easy way to do this is to solicit information from all the team members and stakeholders. Do not try and categorize or justify the risk; purely collect the information and record the risk.

How to do it...

The risk register is key to the project. It is important to keep this a living document.

  1. 1. Open your Project Control Register and create a new tab called RFMEA:

  2. 2. Create your basic headings for your RFMEA or Risk Log:

    • a. Risk ID is a unique number assigned to each risk.

    • b. Risk event is a description of the risk.

    • c. Likelihood is the probability...