LIBRARY MANAGEMENT

PROBLEM STATEMENT:

Rungta College of engineering is an affiliated college under the CSVTU, with
4different departments and more than 1800 students studying under it. The main
aim to develop this software is to manage the operations performed in our library.

The basic information about our library is as follows
There are four departments with 60/120 students in each department with a
total strength of 1800 students and 120 lectures.
There are 4000 books available.

The managing services required are

Book management: To maintain the following details
a. Book cost and purchase details.
b. Publisher and author details.
c. To remove the books details in case it had gone out of use or to add new
books name into the document.
Student services:
a. Each student is given three cards (one book per card).
b. The date of books taken and the last date should be documented and
upgraded every weak.
c. On failure of returning the book on or before the due date will be fined
(1Rs per day).
d. Students must submit there cards at the beginning of every semester and
then only the students account should be activated.
Staff services:
a. Each staff is given three cards (one book per card).
b. The date of books taken and the last date should be documented and
upgraded every weak.
c. On failure of returning the book on or before the due date will be fined
(1Rs per day).



SOFTWARE REQUIREMENTS SPECIFICATION

1. INTRODUCTION :

1.1. Purpose:
The main purpose of the specification is to guide the developer about
the book and the account structure, students and staff services, requirements
and the input and output feature.

1.2. Scope:
The LIBRARY MANAGEMENT SYSTEM software has the ability
to display the details of the books available in various departments, the
transactions of books and about the book holders. It enables online
reservation of books. It also enables a fully automated library service, which
makes the word easier and systematic.
BENEFITS:
Saves time.
Reduces the manual work.
Makes the searching work easier.
OBJECTIVES:
Fully automated library service.
Efficient working of the library.

1.3. Definitions, Acronyms and abbreviation:
LAN- Local Area Network.
GUI- Graphical User Network
OS Operating System.
RAM Random Access Memory
ORB-Online Reservation of books
HDD- Hard Disc Drive
LMS- Library Management System

1.4. References:
The books and materials referred during the pre-development stages
of the project include:
Software Engineering- by Roger S. Pressman
Software Engineering- by James Peters
Software Engineering- by Ian Somerville

1.5. Overview:
Section I gives a brief introduction about the document and the
objectives of the software. The overall description such as system interface,
software interface, hardware interface, communication interface are
discussed in section II and the software product featured section III.

2. OVERALL DESCRIPTION:

2.1. PRODUCT PERSPECTIVE:
The product works on a stand alone system. Thus it is independent. It
must be able to run on a LAN of any number of client system under the
control of the server.

2.1.1. System Interfaces:
The client systems should be able to share the data available in the
database among the network connections.

2.1.2: User Interfaces:
The screen format is in the menu type which contains sub-menus
which is used for the interaction with the user. This menu type screen format
allows the user to choose his option. This type of format will make the user
to operate easily.

2.1.3: Hardware interfaces:
The Keyboard and the Printer
Barcode reader
Ethernet Card

2.1.4: Software Interfaces:

NAME VERSION SOURCE
MS-Access 200 or any higher version Microsoft Corporation
OS Windows
XP or 98 or any higher
version
Microsoft Corporation



2.1.5: Communication Interfaces:
Systems are interconnected by a LAN connection. The librarian and
administrators can access it. The LAN has the ability to access his library
accounts from any system within the library.

2.1.6: Memory Constrains:
The system would require a disc space of 20 GB and a 256 MB space
RAM for the service system and 40 GB HDD and a 64 MB RAM for client
systems.

2.1.7: Operations:
The user will be able to take the book through online reservation
system in the website www.mdsathakcollege.org.
The user should get the book from the library on showing his library card.
The user will be able to know his fine amount through this website. The
reservation is done based on the first come first serve bases. There must also
be a back up of the data, which will enable easy recovery from failures that
maybe catastrophic at system oriented.

2.1.8: Site Adaptation Requirements:
The software requires no special modifications to adapt to particular
installations except for the files that are required to be re-created.

2.2. PRODUCT FUNCTIONS:
The major function includes:
Providing details about the books available in library according to
their department and author wise for searching purpose.
Giving details about fine and their time of returning the books.
Provide facility of online registration of books.
Providing facility of online registration of books.
Updating of books by the librarian according to the understandable
order.
Providing the book transaction such as borrowing, renewal, retrieval
of books in an easier manner.




2.3 USER CHARACTERISTICS:
It is sufficient that the users have a basic knowledge needed for
operating the software product. There is no need for any experience or
technical knowledge.

2.4. CONSTRAINTS:
Regularity policies: It is mandatory that no text box must be left
empty or contains insufficient data.
Hardware limitations: There must be a 64 MB on-board memory.
Control Functions: Incase of any errors and service problems, proper
error handling and data recovery mechanism must be included.
Parallel Operations: It must support many users simultaneously.
Language Requirements: Visual basic.
Reliability Requirements: Data redundancy and use of special/blank
characters must be avoided.
Safety/Security Considerations: The application must be exited
always normally.

2.5. ASSUMPTIONS AND DEPENDENCIES
The user requiring the library services must be a member of the
library. The required input files must be present. The details entered about
the books and the cardholders must be a valid one.

2.6. APPORTIONING OF REQUIREMENTS:
Not applicable.











3. SPECIFIC REQUIREMENTS:

3.1. EXTERNAL INTERFACE REQUIREMENTS:

3.1.1. User interfaces:
The interface used is graphical user interface (GUI) and the interface
must be easy to understand. This interface services as a bridge between the
user and the software. It also makes the user interaction with the system
easy. The details about the students and staffs must be filled during online
reservation.

The user interface includes:

3.1.1.1. Screen formats/organisation:
The introductory screen will be the first to be displayed which
will allow the users to choose either of the one option like viewing the
details of the books they are holding and searching the books,
updating the new books on online registration.

3.1.1.2. Windows format/organisation:
When the user chooses some other option then the information
pertaining to that choice will be displayed in a new window, which
ensures multiple windows to be visible on the screen and the users can
switch between them.

3.1.1.3. Data format:
The data entered by the users will be alphanumeric.

3.1.1.4. End message:
When there are some expectations raising error like
entering invalid details, the n error messages will be displayed
prompting the users to re-enter the details. When an event has taken
place successfully like the searching of books, then a message Book
Available will be displayed to the user at the end.



3.1.2. Hardware Interfaces:
The system must basically support certain input and output devices. Their
descriptions are as follows:

Name of
the item
Description of purpose Source of input or
destination of output
Bar Code
Reader
To check the validity of the library card Source of input
Printer To print the list of selected books and
reports regarding the books taken
Destination of output

3.1.3: Software Interfaces:
The operating system used in Windows XP and the database used in
MS-Access.

3.1.4. Communication Interfaces:
Every client system connected via LAN establishes a communication
only with the server and not with any other client system. 10 to 20 systems
are connected using LAN of 10 Mbps is used.




















3.2. SOFTWARE PRODUCT FEATURES:

3.2.1. FEATURE 1: ISSUING IDS TO MEMBERS:
This is the feature provided to all the members of library.

3.2.1.1. Purpose:
Each login of the user will have the entire database of books. Only the
librarian has special privilege to modify the database. This is a feature in
order to access the individuals details regarding his current book status.

3.2.1.2. Stimulus/Response:
By providing IDs to the users the details like the date of returning
already taken books, the fine money etc can be identified for the particular
user.

3.2.1.3. Associated Functional Requirements:
Once the user clicks the respective feature in the stain, he should be
taken to the appropriate section enabling them to view the college details.

3.2.1.3.1.1. Introduction:
The user must be provided with the requested information
within 10seconds.

3.2.1.3.1.2. Inputs:
The user will choose appropriate options out of the options
available, namely viewing college details and applying for
admissions.

3.2.1.3.1.3. Processing:
Recognizing the correct option chosen by the browser.

3.2.1.3.1.4. Outputs:
The pages corresponding to the chosen features will be
displayed.




3.2.2. FEATURE 2: CREATING MEMBERSHIP NUMBER:
At the starting of the year a membership number will be issued to
each and every student or staff of this software.

3.2.2.1. Purpose:
The purpose of issuing a membership number is to increase security
and to make sure that access is given only to the staff or the students.

3.2.2.2. Stimulus/Response:
Once the request is made a window will appear asking for all personal
details of the staff/student so as to issue a membership number.

3.2.2.3. Associated Functional Requirements:
3.2.2.3.1. Functional Requirements- Creating membership number:
It must check that the user enters valid personal details and
display error messages to avoid abnormal interrupt.

3.2.2.3.1.1. Introduction
The membership number will be issued based on precise input
details entered by user.

3.2.2.3.1.2. Inputs
The user must enter input details like name of the staff or
student, roll number, department etc.

3.2.2.3.1.3. Processing
It will be checked whether the entered input is valid or not and
will create a membership for the staff/student.

3.2.2.3.1.4. Outputs:
The issued number should be displayed to the user.







3.2.3. FEATURE 3: UPDATING OF BOOKS IN THE LIBRARY:

The ability of the software to provide easy entering of the books in the
library.

3.2.3.1. Purpose:
The purpose of this software is to enable the library staff members to
enter the book in an easy manner.

3.2.3.2. Stimulus/Response:
Once the user chooses the particular option, the web pages
corresponding to that are to be displayed on the screen.

3.2.3.3. Associated Functional Requirements
3.2.3.3.1.Functional Requirements- Updating of books in the library:
Once the user clicks the respective feature they should be taken
to the appropriate section enabling them to enter the code, author
name, title of the book and the publisher of the corresponding book.

3.2.3.3.1.1. Introduction:
The user must be provided with the requested information
within 12seconds.

3.2.3.3.1.2. Inputs:
The user should give the code, title of the book, author name
and the publisher of the book.

3.2.3.3.1.3. Processing:
Recognising the correct option chosen by the user in the
browser.

3.2.3.3.1.4. Outputs:
The outputs will be displaying to the user the pages
corresponding to the chosen feature.





3.2.4. FEATURE 4: TRANSACTION OF BOOKS:

3.2.4.1. Purpose:
The purpose is to enable the user to lend a book when certain
conditions are satisfied like amount of fine for the last book has been paid or
not, valid membership has been entered etc.

3.2.4.2. Stimulus/Response:
When the user requests for lending the book, screen prompting the
user to enter details about the membership number etc.

3.2.4.3. Associated Functional Requirements:
3.2.4.3.1.Functional Requirements-Lending of books:
If invalid membership number of registration number has been
entered, it must handle this error and ask the user to enter the proper input.

3.2.4.3.1.1. Introduction:
The user must be provided with the requested information namely the
ID and the number of books needed.

3.2.4.1.2. Inputs:
The inputs given are the number of books and the ID of the student.

3.2.4.3.1.3. Processing:
Recognising of the correct option chosen by the user in the browser, it
reduces the number of copy in the file.

3.2.4.3.1.4. Outputs:
Display a message confirming which books the user has taken.









3.2.5. FEATURE 5: RESERVING OF BOOKS:
The software must allow the user to reserve for a particular book.

3.2.5.1. Purpose:
The purpose is to allow the applicants to reserve the books, when
certain conditions are satisfied.

3.2.5.2. Stimulus/Response:
Once the user requests for the particular books, it must be displayed
on the screen prompting the user to fill the details about his roll number,
card number etc.

3.2.5.3. Associated Functional Requirements
3.2.5.3.1.Functional Requirements- Reserving of books:
If any one of the details provided by the user does not meet the
defined parameters then it would notify the person by displaying error
message.

3.2.5.3.1.1. Introduction:
If the register number entered is valid, then it will ask details
about the book which the user has requested to reserve.

3.2.5.3.1.2. Inputs:
The user must enter input details like membership number, title
and the author name of the book to reserved.

3.2.5.3.1.3. Processing:
Processing will be done to check whether the entered detail is
valid or not and whether the requested book is available for
reservation.

3.2.5.3.1.4. Outputs:
A message must be displayed confirming which book has been
reserved for the user.






3.2.6. FEATURE 6:CALCULATION OF FINE AMOUNT WHILE
RETURNING THE BOOK:
If the user wants to reserve or renew a book then the software must
first check if any pending book has to be returned and whether the fine has
been paid.

3.2.6.1. Purpose:
The purpose of this is to enable the students or staff to view the
amount of fine to be paid and last date to return a book.

3.2.6.2. Stimulus/Response:
The user will be asked to enter membership number and the software
will check if any fine has to be paid.

3.2.6.3. Associated Functional Requirements
3.2.6.3.1.Functional Requirements- Calculation of fine:
Proper error messages must be displayed if invalid input is
entered.

3.2.6.3.1.1. Introduction:
The user can check the last date of return or whether the fine
has been paid depending on returning process can be carried out.

3.2.6.3.1.2. Inputs:
The user must enter input details like membership number, title
and author of the book to be reserved.

3.2.6.3.1.3. Processing:
The software will check whether a particular member has
reserved a book or not.

3.2.6.3.1.4. Outputs:
It will display the last date for returning the book and the
amount of fine due.





3.2.7. FEATURE 7: SEARCHING FOR A BOOK:
The software must be able to search and give details for a specified
book on users request.

3.2.7.1. Purpose:
The purpose of this is to enable the users to search for a required book
even if the user is not able to provide information about the book.

3.2.7.2. Stimulus/Response:
Once the user chooses this option , he is asked to enter the title and
name of the author of the book to be searched.

3.2.7.3. Associated Functional Requirements
3.2.7.3.1.Functional Requirements- Searching by Authors name:
It must also be able to handle invalid inputs and search for the
exact book.

3.2.7.3.1.1. Introduction:
The user must be asked to enter the title and author of the
required book upon which the specified book can be searched.

3.2.7.3.1.2. Inputs:
The user can search for a book by giving the title and author
name of the book.

3.2.7.3.1.3. Processing:
The software must provide details of all books given a
particular title of the book and author name and display information
on all books related to the title of the book and name of the author.

3.2.7.3.1.4. Outputs:
All the books with the given title and author name are
displayed. And also the information about where it can be found is
displayed.




3.3. PERFORMANCE REQUIREMENTS :
At ay instant, a maximum of four nodes or users will be given access
simultaneously.
Since the program handles multiple users, if more than one person
attempts to save data to the file stored in database, the program will
lock the data file using a two phase commit protocol to prevent
simultaneous access.

3.4. DESIGN CONSTRAINS:
Requires 256 MB on-board memory.
Based completely on windows functionality platform.
The Software should be portable and must be inaccessible to
unauthorized users.

3.5. SOFTWARE SYSTEM ATTRIBUTES:

3.5.1. Reliability:
The factors needed to establish the softwares expected reliability are :
The user inputs should be valid and within the given range.
Normal termination of the program.

3.5.2. Availability:
The factors that guarantee the softwares availability include proper
termination and correct input details. Also the resources used for the
project development is Microsoft Certified, which speaks of its high
quality standards.

3.5.3. Security:
It must be ensured that access will be provided to the authorized
persons via users ID.
Network security will be provided by the use of firewalls.
Checks can be performed at regular intervals to ensure data
integrity.





3.5.4. Maintainability:
Implementing the concept of modularity, which in turn reduced the
complexity involved in maintaining it, will develop the software. The
administrator should have a sound technical knowledge about
maintaining the software.

3.5.5. Portability:
The application is very adaptable, it can be used in different computer
systems with different operating systems and folders.

3.6. LOGICAL DATABASE REQUIREMENTS :
The system requires the use of text file to maintain the student and
staff details about which book has been reserved and the amount of fine.

4. INDEX:
NIL


5. APPENDICES:
NIL