LIBRARY Store Management System

Software Design Description

Thursday, January 22, 2021
Prepared by
Salman naveed
(FA17M2BA029)

Supervised By
Dr.Roa Akmal

Department of Computer Science & IT

The Islamia University of Bahawalpur 

Prepared for:
CSIT-01701(f20)-DOCS202-BS-CS-BWP-7TH-1M
Final Year Project
 Revision History
Date Description Author
23th Jan 2021 Ver 1.0 Salman naveed

Document Approval
The following Software Requirements Specification has been accepted and
approved by the following

Signature Printed Name Title Date

Roa Akmal Instructor/teacher

SR Table of Content Remarks
1 Library Store Management System I

2 Revision History II
3 Document Approval II
4 1 Introduction 5
1.2 Purpose 5
1.3 Scope 5
1.4 Overview 5
1.5 References 6
1.6 Definitions, Acronym and Abbreviations 6
5 2.1 Overall Description 7
2.2 Product perspective 8
2.3 Product Functions 8
2.4 User and Characteristics 9
2.5 Principal Actors 9
2.6 General Constraints 9
2.7 Assumption and Dependencies 9
6 3.1 Architectural Design 9
 3.2 Decomposition Description 11
3.2.1 Functional Description 11

3.2.1.1 DFD Diagram 11

3.3 Design Rationale 19

7 4 Data Design 20
4.1 Data Description 20
4.2 Data Dictionary 20
4.3 Data Model 22
4.3.1 ERD 23
4.3.2 Database 23
4.3.3 Tables 23
8 5.1 Component Design 25

5.1.1 Algorithm 25

5.1.2 Pseudocode 28

9 6.1 Requirements Matrix 30

1 Introduction
With the expansion in the quantity of peruses, better administration of libraries framework is
required. The Library management framework centers around improving the executives of
libraries in a city or town. "What If you can check whether a book is accessible in the library
through your telephone?" or "imagine a scenario in which rather than having different library
cards for various libraries you can simply have one?" or "you can hold a book or issue a book
from your telephone sitting at your home!". The Integrated Library Management framework
gives you the simplicity of issuing, renewing, or holding a book from a library inside your town
through your telephone. The Integrated LibraryManagement framework is created on the web
stage which fundamentally centers around giving, restoring andreserving a book.

1.1 Purpose
The purpose of the project is to maintain the details of books and library members of different
libraries. The main purpose of this project is to maintain a easy circulation system between
clients and the libraries, to issue books using single library card, also to search and reserve any
book from different available libraries and to maintain details about the user (fine, address,
phone number)

1.2 Scope
Physically refreshing the library framework into an web based application so the client can know
the details of the books accessible and greatest cutoff on acquiring from their PC and
furthermore through their phones.

The ILM System gives data resembles subtleties of the books, addition of new books, erasure of
lost books, limit on giving books, fine on keeping a book over one month from the gave date

1.3 Overview
The proposed Library Management System will take care of the current book detail at any point
of time. The book issue, book return will update the current book details automatically so that
user will get the update current book details.

1.4 References
SMARTDRAW, 2015. SMARTDRAW.com. [Online] Available at:
http://www.smartdraw.com/data-flow-diagram/ [Accessed 5 September 2015].

UML-DIAGRAM.ORG, 2015. UML-DIAGRAM.ORG. [Online] Available at: http://www.uml-

diagrams.org/examples/point-of-sales-uml-use-case-diagram-example.html [Accessed 5 October
2015].

TECHNOPEDIA, 2010. TECHNOPEDIA.com. [Online] Available at:

https://www.techopedia.com/definition/3243/unified-modeling-language-uml [Accessed 4
October 2015].

1.5 Definition’s, Acronym and Abbreviations

LSMS library store management system

CSS Cascading style sheet

HTML Hypertext markup language

PHP LANGUAGE

2 System overview
2.1 PRODUCT PRESPECTIVE
The proposed Library Management System will take care of the current book detail at any point
of time. The book issue, book return will update the current book details automatically so that
user will get the update current book details.
2.2 SOFTWARE REQUIREMENT
Front end:
a) html and css

b) javascript

Back end:

a) MySQL&php

2.3 HARDWARE REQUIREMENT

• Android version 2.3 ginger bread(minimum, android user’s)
• 2GB ram
• 1.2 GHz processor
• Intel i5
• Windows 7/8/8.1/10
2.2 Product Perspective

The proposed Library Management System will take care of the current book detail at any point of time.
The book issue, book return will update the current book details automatically so that user will get the
update current book details.

2.3 Product Functions

• Product Management
• books Management
• Inventory Management
• Fines Management

• Reports Managements
2.4 User Characteristics
This software gives access to two kinds of users.

2.4.1 USER

 They can log in to their account and see their personal information and modify them.

 They can search for a book by the name or search it in a particular department.

 They can easily order a book.

 After the admin approve it they can see the issue and return date beside the book name.

 An automatic timer will set up on the user’s id. It’ll show how much time left until the
return date.

2.4.2 Admin side

1 see which student is online right now.

2.5 Principal actors

Principal actors are librarian and student.

2.6 General constraints

It is necessary to login first before using any functions of the system

2.7 Assumptions and Dependencies

On a computer run the software by clicking on the software icon. Enter username and password
into login form. Employees and manager will use separate ids
3 System architecture
3.1 architecture design
As the name suggests, this database management system project is related to the storage of
information regarding the library. Library is the place with the huge collection of books. It is
place from where the students and the faculties issue the books for their reference purposes.
But the maintenance of keeping the records of issuing and borrowing is difficult if you use a
normal book as a registry. To make this task easier, the library management system database
will be very useful. The system design of library management system will provide the design
phase for the library management system.  The main aim of the design phase is to provide the
solution for the specified requirements.

Functional decomposition can be defined as the process of dividing the functional relationship
into different parts. This can be resolved later. Modularity must be maintained among the
constituent processes. The context flow diagram generalizes the functions of the entire system.
A data flow diagram will show the flow of data from the source to the destination. The data
flow diagram is the starting step of the design phase and it is a very important to understand
the requirements. The descriptions of the components are as follows:

 Register user: A new user can be registered in this component.

 Book issue: Books can be issued to the user and can be added as a record in the
database.
 Book return: The books will be returned by the user within the final date.
 Search/View Book details: This component allow to search or view the books. If
located in the particular shelf, it can be searched in order to get the exact location of the
book.
 Update: The book details can be updated through this component.
 Payment: Manually the payment must be done if the return date exceeds the final date.

3.2 Decomposition Description

Function component 1:
Registration: New user can register.

Input: user details.

Process definition: Processing information and stored in the database.

Output: User details updated in the database.

Function component 2:

Book issue: Here the books will issue to the user.

Input: Book ID.

Process definition: Searching books.

Output: Search and retrieving book information.

Function component 3:

Book return: Here the books will return.

Input: Book ID.

Process definition: Checking book details.

Output: Book is returned.

Function component 4:

Search/view book details: It is used to search and view the details of the book.

Input: Book ID.

Process definition: Searching books.

Output: Details of the book will be shown.

Function component 5:

Update book details: New book entry can be added.

Input: Book ID.

Process definition: Processing the information.

Output: Update in database

Function component 6:

Payment: Here payment is done.

Input: User ID.

Process definition: Checking user account details.

Output: Book will be issued.

3.2.1.1 DFD Diagrams:

It depicts the flow of information and the transformation applied when a data moves in and out
from a system. The overall system is represented and described using input, processing and
output in the DFD. The inputs can be:

 Book request when a student requests for a book.

 Library card when the student has to show or submit his/her identity as a proof.
The overall processing unit will contain the following output that a system will produce or
generate:

 Book will be the output as the book demanded by the student will be given to them.
 Information of demanded book should be displayed by the library information system
that can be used by the student while selecting the book which makes it easier for the
student.
Level 0 DFD 

Figure of Level 0 DFD 

Level 0 DFD
Level 1 DFD:
At this level, the system has to show or exposed with more details of processing.
The processes that are important to be carried out are:
 Book delivery
 Search by topic
List of authors, List of Titles, List of Topics, the bookshelves from which books can be located are some
information that is required for these processes. Data store is used to represent this type of information.

Fig of Level 1- DFD

Level 2- DFD:

Figure of Level 2 DFD

Class Diagram:
Class diagrams are generally used for conceptual modeling of static view of a software application, and for
modeling translating models into programming code in a detailed manner. At time of developing or
construction software systems, a class diagram is widely used. They are also used for data modeling. It is
used to show classes, relationships among them, interface, association, etc.

Figure of class diagram

Sequence Diagram
The store Admin (i.e., End User) interacts with the LSMS interface. After successful login, admin will be
directed to dashboard. From dashboard, admin can add or remove products, update book or delete book. Admin
can add new categories and remove or delete old categories. Admin can add new book and delete old book.
Admin see records and print reports. Admin can add new users to the system like student

Figure of Sequence Diagram

Activity diagram
The activity diagram used to describe flow of activity through a series of actions. Activity diagram is a
important diagram to describe the system. The activity described as a action or operation of the system.

Figure of Activity Diagram

3.3 Design Rationale:
This chapter will discuss about System Design phase which is one of the SDLC phase. The
GUIdesign, database design will be carried out in this chapter.
4 Data Design
4.1 Data Description

This database consists of Users: User and Admin information is added to database with Unique ID based on
their roles. books: Complete products information is stored in this table. status and availibility is stored in this
table.

4.1.2 Data Objects

 The databases that are included in the library management system are as follows:

 Book details: This database contains the field names like account number, author, title, publication,
edition, number of copies, volume price status etc.
 Student: This database contains the field names like name, register number, date of issue, addresses,
date of return, course, account number and gender.
 Issue: This database contains the field names like register number, date of issue books, date of return
books, account number, name, course, author, volume and edition.
 Return: This database contains the field names like register number, date of issue books, date of
return books, account number, name, course, author, volume and edition.
4.2 Data dictionary:

Data dictionary is mentioned in below page

 Name Used in the Description

System
Authors Table name which contains the
information of the Authors of different
books
AuthorId Each author is given a unique AuthorID
AuthorName Name of the Author
Active  
Campus Name given to table which stores
different campus  details
CampusID Each campus is given a unique number
CampusName Name of the Campus
RequestDetails Table name which stores the
information of requests made by
students
RequestDetailId Unique number given to each request
made
RequestedBy Name of the person who made a request
CopydetailId Details of the copy where each copy has
a unique ID
RequestDate Date on which the request is made
RequestDeadline Date for the deadline of the request
Status Status of the book availableor not
SequenceNo This store the sequence numbers
IssueDetails IssueDetails tables stores the details of
the book s which are issued
IssueDetailsId Primary key in Issue details Table
IssuedTo To whom the book is issued
IssuedDate Date when the issue is done
ExpectedDate When the book will be expected to
returned
ReturnDate When the book will is returned
CopyDetailId Details of the Copy of the book
IssueType What is type os issue
RequestDate Date when the request is made
CampusItemID Number for each Campus
ItemID Id given to each Item
CampusId Id given to each Campus
CategoryId Number given to each category
ParentId Number given to each parent Book
CategoryName Name of the Category to which the
book belongs to
Description Description of the book
Active Status whether active or not
ItemName Name of the Item
Publisher Nameof th epublisher
AccessNumber Number for access
ISBN ISBN number of the book
Description Description of the book
Keywords Any keywords for the book
ItemPrice Price of the book
isReference If it is a reference book thisis true
PreferenceId Number given for preference
Active Satus given
MediaType Type of Media for the Item
AuthorId. Number given to each author
BookId Number given to each book
UserId Number given to each user
LoginName User Login name
FirstName First Name of the user
MiddleName Middle Name of the User
LastName Last Name of the user
CampusID ID given to each campus
Password Password given to the User
Email Email id of the user
Active Satus whether true or false
UsertypeId Type of user each user has an ID
UserTypeName Name of the UserType
ReservationId Each Reservation has a unique ID
ItemId Each Item has a Unique ID
ReservationDate Date when the reservation is made
Priority If staff priority is given first to them
CopyPrice Price of the Copy
PaymentId Each payment is given a unique
payment Id
TotalAmount Total Amount to be paid
AmountPaid Amount paid till now
isPaid Whether paymentis paid
IssueDays For how may days the book is issued
Blockdays For how many days the book is blocked

Table of data dictionary

4.3 Data Model
4.3.1 ERD
An ER Model provides a means of communication.

The Library Management System database keeps track of readers with the following considerations

 The system keeps track of the staff with a single point authentication system comprising login Id and
password.
 Staff maintains the book catalog with its ISBN, Book title, price(in pkr), category(novel, general,
story), edition, author Number and details.
 A publisher has publisher Id, Year when the book was published, and name of the book.
 Readers are registered with their user_id, email, name (first name, last name), Phone no (multiple
entries allowed), communication address. The staff keeps track of readers.
 Readers can return/reserve books that stamps with issue date and return date. If not returned within the
prescribed time period, it may have a due date too.
 Staff also generate reports that has readers id, registration no of report, book no and return/issue info.
 Figure of ERD diagram
4.3.2 Database
All about database design explained in above section in database design.

4.3.3 Database Tables

5.Component Design
Summary of algorithm
The pseudocode and draw a flowchart that depicts the registration process for new members. This process
should cater to multiple registrations at one instance. All the relevant information needs to be supplied, and all
the information being accepted need to be validated as described above.

A pseudocode for the requisition of books that are unavailable in the stock.
A procedure that calculates the amount of fine to be paid by a member in case of delay.
A pseudocode for the book return system that calls the procedure for calculating the fine
A flowchart showing the entire system of book return used by Global Library.

Prepare test data for the algorithms and their results.

Prepare a System Manual comprising of the problem statement, all the flowcharts and pseudocode, some test
data, and their results

Pseudocode
begin
Character cMemberId cFirstName cLastName cAdress
Numeric nPhNo
Display "Enter member ID"
Accept cMemberId
Display "Enter First name"
Accept cFirstName
while
Display "Enter Last name"
Accept cLastname
Display "Enter phone No"
Accept nPhNo
Display "Enter Adress"
Accept cAdress
Begin
If cMemberId cFirstName cLastName cAdress or Numeric nPhNo =0
Display "Fields cannot have a null value" else
End

6.1 Requirement Matrix

The traceability model on library management domain
Fig of Requirement Matrix