INTRODUCTION TO

DATABASE SYSTEMS
WEEK 01 LECTURE 01
DR. MUHAMMAD YASEEN
ASSISTANT PROFESSOR

Email: Muhammad.yaseen@riphah.edu.pk
COURSE INTRODUCTION

• Course: Introduction to Database Systems (3 credit Hours theory + 1 Credit hour Lab)
• Course Coordinator : Text Book:
• Ramez Elmasri, Fundamentals of Database Systems (7th Edition)

• Reference Book
 Jeffery Hoffer, Modern Database Management (11 th Edition)
https://drive.google.com/file/d/1Z_8FjBqyZp6PMxNo1OcG1oHA40YTL9Ix/view?usp=sharing
 C. J. Date, An Introduction to Database Systems (8th Edition)
 Raghu Ramakrishnan, Database Management Systems (3rd Edition)
 Silberschatz Korth sudarshan, Database System Concepts (6th Edition)
PLAGIARISM POLICY

• Any attempt to plagiarize will result in ZERO. No further arguments in this case.

• Marks Division(Tentative)
• Class Participation 10%
• Quizzes 15%
• Assignments 15%
• Midterms 20%
• Final 40%
ATTENDANCE POLICY

• Do not waste your leaves.

• Try to come to class on time.

• We can wait 20 minutes after that attendance will be marked.

• Students are requested not to leave during the class.

QUIZ POLICY

• Quiz can be announced or unannounced.

• There will be no retakes of quizzes.

• Average of all quizzes will be marked

• Class participation will be marked based on your valuable participation. Quiz can also be
conducted from the current lecture that will be marked in class participation.
ANNOUNCEMENTS

• Make sure you check your email and announcement section regularly. I keep on posting
announcements for the deadlines.
INTRODUCTION

• Data
• Meaningful facts, text, graphics, images, sound, video segments

• Database
• An organized collection of related data

• Information
• Data processed to be useful in decision making

• Metadata
• Data that describes data

• Database Management System

• Collection of interrelated data and a set of programs to access those data.
• Is a computerize system that enables users to create and maintain a database.

• Goal of DBMS
• To provide a way to store and retrieve database information that is both convenient and efficient.
DATA VS INFORMATION
Figure 1-1a Data in Context

Large volume of facts, difficult

to interpret or make decisions
based on
Figure 1-1b Summarized data
Useful information that managers can use for
decision making and interpretation
Table 1-1 Metadata
Descriptions of the properties or characteristics of the
data, including data types, field sizes, allowable
values, and documentation
 DISADVANTAGES OF FILE PROCESSING SYSTEMS
• 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 information systems budget
Figure 1-2 Three file processing systems at Pine
Valley Furniture
Duplicate
Data
 DATABASE MANAGEMENT
SYSTEM
Application
#1

Application

DBMS
#2
Database
containing
centralized
shared data
DBMS manages data
Application
#3 resources like an operating
system manages hardware
resources
DATABASE MANAGEMENT
SYSTEM
Conceptual Design

Logical Design

Physical Design
ADVANTAGES OF DATABASE APPROACH
• 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 increase data integrity/consistency
• 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
 RELATIONAL MODEL

• Database is represented as a collection of relations.

• Relation is nothing but a table of values. Every row in the table represents a collection of related data
values. These rows in the table denote a real-world entity or relationship.
• The table name and column names are helpful to interpret the meaning of values in each row.
• The data are represented as a set of relations.
• Data are stored as tables.
• However, the physical storage of the data is independent of the way the data are logically organized.
 FORMAL DEFINITIONS

• A Relation may be defined in multiple ways.

• The Schema of a Relation: R (A1, A2, .....An)
Relation schema R is defined over attributes A1, A2, .....An
For Example -
CUSTOMER (Cust-id, Cust-name, Address, Phone#)

Here, CUSTOMER is a relation defined over the four attributes Cust-id, Cust-name, Address,
Phone#, each of which has a domain or a set of valid values. For example, the domain of Cust-id
is 6 digit numbers.
1.Attribute: Each column in a Table. Attributes are the properties which define a relation. e.g.,
Student_Rollno, NAME,etc.
2.Tables – In the Relational model the, relations are saved in the table format. It is stored along with its
entities. A table has two properties rows and columns. Rows represent records and columns represent
attributes.
3.Record – It is nothing but a single row of a table, which contains a single record.
4.Relation Schema: A relational schema is a set of relational tables and associated items that are
related to one another
5.Degree: The total number of attributes which in the relation is called the degree of the relation.
6.Cardinality: Total number of rows present in the Table.
7.Column: The column represents the set of values for a specific attribute.
8.Relation key – Every row has one, two or multiple attributes, which is called relation key.
 INFORMAL DEFINITIONS

• RELATION: A table of values

• A relation may be thought of as a set of rows.
• A relation may alternately be thought of as a set of columns.
• Each row represents a fact that corresponds to a real-world entity or relationship.
• Each row has a value of an item or set of items that uniquely identifies that row in the table.
• Sometimes row-ids or sequential numbers are assigned to identify the rows in the table.
• Each column typically is called by its column name or column header or attribute name.
 FORMAL DEFINITIONS

• A Relation may be defined in multiple ways.

• The Schema of a Relation: R (A1, A2, .....An)
Relation schema R is defined over attributes A1, A2, .....An
For Example -
CUSTOMER (Cust-id, Cust-name, Address, Phone#)

Here, CUSTOMER is a relation defined over the four attributes Cust-id, Cust-name, Address,
Phone#, each of which has a domain or a set of valid values. For example, the domain of Cust-id
is 6 digit numbers.
 FORMAL DEFINITIONS

• A tuple is an ordered set of values

• Each value is derived from an appropriate domain.
• Each row in the CUSTOMER table may be referred to as a tuple in the table and
would consist of four values.
• <632895, "John Smith", "101 Main St. Atlanta, GA 30332", "(404) 894-2000">

is a tuple belonging to the CUSTOMER relation.

• A relation may be regarded as a set of tuples (rows).
• Columns in a table are also called attributes of the relation.
DEFINITION SUMMARY
Informal Terms Formal Terms

Table Relation
Column Attribute/Domain
Row Tuple
Values in a column Domain
Table Definition Schema of a Relation
Populated Table Extension

Chapter 5-24
SOME POPULAR RELATIONAL DATABASES

• Oracle– Oracle
• SQL Server and Access – Microsoft
• mySQL
 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 responsible for
maintaining the database
• System Developers–personnel responsible for designing
databases and software
• End Users–people who use the applications and databases
ELEMENTS OF THE DATABASE
APPROACH
• Data models
• Graphical system capturing nature and relationship of data
• Enterprise Data Model–high-level entities and relationships for the
organization
• Relational Databases
• Database technology involving tables (relations) representing entities
and primary/foreign keys representing relationships
• Use of Internet Technology
• Networks and telecommunications, distributed databases, client-server,
and 3-tier architectures
• Database Applications
• Application programs used to perform database activities (create, read,
update, and delete) for database users
HOW DATABASES FIT IN TO
ORGANIZATION WIDE INFORMATION
SYSTEMS
 INFORMATION SYSTEMS
• PLANNING
Purpose–align information technology with organization’s
business strategies

• Three steps:
1. Identify strategic planning factors
2. Identify corporate planning objects
3. Develop enterprise model