Scribd
Upload
29 views

Database Management Systems

1. Data modeling is a process used to define and analyze data requirements to support business processes within organizational information systems. 2. Data models provide a framework for defining and formatting data within information systems. 3. A data warehouse is a system for reporting and data analysis that integrates data from multiple sources into a single database for analysis.

Uploaded by

shahid mushtaq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
29 views

Database Management Systems

1. Data modeling is a process used to define and analyze data requirements to support business processes within organizational information systems. 2. Data models provide a framework for defining and formatting data within information systems. 3. A data warehouse is a system for reporting and data analysis that integrates data from multiple sources into a single database for analysis.

Uploaded by

shahid mushtaq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 19

Database

Management Systems

Data Modeling And Data


Warehouse
An Overview
• Data modeling is a process used to define and
analyze data requirements needed to support the
business processes within the scope of
corresponding information systems in organizations.

• professional data modelers working closely with


business stakeholders, as well as potential users of
the information system.
Data models
• Data models provide a framework for data to be
used within information systems by providing
specific definition and format.
Data modeling Schema
The ANSI/SPARC three level architecture
Conceptual schema
• First-cut model
• A high-level description of a business's informational
needs.
• Main concepts and the main relationships
• It hides the internal details of physical storage and
targets
Logical & Physical
schema
• A data model of a specific problem domain
expressed independently of a particular database
management product
• Consists of descriptions of tables, columns, object-
oriented classes, and XML tags
• Describes the physical means used to store data.
Data modeling process
Modeling methodologies
• Bottom-up models or View Integration models are
often the result of a reengineering effort.
• start with existing data structures forms, fields on
application screens, or reports.

• Top-down logical data models, on the other hand,


are created in an abstract way by getting
information from people who know the subject
area.
• The model serves as a reference point or template.
Entity relationship diagrams
• The actual model is frequently called "Entity
relationship model", because it depicts data in
terms of the entities and relationships described in
the data.

• Bachman diagrams
• Barker's notation
• Chen's Notation
• Data Vault Modeling
Generic data modeling
• A generic data model assumes as little as possible
about the field of data
• Generic in this sense means non-specific, able to
describe anything
• This allows the classification of any individual thing
and to specify part-whole relations for any
individual object
• A generic data model shall consist of generic entity
types, such as 'individual thing', 'class', 'relationship',
and possibly a number of their subtypes.
Semantic data modeling
• The logical data structure of a DBMS, whether
hierarchical, network, or relational, cannot totally
satisfy the requirements for a conceptual definition
of data because it is limited in scope and biased

A semantic data model can be used to serve many


purposes, such as
o planning of data resources
o building of shareable databases
o evaluation of vendor software
o integration of existing databases
Data Warehouse
• In computing, a data warehouse (DW or DWH), is a
system used for reporting and data analysis, and is
considered a core component of business
intelligence.
• The data stored in the warehouse is uploaded from
the operational systems (such as marketing or
sales).
• The integrated data are then moved to yet another
database, often called the data warehouse
database
History
• 1960s – General Mills and Dartmouth College, in a
joint research project, develop the terms
dimensions and facts.
• 1970s – ACNielsen and IRI provide dimensional data
marts for retail sales
• 1980s when IBM researchers Barry Devlin and Paul
Murphy developed the "business data warehouse“
• 2012 – Bill Imon developed and made public
technology known as "textual disambiguation".
Benefits
• Integrate data from multiple sources into a single
database and data model.
• Maintain data history, even if the source transaction
systems do not.
• Improve data quality, by providing consistent codes
and descriptions
• Provide a single common data model for all data of
interest regardless of the data's source.
• Make decision–support queries easier to write.
Dimensional approach
• In a dimensional approach, transaction data are
partitioned into "facts“

• For example, a sales transaction can be broken up


into facts such as the number of products ordered
and the total price paid for the products

• key advantage of a dimensional approach is that


the data warehouse is easier for the user to
understand and to use
Normalized approach
• the normalized approach, the data in the data
warehouse are stored following, to a degree,
database normalization rules

• Tables are grouped together by subject areas that


reflect general data categories (e.g., data on
customers, products, finance, etc)

• Both normalized and dimensional models can be


represented in entity-relationship diagrams
Design methods
 Bottom-up design
data marts are first created to provide reporting and
analytical capabilities for specific business processes.
 Top-down design
using a normalized enterprise data model. In which
data is on greatest level of detail, are stored in the
data warehouse.
 Hybrid design
A hybrid DW database is kept on third normal
form(3NF) to eliminate data redundancy.
Data warehouse characteristics
• Subject-Oriented

• Integrated

• Time-variant

• Nonvolatile

• Summarized
Evolution in organization use
These terms refer to the level of sophistication of a
data warehouse:

• Offline operational data warehouse


• Offline data warehouse
• On time data warehouse
• Integrated data warehouse

You might also like