Database

System
DRC1123
Week Course Content/Topics

1 Chapter 1 : Introduction To Database

2 Chapter 2: Data Environment
3 Chapter 3: Entity Relationship Model
4 Chapter 4: Enhanced ERD
5 Chapter 5: Logical DB Design & Relationship Mode 6
Chapter 5: Logical DB Design & Relationship Mode 7 Chapter
6: Normalization (Part I)
8 Chapter 6: Normalization (Part II
9 Mid Term Break
10 Chapter 6: Normalization (Part III)
11 Chapter 7: SQL (Part I)
12 Chapter 7: SQL (Part II
13 Chapter 7: SQL (Part III)
14 Chapter 8 : Database Architecture (SBL) 15 Revision
for Final Exam,SQL,Normalization 16 Final Exam

17 Final Exam
Assessments

Method Week Recommended SLT Weight

1 Mid-Term Test 6 32 20%
Continuous/ 2 Quizzes 3,4,11,14 8 5%
Formative 3 Project 14 40 25%
4 Hands On Test 13 16 10%
Final/
16
Summative 5 Final Exam 64 40%
Total 160 100%
INTRODUCTION TO
DATABASE
1.1 Traditional File-Based Systems
File system is collection of data. In this system, user must write procedures for
managing database. It provides details of data representation and storage of data. In
this –

•Data is stored in files.

•Each file has specific format.

•Programs that use these files depend on knowledge about that format.

•In earlier days, database applications were built on top of file systems.
This approach is mostly obsolete but –
•Understanding problems inherent in file-based systems may prevent us from
repeating these problems in our database system.
•Understanding how file system works is extremely useful when converting a file-
based system to a database system.
 Advantages and disadvantages of
traditional File-Based Systems
ADVANTAGES DISADVANTAGES
•File processing cost less and can be more speed •Data redundancy and inconsistency.
than database.

•File processing design approach was well suited •Difficulty in accessing data.
to mainframe hardware and batch input.
•Data isolation – multiple files and
•Companies mainly use file processing to handle
formats.
large volumes of structured data on a regular
basis.
•Integrity problems
•It can be more efficient and cost less than DBMS
in certain situations. •Unauthorized access is not restricted.
•Design is simple.
•It co-ordinates only physical access.
•Customization is easy and efficient.
1.2 Database Approach & the
components
To overcome disadvantages of File system, DBMS came in use:

Database Management Systems (DBMS) refer to the technology solution used to optimize
and manage the storage and retrieval of data from databases. It is collection of inter-
related data. It has set of programs to access the data. Basically, it contains information
about particular enterprise. DBMS offers a systematic approach to manage databases
via an interface for users as well as workloads accessing the databases via apps.

The management responsibilities for DBMS encompass:

•Information within the databases

•The processes applied to databases, such as access and modification

•The database’s logic structure

1.3 Database Life Cycle
•The database life cycle is a cycle that traces the history of the database in an information system.

•The database life cycle incorporates the necessary steps involved in database development, starting
with requirements analysis and ending with monitoring and modification.
•Database life cycle consists of four stages, namely:
(1) requirements analysis
(2) logical design
(3) physical design
(4) database implementation, monitoring, and modification.
Database Life Cycle

 A Conceptual Data Model is a diagram identifying the business concepts (entities)
 Normalization is the process of organizing data in a database to reduce data redundancy.
 1.4 Database Models
Data Model gives us an idea that how the final system will look like after its complete implementation. It defines the data elements and the
relationships between the data elements. Some of the Data Models in DBMS are:

1.Hierarchical Model

2.Network Model

3.Entity-Relationship Model

4.Relational Model

5.Object-Oriented Data Model

6.Object-Relational Data Model

7.Flat Data Model

8.Semi-Structured Data Model

9.Associative Data Model

10.Context Data Model

Hierarchical Model
Hierarchical Model was the first DBMS model. This model organises the
data in the hierarchical tree structure. The hierarchy starts from the
root which has root data and then it expands in the form of a tree
adding child node to the parent node.

Features of a Hierarchical Model:

One-to-many relationship, Parent-Child Relationship, Deletion
Problem, Pointers

Advantages : It is very simple and fast to traverse through a tree-like

structure.
Disadvantages: Complex relationships are not supported, If a parent
node is deleted then the child node is automatically deleted.

Network Model
This model is an extension of the hierarchical model. It was the most
popular model before the relational model. This model is the same as
the hierarchical model, the only difference is that a record can have
more than one parent. It replaces the hierarchical tree with a graph.

Features of a Hierarchical Model:

Ability to Merge more Relationships, Many paths, Circular Linked
List

Advantages : The data can be accessed faster than the hierarchical

model. This is because the data is more related in the network model
and there can be more than one path to reach a particular node.
Secondly, data integrity is present
Disadvantages: As more and more relationships need to be handled the
system might get complex. Any change like update, deletion, insertion
is very complex.
Entity-Relationship Model
Entity-Relationship Model or simply ER Model is a high-level data
model diagram. the ER diagram as a visual tool to represent an ER
Model. ER diagram has the following three components:

Entities: Entity is a real-world thing. It can be a person, place, or even

a concept. Example: Teachers, Students, etc are some of the entities of
a School Management System.
Attributes: An entity contains a real-world property called attribute.
This is the characteristics of that attribute. Example: The entity
teacher has the property like teacher id, salary, age, etc.
Relationship: Relationship tells how two attributes are related.
Example: Teacher works for a department.

Features of ER Model
Graphical Representation for Better Understanding, ER Diagram: ER
diagram is used as a visual tool for representing the model.
Database Design: This model helps the database designers to build the
database and is widely used in database design.

Advantages: Simple, Effective Communication Tool, Easy Conversion.

Disadvantages: No industry standard for notation, Hidden information
Relational Model
Relational Model is the most widely used model. In this model, the
data is maintained in the form of a two-dimensional table.

Advantages: Simple, scalable, Structural Independence.

Disadvantages: Hardware Overheads, Bad Design
Object-Oriented Data Model
• The real-world problems are more closely represented through
the object-oriented data model.
• In this model, both the data and relationship are present in a
single structure known as an object.
• We can store audio, video, images, etc in the database which
was not possible in the relational model(although you can store
audio and video in relational database, it is adviced not to
store in the relational database). In this model, two are more
objects are connected through links.

Object-Relational Model
As the name suggests it is a combination of both the relational
model and the object-oriented model. This model was built to fill
the gap between object-oriented model and the relational model.
It have many advanced features like we can make complex data
types according to requirements using the existing data types.
The problem with this model is it can get complex and difficult to
handle. So, proper understanding of this model is required.

Flat Data Model (Physical data model type)

It is a simple model in which the database is represented as a
table consisting of rows and columns. To access any data, the
computer has to read the entire table. This makes the modes
slow and inefficient.
Semi-Structured Model
Semi-structured model is an evolved form of the relational model. We
cannot differentiate between data and schema in this
model. Example: Web-Based data sources which we can't differentiate
between the schema and data of the website. In this model, some entities
may have missing attributes while others may have an extra attribute.
This model gives flexibility in storing the data. It also gives flexibility to the
attributes. Example: Storing any value in any attribute then that value
can be either atomic value or a collection of values.

Associative Data Model

Associative Data Model is a model in which the data is divided into two
parts. Everything which has independent existence is called as
an entity and the relationship among these entities are called association.
The data divided into two parts are called items and links.
Item: Items contain the name and the identifier(some numeric value).
Links: Links contain the identifier, source, verb and subject.

Context Data Model

Context Data Model is a collection of several models. This consists of
models like network model, relational models etc. Using this model we can
do various types of tasks which are not possible using any model alone.