Case Study based on ERD and Database normalization (20 marks)

Consider the following set of requirements for a Bank database that is used to keep track of
Customer.
 Finwell bank has a multiple branches across the country.
 Each branch has a number, name, city, state, address and phone no.
 Customer includes their name, address, phone no and Adhar card number.
 Accounts have numbers, types (e.g. saving, current) and balance.
 All accounts should have both the branch and the account number.
 An account must have only one customer.
 A customer may have many accounts in different branches.
Based on the above case, solve the following:
 Draw an ER diagram for Bank database.
 Specify key attributes of each entity type.
 Specify the relation type (cardinality) between entities.
 Design a relational database with appropriate tables.
 Normalize the database up-to appropriate level.
To solve questions based on ERD in this case study, write down following theoretical points
from any Database Management System Book.
 Introduction to Entity Relationship Diagram (ERD)
 Components of ERD
 Advantages of ERD
Then draw the ERD as follows:

BRANCH has ACCOUNT

has

CUSTOMER

(Note: Identify the attributes of each entity and add them into ERD. Also mention relation type
between entities as One to One, One to Many or Many to Many.)
To solve questions based on database normalization in the case study, first write down following
theoretical points from Database Management System Book.
 Introduction to Database Management System
 Introduction to relational database
 Introduction to normalization
 Need of normalization
 Different normal form (1NF, 2NF, 3NF)
 (Note: Explanation to each point should be not more than 10-20 lines)
Then prepare single table to record all the data as mentioned in case study as follows:
Table name: Account
Account Number
Branch number
Branch Name
Branch Address
Branch City
Branch State
Branch Phone no
Adhar Card Number
Customer Name
Customer Address
Phone no
Type
Balance

Then convert the tables in first normal form (1NF) by removing repeated groups from single
table and dividing it into different tables along with the Primary key to each table as follows:
Table name: Branch
Branch Number (PK)
Name
Address
City
State
Phone no

Table name: Customer

Adhar Card Number (PK)
Customer Name
Customer Address
Phone no
 Table name: Account
Account Number (PK)
Branch Name
Customer Name
Type
Balance

Now convert tables into second normal form (2NF) by replacing fields from other tables with
primary key as follows:
Table name: Branch
Branch Number (PK)
Name
Address
City
State
Phone no

Table name: Customer

Adhar Card Number (PK)
Customer Name
Customer Address
Phone no

Table name: Account

Account Number
Branch Number (PK)
Adhar Card Number (PK)
Type
Balance
Case Study based on only ERD (10 marks)
ABC Organization is made up of various departments
 Each having a name, no. and an employee who is the manager.
 Information about employee includes name, identification number, birth date, address and
salary.
 Each employee is assigned to one department.
 Each project within the organization is controlled by a department.
 Information about projects includes project name, no. and location.
 Employees from any departments are assigned to projects.
 Hours spent by employees on each project are also recorded.
Based on the above case
a) Draw an ER diagram for the organization.
b) Specify key attributes of each entity type.

To solve questions based on ERD in this case study, write down following theoretical points
from any Database Management System Book.
 Introduction to Entity Relationship Diagram (ERD)
 Components of ERD
 Advantages of ERD
Then draw the ERD by identifying entities (department, employee, project) in the case study
along with their attributes.
Identify the attributes of each entity and add them into ERD. Also mention relation type between
entities as One to One, One to Many or Many to Many.
Case Study based on only Database normalization (10 marks)
A General Hospital consists of a number of specialized wards (such as Radiology, Oncology, etc)

 Each ward hosts a number of patients, who were admitted by a consultant (doctors) employed by
the Hospital.
 The personal details of every patient includes name, number, phone and address.
 Information about ward includes unique name, total numbers of current patients. On admission, the
date and time are kept.
 Doctors are specialists in a specific ward and may check a number of patients and suggest tests.
 A separate register is to be held to store the information of the tests undertaken.
 Number of tests may be conducted for each patient.
 Each test has unique episode No. , category and the final result of test.
Based on the above case
a) Design a relational database with appropriate tables.
b) Normalize the database up-to appropriate level.

To solve questions based on database normalization in the case study, first write down following
theoretical points from Database Management System Book.
 Introduction to Database Management System
 Introduction to relational database
 Introduction to normalization
 Need of normalization
 Different normal form (1NF, 2NF, 3NF)
 (Note: Explanation to each point should be not more than 10-20 lines)
Then prepare single table to record all the data as mentioned in case study.
Then convert the tables in first normal form (1NF) by removing repeated groups from single
table and dividing it into different tables along with the Primary key to each table as follows:
Then convert tables into second normal form (2NF) by replacing fields from other tables with
primary key.

(Note: To solve case studies based on ERD and database normalization, use any book on
Database management system that covers both Entity relationship Diagram and
Normalization topics)