Project Title: Design and Document a

Simple Library Management System

 Objective:
Design and document a console-based library
management system using Java, incorporating
object-oriented programming (OOP) principles, and
basic database or file operations. The system
should manage users and books, support
borrowing/returning books, and provide basic
search and profile management functionalities. This
document will guide the design, development, and
documentation stages, ensuring all functionalities
are implemented systematically.

 Features:

1. Add/Remove books
2. Search books by title/author
3. Display all books
4. Borrow/Return books
5. Display borrowed books
  Technical Requirements:

1. Java 8 or later
2. Eclipse or IntelliJ IDEA
3. Java Collections Framework (e.g.,
ArrayList, HashMap)
4. File handling (e.g., FileReader,
FileWriter)

 Deliverables:

 System Design Document (SDD)

This document will serve as a complete guide
to the design and functionalities of the library
management system. It will cover system
specifications, requirements, and all diagrams
essential for understanding the overall system
design.
 Class Diagram
A detailed UML class diagram that will
represent the core classes, attributes,
relationships, and methods in the system,
helping to outline the relationships between
entities and structure the application.

 Use Case Diagram

This diagram will illustrate the various actors
(such as Admin and User) and their
interactions with the system's main functions.
 Sequence Diagram
This will show the step-by-step interactions
between objects for key operations, such as
user registration, book borrowing, and profile
management, helping visualize the flow of
information within the system.
 Data Flow Diagram (DFD)
This diagram will map the flow of data
between system modules and processes,
offering a high-level view of how information
is processed within the system.
 Entity-Relationship Diagram (ERD)
The ERD will present the database schema,
showing relationships between tables/entities
like User, Book, Borrow Transaction, etc.
 User Manual
This guide will offer instructions for end-users,
covering topics like system login, user
registration, book searching, and borrowing
and returning books, ensuring users can
navigate the application smoothly.
  System Requirements:
 User Registration and Login
 Users can register with personal details.
 A login system verifies user credentials.
 Differentiation between user roles (e.g., Admin
vs. Regular User) and associated permissions.
 Book Registration and Management
 Books can be added, updated, and removed by
authorized personnel (e.g., Admin).
 Each book entry will have attributes like title,
author, ISBN, publication year, etc.
 Book Search Functionality
 Users can search for books by title, author,
genre, or ISBN.
 Search results should be displayed with
essential book details.
 Borrow/Return Books
 Users can borrow available books, with borrow
transactions tracked by the system.
 Books can be returned, updating the system’s
inventory and user borrowing history.
 Display Borrowed Books
 Users can view a list of books they have
borrowed, including due dates and overdue
statuses.


 User Profile Management

 Users can update personal information,
including contact details and preferences.
 Admins have additional privileges to manage
user profiles, track user activities, and ensure
compliance.

 Design Considerations:
 Object-Oriented Programming (OOP)
Principles
 Encapsulation: Each class will encapsulate its
own data and methods, restricting access
where appropriate.
  Inheritance: Common behaviors will be
grouped into base classes, allowing specialized
child classes for users and book items.
 Polymorphism: Methods with similar
functionality will be dynamically handled,
supporting multiple object types.

 Java Collections Framework

 Leverage Java’s collections for efficient data
storage and retrieval.
 Utilize Lists, Sets, and Maps to store and
manage book inventory, user lists, and borrow
transactions.
 File Handling or Database Integration
 Consider using either file handling or a
lightweight database (e.g., SQLite) for
persistence.

 Database tables will be defined for entities such

as Users, Books, and BorrowTransactions.
 User Interface (Console-Based)
  A user-friendly, menu-driven console interface,
with clear prompts and navigation options.
 Input validation, error messages, and success
notifications to enhance the user experience.

 Tools:
 Diagramming Tools
 Use Lucidchart (or any preferred UML tool) for
creating UML diagrams.
 Documentation Tools
 Microsoft Word or Google Docs for
documentation, ensuring clarity and
professional formatting.
 UML Notation
 Adhere to standard UML notation for diagrams,
maintaining consistency and accuracy
throughout the documentation.

 Project Structure:
1. Introduction
Briefly describe the purpose and scope of the
library management system, including target
users and expected functionalities.
2. System Overview
Provide an overview of the system architecture,
key features, and how it addresses user needs.
3. System Design
o Class Diagram: Define system classes,

attributes, methods, and relationships.

o Use Case Diagram: Show user interactions

and system functionalities.

o Sequence Diagram: Detail the flow of

operations like user registration and book
borrowing.
o Data Flow Diagram (DFD): Illustrate data
movement and storage across modules.
o Entity-Relationship Diagram (ERD):
Visualize database structure, entity
relationships, and cardinality.
4. System Components
o User Registration: Outline the process for
new user registration and authentication.
o Book Registration: Describe how books
are added, edited, and managed.
o Search Books: Detail search mechanisms,
including filters and keyword matching.
o Borrow/Return Books: Define borrowing,
return workflows, and book availability
tracking.
 o User Profile Management: Describe
profile updates, preferences, and user
activity tracking.
5. User Manual
o Overview: Describe the library system
interface and main features.
o Account Setup: Guide users through
registration and logging in.
o Using Features: Step-by-step guides for
searching, borrowing, and returning books.
o Profile Management: Instructions on
updating user details and viewing borrowing
history.

6. Conclusion
Summarize the functionality and design aspects
of the library management system, highlighting
key design principles and anticipated impact.

 Grading Criteria:

  Completeness and Accuracy

All required components should be fully
implemented, adhering to the specified
functionalities and requirements.
  Documentation Quality
Documentation should be well-organized,
 clear, and professional. Diagrams should be
detailed, consistent, and easy to understand.
  OOP Principles
The system design must demonstrate
appropriate use of encapsulation, inheritance,
and polymorphism.
  Feature Breadth and Depth
The system should offer all specified
functionalities, with efficient data handling,
error management, and user interface.
  Diagram Quality
Diagrams should be professionally created,
providing valuable insights into system
structure and workflows.

 Tips and Resources:

  Java Documentation and Tutorials
Refer to Java’s official documentation for
syntax, Java Collections Framework, and file
handling.
  UML Diagrams
Use online tutorials to understand UML
conventions, ensuring diagrams meet
professional standards.
  Research Library Management
Systems
Study existing systems to gain insights into
 standard features, design considerations, and
best practices.
  Feedback and Collaboration
Seek feedback from peers or mentors,
especially on design choices and coding
practices, to improve system quality and
adherence to standards.

 Program :
Project Structure:

1. Book.java (class representing a book)

2. Library.java (class managing the library)
3. Main.java (main class for execution)
4. data.txt (file storing book data)

Implementation:
Book.java

public class Book {

private String title;
private String author;
 private boolean isBorrowed;

// Getters and setters

}

Library.java

import java.util.ArrayList;
import java.util.HashMap;
import (link unavailable)*;

public class Library {

private ArrayList<Book> books;
private HashMap<String, Book> bookMap;

public Library() {
books = new ArrayList<>();
bookMap = new HashMap<>();
}

// Add book
public void addBook(Book book) {
 books.add(book);
bookMap.put(book.getTitle(), book);
}

// Remove book
public void removeBook(String title) {
Book book = bookMap.get(title);
if (book != null) {
books.remove(book);
bookMap.remove(title);
}
}

// Search book
public Book searchBook(String title) {
return bookMap.get(title);
}

// Display all books

public void displayBooks() {
for (Book book : books) {
System.out.println(book.getTitle() + " by
" + book.getAuthor());
 }
}

// Borrow/Return book
public void borrowBook(String title) {
Book book = bookMap.get(title);
if (book != null) {
book.setBorrowed(true);
}
}

public void returnBook(String title) {

Book book = bookMap.get(title);
if (book != null) {
book.setBorrowed(false);
}
}

// Display borrowed books

public void displayBorrowedBooks() {
for (Book book : books) {
if (book.isBorrowed()) {
 System.out.println(book.getTitle() + "
by " + book.getAuthor());
}
}
}
}

Main.java

import java.util.Scanner;

public class Main {

public static void main(String[] args) {
Library library = new Library();
Scanner scanner = new
Scanner(System.in);

while (true) {
System.out.println("1. Add book");
System.out.println("2. Remove book");
System.out.println("3. Search book");
System.out.println("4. Display all
books");
 System.out.println("5. Borrow book");
System.out.println("6. Return book");
System.out.println("7. Display borrowed
books");
System.out.println("8. Exit");

int choice = scanner.nextInt();

switch (choice) {
case 1:
// Add book logic
break;
case 2:
// Remove book logic
break;
// ...
}
}
}
}

Output :
Initial Output
1. Add book
2. Remove book
3. Search book
4. Display all books
5. Borrow book
6. Return book
7. Display borrowed books
8. Exit
Add Book
Enter choice: 1
Enter book title: Java Programming
Enter book author: John Smith
Book added successfully!
Display All Books
Enter choice: 4
List of books:
Java Programming by John Smith
Add Another Book
Enter choice: 1
Enter book title: Data Structures
Enter book author: Jane Doe
Book added successfully!
Display All Books
Enter choice: 4
List of books:
Java Programming by John Smith
Data Structures by Jane Doe
Search Book

Enter choice: 3
Enter book title: Java Programming
Book found:
Java Programming by John Smith
Borrow Book
Enter choice: 5
Enter book title: Java Programming
Book borrowed successfully!
Display Borrowed Books
Enter choice: 7
List of borrowed books:
 Java Programming by John Smith
Return Book
Enter choice: 6
Enter book title: Java Programming
Book returned successfully!
Exit

Enter choice: 8
Exiting program...

Conclusion :
- Summarize the functionality and design
aspects of the library management system,
highlighting key design principles and anticipated
impact.

Reference :
Meta Ai, ChatGPT, Google.