Foundations of Business Intelligence: Databases and Information Management
Foundations of Business Intelligence: Databases and Information Management
Foundations of
Business Intelligence:
Databases and
Information
Management
6.1 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
LEARNING OBJECTIVES
A computer system
organizes data in a
hierarchy that starts with the
bit, which represents either
a 0 or a 1. Bits can be
grouped to form a byte to
represent one character,
number, or symbol. Bytes
can be grouped to form a
field, and related fields can
be grouped to form a record.
Related records can be
collected to form a file, and
related files can be
organized into a database.
Figure 6-1
6.5 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
Organizing Data in a Traditional File Environment
The use of a traditional approach to file processing encourages each functional area in a corporation to
develop specialized applications and files. Each application requires a unique data file that is likely to be a
subset of the master file. These subsets of the master file lead to data redundancy and inconsistency,
processing inflexibility, and wasted storage resources.
Figure 6-2
6.7 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
• Database
• Collection of data organized to serve many applications by
centralizing data and controlling redundant data
• Database management system
• Interfaces between application programs and physical data files
• Separates logical and physical views of data
• Solves problems of traditional file environment
• Controls redundancy
• Eliminates inconsistency
• Uncouples programs and data
• Enables organization to central manage data and data security
A single human resources database provides many different views of data, depending on the information
requirements of the user. Illustrated here are two possible views, one of interest to a benefits specialist
and one of interest to a member of the company’s payroll department.
Figure 6-3
6.9 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
• Relational DBMS
• Represent data as two-dimensional tables called relations or files
• Each table contains data on entity and attributes
• Table: grid of columns and rows
• Rows (tuples): Records for different entities
• Fields (columns): Represents attribute for entity
• Key field: Field used to uniquely identify each record
• Primary key: Field in table used for key fields
• Foreign key: Primary key used in second table as look-up field to
identify records from original table
A relational database organizes data in the form of two-dimensional tables. Illustrated here are tables for
the entities SUPPLIER and PART showing how they represent each entity and its attributes.
Supplier_Number is a primary key for the SUPPLIER table and a foreign key for the PART table.
Figure 6-4A
6.11 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
Figure 6-4B
6.12 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
The select, project, and join operations enable data from two different tables to be combined and only
selected attributes to be displayed.
Figure 6-5
6.14 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
Figure 6-6
Microsoft Access has a
rudimentary data dictionary
capability that displays
information about the size,
format, and other
characteristics of each field
in a database. Displayed
here is the information
maintained in the SUPPLIER
table. The small key icon to
the left of Supplier_Number
indicates that it is a key field.
Illustrated here are the SQL statements for a query to select suppliers for parts 137 or 150. They produce a
list with the same results as Figure 6-5.
Figure 6-7
6.18 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
An Access Query
Illustrated here is how the query in Figure 6-7 would be constructed using query-building tools in the
Access Query Design View. It shows the tables, fields, and selection criteria used for the query.
Figure 6-8
6.19 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
• Designing Databases
• Conceptual (logical) design: abstract model from business
perspective
• Physical design: How database is arranged on direct-access
storage devices
• Design process identifies
• Relationships among data elements, redundant database
elements
• Most efficient way to group data elements to meet business
requirements, needs of application programs
• Normalization
• Streamlining complex groupings of data to minimize redundant
data elements and awkward many-to-many relationships
An unnormalized relation contains repeating groups. For example, there can be many parts and suppliers
for each order. There is only a one-to-one correspondence between Order_Number and Order_Date.
Figure 6-9
6.21 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
After normalization, the original relation ORDER has been broken down into four smaller relations. The
relation ORDER is left with only two attributes and the relation LINE_ITEM has a combined, or
concatenated, key consisting of Order_Number and Part_Number.
Figure 6-10
6.22 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
• Entity-relationship diagram
• Used by database designers to document the data model
• Illustrates relationships between entities
• Distributing databases: Storing database in more than
one place
• Partitioned: Separate locations store different parts of database
• Replicated: Central database duplicated in entirety at different
locations
An Entity-Relationship Diagram
This diagram shows the relationships between the entities ORDER, LINE_ITEM, PART, and SUPPLIER that
might be used to model the database in Figure 6-10.
Figure 6-11
6.24 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
• Distributing databases
• Two main methods of distributing a database
• Partitioned: Separate locations store different parts of
database
• Replicated: Central database duplicated in entirety at
different locations
• Advantages
• Reduced vulnerability
• Increased responsiveness
• Drawbacks
• Departures from using standard definitions
• Security problems
6.25 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
The Database Approach to Data Management
Distributed Databases
There are alternative ways of distributing a database. The central database can be partitioned (a) so that each remote
processor has the necessary data to serve its own local needs. The central database also can be replicated (b) at all remote
locations.
Figure 6-12
6.26 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
Using Databases to Improve Business Performance and Decision Making
• Data warehouse:
• Stores current and historical data from many core operational
transaction systems
• Consolidates and standardizes information for use across
enterprise, but data cannot be altered
• Data warehouse system will provide query, analysis, and reporting
tools
• Data marts:
• Subset of data warehouse
• Summarized or highly focused portion of firm’s data for use by
specific population of users
• Typically focuses on single subject or line of business
The data warehouse extracts current and historical data from multiple operational systems inside the
organization. These data are combined with data from external sources and reorganized into a central
database designed for management reporting and analysis. The information directory provides users
with information about the data available in the warehouse.
Figure 6-13
6.29 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
Using Databases to Improve Business Performance and Decision Making
• Business Intelligence:
• Tools for consolidating, analyzing, and providing access
to vast amounts of data to help users make better
business decisions
• E.g., Harrah’s Entertainment analyzes customers to
develop gambling profiles and identify most profitable
customers
• Principle tools include:
• Software for database query and reporting
• Online analytical processing (OLAP)
• Data mining
Business Intelligence
Figure 6-14
A series of analytical tools
works with data stored in
databases to find patterns
and insights for helping
managers and employees
make better decisions to
improve organizational
performance.
Figure 6-15
The view that is showing is
product versus region. If
you rotate the cube 90
degrees, the face that will
show is product versus
actual and projected sales. If
you rotate the cube 90
degrees again, you will see
region versus actual and
projected sales. Other views
are possible.
• Data mining:
• More discovery driven than OLAP
• Finds hidden patterns, relationships in large databases and
infers rules to predict future behavior
• E.g., Finding patterns in customer data for one-to-one
marketing campaigns or to identify profitable customers.
• Types of information obtainable from data mining
• Associations
• Sequences
• Classification
• Clustering
• Forecasting
• Predictive analysis
• Uses data mining techniques, historical data, and
assumptions about future conditions to predict
outcomes of events
• E.g., Probability a customer will respond to an offer or
purchase a specific product
• Text mining
• Extracts key elements from large unstructured data sets
(e.g., stored e-mails)
• Web mining
• Discovery and analysis of useful patterns and information
from WWW
• E.g., to understand customer behavior, evaluate
effectiveness of Web site, etc.
• Techniques
• Web content mining
• Knowledge extracted from content of Web pages
• Web structure mining
• E.g., links to and from Web page
• Web usage mining
• User interaction data recorded by Web server
Figure 6-16
6.39 © 2010 by Prentice Hall
Management Information Systems
Chapter 6 Foundations of Business Intelligence: Databases
and Information Management
Managing Data Resources