logo for information-management-architect.com
leftimage for information-management-architect.com

Solution Delivery Methodology

Improve efficiency with David Bowman’s information management guidelines for data warehouse solution delivery methodology

This site is designed for Information Technology professionals who need  to improve effectiveness and require guidance and direction to help teams consistently produce error free results.

It provides information management guidelines for a data warehouse solution delivery methodology plus it provides deliverable templates which can be used to jump-start a project.

What is a Data Warehouse Solution?


data warehouse architecture

Information management solutions are usually involved with some, or all of, the following:
  • Extracting data from operational source systems;
  • Transforming data as required to ensure consistency;
  • Loading data into a data warehouse or some form of storage optimized for efficient storage;
  • Extracting data from the data warehouse;
  • Loading departmental data marts optimized for reporting and analytics; and
  • Some form of reporting tool architecture e.g. universe design or some middle ware design to insulate users from the data warehouse.
Information is a valuable corporate asset and getting the right information, to the right people at the right time is a key management objective.

Achieving this objective requires robust technology, optimal data architecture and a data warehouse solution delivery methodology based  on industry best practices. 
Project Planning
  • Should provide sufficient detail to commence analysis;
  • Should ensure mutual understanding of roles, responsibilities, project tasks and deliverables;
  • Should be completed by a Solution Architect, or Technical Lead;
  • Should not exceed two weeks;
  • Should deliver a data warehouse project implementation plan;
  • Should deliver a configuration management plan;
  • Should deliver a project software quality assurance plan;
  • Should be approved before commencing analysis; and
  • Should ensure that approved project plan is placed under under version control.
Requirements Analysis
  • Should be based on an approved project implementation plan;
  • Should provide sufficient detail to commence architecture and design;
  • Should ensure mutual understanding of data warehouse requirements;
  • Should be completed by some combination of Solution Architect, Data Architect, Data Integration Architect and Business Intelligence Architect;
  • Should deliver data profiles of each source system;
  • Should deliver a requirements specification;
  • Should specify data requirements;
  • Should specify requirements for data conversion projects;
  • Should specify requirements for data warehouse security;
  • Should specify data warehouse requirements;
  • Should commence the requirements traceability matrix;
  • Should be approved before commencing Architecture and Design; and
  • Should ensure that approved requirements specification is placed under version control.
Architecture and Design Build and Test
  • Should commence upon approval of project implementation plan, requirements specification, architecture specification, detail source to target mappings and detail design specifications;
  • Should deliver code required to extract data from the source systems and load it into a temporary staging area;
  • Should deliver an automated process to extract data from source systems;
  • Should deliver data base scripts for views, indexes, synonyms and aggregations;
  • Should deliver programs that load the data warehouse with source data from staging areas;
  • Should deliver processes to clean the data in the staging area and ensure that it is fully consistent with business rules;
  • Should deliver programs and scripts that ensure backup/recovery, access control and archiving;
  • Should deliver query manager to support business intelligence requirements;
  • Should deliver pre-developed queries and reports and user access tools to access information;
  • Should deliver a set of repeatable system integration, volume and aggregation tests;
  • Should deliver a set of repeatable manual reconciliation tasks;
  • Should deliver routines required to extract source data, transform it to appropriate structures, and load to a data warehouse and/or to dimensional data marts;
  • Should deliver unit test cases;
  • Should deliver routines required to move data per the interface specifications;
  • Should deliver error handling routines to meet detail design specifications;
  • Should test all code to ensure it works properly which should include verifying all code for errors, bugs and interoperability;
  • Should deliver unit test plan and unit test results; and
  • Should deliver a fully tested solution that meets requirements and should involve:
Solution Delivery Methodology for Quality Assurance
  • Should commence upon approval of approved build and test cycle;
  • Should ensure that the solution meets design specifications;
  • Should deliver approved quality assurance results based on information management guidelines for software testing lifecycle and software testing strategies;
  • Should ensure that the quality assurance team follows software testing best practices;
  • Should ensure that information management guidelines for software testing procedures are followed;
  • Should be approved before commencing user acceptance testing and
  • Should ensure that the approved quality assurance test results are available for migration to production.
User Testing
  • Should commence upon approval of approved quality assurance test;
  • Should be conducted by a client defined user acceptance test team;
  • Should ensure that the solution meets requirements;
  • Should deliver approved user test results based on information; and management guidelines for software testing lifecycle and software testing strategies.
Transition to Production
  • Should commence upon approval of approved user acceptance test;
  • Should migrate the solution into a production environment via a transition to production process based on an approved release plan
  • Should load initial data;
  • Should be the responsibility of a release team;
  • Should deliver an object migration plan documenting details concerning the migration of objects from one environment to another; and
  • Should deliver an object migration inventory documenting all objects migrated from one environment to another.
Summary...

Information is a valuable corporate asset and getting the right information, to the right people at the right time is a key management objective.

Achieving this objective requires robust technology, optimal data architecture and a data warehouse solution delivery methodology based on industry best practices.

This site provided information management guidelines for a data warehouse solution delivery methodology plus it provided deliverable templates which can be used to jump-start a project.