CHAPTER 1

Fundamentals of Database
Management System

1.1 Understand Database

DFC20123| DATABASE DESIGN|

Learning Outcomes: 2
At the end of this lecture, student should be able to :-

► 1.1.1 Define database

► 1.1.2 Describe uses of database in the business world
► 1.1.3 Relate the importance of databases to everyday life
► 1.1.4 Explain the three major steps in the database development process
► a) Requirement analysis

► b) Database design

► c) Implementation

► 1.1.5 Describe the sharing concept of data in database

► 1.1.6 Describe the properties of databases:
► a) Completeness

► b) Integrity

► c) Flexibility

► d) Efficiency

► e) Usability
Before we learn about a database, let us understand
What is Data? 3
Data is a collection of facts, such as numbers, words,
measurements, observations or just descriptions of things.

Data can be anything….

► In simple words, data can be facts related to
any object in consideration. For example,
your name, age, height, weight, etc. are some
data related to you. A picture, image, file, pdf,
etc. can also be considered data.

Data can be
anything…
“Ali , 25,
30/12/78”
DATA vs INFORMATION 4
◼ Data refers to unprocessed data while
information refers to processed data.
◼ Data are like raw materials; they may or
may not have any value to the user or
decision maker.
◼ Information is like the finished product.
It offers value to the decision maker.
◼ Example :
▪ Data : quantity of a product sold on a
particular day.
▪ Information: sales trend based on the past
six month’s sales.
 5
Database Definition

► Database definition:-
A set of related tables/ data.
a) Each table consists of columns
(fields/attributes) and rows (records).
b) The links between tables (using primary key
and/or foreign key) and rules associated with
those links are established at design time.
c) Database system stores all this information as
metadata.
(Dr.P.Sellapan, Database Management)
 6
Database
Definition
A shared, integrated computer
structure that houses a collection of:
► End user data; raw facts of interest
to the end user.
► Metadata; provide a description of
the data, characteristics and the set
of relationships that link the data
found within the database.
(Rob & Coronel, Database System :
Design, Implementation &Management)
 7
Database usage

► A database is a systematic collection of data. They

support electronic storage and manipulation of
data. Databases make data management easy.

► Let us discuss a database example: An online

telephone directory uses a database to store data
of people, phone numbers, and other contact
details. Your electricity service provider uses a
database to manage billing, client-related issues,
handle fault data, etc.

► Let us also consider Facebook. It needs to store,

manipulate, and present data related to members,
their friends, member activities, messages,
advertisements, and a lot more. We can provide a
countless number of examples for the usage of
databases.
 Evolution of database 8
TIME DEVELOPMEN COMMENTS
FRAME T
1960a File-based Precursor to the database system.
(onwards) systems Decentralized approach: each
department stored and controlled its own data.
Mid-1960s Hierarchical and Represents first-generation DBMSs. Main hierarchical system is IMS
network data from IBM and the main network system is IDMS/R from Computer
models Associates. Lacked data independence and required complex programs
to be developed to process the data.
1970 Relational model Publication of E. F. Codd’s seminal paper “A relational model of
proposed data for large shared data banks,” which addresses the weaknesses
of first-generation systems.
 Evolution of database 9
TIME DEVELOPMEN COMMENTS
FRAME T
1970s Prototype During this period, two main prototypes emerged: the Ingres
RDBMSs project at the University of California at Berkeley (started in 1970)
developed and the System R project at IBM’s San José Research Laboratory in
California (started in 1974), which led to the development of SQL.
1976 ER model Publication of Chen’s paper “The Entity-Relationship model—
proposed Toward a unified view of data.”
ER modeling becomes a significant component in methodologies for
database design.
1979 Commercial Commercial RDBMSs like Oracle, Ingres, and DB2 appear. These
RDBMSs appear represent the second generation of DBMSs.
1987 ISO SQL standard SQL is standardized by the ISO (International Standards Organization).
There are subsequent releases of the standard in 1989, 1992 (SQL2),
1999 (SQL:1999), 2003 (SQL:2003), 2008 (SQL:2008), and
2011 (SQL:2011).
 Evolution of database 10
TIME DEVELOPMEN COMMENTS
FRAME T
1990s OODBMS and This period initially sees the emergence of OODBMSs and later
ORDBMSs appear ORDBMSs (Oracle 8, with object features released in 1997).
ER model
proposed
1990s Data warehousing This period also see releases from the major DBMS vendors of
systems appear data warehousing systems and thereafter data mining products.
Mid-1990s Web–database The first Internet database applications appear. DBMS vendors and
integration third-party vendors recognize the significance of the Internet and
support web–database integration.
1998 XML XML 1.0 ratified by the W3C. XML becomes integrated with
DBMS products and native XML databases are developed.
 11
Evolution of Database
 12
?????

Database System
Application????

?????
 13
Database System Application
► Enterprise Information

o Sales: For customer, product, and purchase information.

o Accounting: For payments, receipts, account balances, assets and other accounting
information.
o Human resources: For information about employees, salaries, payroll taxes, and
benefits, and for generation of paychecks.
o Manufacturing: For management of the supply chain and for tracking production of
items in factories, inventories of items in warehouses and stores, and orders for items.
o Online retailers: For sales data noted above plus online order tracking, generation of
recommendation lists, and maintenance of online product evaluations.
 14
Database System Application
► Banking and Finance

o Banking: For customer information, accounts, loans, and banking transactions.

o Credit card transactions: For purchases on credit cards and generation of monthly
statements.
o Finance: For storing information about holdings, sales, and purchases of financial
instruments such as stocks and bonds; also for storing real-time market data to enable
online trading by customers and automated trading by the firm.
Database System Application 15

► Universities: For student information, course registrations, and grades (in addition
to standard enterprise information such as human resources and accounting).
► Airlines: For reservations and schedule information. Airlines were among the first
to use databases in a geographically distributed manner.
► Telecommunication: For keeping records of calls made, generating monthly bills,
maintaining balances on prepaid calling cards, and storing informationabout the
communication networks.
 16
Importance of database to everyday
life
1. Improved data sharing
2. Improved data security
3. Better data integration
4. Minimized data inconsistancy
5. Improved data access
6. Improved decision making
7. Increased end user productivity
 17

Business Information Requirement

Three major Conceptual Data

Business View
Modelling
steps in
database Logical
development
System View
Database Design

process
Physical
Database Build

Operational Database
Sharing concepts of data in database 18

▪ data sharing - Computer Definition.

– It implies that the data are stored in one or more servers in the network
and that there is some software locking mechanism that prevents the same
set of data from being changed by two people at the same time.
– Data sharing is a primary feature of a database management system
(DBMS).
 19
Properties of databases

Completeness

Integrity

Flexibility

Efficiency

Usability
Properties of databases 20

◼ Completeness
◼ Ensures that users can access the data they want.
◼ Note that this includes ad hoc queries,
◼ which would not be explicitly given as part of a statement
of data requirements.

◼ Integrity
◼ Ensures that data is both consistent (no contradictory data) and correct (no invalid data)
◼ ensures that users trust the database.

◼ Flexibility
◼ Ensures that a database can evolve (without requiring excessive effort) to satisfy changing user
requirements.
 21
Properties of Databases
◼ Efficiency
◼ Ensures that users do not have unduly long response times when accessing data.

◼ Usability (ease of use)

◼ Ensures that data can be accessed and manipulated in ways which match user
requirements.
 22
References
1. Connolly, T. M., & Begg, C. E. (2015). Database systems: a practical approach to
design, implementation, and management(6th edition). Pearson Education.
2. https://mhaadi.wordpress.com/2010/10/18/the-evolution-of-database/
3. http://www.learn.geekinterview.com/database/oracle/evolution-of-database-system
s.html