INDEX

SR NO. TITLE

1.0 Title of Micro-Project

2.0 Rationale
3.0 Literature Review
4.0 Methodology
5.0 Resources Used
6.0 Actual Procedure Followed
7.0 Output
8.0 Applications
  Title of Micro-Project
Library management system

 Rationale
An integrated library management system (LMS) is ERP software that helps in simplifying the daily operations of the library. The purpose of a
library management system is to manage & track the daily work of the library such as issuing books, return books, due calculations, etc.
Conventional libraries are having difficulty integrating various formats, including multimedia and e-resources, because of outdated management
systems. Inefficient cataloguing, resource tracking bottlenecks, and a lack of analytics tools hinder librarians from optimizing collections and
improving user experiences. To close the gap, libraries require a modern library management system with an intuitive interface, effective
cataloguing, and analytics capabilities to resurrect libraries as vibrant centres of knowledge and community involvement in the digital era.

 Literature Review
A Library Management System (LMS) is a software web based application that simplifies and automates the operations of libraries. It is a
complete system for managing library duties such as issue ,return , login,member management, monitoring, storing, and circulation. The
primary objective of an LMS is to properly organize and manage the resources available in a library, making it easier for librarians to conduct
everyday operations and create a user-friendly experience for users.Conventional libraries are having difficulty integrating various formats,
including multimedia and e-resources, because of outdated management systems. Inefficient cataloguing, resource tracking bottlenecks, and a
lack of analytics tools hinder librarians from optimizing collections and improving user experiences. To close the gap, libraries require a
modern library management system with an intuitive interface, effective cataloguing, and analytics capabilities to resurrect libraries as vibrant
centres of knowledge and community involvement in the digital era. we will be providing User-friendly interface for easy navigation ,
Efficient book search functionality , seamless book issuance and return policy , automated tracking of library activities, Regular maintenance
of book availability records and Secure login and access control managed by the admin.
  Resources used
Operating System: Windows 7, 8, 9, 10
Processor: Intel core i3 or above
Hard Disk: 40GB and above
Software : jira 1
RAM: 256 MB or more, recommended 2 GB.

 Applications

 Proper Book Management

 Efficient data management:
 Time and effort saver:
The automated library system software eliminates the need for manual entries. This saves the effort and time consumed in data entry. Automation
makes the database error free and accurate.
 Automated reports:
The system reports the performance of the library automatically. Charts and graphs are provided for review and tracking of the library functions.
This aids in making changes and improvements to the library.
 Cost effective:
Digital libraries eliminate the need for extensive paperwork and too many staff. Maintenance overheads and operation costs are reduced.
 Simplification of librarian duties:
 The system allows the librarian to maintain a wide collection of books, periodicals, journals, audio and video books and pictorials. The
librarian operations of addition and deletion of books, tracking books, tracing missing books, reserving books can be performed very
easily
  Methodologies
The LMS store all information about librarian and other users (students and faculty members) like their login info , books issued , book
returned, etc.
 The LMS store all information about the books and users in two separated databases.
 The LMS s allow searching books / journals by author, title , keywords or availability.

 The LMS provides the module to Issue or return the books.

The Admin must be able to add/remove/manage books or users.

A) ER Model of Library Management System Project:

An Entity-Relationship Diagram (ERD) for a Library Management System (LMS) models the entities and their relationships within the system.
Below is a simplified ERD for a Library Management System.
he 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 INR), 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.
ER Model of Library Management System Project
Entities:

 Book: Attributes: ISBN (Primary Key), Title, Author, Genre, Published Year, Copies Available, etc.

 Readers: Attributes: User ID (Primary Key), Name, Email, Address, Phone Number, etc.

 Staff: Attributes: Staff ID (Primary Key), Name, etc.

 Authentication System: Attributes: Login ID (Primary Key) and Password

 Publisher: Attributes: Publisher ID (Primary Key) , Year of Publication, Name, etc.

 Reports: Attributes: Reg No(Primary Key), User ID, Book No, Issue/Return

Relationships:

1. Borrow (Association between Readers and Book):

 A Reader can borrow multiple books.

 A Book can be borrowed by multiple Readers.

 Attributes: Borrow Date, Return Date

2. Manage (Association between Staff and Book):

 A Staff member manages the catalogue, which includes adding, updating, or removing books.

 A Book is managed by a Staff member.

 Attributes: Management Date, Operation Type (Add/Update/Remove)

3. Issue (Association between Staff and Readers):

 A Staff member issues library cards to Readers.

 A Reader can have only one Staff member issuing their card.

 Attributes: Issue Date, Expiry Date

 4. Authenticate (Association between Authentication System and Staff/Readers):

 The Authentication System authenticates Staff and Readers during the login process.

 Attributes: Last Login Date, Login Attempts

5. Publisher (Association between Book and Publisher):

 A Book is published by a Publisher.

 A Publisher can have multiple books.

 Attributes: Publication Date

6. Manages (Association Between Staff and Report):

 A Report is generated for transactions involving Readers and Books.

 Attributes: Generation Date, Report Type (Issue/Return)

Case Diagram of Library Management System

Login page
Functionalities of this page:
 You Can show some important details on the landing page.

 Existing Users will be able to login through user login page.

 Admins can also login using admin login form.

 Users will be able to signup using above signup button.

 These will be our main functionalities of login page

 User Dashboard
 Functionalities of this page:
 Page will show the username and email id .
 User can view Issued books and its count.
 User can view and edit its profile as well.
 Users can change his password also.
 These will be one button for logging out from this page.
Creation of Admin Dashboard
 Managerial features:
 Admin can add or manage existing books.
 Admin can add or manage categories of books.
 Admin can add or manage the authors.
 One Important feature is Admin can Issue Book to any user.

Add/Manage Book Category

 Features:
 Admin can add a new book category using its details.
 Admin can edit the existing book category.
 All changes will be reflected on our SQL database.
  Similarly we can add and manage the author details as well.
Issue Book Module

Features:

 Admin can use this feature to Issue any book from library to the user.

 Database will store the student id and book details for security.
  Actual Procedure Followed

Library Management System consists of last of records bout the management of the details of the students and the issues going on and also about
some books and
all. This is a web-based application. The project has three modules namely- User.
Registration. Librarian. According to the Modules the Distributor and Sub
Distributors can manage and do their acti ties in easy manner.
As the modern organizations are automated and computes are working as per
the instructions. it becomes essential for the coordination of human beings.
‘Commodity and computers in a modern organization. This information helps the distributors to purchase or sale the products very efficiently
The administrators and all the others can communicate With the system through this project. thus faciliating effective implementation and
monitoring of various activities of the distributor of a supermarket.

TESTING:
The testing phase is an important part of software development. It is the computerized system will help in automate process of finding emors and
missing Operations and also & complete verification to determine whether the objectives are met and the user requirements are satisfied
Testing is the process of executing a program with the aim of finding errors To make ou sofware perform well it should be error-free. IF testing is done
successfully it will emove all the errors from the software.

System Testing
The various types of testing on the system are:
 Unit testing
 Integrated testing
  Validation testing
 Output testing
 User acceptance testing
Unit testing
Unit testing focuses on verification effort on the smallest unit of software design module. Using the unit test plans. Prepared in the design
phase of the system as a guide, important control paths are tested to uncover errors within the boundary of the modules. The interfaces of each
of the modules under consideration are also tested. Boundary conditions were checked. All independent paths were exercised to ensure that all
statements in the module are executed at least once and all error-handling paths were tested. Each unit was thoroughly tested to check if it
might fall in any possible situation. This testing was carried out during the programming itself. At the end of this testing phase, each unit was
found to be working satisfactorily, as regarded to the expected out from the module.
Integration Testing
Data can be across an interface one module can have an adverse effect on another’s sub function, when combined may not produce the desired
major function; global data structures can present problems. Integration testing is a symmetric technique for constructing tests to uncover
errors associated with the interface. All modules are combined in this testing step. Then the entire program was tested as a whole.
Validation Testing
At the culmination of integration testing, software is completely assembled as a package. Interfacing errors have been uncovered and
corrected and final series of software test-validation testing begins. Validation testing can be defined in many ways, but a simple definition is
that validation succeeds when the software functions in manner that is reasonably expected by the consumer. Software validation is achieved
through a series of black box tests that demonstrate conformity with requirement. After validation test has been conducted, one of two
conditions exists.
 The function or performance characteristics confirm to specification that are accepted.
 A validation from specification is uncovered and a deficiency created.
Deviation or errors discovered at this step in this project is corrected prior to completion of the project with the help of user by negotiating to
establish a method for resolving deficiencies. Thus the proposed system under consideration has been tested by using validation testing and
found to be working satisfactorily.
Output Testing
After performing the validation testing, the next step is output testing of the proposed system, since a system is useful if it does not produce
the required output in the specific format required by them tests the output generator displayed on the system under consideration. Here the
output is considered in two ways: – one is onscreen and the other is printed format. The output format on the screen is found to be correct as
the format was designed in the system design phase according to the user needs. As far as hardcopies are considered it goes in terms with the
user requirement. Hence output testing does not result any correction in the system.
User Acceptance Testing
User acceptance of the system is a key factor for success of any system. The system under consideration is tested for user acceptance by
constantly keeping in touch with prospective system and user at the time of developing and making changes whenever required.

Prepared Test cases for the following :

1. New User Registration:

 This feature allows new users (students, teachers, etc.) to sign up for the system by providing the necessary details.

2. Student Login:

 This feature Provides authenticated access for registered users to use the system.

3. Search Book:

 This feature allow users to search for books based on criteria such as book ID, book name, or author name, enhancing the ease of locating
desired materials.

4. Issue Book:

 This feature allow users in borrowing books from the library by recording the transaction and updating the availability status.
 5. Return Book:

 This feature allows users to return books either before the due date or after the specified time with a late fine, ensuring proper
management of borrowed materials.

For Admin:

1. Record Library Activities:

 This feature allows librarians to enter various records into the system, such as book issuances, returns, and non-availability of books.

2. Manage Books:

 This feature allow librarians to keep track of the library's books by adding new books or removing them.

3. Manage Student:

 This feature allow librarians to keep track of number of students and their details.

4. View Issued Books:

 This feature allows librarians to view all Issued books with their status.

5. Defaulter List:

 This feature allows librarians to show the details of the student who did not return the books before the deadline.

6. Issue Book:

 This feature allow users in borrowing books from the library by recording the transaction and updating the availability status.

7. Authentication and Authorization:

 The system implements a secure login mechanism for users, and administrators. The admin has the authority to manage user access and ensure
data integrity.
 Output

 Adding Registration form:

Seri Condition Expect

Test
al To be ed Remarks
Data
No. Tested Output

Kindly
If we are
Select select SUCCESSF
1 not selected
Course the UL
any field.
fields.

Please
If we are
enter SUCCESSF
2 not entered Name
the UL
the name.
name.
 Please
If we are
enter
not entered SUCCESSF
3 Roll no the
the valid UL
valid
roll no.
roll no.

Please
If we are enter
Enter
not entered the SUCCESSF
4 Passwo
the valid valid UL
rd
password. passwor
d.

Please
If the enter
Confir
password is the
m SUCCESSF
5 not same as valid
passwo UL
previous passwor
rd
password. d once
again.

6 If we are Email Kindly SUCCESSF

not entered id insert UL
the valid the
 emailid. emailid.

Please
If we are
enter
not suppose Contact SUCCESSF
7 the
to enter no. UL
contact
contact no.
no.

If we are
not suppose
to add any Kindly
Choose SUCCESSF
8 image files upload
file UL
on the Image.
choose
File.
 Adding Login page

Seria Test Expected

Condition To be Tested Remarks
l No. Data Output
 LOGIN
If we are not enter the valid roll no Please fill out
1. ID or SUCCESSFUL
or LOGIN ID. this field.
Roll no

If we only put the valid roll no or

Your Please fill out
2. LOGIN ID and after pressing the SUCCESSFUL
password this field.
login button.

If we are putting the correct user

Select
name and wrong password and Kindly select
3. the user SUCCESSFUL
after selecting the valid login the status
type
credential.

 Admin/book:

Serial
Condition To be Tested Test Data Expected Output Remarks
No.

1. If you are not selected category. Book category Please fill out this field. SUCCESSFUL

2. If we are not enter the book name. Book name Please enter book name. SUCCESSFUL
3 If we are not enter the book cost fields. Book cost Please enter book cost. SUCCESSFUL

4 If we are not enter book author fields. Book author Please enter book author. SUCCESSFUL

5 If we not selected any status. Book status Kindly select status. SUCCESSFUL

If we are not suppose to add any image files on the choose

6 Book Image Kindly upload Image. SUCCESSFUL
File.

Book Book description should not be

7 If we are not enter book description. SUCCESSFUL
description empty.

 Admin/Librarian:

Serial No. Condition To be Tested Test Data Expected Output Remarks

1 If we are not entered the name. Name Please enter the name. SUCCESSFUL
2 If we are not selected the type. Type Please select the type. SUCCESSFUL

3 If we are not entered the valid login id Login id Enter the valid Login id. SUCCESSFUL

4 If we are not entered the password field. Password Enter the valid password. SUCCESSFUL

5 If we are not entered the same password. Confirm password Enter the valid password once again. SUCCESSFUL

6 If we are not selected any status. Status Kindly select the status SUCCESSFUL

 Admin/Student:

Serial No. Condition To be Tested Test Data Expected Output Remarks

1 If we are not selected any course. Course Please fill out the fields. SUCCESSFUL

2 If we are not entered the student name. Student name Please enter the student name. SUCCESSFUL

3 If we are not entered the valid roll no. Roll no Please enter the valid roll no. SUCCESSFUL

4 If we are not entered the valid password. Password Please enter the valid password. SUCCESSFUL

5 If the password is not same as previous password. Confirm password Please enter the valid password once again. SUCCESSFUL
 6 If we are not entered the valid emailid. Email id Kindly insert the emailid. SUCCESSFUL

7 If we are not suppose to enter contact no. Contact no. Please enter the contact no. SUCCESSFUL

8 If we are not selected status Status kindly select status. SUCCESSFUL

9 If we are not suppose to choose the image file. Student image Kindly upload the image. SUCCESSFUL

BOOK ENTRY FORM:

SL.N Test Case Excepted Result Test

o Result

1 On the click of ADD At first user have to fill all fields with proper data , if any Error like entering text data instead of successful
button number or entering number instead of text..is found then it gives proper message otherwise Adds
Record To the Database

2. On the Click of This deletes the details of book by using Accession no. Successful
DELETE Button

3. On the Click of Modified records are Updated in database by clicking UPDATE button. Successful
UPDATE Button

4. On the Click of Displays the Details of book for entered Accession no. Otherwise gives proper Error message. Successful
SEARCH Button

5. On the Click of Clears all fields Successful

CLEAR Button

6. On the Click of EXIT Exit the current book details form successful
 button

7. On the Click of NEXT Display the next form successful

button

USER ACCOUNT FORM:

SL.N Test Case Excepted Result Test

o Result

1 On the click of ADD At first user have to fill all fields with proper data , if any Error like entering text data instead of number or entering successful
button number instead of text..is found then it gives proper message otherwise Adds Record To the Database

2. On the Click of DELETE This deletes the details of student by using Register no. Successful
Button

3. On the Click of Modified records are Updated in database by clicking UPDATE button. Successful
UPDATE Button

4. On the Click of SEARCH Displays the Details of book for entered Register no. Otherwise gives proper Error message. Successful
Button

5. On the Click of CLEAR Clears all fields Successful

Button

6. On the Click of EXIT Exit the current book details form successfu
button l

7. On the Click of NEXT Display the next form successfu

 button l

BOOK ISSUE FORM:

SL.N Test Case Excepted Result Test

o Result

1 On the click of ADD button At first user have to fill all fields with proper data ,if the accession number book is already issued then it will successful
giving proper msg.

2. On the Click of DELETE This deletes the details of book by using Register no. Successful
Button

3. On the Click of UPDATE Modified records are Updated in database by clicking UPDATE button. Successful
Button

4. On the Click of SEARCH Displays the Details of issued book..Otherwise gives proper Error message. Successful
Button

5. On the Click of CLEAR Clears all fields Successful

Button

6. On the Click of EXIT button Exit the current book details form successfu
l

7. On the Click of NEXT button Display the next form successfu

l
BOOK RETURN FORM:

Sr.N Test Case Excepted Result Test

o Result

1 On the click of ADD At first user have to fill all fields with proper data , if any Error like entering text data instead of number or entering successful
button number instead of text..is found then it gives proper message otherwise Adds Record To the Database

2. On the Click of DELETE Which deletes the details of book by using Register no. Successful
Button

3. On the Click of Modified records are Updated in database by clicking UPDATE button. Successful
UPDATE Button

4. On the Click of SEARCH Displays the Details of returned book … Otherwise gives proper Error message. Successful
Button

5. On the Click of CLEAR Clears all fields Successful

Button

6. On the Click of EXIT Exit the current book details form successfu
button l

7. On the Click of NEXT Display the next form successfu

button l