8/3/2019 LMS_SRS

1/10

Index

1 Purpose

2 Scope

3 Glossary

4 Overview

5 System Environment

6 Feasibility Study

7 Working of Present System

8 Drawback of present system

9 Proposed System

10 Requirement analysis

11 ER diagram

8/3/2019 LMS_SRS

2/10

Lib r a r y Manag e ment S ys te m

1) Purpose:-

The purpose of this application are as follows :a) The software is for automation of library.b) It provides following facilities to :

Operator :

a) Can enter details related to a particular book.b) Can provide membership to members.

Admin :a) Can read and write information about any

member.b) Can update, create, delete the record of membership

as per requirement and implementation plants.

1) Scope : This software system will be a Library managementSystem for a user. This system will be designed to maximizeproductivity by providing information about books from entire library andin various category. The user will get the details of the respective booksalong with the shell no., availability of book, which would otherwisehave to be performed manually.

By maximizing the efficiency, the system will meet the usersneeds while remaining easy to understand and use more specifically, Itwill provide the information about the books in a well categorizedmanner reducing the overheads. It will provide the most unique detailabout the books which tell the most important reason to read the book.It will provide the name of book if you just entered topic name . It willalso provide the search based on author name.

8/3/2019 LMS_SRS

3/10

2)Glossary

Term Definition

Member Person who access the system.Database Collection of all the books stored by this system.Software RequirementsSpecification

A document that completely describes all of thefunctions of a proposed system and the constraintsunder which it must operate.

Librarian Person who update the system.

3) 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 can take home and return them.

4)System Environment

Ask Name Name

8/3/2019 LMS_SRS

4/10

5)Feasibility StudyIn 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.

6) WORKING OF PRESENT MANUALSYSTEM

The staffs of library are involved in the following tasks.

a) person have to fill membership form and they are provided with

Display

Screen

Library

Mgmt

SystemMember

Ask Author

Wise Author

Publishe

Availability of

Book

Ask

availability

Asks

ublisher

8/3/2019 LMS_SRS

5/10

membership id.

b) Each time member want to issue book, librarian have to searchthe book shelf.

c) Before Issuing new book , Librarian have to check the record ofthat particular member.

d) If member had particular book more than allowed time thenLibrarian has to calculate the fine manually .

1) DRAWBACKS OF PRESENT SYSTEM

Some of the problems being faced in manual system are as follows:

a) Fast report generation is not possible.

b) Tracing a book is difficult.

c) Information about issue/return of the books are not

properly maintained.

d) No central database can be created as information is not

available in database.

1) PROPOSED SYSTEM

There will be three major components :

a). Stock maintenance.

b). Transaction entry.

8/3/2019 LMS_SRS

6/10

c). Reports.

Proposed system provides with following solutions :a) It provides "better and efficient" service to members.

b) Reduce the workload of employee.c) Faster retrieval of information about the desired book.

d) Provide facility for proper monitoring reduce paper work and

provide data security.

e) All details will be available on a click.

2)Requirement AnalysisA 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 journals

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. Eachlibrary 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

8/3/2019 LMS_SRS

7/10

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 number(s)

Fines

Media currently checked out

Media on hold

Put media on hold

Pay fines for lost or late items

Update personal information:

Phone numbers

Addresses

Passwords

Functions for librarians are the same as the functions for

customers plus the following:

Add customers

Add library cards and assign them to customers

Check out media

Manage and transfer media that is currently on hold

Handle returns

Modify customers' fines

Add media to the database

Remove media from the database

Receive payments from customers and update the

customers' fines

View all customer information except passwords

8/3/2019 LMS_SRS

8/10

11)ER Diagram :

It is clear that the physical objects from the previoussection

a) the memberb) booksc) library

correspond to entities in the Entity-Relationship model, and theoperations to be done on those entities holds, checkouts, and soon correspond to relationships. However, a good design willminimize redundancy and attempt to store all the required

information in as small a space as possible.

8/3/2019 LMS_SRS

9/10

8/3/2019 LMS_SRS

10/10