WACHEMO UNIVERSITY

COLLEGUE OF ENG & TECHNOLOGY

SCHOOL OF COMPUTING AND INFORMATICS

DEPARTMENT OF COMPUTER SCIENCE

LIBRARY MANAGEMENT SYSTEM

GROUP MEMBERS

NAME ID

1 YOSEPH TOLOSA……………………………….12D0905

2 SAMUEL HUSSEN ………………………………12D0440

3 SELEABAT ASHAGRE ………………….……..12D0472

4 YARED MISRAK……….…………………………12D0800

5 FIREHIWOT HAILU…….……………………….1301213

6 BEZA ADINEW…………………………..………. 1301161

SUB TO MR.ABENEZER.D

SUB-DATE WED-21-JULY
ABSTRACT

This project describes our group's implementation of a 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,
readers,employs, library locations, books, and the relationships between them.

We have created databases allows users and librarians to access the system remote.
 LIBRARY MANGMENT SYSTEM

Acknowledgement
After we complete our second year first simister database project we would
like to take this chance to express our sincere gratitude to our project
instructor Mrs.Abenezer.D who has guided our a lot through the project
development.

We also want to thanks Director of library and others(seniours & friends)

who give us some information about library system.
TABLE OF CONTENTS PAGE
ABSTRACT ……………………………………………………………………..I
ACKNOLEDGEMENT ………………………….………………………………II
INTRODUCTION ………………………………………..………………….…..III

PART ONE
1.1OBJECTIVES ………………………………………………………………….......1
1.2 BACKGROUND OF PROJECT …………….………………………….......1
PART TWO
2.1 REQUIREMENT AND ANALYS……………........................................2
2.2 COMPARATION B/N THE TWO SYSTEM..…………………………..3
2.3 ADVANTAGE OF PROPOSED SYSTEM……………………...............3
PART THREE
3.1 KEYWORD…………………………………………………………………………4

3.2 CONCEPTUAL DESIGN ……………………………………………............5

3.2.1 REQUIRMENT ANALYSIS………………………………………….………5

3.2.2 ER-DIAGRAM……………………………………………………………………6

3.2.3 PARTICIPATION……………………………………………………………….7

PART FOUR
4.1LOGICAL DESIGN………………………………………………………………….8

4.1.1 NORMALIZATION…………………………………………………………….10

PART FIVE

5.1 PHYSICAL DESIGN………………………………………………………………12

5.1.1 TABLE CREATING SQL SYNTAX…………………………………………12

5.1.2 RELATIONAL SCHEMA DIAGRAM………………………………………13

5.2 QUERIES………………………………………………………………………………14
 LIBRARY MANGMENT SYSTEM

INTRODUCTION
This project will provide a detailed account of the processes our group used to
design and implement a database that can be used to manage a library system.
Each subsection of the project corresponds to an important feature of
database design.
1

PART ONE
1.1 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
1.2 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.
 LIBRARY MANGMENT SYSTEM

PART TWO
2.1 REQUIRMENT AND ANALYSIS
In this chapter, 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

 Microsoft word
 Structural query language server
 Computer
2
2.2 COMPARATION BETWEEN THE TWO SYSTEMS
Existing system does not have any facility of reader login where as proposed system will have a
facility of reader login as well as.

Existing system does not have a facility of online reservation of books whereas proposed system has
a facility of online reservation of books.

Existing system does not have any facility of online notice board where description of workshops
happening in our college as well as nearby colleges is being provided.

Existing system does not have any option of lectures notes uploaded by teachers whereas proposed
system will have this facility.

Existing system does not have any facility to generate reader reports as well book issue reports
whereas proposed system provides librarian with a tool to generate reports.

Existing system does not has any facility for book request and suggestions where as in proposed
system after logging in to their accounts reader can request books as well as provide
suggestions to improve library .

Library management system has been design to automatic, manage and look after over all
processing very large scale library.

This software is capable of managing look issues returns, magazines or new paper sub subscription,
calculating or managing fine and balance payments due from members.

2.3 ADVANTAGE OF PROPOSED SYSTEM

 Immediate retrieval of information

 Better storage of capacity
 Better sorting of efficient reports
 Quick sorting of a information
 Accuracy of data can be non redundancy hence no inconsistency
 Easy to update the information
 In general requirement analysis for our project(library management system) are as follows:
A library database needs to store information pertaining to its users(or customers), its workers,
the physical locations of its branches, and The media stored in those locations. We have decided
to limit the Media to books .
 LIBRARY MANGMENT SYSTEM

PART THREE
3.1Key words
 -Data base design is the process of producing a detailed DATA MODEL of
DATABASE. This data model contains all the needed logical and physical design
choices and physical storage parameters needed to generate a design in a DATA
DEFINITION LANGUAGE, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity.
 The requirements identified in the analysis phase are used as the basis to
develope the new system called database design. in chapter two we
identify What data are required and What are the problems to be solved. in
these chapter we mainly concerned how that data can structured and how
can we accessed those data
 Entity:- Real world objects distinguishable from other objects. That is a person, place,
things, or even for which data is collected and maintained. An entity is described in
database using a set of attributes.This may be strong or weak.
 Entity type: a collection or a set of entities that have the attribute.
 Entity Set: A collection of similar entities.
 Entity Instance: is a single occurrence of an entity type. It is describe just one time in
data model.
 Attribute A particular properties that describe an entity.
 Primary key: is a field or combination of fields that uniquely and minimally identifies
particular member of an entity
 Foreign key: is a field in one table that must match a primary key value in another table
in order to establish the two tables.
 Relationship: Association among two or more entities.
 Candidate Key: Any field that could serve as a primary key.
4

3.2CONCEPTUAL DESIGN

3.2.1 REQUIREMENTS ANALAYSIS

 Watchemo university has its own distinictive

NAME AND ADRESS./it has Also 5 branchs based on Their colleges/.
 Each branches have
NAMES ,LOCATIONS AND BEULDING BLOCKS.
 Employe has
ID,NAME,PHONENUMBER,SEX,AGE,EDUCATIONAL_LEVEL,
ADRESS(CITY,KEBELE,HOUSENUMBER).
 Books have
TITLE,COLLEGUE_TYPE,CARD_NUMBER,AUTHOR,PUB_DATE,EDITION_TYPE
AND SHELF_NUMBER.
 Reader have
NAME,ID_NO,AGE,SEX,DEPARTMNET,PHONE_NUMBER.
 Staff have
NAME,ADRESS(E-MAIL,CITY,BEREOU_NO),EDUCATIONAL_LEVEL,POSITION AND
PHONE_NUMBER.
 Publisher has
PUB_ID,NAME,ADRESS,LOCATION AND ADRESS(E-MAIL,COUNTRTY,CITY)
 Author has
AU_ID,NAME,PHONE_NUM,ED_LEVEL AND ADRESS(CITY,E-MAIL).

SHORT DESCRIPTIVE RELATION_SHIP PARAGRAPH FOR THE REQUIRNMENT.

WATCHEMO UNIVERSITY LIBRARY has to be MANAGED BY STAFF, and the staff LEADS
the BRANCH, each branches HAVE their own EMPLOYEES to GIVE SERVICE for the
READERS the readers use BOOKS based on a time interval and the book PUBLISHED by
PUBLISHER and WRITTEN by the AUTHOR at last the LIBRARY can PURCHASE the book
from the publisher.
 LIBRARY MANGMENT SYSTEM

5 3.2.2 ER-DIAGRAM
E-mail wpage

name adress Ed-lvl

name
ID p-num
phone
LIBRARY
Mn_b
E-mail
adress
STAFF
city
country city
name position
adres leads

phone
phone
publisher Bld-blk
pid
Branch

have name
location

Name phone

Ed-lvl employe
aid ID
publish
adr
author name
city
serve
kebele

title
written
name
Start t

book
reader r-id
BO-ID
use

autho
sex
Editio colleg dept
Return t
6 3.2.3 PARTICIPATION
1 1
LIBRARY Manged by STAFF

1 5

STAFF leads BRANCH

1 M
EMPLOYEE
BRANCH have

M M
EMPLOYEE serve READER

1 M BOOK
RAEDER use

M M
BOOK written Author

M 1
BOOK published publisher
 LIBRARY MANGMENT SYSTEM

7 PART FOUR

4.1 LOGICAL DESIGN

4.1.1RELATIONAL MAPPING
LIBRARY

Name E-mail Web-page

BRANCH

BLOCK-NO LOCATION NAME

STAFF

S-ID NAME ED-LEVEL POSITION E-MAIL CITY

STAFF PHONE

S-ID PHONE

EMPLOYEE

E-ID NAME CITY KEBELE SEX

EMPLOYEE PHONE

E-ID PHONE

READER

R-ID DEPARTMENT SEX NAME

BOOK

B-ID TITLE EDITION COLLEGUE AUTHOR

AUTHOR

A-ID AUTHOR NAME ED-LEVEL

Publisher

p-id Name Country City

Publisher phone

P-id Phone
8 MANAGED BY

Name E-mail Web-page S-ID*

LEADS

B-number Location Name S_id* B-id

HAVE

E-ID NAME Kebele CITY B-ID*

SERVE

E-ID* B-ID*

USE

STARTING RETURN B-ID* R-ID*

TIME TIME

WRITTEN

A-ID* B-ID*

PUBLISHED

B-ID TITLE AUTHOR- Edition P-ID* Collegue

NAME

READER

R-ID DEPARTMENT SEX FULL_NAME

 LIBRARY MANGMENT SYSTEM

4.1 .1NORMALIZATION
STAFF

S_ID S_NAME EDU_LEVEL POSITION

STAFF_EMAIL_CITY

S_ID* EMAIL CITY

STAFF-PHONE

S-ID* Staff PHONE

EMPLOYE PHONE

E-ID* Employee PHONE

AUTHOR

A_ID NAME EDU_LEVEL

PUBLISHER

P-ID NAME COUNTRY CITY

PUBLISHER-PHONE

P-ID* PUBLISHER PHONE

MANAGED BY

LIBRARY_NAME EMAIL WEBPAGE S_ID*

10

LEADS

BLOCK-NUM LOCATION BRANCH_NAME S-ID*

HAVE

E-ID EMPLOYEE NAME KEBELE CITY B-ID*

SERVE

E-ID* R-ID*

USE

START TIME RETURN TIME B ID* R-ID*

PUBLISHED

BOOK-ID TITLE AUTHOR- NAME ED- LEVEL P-ID*

WRITTEN

A-ID* B-ID*
 LIBRARY MANGMENT SYSTEM

11

PART FIVE
5.1 PHYSICAL DESIGN
5.1.1 physical table creating syntaxs
create table staff(s_name varchar(50),s_id varchar(50)primary key,ed_level varchar(30),position varchar(30))

create table author(author_name varchar(50),a_id varchar(50)primary key,ed_level varchar(30))

create table publisher(name varchar(50),p_id varchar(50)primary key,country varchar(30),city varchar(30))

create table staff_phone(s_id varchar(50) foreign key references staff(s_id),staff_phone int)

create table staff_email_city(s_id varchar(50) foreign key references staff(s_id),e_mail varchar(50),city varchar(50))

create table published(b_id varchar(50) primary key,p_id varchar(50) foreign key references
publisher(p_id),author_name varchar(50),edition varchar(50),collegue varchar(50),book_title varchar(50))

create table have (e_idvarchar(50) primary key, employe_name varchar(50),kebele varchar(30),b_id varchar(50)
foreign key references published(b_id))

create table employe_phone(e_id varchar(50) foreign key references have (e_id),employe_phone int)

create table publisher_phone(p_id varchar(50) foreign key references publisher (p_id),publisher_phone int)

create table managed_by(s_id varchar(50) foreign key references staff (s_id),library_name varchar(50),email
varchar(50),webpage varchar(50))

create table leads(s_id varchar(50) foreign key references staff (s_id),block_num int primary key,location
varchar(50),branch_name varchar(50))

create table serve(e_id varchar(50) foreign key references have(e_id),r_id varchar(50) foreign key references
reader(r_id))

create table reader(r_id varchar(50) primary key,full_name varchar(50),sex char,department varchar(50))

create table _use(start_time varchar(50),return_time varchar(50),r_id varchar(50) foreign key references

reader(r_id),b_id varchar(50 )foreign key references published(b_id))

create table written(a_id varchar(50) foreign key references author(a_id),b_id varchar(50) foreign key references
published(b_id))
12

5.1.2 RELATIONAL SCHEMA DIAGRAM

 LIBRARY MANGMENT SYSTEM

13

5.2 Queries

1:- show tha name of female reader with department name?

selectfull_name,departmentfrom reader where sex='f'

2:- show author name only start with s?

selectauthor_namefrom author whereauthor_namelike('s%')

3; show book title found In social collegue?

selectbook_titlefrom published wherecollegue='social'
14

4,list the phone number the staffs with their names?

selects.staff_phone,p.s_namefromstaff_phone s join staff p ons.s_id=p.s_id

5, show books with collegue name and book id?

selectbook_title,b_id,colleguefrom published

6: list librarys branch name and their location

selectbranch_name,locationfrom leads
 LIBRARY MANGMENT SYSTEM

15

7, show the reader name to use the book at 2:00 and the title of the book that
they used?
selectu.start_time,r.full_name,p.book_titlefrom _use u join reader r
onr.r_id=u.r_idinnerjoin published p onp.b_id=u.b_idwherestart_time='2:00'

8 ;list staff members with positions and phone num

selects.s_name,s.position,p.staff_phonefrom staff s joinstaff_phone p ons.s_id=p.s_id

9: List employe name with their phone numbers

selecth.employe_name,e.employe_phonefrom have h joinemploye_phone e one.e_id=h.e_id
16

10 : list cs department students with their names

select department ,full_namefrom reader where department='cs'

17