Lovely Professional

University

TERM PAPER
Of
DBMS

TOPIC: - Online LMS

[Online Library Management System]

Submitted to: Submitted by:

Mr. Nandan Sujati Pramod Ku. Tiwari
Lecturer, LSM Roll no. - B44
LPU Reg.No-
10901147
Sec. -
S1906
MBA
-IT

Index

1. Declaration Page no: 3

2. Acknowledgement Page no: 4

3. Preface Page no: 5

4. Introduction Page no: 6

5. Feasibility Study Page no: 8

6. Online Libraries Are Great for Research Page no: 9

7. Data Tables Page no: 10

8. Physical Database Design Page no: 13

9. Data Flow Diagram (DFD) Page no: 15

10. Entity Relationship Diagram Page no: 16

11. Screen Shots of Form Page no: 18

12. Future Scope Page no: 21

13. Conclusion Page no: 22

14. References Page no: 20

DECLARATION

I, Pramod Kumar Tiwari student of Lovely Professional University have

completed the Project on:

Online LMS: Online Library Management System

The information given in this project is true to the best of my knowledge.

(PRAMOD KU. TIWARI)

ACKNOWLEDGEMENT
First of all I would like to thank the Lovely Professional University and take the
opportunity to do this project as a part of the MBA-IT.

Many people have influenced the shape and content of this project, and many
supported me through it. I express my sincere gratitude to Mr. Nandan
Sujati for assigning me a project on DBMS, which is an interesting and
exhaustive subject.

He has been an inspiration and role model for this topic. His guidance and active
support has made it possible to complete the assignment.

Last but not the least I would like to thank the Almighty for always helping me.
 PREFACE

This project is undertaken to fulfil the project work component of the MBA-IT
programme in 2nd Semester. My project guide from L.P.U is Lect. Mr.
Nandan Sujati.

This term paper is based on the Computer and Introduction of the Online LMS .
INTRODUCTION OF ONLINE LIBRARY MANAGEMENT SYSTEM:

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

Online library management system, also known as an automated library system is

software that has been developed to handle basic housekeeping functions of a library.

NEED OF LIBRARY DATABASE :

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 two types: books and videos.

The library must keep track of the status of each media item: its location, status,
descriptive attributes, and cost for losses and late returns. Books will be identified by
their ISBN, and movies by their title and year. In order to allow multiple copies of the
same book or video, each media item will have a unique ID number.

Customers will provide their name, address, phone number, and date of birth when
signing up for a library card. They will then be assigned a unique user name and ID
number, plus a temporary password that will have to be changed. Checkout operations
will require a library card, as will requests to put media on hold. Each library card will
have its own fines, but active fines on any of a customer's cards will prevent the customer
from using the library's services.

The library will have branches in various physical locations. Branches will be identified
by name, and each branch will have an address and a phone number associated with it.
Additionally, a library branch will store media and have employees.

Employees will work at a specific branch of the library. They receive a paycheck, but
they can also have library cards; therefore, the same information that is collected about
customers should be collected about employees.

FUNCTIONS FOR CUSTOMERS:

 Log in.
 Search for media based on one or more of the following criteria.

○ Type (book, video, or both)

○ Title.
○ Author or director.
○ Year.
Access their own account information:

○ Card numbers.
○ Fines.
○ Media currently checked out.
○ Media on hold.

1- PURPOSE :
The purpose of this application are as follows -
 The software is for automation of library.
 It provides following facilities .

Operator :

 Can enter details related to a particular book.

 Can provide membership to members.

Administrator :

 Can read and write information about any member.

 Can update, create, delete the record of membership as per requirement
and implementation plants.

2- SCOPE :
The different areas where we can use this application are –

 Any education institute can make use of it for providing information about
author, content of the available books.
 It can be used in offices and modifications can be easily done according to
requirements.

3- TECHNOLOGY USED :

Front End : Servlets, HTML, Java script.

Back End : MS Access, Apache Tomcat server.

4- ASSUMPTIONS :
  This application is used to convert the manual application to the online
application.
 Customized data will be used in this application.
 User does not have right to enter information about books.

5- OVERVIEW :
Project is related to library management which provides reading services to its
members. Any person can become a member of the library by filling a
prescribed form.
They can get the book issued, so that they cab take home and return them.

6- FUNCTIONALITY :

 Online membership.
 Keeps the track of issues and submission of books.

FEASIBILITY STUDY-

In feasibility study phase we had undergone through various steps which are
describe as under :
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized system.
3. Analyze the draw back of existing system (manual) system.

WORKING OF PRESENT MANUAL SYSTEM-

The staffs of library are involved in the following tasks.

1- Membership process : person have to fill membership form and they are
provided with member id.

DRAWBACKS OF PRESENT SYSTEM-

Some of the problems being faced in manual system are as

follows:
1. Fast report generation is not possible.
2. Tracing a book is difficult.
3. Information about issue/return of the books are not properly maintained.
4. No central database can be created as information is not available in
database.

PROPOSED SYSTEM-

There will be three major components :

1. Stock maintenance.
2. Transaction entry.
3. Reports.

Proposed system provides with following solutions :

1. It provides "better and efficient" service to members.
2. Reduce the workload of employee.
3. Faster retrieval of information about the desired book.
4. Provide facility for proper monitoring reduce paper work and provide data
security.
5. All details will be available on a click.

ONLINE LIBRARIES ARE GREAT FOR RESEARCH-

I had no idea that there were so many online libraries until I took a research assistant
job. It was a very pleasant surprise. There are so many quality libraries available
online to use. You might feel a little overwhelmed with how many resources are
literally at your fingertips. The great news is that students can use these online
libraries anytime of the day or night.

CONVIENANCE :
You remember the days when you had to drive to the library.
You hoped that what they had on the shelves would cover your project. Sometimes,
you would have to go to another library just to finish getting your research. The
online libraries gets rid of all this. You can sit on your laptop in a coffee shop or be at
your desk at home and access these libraries.

USER FRIENDLY:
One terrific thing about online libraries is how user friendly
they are. You don't have to have a ton of computer skills to get around in them. The
majority of them even offer a video or slide show tutorial if you want to learn how to
navigate through their books. You no longer have to lug books back and forth to a
physical library. You can go to the online library anytime that you have time to both
study and have a PC.
HIGHLIGHT FEATURE :
I'm sure you remember how mad your teachers would
get if you underlined in the books. It was even worse if you whipped out a highlighter
and started using it. Would you ever get bad looks! The good news about online libraries
is that the majority of them have a highlighting tool. You click a button, highlight your
text online and you have marked up the book. You can highlight the important stuff
without getting into any trouble!

CITATION FEATURE :
The other cool thing about the highlights for the online
libraries is that they will remember what you highlighted. You can use the bibliography
tool. It will let you choose to get the reference for the highlight. This is so helpful if you
use the highlights for quotes in your paper. You don't have to sit there and figure out how
to properly footnote or cite your work. The online library does all that work for you. All
you have to do is copy and paste it directly into your paper.

DATA TABLES :
Table : Members

S.no. Column Data Type Length Description

Name
1 Id_no Text 50 Unique identification
of the members
2 Name Text 70 Name of members

3 Address Text 100 Location of Members

4 Date of issue Date/Time Date of Registration

5 Date of expiry Date/Time Registration Expiry Date

6 Status Text 50 Permanent/Temporary

Table : Add Books

S.no. Column Name Date-Type Description

1 Book_name Text Title of the book

2 Book code Text Book identification

number

3 Author Text Author of books

4 Date of Date/time Date on which book

Arrival was
Received

5 Price Text Cost of books

6 Rack_no. Text Almirah no.

7 No_of_books Text Quantity of books

8 Subject_code Text Unique identification

no of
particular subject
Table : Issue

S.no. Column Type Date Type Description

1 Id_no Text User identification

number

2 Book_name Text Title of books

3 Issue_date Date/time Date on which book is

Issued

4 Due_date Date/time Due date on which

book is
to be returned
PHYCICAL DATABASE DESIGN-
The next step was to create the physical
database and input some sample data. In order to turn the relational design into a
database, we ran the following script in UNCC's Oracle database:

Table-1 : Member
CREATE TABLE Member ( S.no. INTEGER, Column name CHAR(50), Data Type
VARCHAR(50),Length INTEGER, Description VARCHAR(100));

INSERT INTO Member

Values(‘& S.no.’, ‘& Column name’, ‘& Data Type’, ‘& Length’, ‘& Description’);

INSERT INTO Member

Values(1, ‘Id_no’, ‘Text’, 50, ‘Unique identification of the members’);

INSERT INTO Member

Values(2, ‘Name’, ‘Text’, 70, ‘Name of members’);

INSERT INTO Member

Values(3, ‘Address’, ‘Text’, 100, ‘Location of members’);

INSERT INTO Member

Values(4, ‘Date of issue’, ‘Date/Time’, ‘Date of Registration’);

INSERT INTO Member

Values(5, ‘Date of expiry’, ‘Dtae/Time’, ‘Registration Expiry Date’);

INSERT INTO Member

Values(6, ‘Status’, ‘Text’, 50, ‘Permanent/Temporary’);

Table-2 : Add Books

CREATE TABLE Add Books ( S.no. INTEGER, Column name CHAR(50), Data Type
VARCHAR(50), Description VARCHAR(100));

INSERT INTO Add Books

Values(‘& S.no.’, ‘& Column name’, ‘& Data Type’, ‘& Description’);

INSERT INTO Add Books

Values(1, ‘Book _name’, ‘Text’, ‘Title of the book’);

INSERT INTO Add Books

Values(2, ‘Book _code’, ‘Text’, ‘Book identification number’);
INSERT INTO Add Books
Values(3, ‘Author’, ‘Text’, ‘Author of book’);

INSERT INTO Add Books

Values(4, ‘Date of arrival’, ‘Date/Time’, ‘Date on which book was Received’);

INSERT INTO Add Books

Values(5, ‘Price’, ‘Text’, ‘Cost of books’);

INSERT INTO Add Books

Values(6, ‘Rack_no.’, ‘Text’, ‘Almirah no.’);

INSERT INTO Add Books

Values(7, ‘No_of_books’, ‘Text’, ‘Quantity of book’);

INSERT INTO Add Books

Values(8, ‘Subject_code’, ‘Text’, ‘Unique identification no of particular subject’);

Table-3 : Issue

CREATE TABLE Issue ( S.no. INTEGER, Column Type CHAR(50), Date Type
VARCHAR(50), Description VARCHAR(100));

INSERT INTO Issue

Values(‘& S.no.’, ‘& Column Type’, ‘& Data Type’, ‘& Description’);

INSERT INTO Issue

Values(1, ‘Id _no’, ‘Text’, ‘User identification number’);

INSERT INTO Issue

Values(2, ‘Book _name’, ‘Text’, ‘Title of books’);

INSERT INTO Issue

Values(3, ‘Issue_date’, ‘Date/Time’, ‘Date on which book is Issued’);

INSERT INTO Issue

Values(4, ‘Due_date’, ‘Date/Time’, ‘Due date on which book is
to be returned’);
 DATA FLOW DIAGRAM (DFD)-

-----Send no dues
Student --------Request for create member

-------Send membership details

Management
Membership
Managemet
Send report-----

Req. for report

Req. for discounting membership

----- Member details

Penalty
Member Report
Managemet

------- Penalty amount

-------- Book details

Books

Book Issue
Managemet
------ Issue details

---- Book issue details

Book Issue
----- Req. for book issue

------- Reminder for return book with penalty

-------Send penalty report

------ Return book

Student
 ER- DIAGRAM-

It is clear that the physical objects from the previous section – the member, books,
library – correspond to entities in the Entity-Relationship model, and the operations to
be done on those entities – holds, checkouts, and so on – correspond to relationships.
However, a good design will minimize redundancy and attempt to store all the
required information in as small a space as possible.
 LIBRARY

boo no_of_b
k_n ooks
e a m
boo
k _c o
de .
rack_no
contai
ns

authe t
r subjec
code
BOOKS
price

issue
s
status addres
nt
amou
is sue
date_
retur MEMBER
n issue

Date_
id name ex piry
type

id

STATUS OF ISSUE
id book
e _nam
na Date
Book_ e _iss
u
me
STATUS OF RETURN Date_expir
e
_c od y
Book

od Date_ex
Te_book_c ry
pi
e
date
_iss
e u
SNAPSHOTS-
 FUTURE SCOPE-

FUTURE SCOPE OF APPLICATION-

This application can be easily implemented under various situations. We can add new
features as and when we require. Reusability is possible as and when require in this
application. There is flexibility in all the modules.

SOFTWARE SCOPE-

 EXTENSIBILITY-
This software is extendable in ways that it original
developers may not expect. The following principles enhance extensibility like
hide data structure, avoid traversing multiple links or methods, avoid case
statement on object type and distinguish public and private operations.

 REUSABILITY-
Reusability is possible as and when require in this
application. We can update it next version. Reusable software reduces design,
coding and testing cost by amortizing effort over several designs. Reducing the
amount of code also simplifies understanding, which increases the likelihood that
the code is correct. We follow up both types of reusability: Sharing of newly
written code within a project and reuse of previously written code on new
projects.

 UNDERSTANDABILITY-
A method is understandable if someone other
than the creator of the method can understand the code (as well as the creator after
a time lapse). We use the method, which small and coherent helps to accomplish
this.

 COST-EFFECTIVENESS-
Its cost is under the budget and make within
given time period. It is desirable to aim for a system with a minimum cost subject
to the condition that it must satisfy the entire requirement.
Scope of this document is to put down the requirements, clearly identifying the
information needed by the user, the source of the information and outputs
expected from the system.
CONCLUSION-
From a proper analysis of positive points and constraints on
the component, it can be safely concluded that the product is a highly efficient
GUI based component. This application is working properly and meeting to all
user requirements. This component can be easily plugged in many other systems.

REFERENCES:

 http://www.apache.org/

 http://www.wikipedia.org/

 http://www.google.co.in/search/project+on+library+management
+system.
 http://www.freetutes.com/systemanalysis/sa7-designing-basic-
model-er-diagrams.html