Business Intelligence

Business Intelligence


Contributors:


Leonardo Legorreta
Jerry Valentine


Proposal for cover art and water mark
Proposal for cover art and water mark
Wikibook Development Stages
Sparse text 0% Developing text 25% Maturing text 50% Developed text 75% Comprehensive text 100%

Prologue 100% developedEdit

Introduction 100% developedEdit

Understanding Strategy 75% developed  as of June 1, 2009Edit

Frame Building - One frame at a time 100% developed  as of June 4, 2009Edit

Framing stage 75% developed  as of June 4, 2009Edit

  • Clarify strategy 50% developed  as of June 1, 2009
    • Purpose: Understand the decision maker's frame of reference
    • Input: List of BI system users, administrators and decision makers; understanding of strategy and frames
    • Activities: Interview decision makers to understand their strategy, from their frame of referencve
    • Outputs: Users' strategies
    • Documentation: Detailed notes on users strategies
  • Framing the strategy 25% developed  as of June 2, 2009
    • Purpose: this step demonstrates how to turn decision maker strategy into diagrams. Each strategy diagram provides a slightly different view of the strategy. The causal link map and the strategy map provide ways to test strategic effectiveness and operational effectiveness. After testing to make sure that the theory behind the strategy is sound (testing the causal link map) the next stage is to use the strategy map to develop KPI's that will fill the dashboard.
    • Input: List of decision makers; Decision makers' business knowledge
    • Activities: Interview decision makers; Create Strategy Diagrams
    • Outputs: Formalized decision maker knowledge
    • Documentation: Strategy Diagrams
  • Test Causal Link Map 50% developed  as of June 2, 2009
    • Purpose: Test the validity of the causal links in the strategy diagrams
    • Input: Causal link map
    • Activities: Turn the causal link map into a theory and test hypotheses deduced from the theory
    • Outputs: Evidence demonstrating the validity of the theory behind the strategy diagrams
    • Documentation: Validated Strategy Diagrams
  • Create and disseminate scorecard 25% developed  as of June 2, 2009
    • Purpose: To create the frame scorecard based on the strategy map
    • Input: Strategy Diagram, Strategy Map the most important
    • Activities: Create and disseminate scorecard
    • Outputs: Slice of strategy map for theme or decision maker (Scorecard)
    • Documents: Scorecard
  • Distill KPIs, dimensions and budgets from scorecard 25% developed  as of June 2, 2009
    • Purpose: To develop KPIs, dimensions and budgets for the reports and dashboard
    • Input: Scorecards
    • Activities: Using the scorecard to list KPIs, dimensions and budgets
    • Outputs: List of dimensions, facts and budgets
    • Documentation: Dimensions, facts and budgets
  • Documentation of sources data for frame 50% developed
    • Purpose:
    • Input: KPIs, dimensions and budgets
    • Activities: Identifying the data sources necessary to populate the dashboard and reports with data
    • Outputs: List of dimensions, facts and budgets
    • Documentation: The output is the documentation of data sources for the frame.
  • Data extraction architecture for frame 25% developed  as of June 2, 2009
    • Purpose:
    • Input: Scorecard, KPIs, budgets, dimensions and data sources
    • Activities: Create data extraction architecture for frame
    • Outputs: Diagrams and explanations of data extraction architecture
    • Documentation: Data extraction and integration architecture and metadata
  • Data Mart Data Model 25% developed  as of June 2, 2009
    • Purpose:
    • Input: List of KPIs, Dimensions and Budgets
    • Activities: Create an ERD for the frame's data mart
    • Outputs: ERD and Relational data model
    • Documentation: ERD and Relational data model diagrams
  • Frame Architecture 50% developed  as of June 2, 2009
    • Purpose:
    • Input: Framework architecture and scorecards
    • Activities: Diagram frame architecture (Legorreta and Valentine)
    • Outputs: Frame architecture - conceptual, logical and physical
    • Documentation: Frame Architecture
  • Project charter 50% developed  as of June 2, 2009
    • Purpose:
    • Input: All documentation
    • Activities: Consolidate Documentation from planning stage
    • Outputs: Acceptance of project charter by frame stakeholders
    • Documentation: Project charter

Frame PrototypeEdit

  • Create Dashboard prototype 25% developed  as of June 2, 2009
    • Purpose: this step produces a dashboard for the frame. The dashboard serves as the central report for the frame. In this sense the reporting system works like a hub and spoke system. The hub is the dashboard. Each spoke emanates from a KPI in order to provide detailed information.
    • Input: KPIs, dimensions and budgets
    • Activities: Create dashboard prototype
    • Outputs: Dashboard prototype
    • Documentation: Dashboard prototype documentation
  • Evaluate Dashboard Prototype 50% developed  as of June 2, 2009
    • Purpose: This step requires the analysis of the dashboard to make sure it meets all criteria. The criteria are broadly divided into form and function. A well-formed dashboard presents data that is appealing to the eye and easily understood. A functional dashboard allows the decision maker to evaluate strategic and operational effectiveness
    • Input: Dashboard prototype
    • Activities: Evaluate dashboard prototype
    • Outputs: Acceptable dashboard prototype
    • Documentation: Evaluation of dashboard prototype against criteria
  • Report prototypes and documentation 25% developed  as of June 2, 2009
    • Purpose:
    • Input: Dashboard prototype and decision maker input
    • Activities: Create report prototypes
    • Outputs: Report prototypes
    • Documentation: Report prototype documentation
  • ETL system 25% developed  as of June 2, 2009
    • Purpose:
    • Input: Data extraction architecture
    • Activities: Create ETL infrastructure
    • Outputs: ETL infrastructure
    • Documentation: ETL system
  • Prototype data mart 25% developed  as of June 2, 2009
    • Purpose:
    • Input: Metadata, data architecture and list of facts and dimensions
    • Activities: Create ERD and data mart from ERD
    • Outputs: ERD, Physical Data Mart
    • Documentation: ERD Diagram and physical data mart
  • Link dashboard and reports to data mart 25% developed  as of June 2, 2009
    • Purpose:
    • Input: Report prototypes, data mart prototype and information architecture
    • Activities: Bring technical infrastructure together into one system
    • Outputs: BI Frame Prototype
    • Documentation: Finalized Frame BI Prototype
  • Consolidate project documentation 25% developed  as of June 2, 2009
    • Purpose: To complete and consolidate project documentation
    • Input: All Documentation
    • Activities: Consolidate Documentation from development
    • Outputs: Project documentation
    • Documentation: Project documentation
  • Prototype Acceptance 25% developed  as of June 2, 2009
    • Purpose: Determine if frame meets user needs
    • Input: Prototype
    • Activities: Allow decision makers to test prototype
    • Outputs: Completed Frame Prototype
    • Documentation: Acceptance of prototype

ProductionEdit

  • Align project with Information Technology Policies and Regulations 25% developed  as of June 2, 2009
    • Purpose: To align the frame with IT production specifications
    • Input: Project charter and documentation
    • Activities: Align project to IS policies and regulations
    • Outputs: Project and policy alignment
    • Documentation: Production specification: project alignment with policies and regulations
  • Produce dashboard 25% developed  as of June 2, 2009
    • Purpose: Improve the reports and make sure they meets organization IS guidelines
    • Input: Dashboard prototype
    • Activities: Produce dashboard according to production specifications
    • Outputs: Finalized Dashboard Documentation and Manual dashboard
    • Documentation: Dashboard Documentation and Manual dashboard
  • Produce reports 25% developed  as of June 2, 2009
    • Purpose: Improve the reports and make sure they meets organization IS guidelines
    • Input: Report prototype
    • Activities: Produce reports according to production specifications
    • Outputs: Finalized reports
    • Documentation: Report Documentation and Manual
  • Produce data mart 25% developed  as of June 2, 2009
    • Purpose: Improve the data mart and make sure it meets organization IS guidelines
    • Input: Data mart prototype
    • Activities: Produce data mart according to production specifications
    • Outputs: Finalized data mart
    • Documentation: Data mart Documentation and Manual
  • Produce ETL system 25% developed  as of June 2, 2009
    • Purpose: Improve the ETL system and make sure it meets organization IS guidelines
    • Input: ETL system
    • Activities: Produce ETL system according to production specifications
    • Outputs: Finalized ETL system
    • Documentation: ETL system Documentation and Manual
  • Link dashboard and reports to data mart 25% developed  as of June 2, 2009
    • Purpose: Bring the infrastructure of the frame together and complete the frame
    • Input: Data mart, reports and dashboard
    • Activities: Bring technical infrastructure together into one system
    • Outputs: Finalized BI Frame
    • Documentation: Finalized BI system, including technical infrastructure, documentation and manuals
  • Frame Testing and acceptance 25% developed  as of June 2, 2009
    • Purpose: to determine if users accept the frame
    • Input: BI Frame
    • Activities: Decision makers test and accept prototype
    • Outputs: Completed BI System
    • Documentation: User acceptance of BI Frame


Works Cited
Last modified on 25 June 2010, at 18:33