$($DONT INSTRUCT, JUST DO IT$)$

Designing and implementing a simple Library Management System $($LMS$)$ for a small

library. The goal of this assignment is for you to practice designing a system using

Object$-$Oriented Programming $($OOP$)$ principles, create the necessary UML diagrams,

and implement the system in Java.

General Requirements

You should implement inheritance, encapsulation, abstraction or polymorphism to

store the necessary information. There is no need to implement any database.

However, it will be an advantage to those who are able to connect the system to a

database

You are advised to conduct some research and understand the concepts and

implementation of composition as well as the necessary UML diagram such as Class

diagram.

System Requirements

$1.$ Manage Library Books

The system must allow the librarian to:

$$ Add new books: Each book should have attributes such as title, author,

ISBN number, and availability status $($whether the book is currently

available for borrowing or not$).$

$$ Update book information: The librarian should be able to modify the

details of existing books.

$$ Delete a book: The system should allow the deletion of a book from the

catalog.

$$ Search for books: The librarian should be able to search for books by

title, author, or ISBN number.

$$

$2.$ Borrowing and Returning Books

The system must support:

$$ Borrowing books: Members should be able to borrow books from the

library. The system should check if the book is available and update the

availability status accordingly.

$$ Returning books: Members should be able to return books. The system

should update the availability status of the returned books.

$$ Transaction recording: The system should keep track of all borrowing

transactions, including which member borrowed which book and when

it was borrowed and returned.

GENERAL INSTRUCTION

$1.$ UML Class Diagram

$$ Before writing the code, create a UML class diagram that visually

represents the relationship between the classes in your system $($Book$,$

Member, Library$).$ Your UML should include class attributes, methods,

and relationships between classes $($e$.$g$.,$ composition, association$).$

$2.$ Implementation

$$ Implement the Library Management System in Java. Ensure that your

code adheres to the principles of Object$-$Oriented Programming such

as encapsulation, inheritance, and polymorphism.

$$ Your program should consist of multiple classes and each class should

have clearly defined responsibilities.

$$ Data should be stored in arrays or ArrayLists $($no database or GUI

is required$).$

$3.$ Main Program

$$ Write a main$()$ method that demonstrates the functionality of your

Library Management System. The main program should allow a user

$($simulating the librarian$)$ to perform the following operations through

a text$-$based menu:

$$ Add, update, and delete for books.

$$ Register, update, and view book information.

$$ Borrow and return books records accordingly.

$$ Exit the system.

$4.$ Test Plan

$$ The goal is to verify the correctness, completeness, and reliability of

the Library Management System you implemented using Object$-$

Oriented Programming $($OOP$)$ in Java. This involves testing various

functionalities, ensuring that they work as expected, and documenting

the test cases and results.

$$ Prepare Test Cases:

o For each test scenario, write detailed test cases. Each test case

should include the following details:

$1.$ Test Case ID: A unique identifier for the test case $($e$.$g$.,$

TC$001).$

$2.$ Test Case Description: A brief description of what is

being tested $($e$.$g$.,$ Add a new book to the system$).$

$3.$ Preconditions: Any conditions that must be met before

the test can be executed $($e$.$g$.,$ The system is running,

and the librarian is logged in$).$

$4.$ Test Steps: The specific steps that need to be followed

to perform the test.

$5.$ Expected Result: The expected outcome of the test $($e$.$g$.,$

The book is successfully added and available for

borrowing$).$

$6.$ Actual Result: The actual result when you run the test

$($to be filled in during testing$).$

$7.$ Pass$/$Fail: Whether the test passed or failed.