Business Rules: The Promise of Data Warehousing. In the Beginning: Formulating Business Rules The Business Objectives The Promise (Data Warehousing) –

Slides:



Advertisements
Similar presentations
Entity Relationship Diagrams
Advertisements

Database Design: ER Modelling
Introduction to Databases
Prentice Hall, Database Systems Week 1 Introduction By Zekrullah Popal.
Managing Data Resources
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 BGS Customer Relationship Management Chapter 6 Technology and Data Platforms Chapter 6 Technology and Data Platforms Thomson Publishing 2007 All Rights.
File Systems and Databases
1 1 File Systems and Databases Chapter 1 The Worlds of Database Systems Prof. Sin-Min Lee Dept. of Computer Science.
Lecture Fourteen Methodology - Conceptual Database Design
Recording / Financing Fixed Asset Acquisition Human Resources Purchasing Revenue Traditional files approach: separate systems (Legacy Systems) Expenditure.
System Analysis and Design
BUSINESS DRIVEN TECHNOLOGY
Methodology Conceptual Database Design
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
1 1 File Systems and Databases Chapter 1 Prof. Sin-Min Lee Dept. of Computer Science.
Configuration Management
Database Environment 1.  Purpose of three-level database architecture.  Contents of external, conceptual, and internal levels.  Purpose of external/conceptual.
By N.Gopinath AP/CSE. Why a Data Warehouse Application – Business Perspectives  There are several reasons why organizations consider Data Warehousing.
Database Systems: Design, Implementation, and Management Ninth Edition
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
Bina Nusantara 2 C H A P T E R INFORMATION SYSTEM BUILDING BLOCKS.
Week 1 Lecture MSCD 600 Database Architecture Samuel ConnSamuel Conn, Asst. Professor Suggestions for using the Lecture Slides.
Data at the Core of the Enterprise. Objectives  Define of database systems.  Introduce data modeling and SQL.  Discuss emerging requirements of database.
Chapter 1: Business Intelligence and its Impacts
Database Design - Lecture 1
DBS201: DBA/DBMS Lecture 13.
6-1 DATABASE FUNDAMENTALS Information is everywhere in an organization Information is stored in databases –Database – maintains information about various.
MSF Requirements Envisioning Phase Planning Phase.
1 Introduction An organization's survival relies on decisions made by management An organization's survival relies on decisions made by management To make.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 1 DATABASE SYSTEMS (Cont’d) Instructor Ms. Arwa Binsaleh.
1 CSBP430 – Database Systems Chapter 1: Databases and Database Users Mamoun Awad College of Information Technology United Arab Emirates University
CHAPTER 5 Data and Knowledge Management. CHAPTER OUTLINE 5.1 Managing Data 5.2 Big Data 5.3 The Database Approach 5.4 Database Management Systems 5.5.
Chapter 3 Network and System Design. Objectives After reading the chapter and reviewing the materials presented the students will be able to: Understand.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Database System Concepts and Architecture
BGS Customer Relationship Management Chapter 6 Technology and Data Platforms Chapter 6 Technology and Data Platforms Thomson Publishing 2007 All Rights.
Chapter 1 In-lab Quiz Next week
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
Organizing Data and Information AD660 – Databases, Security, and Web Technologies Marcus Goncalves Spring 2013.
1 Welcome: To the second learning sequence “ Data Base (DB) and Data Base Management System (DBMS) “ Recap : In the previous learning sequence, we discussed.
Databases and Database Management Systems
HNDComputing – DeMontfort University  DeMontfort University 2011 Database Fundamentals wk2 Database Design ConceptsDatabase Design Concepts Database Design.
© 2007 by Prentice Hall 1 Introduction to databases.
Lecturer: Gareth Jones. How does a relational database organise data? What are the principles of a database management system? What are the principal.
Data Warehouse. Design DataWarehouse Key Design Considerations it is important to consider the intended purpose of the data warehouse or business intelligence.
1.file. 2.database. 3.entity. 4.record. 5.attribute. When working with a database, a group of related fields comprises a(n)…
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
MANAGING DATA RESOURCES ~ pertemuan 7 ~ Oleh: Ir. Abdul Hayat, MTI.
1 CSE 2337 Introduction to Data Management Textbook: Chapter 1.
Database Systems Database Systems: Design, Implementation, and Management, Rob and Coronel.
Chapter 2 Database Environment.
1 Chapter 2 Database Environment Pearson Education © 2009.
Lecture On Introduction (DBMS) By- Jesmin Akhter Assistant Professor, IIT, Jahangirnagar University.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 1 Database Systems.
OUTCOMES OBJECTIVES FUNCTIONS ACTIONS TERRITORIES LOCATIONS MARKET SEGMENTS TIME LINESCHALLENGE IMPACT RESOURCESACTIVITIESCHANNELS RELATIONS PARTNERS CUSTOMERS.
Chapter 8: Data Warehousing. Data Warehouse Defined A physical repository where relational data are specially organized to provide enterprise- wide, cleansed.
Foundations of information systems : BIS 1202 Lecture 4: Database Systems and Business Intelligence.
Managing Data Resources File Organization and databases for business information systems.
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
What is it ? …all via a single, proven Platform-as-a-Service.
MANAGING DATA RESOURCES
Chapter 1 Database Systems
File Systems and Databases
Database Systems Chapter 1
Data Warehousing Data Model –Part 1
Database (DB) and Database Management System (DBMS)
The Database Environment
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Presentation transcript:

Business Rules: The Promise of Data Warehousing

In the Beginning: Formulating Business Rules The Business Objectives The Promise (Data Warehousing) – What Exactly is Data Warehousing? – How Data Warehousing overcomes those obstacles The Map – Planning – Discover Business Needs – Model the Business The Business Rules The Future – Active Data Warehousing The Conclusion – Delivering on the Promise

Key Business Objectives Improve Business Efficiency Flexibility to develop new revenue streams Improve the Customer Experience Promote brand strength and market position

Business Imperatives Must get closer to the customer ! Must improve productivity of knowledge workers ! Must be able to integrate new technologies quickly ! Must become flexible to facilitate rapid market changes ! BUSINESS RULES are a foundational element of achieving these objectives.

Obstacles to Meeting Business Objective

Getting the Wrong Answer...

The Solution: A Single Source...

The Problem: Incomplete Answers

The Solution: Integrated Historical Data

The Promise of Data Warehousing One Corporate Version of the Truth – Speaking one language – No dueling numbers Single Source – One stop shopping – Saves user time by eliminating need to obtain multiple interfaces and files Accessibility and timeliness of information – Allows End-User access without IT dependence – Reporting takes minutes or hours not weeks or months

The Promise of Data Warehousing Cost avoidance – Multiple applications access the same data – Offloads Legacy systems for DSS reporting – Avoids development of standalone applications to address specific data needs – Eliminates redundant systems Infrastructure to integrate future corporate acquisitions and data growth – Platform proven, highly scalable Ability to anticipate and respond to changes in the competitive marketplace

Attributes of the Optimum Solution

What is an Enterprise Data Warehouse?

Business Analysis – Which Environment supports your Business Objectives?

Data Warehouse Core Issues Scalability – Ability to meet increasing demands for: Data Volumes Concurrent Users Complex Queries Accessibility – Ability to ask any question, at any time, of any data – Currency of data to meet demands Manageability – Low maintenance requirements – Integrated, parallel utilities

Where Do I Start?

Types of Business Rules Constrains information on the behalf of the business event – Constraints are mandatory – Guidelines are suggestive Enables other action on behalf of the business event – Action enabling rules Creates new information on the behalf of the business event – Computations – Inferences

Definitions Term: A noun or noun phrase with an agreed upon definition – Customer – Credit Rating Code – Female – Days of the American work week Fact: A statement that connects terms, through prepositions and verbs, into sensible business relevant observations – Customer can place order – Order is for line item – Line item is for order – customer qualifies for customer credit rating code

Definitions and Examples of Rules

Model the Business Business information MODELING – Determined by BUSINESS RULES & VISION – The ER MODEL NEVER changes UNLESS Underlying way of doing business changes, or Adding NEW subject areas to MODEL will not impact existing model

What is a Logical Data Model (LDM)? A Logical Data Model (LDM) is the result of information modeling A LDM is a diagram which shows: – Entities (data of importance to the organization) – Attributes (properties of the data) – Relationships between entities LDMs are completely technology independent of any particular database or hardware platform A schematic view of the environment and a mock-up representation of something in the real world.

Opportunity Analysis

Information Evolution in an Active Data Warehouse Environment

What Drives Active Data Warehouse Evolution? Customer Relationship Management is the primary relationship driving the next generation of data warehousing… business rules are critically important in a CRM environment.

A Complex Operational Topology

An Enterprise Active Warehouse