Chapter 4-Intro to DW Architecture Flashcards
What is the Value of Architecture
-Communication
-Planning
-Flexibility and Maintenance
-Learning
-Productivity and Reuse
Communication
-excellent communication tool at several levels, providing a way to help management understand the magnitude and complexity of project
Planning
-Provides cross check for the project plan
-Brings all the architecture details in one place and prescribes how they fit together
-uncovers tech requirements and dependencies that do not come out as part of the planning process for a specific project
Flexibility and Maintenance
-Helps anticipating as many issues as possible
-semantic layer added to the warehouse and used in processes to create, navigate and maintain the warehouse
-Layer makes DW flexible and easier to maintain
Learning
-Arch is an important role as documentation for the system
- can help new team members get up to speed with components contents and connections
Productivity and Reuse
-Takes advantage of tools and metadata
-Helps automate parts of the warehouse process
- makes it easier to understand warehouse process and database contents
Arch Framework: Column headings
-Data
-technical
-Infrastructure
Arch Framework: Rows
-Business requirements
-Arch Models
-Detailed models
-Implementation
Columns: Data
- The “what” DW is all about
-List of data that is important to the business
-Data stores that make up warehouse environment
-Design of physical and logical data models
-Defines granularity, volume, and timing of the data at various oints in the warehouse
Column: Tech Arch Area
Answers the “How” how we get data at this source
What is tech Arch made up of?
-Tools
-Utilities
-Code
-Places where data is moved from and to
-Brings Warehouse to life Using two areas, back and front Room
Back Room
Responsible for gathering and preparing the data
Front Room
Responsible for delivering the data to the user community
Columns: Infrastructure Arch Area
-Platforms that host the data and processes
-hardware and the operating-level software
-needs to be examined carefully to make sure any special needs are addressed
Defining Rows: Business Requirement Level
- explicitly non-technical
Analyst should understand the major business forces and boundary conditions