“DATABASE SYSTEMS”

Book:
Modern Database Management

Jeffrey A. Hoffer,
Mary B. Prescott,
Fred R. McFadden
Instructor: Ayesha Siddiqa
We will study this course

 to understand the basic concepts of Databas

e
 to learn the design issues of a relational data
base
 to learn the development of relational databa
se systems using oracle
 to get hands on with oracle forms and report
s

3
Goal
 At the end of this course it is expecte
d that each student must be able to d
evelop a database System independe
ntly

4
 Objectives
 Definition of terms
 Explain growth and importance of databases
 Name limitations of conventional file processi
ng
 Identify five categories of databases
 Explain advantages of databases
 Identify costs and risks of databases
 List components of database environment
 Describe evolution of database systems

5
 Definitions

 Database: organized collection of logically relate

d data
 Data: stored representations of meaningful obje
cts and events
 Structured: numbers, text, dates
 Easily searchable
 Unstructured: images, video, documents
 Not easily searchable

 Information: data processed to increase knowled

ge in the person using the data
 Metadata: data that describes the properties and
context of user data
6
Figure 1-1a Data in context

Context helps users understand data

Figure 1-1b Summarized data

Graphical displays turn data into useful infor

mation that managers can use for decision ma
king and interpretation
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable value
s, and data context
Disadvantages of File Processing

 Program-Data Dependence
 All programs maintain metadata for each file they use
 Duplication of Data
 Different systems/programs have separate copies of the sa
me data
 Limited Data Sharing
 No centralized control of data
 Lengthy Development Times
 Programmers must design their own file formats
 Excessive Program Maintenance
 80% of information systems budget
10
Problems with Data Dependency
 Each application programmer must maintai
n his/her own data
 Each application program needs to include
code for the metadata of each file
 Each application program must have its ow
n processing routines for reading, inserting
, updating, and deleting data
 Lack of coordination and central control
 Non-standard file formats

11
Figure 1-3 Old file processing systems at Pine Valley F
urniture Company
Duplicate Data
Problems with Data Redundanc
y
 Waste of space to have duplicate d
ata
 Causes more maintenance headach
es
 The biggest problem:
 Data changes in one file could cau
se inconsistencies
 Compromises in data integrity
13
SOLUTION:
The DATABASE Approach
 Central repository of shared data
 Data is managed by a controlling
agent
 Stored in a standardized, conveni
ent form

Requires a Database Management System (DBMS)

14
 Database Management System
 A software system that is used to create, maintain, and pr
ovide controlled access to user databases

Order Filing
System

Invoicing Central database

DBMS
System
Contains employee,
order, inventory,
pricing, and
Payroll
customer data
System

DBMS manages data resources like an operating system manages hardware resources
15
Advantages of the Database Approach
 Program-data independence
 Planned data redundancy
 Improved data consistency
 Improved data sharing
 Increased application development productivi
ty
 Enforcement of standards
 Improved data quality
 Improved data accessibility and responsivene
ss
 Reduced program maintenance
 Improved decision support
16
Costs and Risks of the Database Approa
ch

 New, specialized personnel

 Installation and management cost and
complexity
 Conversion costs
 Need for explicit backup and recovery
 Organizational conflict

17
Elements of the Database Approach

 Data models
 Graphical system capturing nature and relationship of d
ata

 Enterprise Data Model – high-level entities and relation

ships for the organization

 Project Data Model – more detailed view, matching dat

a structure in database or data warehouse

18
Elements of the Database Approach C
ont ….
 Relational Databases
 Database technology involving tables (relations)
representing entities and primary/foreign keys r
epresenting relationships
 Use of Internet Technology
 Networks and telecommunications, distributed d
atabases, client-server, and 3-tier architectures
 Database Applications
 Application programs used to perform database
activities (create, read, update, and delete) for d
atabase users

19
Segment of an Enterprise Data Model

Segment of a Project-Level Data Model

One customer ma
y place many orde
rs, but each order
is placed by a sing
le customer
 One-to-many r
elationship
One order has man
y order lines; each
order line is associ
ated with a single
order
 One-to-many re
lationship
One product can
be in many orde
r lines, each ord
er line refers to
a single product
 One-to-many
relationship
Therefore, one or
der involves many
products and one
product is involve
d in many orders

 Many-to-many
relationship
Figure 1-4 Enterprise data model for Figure 1-3 segments
Figure 1-5 Components of the Database Environment
 Components of the
Database Environment
 CASE Tools – computer-aided software engineering
 Repository – centralized storehouse of metadata
 Database Management System (DBMS) –software
for managing the database
 Database – storehouse of the data
 Application Programs – software using the data
 User Interface – text and graphical displays to users
 Data/Database Administrators – personnel respon
sible for maintaining the database
 System Developers – personnel responsible for desi
gning databases and software
 End Users – people who use the applications and dat
abases

27
The Range of Database Applications

 Personal databases
 Workgroup databases
 Departmental/divisional databases
 Enterprise database
 Web-enabled databases

28
Figure 1-6
Typical data
from a perso
nal database
Figure 1-7 Workgroup database with wireless
local area network
Enterprise Database Applications
 Enterprise Resource Planning (ERP)
 Integrate all enterprise functions (manufa
cturing, finance, sales, marketing, invento
ry, accounting, human resources)
 Data Warehouse
 Integrated decision support system derive
d from various operational databases

32
Figure 1-8 An enterprise data warehouse
Evolution of DB Systems
THANK YOU

35