C0LLEGE OF COMPUTING AND INFORMATICS

DEPARTMENT OF INFORMATION SCIENCE

GROUP PROJECT DOCUMENTATION FOR THE COURSE ADVANCED

DATABASE
ON LIBRARY MANAGEMENT SYSTEM

NAME ID NO
1. SAMUEL TEFERA DEMISSIE----------------------------------2716/12
2. RAMADAN JEMAL------------------------------------------------2647/12
3. ROBEL NEGESA----------------------------------------------------2676/12

INSTRUCTOR: ABEBE SH.

DATE OF SUBMISSION: NOV, 24, 2021

HARAMAYA, ETHIOPIA
 ABSTRACT
This project describes our group's work on library Management system.
We used the Entity-Relationship model to design the Databases that will
store and organize the library's data. We have created the database using
structured query language (sql) and organized it with some sample data.
The system can keep track of library cards (borrower detail), readers,
staff, books, and the relationships between them. We have created
databases allows users and librarians to access the system remote.
 Library Management System

Introduction
The Database Library System is intended to Automate the library activities such as creating a new
borrower, giving books to the borrowers, maintaining the details of all the item that were available in the
books. This also helps the librarians by providing information such as total copies available each book,
list of books that belong to a particular category (Short, Long Loan, Reference items, etc.).
 PART ONE
OBJECTIVES
 The main objective of this project is to manage the detail of book, reader, and staff, employee.
The project is totally built at administrative to guarantee of the access.
 The purpose of this project is to building application program and simple understanding of entity
of attribute. It tracks all the about book reader and issue. To understanding of any work of entity.
 To generate the report on address member of librarian Manage the information of member
Facilities based on entity and value of attribute
BACKGROUND OF PROJECT
 Library Management System is an application which refers to library systems which are
generally small or medium in size. It is used by librarian to manage the library using a
computerized system where he/she can record various transactions like issue of books, return of
books, addition of new books, addition of new reader etc. With this computerized system there
will be no loss of book record or member record which generally happens when a non-
computerized system is used. In addition, report module is also included in Library Management
System. If user’s position is admin, the user is able to generate different kinds of reports like lists
of reader registered, list of books, issue and return reports.

PART TWO
 2.1 REQUIRMENT AND ANALYSIS
In this section, we will discuss and analyze about the developing process of Library Management System
including requirement and analysis (RAA) and comparison between existing and proposed system. The
functional and non-functional requirements are included in RAA part to provide complete description and
overview of system requirement before the developing process is carried out. Besides that, existing and
proposed provides a view of how the proposed system will be more efficient than the existing one.
1. It can help user to manage the transaction or record more effectively and time-saving.
2. It reduces the risk of paper work such as file lost, file damaged and time consuming.
3. Improvement in control and performance
4. The system is developed to cope up with the current issues and problems of library.
5. The system can add user, validate user and is also bug free. -System must be able to enter issue
information in database.
6. System must be able to update number of books.
7. System must be able to search if book is available or not before issuing books and return date
information.
8. Requirements of analysis a database design determine the data, information, system component,
data processing, data observation, data manipulate and analysis of function required by system.

REQUIRMENT OF THE PROJECT

Ms word
Xampp
Mysql server
Mysql workbench
Window 11 operating system
 PART THREE
3.1 CONCEPTUAL DESIGN
Author:
This table used for all authors name that are found in the book.

Colomns:
Author_id:
Father_name: father name of the author.
last_name:
Awards: the name of the award which the author take.

Book_Details:

This is the master table for all the books that are available in the library. This table contains the complete
list of books that are available in the library. Each Book id provided with a unique ISBN which serves as
a primary key. The book details include the ISBN, Book Title, the year in which that particular book was
published, the type of binding either soft cover or hard cover and the category.

Columns:

ISBN: This is unique ID given to every book .Since there may be a large no. of books with same TITLE,
this ISBN no. will help us to distinguish between books of same title.

Book_Title: Provides the name of the book.

Publication_year: Contains the year of publication in ‘YY’ format (eg:2009à09)

Language: Contains the language in which this book was published.

Category_Type:
This column contains the Category ID whose details can be fetched form the category_master table. The
category ID is a Unique number given to each category.

No_Of_Copies_Actual: This column contains the total no. of copies of each book that were initially
present.

No_Of_Copies_Current: This column contains the total no. of copies of each book that were currently
available .
Author:
This table contain the name of the author in case an author may have more than one book.
Colomns:
F_name : first name
L_name: last name

Category_Details:

This includes the Category ID and Category Name. The Category ID servers as a primary key.
Columns:

Category _ID: This column contains the Unique number that was given to each type of Category.

Category _Name: This column give the names of different types of categories.

Borrower_Details:

This table contains the details of all the persons who lent a book from the library. Each Student will be
given a Unique borrower ID. All the library related activity for a particular person will be captured based
on the Borrower ID. This table will be used to track the borrowing records. The borrower ID will serve as
a primary key here.

Columns:

Borrower_ID: Unique ID given to each Student.

Book_ID: This column contains the book ID which was give to the borrower.

Borrowed_From_Date: The date on which the book was given a particular borrower.

Borrowed_To_Date: The date on which that book was supposed to be returned back or should be
renewed.

Actual_Return_date: The date on which the borrower returned the book to the library.

Issued_by: The ID of the Librarian who issued book to the borrower.

Fin: If the student does not return the book on due date there is punishment from the day counting from
the last returning day.

Staff_Details:

This table contains the details of the staff in the Library. Each Staff member will be given a unique User
ID which serves as a Primary Key.
Columns:

User_ID: The unique ID given to each staff member present in the Library.

User_Name: The Name of the staff member.

Is_Admin: Just checking user is admin or not.

Designation: The role of the staff member in the library such as librarian, assistant, etc.

Student_Details:

This table contains the details of all the students they are eligible for availing Library facilities. Each
student will be provided with a unique Student ID and Borrower ID. The student ID will be Primary Key,
whereas Borrower_ID and Phone_no will be Unique.

Columns:

Student_id: Unique ID given to Each Student.

Student_Name: The Name of the Student.

Sex : Gender of the Student either Male or Female.

Date_Of_Birth: The Date of Birth of the student.

Borrower_ID: The borrower ID assigned to each student.

Department: This is contains student department.

Contact_Number: Contact number of the student.

Shelf_Details:

This table contain the position of the book…That means which floor and shelf the obook is situated.

Column:

Shelf_Id: Contains the shelf number.

Floor: Which floor the shelf is situated.

PART FOUR
Library Management System (SQL Commands)
Creating table “Book_Details”:

Inserting Some Data in “Book_Details” :

Creating Author Table:

Creating Category Table:

Inserting some data in Category Table:

Building Relationship between Book & Category Table:

Creating Borrower Table:

Inserting Some data in Category Table:

Building Relation Between Book & Borrower Table:

ALTER TABLE Borrower_details ADD CONSTRAINT Book_Id_FK FOREIGN KEY(Book_Id) RE
FERENCES Book_Details(ISBN_Code);

Checking Relationship:

Creating Staff Table :

Creating relationship:

Inserting some data in Staff Table:

Creating Student Table:

Inserting Some Data in Student Table:

All Data of Student Table:

Adding Relationship Between Shelf and Book Table:

Creating views:
Checking all relationships :
RELATIONAL SCHEMA DIAGRAM

Creating trigger:
Acknowledgement
First of all we would like to thank God and then our friend Samuel Tefera for his
effort to make this project as real as possible by giving much of his time on this
project and finally we would like to thank our instructor Abebe Shimelis for his
guidance and good teaching .