Scribd
Upload
6 views

Library Management System

The document outlines the development approach for a Library Management System, addressing issues such as manual processes, tracking difficulties, and user experience challenges. It details functional and non-functional requirements, including book and user management, scalability, security, and performance. The system will utilize a CRUD design approach with Java and MySQL as the technology stack, aiming for a user-friendly interface and efficient data handling.

Uploaded by

Enamul Arif
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
6 views

Library Management System

The document outlines the development approach for a Library Management System, addressing issues such as manual processes, tracking difficulties, and user experience challenges. It details functional and non-functional requirements, including book and user management, scalability, security, and performance. The system will utilize a CRUD design approach with Java and MySQL as the technology stack, aiming for a user-friendly interface and efficient data handling.

Uploaded by

Enamul Arif
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

LIBRARY

MANAGEMENT
SYSTEM:
SOFTWARE
DEVELOPMENT
APPROACH

Group 9
Information System Analysis and
Software Engineering Lab
Manual Processes: Time-consuming tasks
PROBLEM like book check-in/check-out and record-
keeping.

STATEMENT Tracking Issues: Difficulty tracking


borrowed books, leading to losses or
disputes.

User Experience: Inconvenience for users


(students/staff) in searching for books or
checking availability.

Overdue Management: Inefficient handling


of overdue books and fines.

Scalability: Existing systems (if any) can’t


handle growing library demands
REQUIREMENT ANALYSIS

Functional Non-
Requirement Functional Constraints
Divided into 3
s (What the Requirement (Limitations &
sections:
system must s (System challenges)
do) qualities)
FUNCTIONAL
REQUIREMENTS
📚 Book Management
• Add new books.
• Update book details.
• Delete books.
• Search for books.
• View all books.
• Display book availability (issued or
available).
FUNCTIONAL REQUIREMENTS

👤 Student (User) Management


Add new students.
Update student details.
Delete students.
Search for students.
View all students.
FUNCTIONAL
REQUIREMENTS
Borrow/Return System
• View available books for issuing.
• Search for available books.
• Issue books to students.
• Return books.
• View issued books.
1. Scalability: Handle large volumes of
NON- books and users efficiently.

FUNCTIONAL 2. UI/UX Design: Simple, user-friendly, and


responsive.
REQUIREMEN
3. Security: Encrypted storage, role-based
TS access.

4. Performance: Fast query responses and


optimized operations.

5. Data Backup & Recovery: Prevent data


loss with regular backups.

6. Platform Compatibility: Accessible via


desktop, mobile, and web.
Time Constraint – Project must be completed by

CONSTRAINTS
end of the semester. Also, can’t invest too much time
on the project.

Team Experience – First time developing software,


with varying programming skills among team
members.

Team Collaboration – First time working as a team;


potential coordination and communication
challenges.

Technology Constraint – Must be


desktop/Android-based development instead of
web-based.

Learning Curve – Need to quickly learn UML,


database design, and software architecture
while developing.

Scope Management – Balancing project scope to


ensure functional completion within time limits
To make the make the
CRUD APPROACH TO DESIGN database design less
complex we use CRUD
method.
CRUD APPROACH TO DESIGN

1. Books (Managed by 2. Users (Managed by System


Librarian, Student) and Librarian, Student)
Create: Adding a new book to the system. Create: Registering a new user.
Read: Searching for a book, viewing book Read: Viewing user profile, checking
details. borrowed books.
Update: Editing book information (title, Update: Modifying user details.
author, availability). Delete: Deactivating or removing a user
Delete: Removing a book from the system. account.
CRUD APPROACH TO DESIGN

3. Transactions 4. Notifications (Handled


(Reservations, Borrowing, by Database)
Fines)
Create: Reserving or borrowing a Create: Generating overdue or
book. reservation notifications.
Read: Checking due dates, reservation Read: Retrieving past notifications.
status, and fines. Update: Modifying notification
Update: Renewing a book, updating settings.
fine status. Delete: Removing expired
Delete: Canceling a reservation. notifications.
USE CASE
DIAGRAM:
LIBRARY
MANAGEMENT
SYSTEM (INITIAL)
ACTIVITY
DIAGRAM
(INITIAL)
CLASS
DIAGRAM
(INITIAL)
DEPLOYMENT
DIAGRAM
TECHNOLOGY STACK

Java and MySQL


Why Java?
• Object-oriented, secure, and platform-independent.
• Rich libraries for GUI (JavaFX, Swing) and backend (JDBC, Hibernate).
• Strong community support and scalability.
• We’ve more experience in this language than the alternatives
TECHNOLOGY STACK

Why MySQL?
• Reliable, efficient, and widely used relational database.
• Works well with Java using JDBC (Java Database Connectivity).
How Java & MySQL Work Together?
• Java application (frontend/backend) interacts with MySQL using JDBC.
• Queries are executed to fetch, insert, update, and delete data.
• Data is stored in MySQL tables for books, students, and transactions.
TECHNOLOGY STACK

System Architecture Overview


Java Application (GUI or Backend) → Connects to → MySQL Database
• Librarian/Student interacts via Java UI → Queries run on MySQL

Thank You!

You might also like