Chapter 4-Intro to DW Architecture Flashcards

1
Q

What is the Value of Architecture

A

-Communication
-Planning
-Flexibility and Maintenance
-Learning
-Productivity and Reuse

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Communication

A

-excellent communication tool at several levels, providing a way to help management understand the magnitude and complexity of project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Planning

A

-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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Flexibility and Maintenance

A

-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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Learning

A

-Arch is an important role as documentation for the system
- can help new team members get up to speed with components contents and connections

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Productivity and Reuse

A

-Takes advantage of tools and metadata
-Helps automate parts of the warehouse process
- makes it easier to understand warehouse process and database contents

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Arch Framework: Column headings

A

-Data
-technical
-Infrastructure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Arch Framework: Rows

A

-Business requirements
-Arch Models
-Detailed models
-Implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Columns: Data

A
  • 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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Column: Tech Arch Area

A

Answers the “How” how we get data at this source

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is tech Arch made up of?

A

-Tools
-Utilities
-Code
-Places where data is moved from and to
-Brings Warehouse to life Using two areas, back and front Room

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Back Room

A

Responsible for gathering and preparing the data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Front Room

A

Responsible for delivering the data to the user community

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Columns: Infrastructure Arch Area

A

-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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Defining Rows: Business Requirement Level

A
  • explicitly non-technical
    Analyst should understand the major business forces and boundary conditions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Defining Rows: Arch Models Level

A
17
Q

Row: Arch Model Level

A

-Proposes major components of arch that must be available
-all types of tech must be named specifically and argued hoe tech will fit together
-It addresses whether tech components can communicate with each other

18
Q

Rows: Detailed Models Level

A

-functional specifications of each of the arch components ( Very Detail)
-Include enough info to serve as a reliable implementation guide for the team member or contractor
-Help check whether implementation is complete and conforms to the specification

19
Q

Rows: Implementation Level

A

-response to detailed models
-code software deliverable

20
Q

Logical Model

A

-Vision of what the warehouse should be- Ideal that we would like to attain

21
Q

Characteristics of Logical Model

A

-Simple
-Understandable
-solves the problem
-Top row of Framework

22
Q

Physical Models

A

-Face the real world
-Some of our business requirements might rely on data
-reflect changes that were made to the logical model to get to work
-Create bottom rows of the framework

23
Q

Framework Summary

A
  • Breaks arch task into manageable pieces
  • 3 Columns- Data, tech and infrastructure
24
Q

Services

A

-functions needed to accomplish the required tasks of the warehouse

25
Q

Data Stores

A

Temporary or permanent landing places for data

26
Q

Key Tech Arch Features

A

-metadata Driven
-Flexible Service Layers
-Caveats

27
Q

Metadata Driven

A
  • Drives the warehouse
    -Provides flexibility by buffering components
    -catalog holds mapping info from source target
    -Crucial to have a single source for metadata within DW
28
Q

Flexibel Service

A

Data Staging services and data query services add flexibility of arch

29
Q

Caveats

A

-not all tools and services support of metadata catalog
-phased approach to implementing the arch recommended
-