SCS2203 Introduction

to Database
Management Systems

Lecture one
 Course Description

• This course introduces the student to;

– database concepts and design.
– File system and database system
– goals of DBMS
• The course further looks at
– DBMS models (hierarchical, network and relational and
objected-oriented).
• Data definition language and data manipulation language as
two database sub-languages implemented via SQL.
• Physical database design;
• Implementation of DB systems on current hardware systems
and case studies will be discussed.

Database Management Systems 2

Course Objectives
The objectives of the course are to:
 Expose the student to the different
concepts of database systems.
 Introduce the student to the different
functions of a DBMS.
 Expose the student to database sub-
languages: DDL and DML.
 Introduce the student to the development
and implementation of a physical
database.
 Impart practical skills to the student of
how to design, implement a database
system using MySQL.
Database Management Systems 3
 Learning Outcomes

By the end of the course, the student should be able to:

 Demonstrate an understanding of database principles and the
technologies and theory underlying database management
systems;
 Apply the acquired knowledge and skills to select the most
appropriate database system.
 Use the database sub-languages DDL and DML to create and
manipulate data in the database.
 Design a relational database in a chosen DBMS, e.g., MySQL.
 Design database systems using MySQL IDE. (integrated
development environment consists of at least a source code editor,
build automation tools and a debugger)

Database Management Systems 4

Course Outline
File Systems and Databases: File systems, database systems, DBMS, DB (8 hours)
architecture, components, languages and interfaces.

Database models: hierarchical model, network model, relational model (6 hours)

and object-oriented model.

The Relational Model: Logical view of data, integrity rules, relational (6 hours)
database, relational database software classification, DB keys, data
redundancy, relevant examples.
Normalization of Database Tables: Normalization, first normal form, (8 hours)
second normal form, third normal form.

Database development life Cycle: Initial study, database design, (8 hours)

implementation, loading, testing, evaluation, operation & maintenance.
Database Design: Conceptual database design, logical database design, (12 hours)
data modeling: entity-relationship diagrams, physical database design.

Case study: Database system implementation (how to build the (12 hours)
database application) using MySQL or Microsoft SQL server. OR Access
the database: using an event driven programming language e.g. Visual
basic. Database Management Systems 5
Mode of delivery

This course is taught by lectures, assignments, practical

sessions and student presentations.

Assessment: Assignments: 15%

Tests /Project: 25%
Final course Examination: 60%
Total 100%

Database Management Systems 6

 Reading List/ Study
Materials

Online Material:
 Links to up-to-date online materials
 Text books
 Links to up-to-date Journal articles and conference paper materials
Books:
 Connolly T., Begg, C. (2014). Database Systems: A Practical Approach to Design, Implementation and
Management. 6th Ed. Addison Wesley. ISBN-10: 0132943263, ISBN-13: 978-0132943260
 Connolly T., Begg, C. (2014). Database Systems: A Practical Approach to Design, Implementation and
Management. Global Edition. Addison Wesley. ISBN-10: 1292061189 ISBN-13: 978-1292061184
 Abraham Silberschatz, Henry F. Korth, S. Sudarshan, S. (2010). Database System Concepts. 6th
Ed. McGraw-Hill Higher Education. ISBN-10: 0073523321, ISBN-13: 978-0073523323
 Carlos Coronel, Steven Morris. (2014). Database Systems: Design, Implementation and
Management. Cengage Learning. ISBN-10: 1285196147, ISBN-13: 978-1285196145
 Ramez Elmasri, Shamkant B. Navathe. (2006). Fundamentals of Database Systems, 5th Edition.
Pearson / Addison Wesley; 5th edition. ISBN-10: 0321369572, ISBN-13: 978-0321369574
 Ramakrishnan, R. and Gehrke, J. (2002). Database Management Systems, McGraw-Hill Higher
Education; 3rd edition. ISBN-10: 0072465638, ISBN-13: 978-0072465631

Database Management Systems 7

 Introduction

What is a Database?
 A database is a collection of related data which represents some aspect of the real
world.
What is DBMS?
 A database management system (DBMS) is a software package designed to define,
manipulate, retrieve and manage data in a database.
 A DBMS generally manipulates the data itself, the data format, field names, record
structure and file structure.
 It also defines rules to validate and manipulate this data.
 Some other DBMS examples include:
 MySQL
 SQL Server
 Oracle
 Access
 dBASE
 Foxpro, etc

Database Management Systems 8

 Introduction…

 A DBMS makes it possible for end users to create, read, update and
delete data in a database.

 The DBMS essentially serves as an interface between databases and

end users or application programs, ensuring that data is consistently
organized and remains easily accessible.

File-based Systems
 Collection of application programs that perform services for the end
users (e.g. reports).

 NOTE: Each program defines and manages its own data.

Database Management Systems 9

 File-based Processing

Database Management Systems 10

Limitations of the File-based
Approach
• Separation and isolation of data
– Each program maintains its own set of data.
– Users of one program may be unaware of
potentially useful data held by other
programs.

• Duplication of data
– Same data is held by different programs.
– Wasted space and potentially different
values and/or different formats for the same
item.

Database Management Systems 11

Limitations of the File-based
Approach….
 Data dependence
◦ File structure is defined in the program code.

 Incompatible file formats

◦ Programs are written in different languages,
and so cannot easily access each others files.
 Fixed Queries/Proliferation of application
programs
◦ Programs are written to satisfy particular
functions. Any new requirement needs a
new program.

Database Management Systems 12

 The Database Approach

• Arose because:
– Definition of data was embedded in application programs,
rather than being stored separately and independently.
– No control over access and manipulation of data beyond that
imposed by application programs.

• Result
– the database and Database Management System (DBMS).

Database Management Systems 13

 Database Approach

 Data definition language (DDL).

Permits specification of data types, structures and any data
constraints.
All specifications are stored in the database.
 Data manipulation language (DML).
General enquiry facility (query language) of the data.
 Controlled access to database may include:
◦ A security system.
◦ An integrity system.
◦ A concurrency control system.
◦ A recovery control system.
◦ A user-accessible catalog.
 A view mechanism.
◦ Provides users with only the data they want or need to use.
Database Management Systems 14
 Databases

 Shared collection of logically related data (and a description

of this data), designed to meet the information needs of an
organization.

 System catalog (metadata - a set of data that describes and

gives information about other data) provides description of
data to enable program–data independence.

 Logically related data comprises entities, attributes, and

relationships of an organization's information.

Database Management Systems 15

Examples of Databases
– Amazon
– Student results database
– Jumia
– Facebook
– Google scholar
– Bank systems, etc

Database Management Systems 16

 Describing Data: Data
Models
• A data model
– A collection of concepts for describing data.

• A schema
– A description of a particular collection of data, using a given data model.

• The relational data model

– The most widely used model today.
– Main concept: relation, basically a table with rows and
columns.
– Every relation has a schema, which describes the columns, or
fields.

Database Management
17
Systems
 Levels of Data
Abstraction
 Abstraction: The process of
removing attributes in the study of objects
or systems to focus attention on details of
Users
greater importance
View 1 View 2 View 3
 Views
 describe how users see the data.
 Conceptual schema Conceptual Schema
 defines logical structure
Physical Schema
 Physical schema
 describes files and indexes used.
These levels of abstraction sometimes called
the ANSI/SPARC architecture DB
 American National Standards Institute, Standards
Planning And Requirements Committee
 Describe the external model / level, conceptual
model and physical model/level
18
Database Management Systems
 Data Independence

• Applications insulated from how data

is structured and stored. View 1 View 2 View 3

• Logical data independence:

– Protection from changes in logical Conceptual Schema
structure of data.
• Physical data independence: Physical Schema
– Protection from changes in
physical structure of data.
• Q: Why are these particularly DB
important for DBMS?

Database Management
19
Systems
 View of Data
An architecture for a database system

•Allows each user to have his or her own view of the database.
•A view is essentially some subset of the database.

Database Management Systems 20

 Database architecture
• Physical: This is the lowest level of data abstraction.
– It tells us how the data is actually stored in memory.
– The access methods like sequential or random access and file organization methods like
hashing.
– Usability, size of memory, and the number of times the records are factors that we need to
know while designing the database.
– Suppose we need to store the details of an employee. Blocks of storage and the amount of
memory used for these purposes are kept hidden from the user.
• Logical: This level comprises the information that is actually stored in the database in the form of
tables.
– It also stores the relationship among the data entities in relatively simple structures.
– At this level, the information available to the user at the view level is unknown.
– We can store the various attributes of an employee and relationships, e.g. with the manager
can also be stored.
• View: This is the highest level of abstraction.
– Only a part of the actual database is viewed by the users.
– This level exists to ease the accessibility of the database by an individual user.
– Users view data in the form of rows and columns. Tables/relations are used to store data.
– Multiple views of the same database may exist.
– Users can just view the data and interact with the database, storage and implementation
details are hidden from them.
Database Management Systems 21
Views
• Benefits include:
– Reduce complexity;
– Provide a level of security;
– Provide a mechanism to customize the
appearance of the database;
– Present a consistent, unchanging picture of
the structure of the database, even if the
underlying database is changed.

Database Management Systems 22

 Database Management
System (DBMS)

A software system that enables users to define, create, and maintain the database
and which provides controlled access to this database

Database Management Systems 23

Why Use a DBMS?
• Data independence
• Efficient access.
• Reduced application development
time.
• Data integrity and security.
• Uniform data administration.
• Concurrent access,
• Recovery from crashes.
Database Management Systems 24
 Components of DBMS
Environment

• Procedures - Instructions and rules that should be applied to the

design and use of the database and DBMS.
• People
• Hardware - Can range from a PC to a network of computers.
• Software - DBMS, operating system, network software (if
necessary) and also the application programs.
• Data - a description of this data called the schema.

Database Management Systems 25

Roles in the Database
Environment
• Data Administrator (DA)
• Database Administrator (DBA)
• Database Designers (Logical and
Physical)
• Application Programmers
• End Users (naive and sophisticated)

EXERCISE.

Database Management Systems 26

 Database Administrator

❖Coordinates all the activities of the database

system; the database administrator has a good
understanding of the enterprise’s information
resources and needs.
❖Database administrator's duties include:
o Schema definition
o Storage structure and access method definition
o Schema and physical organization modification
o Granting user authority to access the database
o Specifying integrity constraints
o Acting as liaison with users
o Monitoring performance and responding to changes in requirements

Database Management Systems 27

History of Database Systems
• First-generation
– Hierarchical and Network

• Second generation
– Relational

• Third generation
– Object Relational
– Object-Oriented

Database Management Systems 28

 Advantages of DBMS

Control of data redundancy

Data consistency
More information from the same amount of data.
Sharing of data
Improved data integrity
Improved security
Enforcement of standards
Economy of scale (When more units of a good or service can be
produced on a larger scale, yet with (on average) fewer input costs)

Database Management Systems 29

 Advantages of DBMS
 Balanced conflicting requirements
(Two requirements are conflicting if you cannot implement them both.
the solution to one requirement prohibits implementing the other).
 Improved data accessibility and responsiveness
 Increased productivity
 Improved maintenance through data independence
◦ Applications insulated from how data is structured and stored.
◦ Logical data independence: Protection from changes in logical
structure of data.
◦ Physical data independence: Protection from changes in physical
structure of data.
 Increased concurrency
 Improved backup and recovery services

Database Management Systems 30

Disadvantages of DBMS
• Complexity
• Size
• Cost of DBMS
• Additional hardware costs
• Cost of conversion
• Performance
• Higher impact of a failure

Database Management Systems 31

 End

THANK YOU…….

Database Management Systems 32