LMS
LMS
A
Project Report On
Library Management System “Project Title”
Developed by,
ll/ Seat No: 8774 Student: Name Shubham Patil Roll/ Seat No:8735 Student: Name Atharv N
TYBSC CS(SCIENCE)
Under
Savitribai Phule Pune University (2023-2024)
Kamala Education Society’s
Pratibha College of Commerce & Computer Studies, Chinchwad, Pune-19
Certificate
This is to certify that & have satisfactorily completed the Project
titled “Project Title” for T.Y .BCA(Science) under the Savitribai Phule Pune Uni
ACKNOWLEDGEMENT
We would like to take this opportunity to thanks all the people who
have directly or indirectly helped in completing this project. We would
like to thank our guide Mrs. Guide Name, for her valuable guidance.
Shubham Patil
Atharv Nigde
Index
Table of Contents
Particulars Page
No.
Abstract (Short Summary of project)
Introduction
Motivation
problem statement
purpose/objective and goals
literature survey
project scope and limitations
System analysis
Existing systems
scope and limitations of existing systems
project perspective, features
stakeholders
Requirement analysis- Functional
requirements,
Performance requirements, security
requirements etc.
System Design
Design constraints
System Model: Using OOSE
Data Model
User interfaces
Implementation details
Software/hardware specifications
Outputs and Reports Testing
Test Plan, Black Box Testing or
Data Validation Test Cases,
White Box Testing or Functional Validation
Test cases and
Results
Conclusion and Recommendations
Future Scope
Bibliography and References
Introduction
The admin side manages all the management like adding and
managing categories, authors, books, issued books, and so on. The admin has an im
Objective
Many libraries still use manual processes for tasks like cataloging,
lending, and tracking overdue books. This can be time-consuming, error-prone, an
Paper is wasted.
The need for a system project stepout from the fact that libraries have
to manage a vast amount of information, and manual systems are inefficient and err
Overall LMS has become an essential tool for any modern library.It helps to do the
Scope of Proposed System
Modules
Student can register yourself and after registration they will get
studentid. After login student can view own dashboard. Students can also view the l
Student can update own profile.Student can view issued book and book return date-
Student can also change own password.
Student can also recover own password.
Feasibility Study
UML Diagrams
Use Case Diagram:
ER Diagrams
Class Diagram:-
Sequence Diagram:-
Activity Diagram:-
Deployment Diagram:-
Data Dictionary
Table Design:
Table Users/Student
This table stores information about authors of the books in the library.
Sr.no Field name Data type Constraint
1 Id Int Primary key
2 AuthorName Varchar Default Null
3 CreationDate Timestamp Default Null
4 UpdationDate Timestamp Default Null
Table Books
This table stores information about books in the library, including the
book's title, author, publisher, ISBN, and other relevant data.
Sr.no Field name Data type Constraint
1 Id Int Primary key
2 BookName Varchar Default Null
3 CatId int Default Null
4 AuthorId Int Default Null
5 ISBNNumber Varchar Default Null
6 BookPrice Decimal Default Null
7 bookImage Varchar Not Null
8 isIssued Int Default Null
9 RegDate timestamp Default Null
Table Admin
Table Category
Table Issuedbooks
Home Page
Testing Strategy
SYSTEM TESTING
The aim of the system testing process was to determine all
defects in our project .The program was subjected to a set of test
inputs and various observations were made and based on these
observations it will be decided whether the program behaves as
expected or not. Our Project went through two levels of testing
1. Unit testing
2. Integration testing
INTEGRATION TESTING
In this type of testing we test various integration of the project module
by providing the input .The primary objective is to test the module
interfaces in order to ensure that no errors are occurring when one
module invokes the other module.
UNIT TESTING
Unit testing is undertaken when a module has been created and
succesfully reviewed .In order to test a single module we need to
provide a complete environment ie besides the module we would
require
The procedures belonging to other modules that the module under test calls
Non local data structures that module accesses
A procedure to call the functions of the module under test with appropriate paramete
Limitations
There are not many limitations of the project but it includes some
limitations, which are listed below or are as follows:
Limited scope: LMS projects have a limited scope, as it focuses
mainly on the tasks associated with managing library materials. They
may not able to to meet or modify large organizational needs.
Cost: Implementing an LMS can be expensive, particularly for
smaller libraries or those with limited budgets. In addition to the
initial purchase and implementation costs, ongoing maintenance and
support can be costly.
Technical Knowledge: LMS software can be complex, requiring staff
to be trained in its use. This can take time and resources, and staff
turnover can result in the need for ongoing training.
Technical issues: LMS project may experience technical issues, such
as software bugs ,loading errors and crashes. It may face
compatibility issues with other sytem. These issues can cause delays
or disruptions in library services.
Security: LMS projects often involve collecting and storing User
information, such as names, addresses, and borrowing history. Hence
it cab be vulnerable to cyber attacks and data breaches which can
degrade user trust.
Future Enhancement
Conclusion
BiblioGraphy