Normalize DatabaseNormalize Database 1

Rdbms Project
On
“Library Management System”
Submitted In Partial Fulfilment For The Degree Of
Masters In Computer Application
In
Department Of School Of Computer Science
From Dr.Vishwanath Karad MIT World Peace University Pune

Session: 2022-2023

Submitted By: Submitted To:

JIGYASU SINGH CHOUHAN DR. C. H. PATIL

Dr.Vishwanath Karad MIT World Peace University Pune

MIT World Peace University
Pune
Department Of School Of Computer Science
September 2022

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 2

Session 2022-23

Certificate

This Is To Certify That The Work Which Is Being Presented In The Rdbms Project Entitled
“Library Management System ” Has Been Submitted To DR. C. H. PATIL Fulfilment Of
The Requirement For The Award Of Degree Of Masters In Computer Application

Date:

Place:

Head Of Department Principal

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 3

Contents
Rdbms Project.........................................................................................................................................................1
Certificate...............................................................................................................................................................2
1. Problem Of Statement....................................................................................................................................4
2. Entities And Their Attributes...........................................................................................................................6
3. Relationships Between Entities –....................................................................................................................7
4. Er Diagram......................................................................................................................................................8
5. CONVERT TO DATABASE.................................................................................................................................9
 The Library Has The Following Tables In Its Database............................................................................9
A. BOOKS...................................................................................................................................................9
B. STUDENT................................................................................................................................................9
C. STAFF.....................................................................................................................................................9
D. FACULTY................................................................................................................................................9
E. PERIODICALS........................................................................................................................................10
F. LIBRARIAN...........................................................................................................................................10
G. AUTHOR...............................................................................................................................................10
6. Normalize Database......................................................................................................................................11
A. Why Normalization:.............................................................................................................................11
 Step Number 1:.....................................................................................................................................11
 Step Number 2:.....................................................................................................................................11
B. 2nd Normal Form.................................................................................................................................11
C. Third Normal Form (3nf)......................................................................................................................12
1. Normalize Database 1nf.......................................................................................................................13
 After First Normalization.......................................................................................................................13
2. Normalize Database 2nf.......................................................................................................................13
3. Normalize Database 3nf.......................................................................................................................14
 Before third normal form......................................................................................................................14
 Staff table..............................................................................................................................................14
 Staff contact..........................................................................................................................................15
 STUDENT Table before Third normalized Form:....................................................................................15
4. Final Form.............................................................................................................................................15
 Student contact table:...........................................................................................................................15
 Student table:........................................................................................................................................16
Normalization End................................................................................................................................................16
LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN
 Normalize DatabaseNormalize Database 4

1. Problem Of Statement

In Our Existing System All The Transaction Of Books Are Done Manually, So Taking
More Time For A Transaction Like Borrowing A Book Or Returning A Book And Also
For Searching Of Members And Books. Another Major Disadvantage Is That To
Preparing The List Of Books Borrowed And The Available Books In The Library Will
Take More Time, Currently It Is Doing As A One-Day Process For Verifying All
Records. So, After Conducting The Feasibility Study We Decided To Make The Manual
Library Management System To Be Computerized. Proposed System Is An Automated
Library Management System. Through Our Software User Can Add Members, Add
Books, Search Members, Search Books, Update Information, Edit Information, Borrow,
And Return Books In Quick Time.

Some Of The Problems Being Faced In Manual System Are As Follows:

 Fast Report Generation Is Not Possible.
 Tracing A Book Is Difficult.
 Information About Issue/Return Of The Books Is Not Properly Maintained.
 No Central Database Can Be Created As Information Is
 Not Available In Database.
 Our Proposed System Has The Following Advantages.
 User Friendly Interface
 Fast Access To Database
 Less Error

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 5

 More Storage Capacity

 Search Facility
 Look And Feel Environment
 Quick Transaction All The Manual Difficulties In Managing The Library Have Been
Rectified By Implementing Computerization
 A College Library Management Is A Project That Manages And Stores Books
Information Electronically According To Student’s Needs. The System Helps Both
Students And Library Manager To Keep A Constant Track Of All The Books
Available In The Library. It Allows Both The Admin And The Student To Search For
The Desired Book. It Becomes Necessary For Colleges To Keep A Continuous
Check On The Books Issued And Returned And Even Calculate Fine. This Task If
Carried Out Manually Will Be Tedious And Includes Chances Of Mistakes. These
Errors Are Avoided By Allowing The System To Keep Track Of Information Such
As Issue Date, Last Date To Return The Book And Even Fine Information And Thus
There Is No Need To Keep Manual Track Of This Information Which Thereby
Avoids Chances Of Mistakes.
 Thus, This System Reduces Manual Work To A Great Extent Allows Smooth Flow
Of Library Activities By Removing Chances Of Errors In The Details.

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 6

2. Entities And Their Attributes

 BOOK: Strong entity set- book_code is used to identify each entity

uniquely Book_code,book_name, Author, date_of_purchase, price,
subject_code, rack_no, no_of_books
 STAFF: Strong entity set- staff_id is used to identify each entity
uniquely Staff_id, staff_name, dob, address, designation, salary,
date_of_joining
 STUDENT: Strong entity type- student_id is used to identify each
entity uniquely Student_id, name, branch, fine, address, phone_no,
issue_date, expiry_date
 FACULTY: Strong entity type- f_id is used to identify each entity
uniquely F_id, name, address, phone_no, department
 LIBRARIAN: Strong entity type- admin_login is used to identify each
entity uniquely Admin_login,admin_password
 AUTHOR: Strong entity type- author_id is used to identify each entity
uniquely Author_id,author_name, dob, address, experience
 PERIODICALS: Strong entity type- pr_id is used to identify each
entity uniquely pr_id, pr_name, month_of_release, publisher_name

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 7

3. Relationships Between Entities –

 BOOK – STUDENT relationship It’s a one to many relationship as one book can
be issued by only one student. This participation is partial from both the side
because all the book cannot be issued and it is also not necessary that all the
students of the library is issuing the book.
 BOOK – FACULTY relationship It’s a one to many relationship as one book
can be issued by only one faculty. This participation is partial from both the side
because all the book cannot be issued and it is also not necessary that all the
faculty is issuing the book.

 All other relationship is managed by the librarian ie. managing the other
entity types of the library

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 8

4. Er Diagram

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 9

5. CONVERT TO DATABASE
 The Library Has The Following Tables In Its Database
A.BOOKS
BOOK_CODE BOOK_NAME SUBJECT_CODE NO_OF_BOOKS rack_no price DATE_OF_PURCHA

STUDENT_ID NAME TYPE ADDRESS FIN PHONE_NUMBER ISSUE_DATE EXPIRY_DA

E

B.STUDENT

C. STAFF
STAFF_I STAFF_NAME STAFF_DESIGNATION ADDRESS DATE_OF_JOINING SALAR DOB
D Y

D. FACULTY
F_ID NAME PHONE NO DEPARTMENT ADDRESS

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 10

E. PERIODICALS
PR_ID PR_NAME MONTH_OF_RELEASE PUBLISHER_NAME

F. LIBRARIAN
ADMIN_LOGIN ADMIN_PASSWORD

G. AUTHOR
AUTHOR_ID AUTHOR_NAME DOB ADDRESS EXPERIENCE
,

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 11

6. Normalize Database

Why Normalization:

Database Normalization Is The Process Of Removing Redundant Data From Your

Tables In

Order To Improve Storage Efficiency, Data Integrity, And Scalability. Normalization

Generally Involves Splitting Existing Tables Into Multiple Ones, Which Must Be

Re-Joined Or Linked Each Time A Query Is Issued. Given Table Is Converted To Its 1nf
As Follows.

Step Number 1:
Elimination Of Duplicative Columns From Table 1.

Step Number 2:
Create Separate Table For Each Group Of Related Data And Identify Each Row With
Unique Column (Primary Key).

 2nd Normal Form

A Table Is In First Normal Form And Each Non-Key Field Is Functionally Dependent
Upon Primary Key.

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 12

Now We'll Take The Table Above And Design New Tables That Will Eliminate The
Repeated Date In Non Key _Field

To Decide What Fields Belong Together In A Table, Think About Which Field
Determines The Values In Other Fields.

Create A Table For Those Fields And Enter The Sample Data. Think About What The
Primary Key For Each Table Would Be And About The Relationship Between The
Tables.

Mark The Primary Key For Each Table And Make Sure That You Do Not Have
Repeated Data In Non-Key Fields.

 Third Normal Form (3nf) –

Requires That There Are No Functional Dependencies Of Non-Key Attributes On
Something Other Than A Candidate Key.
Table Is In 3nf If All Of The Non Primary-Key Attributes Are Mutually Independent
There Should Not Be Transitive Depeinces

1. Normalize Database 1nf

Issue_Id Book_Id Student_Id
1122 110,120,320 Bite183

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 13

In The Issue_Id Table There Is Repeating Book_Id . A Student Has Issued 3 Books

 After First Normalization

Issue_Id Book_Id Student_Id

1122 110 Bite183
1122 320 Bite183
1122 120 Bite183

2. Normalize Database 2nf

In The Following Student Relation All Attributes Are Dependent On The Primary Key
Student_Id

Student_Id Name Depid Issue_Date Expairy_Date Phone

Bite183 JIGYASU 11 22-09-22 20-10-22 8619708469

We Can Create Two Other Relations From Student Table One Is Department Fields Are
Fully Dependent On The Primary Keys Dep_Id

Dep_Id Dep_Name

11 Cs & It Department

22 Education Department

33 Economics Department

44 Laaw Department

Student_Id Name Issue_Date Expairy_Date Phone

Bite183 Jigyasu 22-09-22 20-10-22 8619708469

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 14

3. Normalize Database 3nf

 Before third normal form

Staff_id Name Genda r Designation Address City state PHONE

1101 JIGYASU M Librarian Kothrud PUNE Maharashtra 9414673244
1345 ANIKA F ACCOUNTANT Baner PUNE Maharashtra 8619708469
1452 HARSH M Data entry Hinjewadi PUNE Maharashtra 9632587410
2264 SAURAV M MANAGER KARADI PUNE Maharashtra 9517537412

 After 3rd Normalization

 Staff table

Staff_Id Name Gender

 Staff contact
Staff_Id Address City State PHONE

 STUDENT Table before Third normalized Form:

Std_id Name Gender Address City State Phone Dep_id

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN

 Normalize DatabaseNormalize Database 15

4. Final Form

Student_id Dep_id Department

Bite01 11 Cs & IT
Bite02 22 Education
Department
Bite03 33 Economics
Department

 Student contact table:

Student_id Address City State Phone
Bite01 Kothrud Pune Maharashtr 9414673244
a
Bite02 Baner Pune Maharash 8619708469
tra

 Student table:

Student_id Name Gender studentDepartment

Normalization End

LIBRARY MANAGEMENT SYSTEM JIGYASU SINGH CHOUHAN