Cover Page

Project Title:

E-Library Management System

Submitted By:

Rajalaxmi Mohanty
BSc Computer Science
Loisingha Degree College, Bolangir

Date of Submission:

28.12.2024

Content Table

1. Project Summary

2. Details of Process/Project

3. Data Flow Diagram / Algorithms

4. Input / Output Datasets / Screenshots

5. Text / Code / Program

6. References

1. Project Summary

The E-Library Management System is designed to streamline the processes in managing books and
user interactions within a library. This system allows users to search for books, borrow them, and
keep track of their due dates. Administrators can manage the collection of books, monitor user
activity, and generate detailed reports regarding the library’s transactions.

Project Goals:

• To enhance the efficiency of library operations through automation.

• To provide an intuitive and user-friendly interface for both students and administrators.

• To facilitate seamless tracking of book availability, borrowing, and returns.

• To allow administrators to generate real-time usage reports for informed decision-making.

Technologies Used:

• Programming Language: Java (for business logic)

• GUI Development: JavaFX or Swing (for user interface)

• Database: MySQL (for data storage and management)

• Backend: JDBC (for database connection)

Project Overview:

The project is divided into two main modules:

• User Module: Handles tasks like searching for books, borrowing/returning books, and
viewing history.

• Admin Module: Provides features for managing books, users, and generating reports.

System Architecture:

The system follows a client-server architecture, with the client-side consisting of JavaFX/Swing for
the user interface, and the server-side responsible for managing business logic and connecting to the
MySQL database.

• Client-Side: Facilitates interaction with the system, enabling users to perform tasks such as
book borrowing and searching.

• Server-Side: Manages the business logic like book issue/return, updating user records, and
database connectivity.

Functional Overview:

1. User Features:

o Book Search: Allows users to search books by title, author, genre, etc.

o Borrow and Return: Users can borrow and return books, with due dates.

o Reservation System: If a book is unavailable, users can reserve it for future

o User History: Displays a list of books borrowed by the user.

2. Admin Features:

o Book Management: Admins can add, remove, or modify book records.

o User Management: Admins can view and manage user accounts.

o Transaction Management: Admins track borrowed books, due dates, and overdue
returns.

o Reporting: Admins can generate reports based on book transactions, overdue

System Design:

• Frontend: JavaFX/Swing is used to create the GUI, offering an intuitive user interface for
users and admins.

• Backend: Java handles the core business logic, including user authentication, book
transactions, and generating reports.
 • Database: MySQL stores data such as book records, user information, and transaction logs.

3. Data Flow Diagram / Algorithms

Data Flow Diagram (DFD):

Level 1 (High-Level DFD):

• Users interact with the system to borrow, return, or reserve books.

• Admins manage books, users, and generate reports.

• The system connects to the database to store and retrieve necessary data.

Level 2 (Detailed DFD):

• User Actions: Users perform searches, borrow books, and view transaction history.

• Admin Actions: Admins manage books, monitor user activity, and generate reports.

Key Algorithms:

1. Book Search Algorithm:

o Input: Search query (title, author, genre).

o Process: Match the query with book records in the database.

o Output: List of books that match the query.

2. Borrow Book Algorithm:

o Input: User ID and Book ID.

o Process: Check if the book is available, then log the borrowing transaction.

o Output: Success or failure message.

4. Input / Output Datasets / Screenshots

Input Datasets:

• Book Information: Attributes such as title, author, genre, and availability.

• User Information: Attributes include user name, email, user ID, and password.

• Transaction Records: Borrowed book IDs, transaction dates, due dates.

Output Datasets:

• Transaction Logs: Detailed information on borrowed and returned books, including overdue
fines.

• User Reports: A list of books borrowed by a specific user and their return status.

Screenshots:
 • Login Page: Screenshot of the user login interface.

• Admin Dashboard: Screenshot of the admin control panel.

• Book Reservation: Interface for reserving unavailable books.

5. Text / Code / Program

Sample Code:

1. Database Connection (JDBC):

java

Copy code

public Connection getConnection() {

try {

Class.forName("com.mysql.cj.jdbc.Driver");

return DriverManager.getConnection("jdbc:mysql://localhost:3306/library", "username",

} catch (SQLException | ClassNotFoundException e) {

e.printStackTrace();

return null;

2. Adding a New Book:

java

Copy code

public boolean addBook(Book book) {

String sql = "INSERT INTO books (title, author, genre, status) VALUES (?, ?, ?, ?)";

PreparedStatement stmt = conn.prepareStatement(sql);

stmt.setString(1, book.getTitle());

stmt.setString(2, book.getAuthor());

stmt.setString(3, book.getGenre());

stmt.setString(4, book.getStatus());

int result = stmt.executeUpdate();

return result > 0;

6. References

1. Oracle Java Documentation: Oracle Java Docs

2. MySQL Database Documentation: MySQL Docs

3. JavaFX Tutorials: JavaFX Official Site

4. JDBC Guide: JDBC Documentation