VisibleForum.com

[MCesino]

This strategy briefing describes tools and methods for developing and documenting a data warehouse architecture for strategic information management.

"Engineering" a data warehouse is a lot like "engineering" a physical warehouse. Both involve a rigorous development cycle and require the right tools. A building is constructed using architectural diagrams (blueprints) that clearly depict the building's infrastructure (structural elements, walls, electrical wiring, plumbing, etc.). Visible builds data warehouses from architectural models of enterprise infrastructure (policies, goals, measures, critical success factors, etc.).

Blueprints are also used to enlarge a building or make any significant modifications. Without a diagram of the infrastructure, such changes are quite difficult and very costly and can even be dangerous. It is the same with data warehouses. Visible first updates an enterprise's data warehouse architecture model so that it reflects changes (e.g., new performance measures, product lines, or services) and then modifies the data warehouse to support the changed enterprise.

Data warehouse engineering is easier and less costly when based upon an accurate architectural model of the enterprise. Further, a data warehouse is easier to use and consistently produces desired outcomes when decision-makers have access to an enterprise architecture (metadata) that accurately reflects enterprise infrastructure.

This strategy briefing and its associated forum postings are designed to help you now in your endeavor to build a more effective Enterprise Architecture more efficiently. Please feel free to learn from other postings and share your experiences through your own postings via the Visible Forum.