Ch 1

Database Management
System

Fall 2009
Department of Computer Systems
Engineering, UET Peshawar

1
 Ch 1
Definitions

• Data: Meaningful facts, text, graphics, images, sound,

video segments
• Database: An organized collection of logically related data
• Information: Data processed to be useful in decision
making
• Field (data item): collection of related characters (numeric
or alphabetic) that define a characteristic of an entity
(person, place or thing)
• Record: collection of related (logically connected) fields
• File: collection of similar types of records

Database Management Systems, Fall 2009, DCSE 2

 Ch 1
Definitions (cont.)

• Database Management System (DBMS): a system software

that facilitates the management of a database and controls
the access to the data stored in the database
• Database system: system consisting of a database, a DBMS,
hardware and people
• Database design: The design of the database structure that
will be used to store and manage data (not the design of the
DBMS)
• Data dictionary (DD) or metadata: describes the
characteristics of data stored in a database and the inter-
relationships among data

Database Management Systems, Fall 2009, DCSE 3

Figure 1-1a Data in Context Ch 1

Large volume of facts,

difficult to interpret or
make decisions based on

Database Management Systems, Fall 2009, DCSE 4

 Ch 1
Figure 1-1b Summarized data
Useful information that managers
can use for decision making and
interpretation

Database Management Systems, Fall 2009, DCSE 5

 Ch 1
Table 1-1 Metadata
Descriptions of the properties or
characteristics of the data, including data
types, field sizes, allowable values, and
documentation

Database Management Systems, Fall 2009, DCSE 6

 Ch 1
Disadvantages of File Processing
• Program-Data Dependence
– All programs maintain metadata for each file they use
• Data Redundancy (Duplication of data)
– Different systems/programs have separate copies of the same
data
• Limited Data Sharing
– No centralized control of data
• Lengthy Development Times
– Programmers must design their own file formats
• Excessive Program Maintenance
– 80% of of information systems budget

Database Management Systems, Fall 2009, DCSE 7

Figure 1-2 Three file processing systems at Pine Ch 1
Valley Furniture
Duplicate
Data

Database Management Systems, Fall 2009, DCSE 8

 Ch 1
Problems with Data Dependency

 Each application programmer must maintain their own

data
 Each application program needs to include code for
the metadata of each file
 Each application program must have its own
processing routines for reading, inserting, updating
and deleting data
 Lack of coordination and central control
 Non-standard file formats

Database Management Systems, Fall 2009, DCSE 9

 Ch 1
Problems with Data Redundancy

• Waste of space to have duplicate data

• Causes more maintenance headaches
• The biggest Problem:
– When data changes in one file, could
cause inconsistencies
– Compromises data integrity

Database Management Systems, Fall 2009, DCSE 10

SOLUTION: Ch 1
The DATABASE Approach

• Central repository of shared data

• Data is managed by a controlling agent
• Stored in a standardized, convenient
form

Requires a Database Management System (DBMS)

Database Management Systems, Fall 2009, DCSE 11

 Ch 1
Database Management System

• A DBMS is a data storage and retrieval

system which permits data to be stored
non-redundantly while making it appear to
the user as if the data is well-integrated.

Database Management Systems, Fall 2009, DCSE 12

 Ch 1
Database Management System

Application
#1

Application

DBMS
#2
Database
containing
centralized
shared data

Application
#3 DBMS manages data
resources like an operating
system manages hardware
resources

Database Management Systems, Fall 2009, DCSE 13

Advantages of Database Approach Ch 1

• Program-Data Independence
– Metadata stored in DBMS, so applications don’t need to worry
about data formats
– Data queries/updates managed by DBMS so programs don’t
need to process data access routines
– Results in: increased application development and maintenance
productivity
• Minimal Data Redundancy
– Leads to increased data integrity/consistency

Database Management Systems, Fall 2009, DCSE 14

 Ch 1
Advantages of Database Approach

• Improved Data Sharing

– Different users get different views of the data
• Enforcement of Standards
– All data access is done in the same way
• Improved Data Quality
– Constraints, data validation rules
• Better Data Accessibility/ Responsiveness
– Use of standard data query language (SQL)
• Security, Backup/Recovery, Concurrency
– Disaster recovery is easier

Database Management Systems, Fall 2009, DCSE 15

 Ch 1
Database vs. File Systems

Database Management Systems, Fall 2009, DCSE 16

 Ch 1
Costs and Risks of the Database Approach

• Up-front costs:
– Installation Management Cost and Complexity
– Conversion Costs
• Ongoing Costs
– Requires New, Specialized Personnel
– Need for Explicit Backup and Recovery
• Organizational Conflict
– Old habits die hard

Database Management Systems, Fall 2009, DCSE 17

 Ch 1
The Database Approach:
Enterprise Data Model

• The enterprise data model is a graphical model

that shows the high-level entities for the
organization and the relationships among those
entities.
• Enterprise data model is represented with the
help of a E-R diagram that shows the entities,
attributes, relations, connectivities and
cardinalities.

Database Management Systems, Fall 2009, DCSE 18

 Ch 1
E-R Model Constructs
• Entity instance – something about which we store data. E.g. person,
place, object, event, concept (often corresponds to a row in a table)
– Entity Type – collection of entities (often corresponds to a table)
• Attribute - property or characteristic of an entity type (often
corresponds to a field in a table)
• Relationship instance – link between entities (corresponds to primary
key-foreign key equivalencies in related tables)
– Relationship type – category of relationship…link between entity types

When we represent entities in a database, we actually store only the attributes.

Database Management Systems, Fall 2009, DCSE 19

 Ch 1

Entities…

• CUSTOMER: People and organizations that buy or

may potentially buy products from Pine Valley
Furniture
• ORDER: The purchase of one or more products by a
customer
• PRODUCT: The items Pine Valley Furniture makes
and sells
• ORDER LINE: Details about each product sold on
particular customer order (such as quantity and price)

Database Management Systems, Fall 2009, DCSE 20

 Ch 1

Relationships…

• Each CUSTOMER Places any number of

ORDERs. Conversely, each ORDER Is
placed by exactly one CUSTOMER.
• Each ORDER Contains any number of
ORDER LINEs. Conversely each ORDER
LINE Is contained in exactly one ORDER.
• Each PRODUCT Has any number of ORDER
LINEs. Conversely, each ORDER LINE Is for
exactly one PRODUCT.
Database Management Systems, Fall 2009, DCSE 21
 Ch 1
Types of Relationships

• One-to-one relationship (1:1): each car has one plate

number and each plate number identifies one car.
• One-to-many relationship (1:M): a building contains many
apartments but those apartments belong to the same
building.
• Many-to-many relationship (M:M): a student can take
many courses and each course can be taken by many
students.

Database Management Systems, Fall 2009, DCSE 22

 Ch 1
Figure 1-3 Segment from enterprise data
Figure 3
model

Database Management Systems, Fall 2009, DCSE 23

 Ch 1
Figure 1-3 Segment from enterprise data
model
Figure 3

One customer may place many

orders, but each order is placed
by a single customer
 One-to-many relationship

Database Management Systems, Fall 2009, DCSE 24

 Ch 1
Figure 1-3 Segment from enterprise data
Figure 3
model

One order has many order

lines; each order line is
associated with a single order
 One-to-many relationship

Database Management Systems, Fall 2009, DCSE 25

Figure 1-3 Segment from enterprise data Ch 1
Figure 3
model

One product can be in many

order lines, each order line refers
to a single product
 One-to-many relationship

Database Management Systems, Fall 2009, DCSE 26

Figure 1-3 Segment from enterprise data Ch 1
Figure 3
model

Therefore, one order involves

many products and one product
is involved in many orders
 Many-to-many relationship

Database Management Systems, Fall 2009, DCSE 27

Figure 1-4 Order, Order_Line, Customer, Ch 1
and Product tables
Relationships established in special columns that provide links
between tables

●Each table row (tuple) represents a single entity occurrence within the entity set.
●Each table column represents an attribute, and each column has a distinct name.
●Each column/row intersection represents a single data value.
●All values in a column must confirm to the same data format.
●The order of the row and columns is immaterial to the DBMS.
●Each table must have an attribute or a combination of attributes that uniquely identifies each row.
Database Management Systems, Fall 2009, DCSE 28
 Ch 1
Figure 1-5
Client/server
system for
Pine Valley
Furniture
Company

Database Management Systems, Fall 2009, DCSE 29

Figure 1-6 Customer invoice (PVF) Ch 1
Application program functions:
inserting new data, updating existing data,
deleting existing data, reading data for display

Database Management Systems, Fall 2009, DCSE 30

 Ch 1
The Range of
Database Applications
• Personal Database – standalone desktop database
• Workgroup Database – local area network (<25 users)
• Department Database – local area network (25-100 users)
• Enterprise Database – wide-area network (hundreds or thousands of
users)

Database Management Systems, Fall 2009, DCSE 31

 Ch 1
Figure 1-7
Typical data
from a
personal
computer
database

Database Management Systems, Fall 2009, DCSE 32

Figure 1-8 Workgroup database with Ch 1
local area network

Database Management Systems, Fall 2009, DCSE 33

 Ch 1
Figure 1-9 An
enterprise
data
warehouse

Database Management Systems, Fall 2009, DCSE 34

Components of the Database Ch 1
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 Administrators – personnel responsible for maintaining the
database
• System Developers – personnel responsible for designing
databases and software
• End Users – people who use the applications and databases

Database Management Systems, Fall 2009, DCSE 35

 Ch 1

Figure 1-10
Components
of the
database
environment

Database Management Systems, Fall 2009, DCSE 36

 Ch 1

Evolution of DB Systems

• Flat files - 1960s - 1980s

• Hierarchical – 1970s - 1990s
• Network – 1970s - 1990s
• Relational – 1980s - present
• Object-oriented – 1990s - present
• Object-relational – 1990s - present
• Data warehousing – 1980s - present
• Web-enabled – 1990s - present

Database Management Systems, Fall 2009, DCSE 37

 Ch 1
Concept Map

Database Management Systems, Fall 2009, DCSE 38

 Ch 1

Next…

• We will skip Chapter 2 of the Text (Hoffer, 6th

Edition) for the time being. So we will start
Chapter 3 next.

Database Management Systems, Fall 2009, DCSE 39