Software Requirements Specifications (SRS)

Project Name: Library Management System

Group:

Muhammad Ahsan F2022065099

Bahawal Hasnain F2022065108

Zeeshan Akram F2022065166

Section: W2

Resource Person: Ms. Uzma Farooq

Department of Software Engineering

School of System and Technology

University of Management and Technology

Lahore

2024
1. Use Cases

1.1Use Case Name: Add New Book

Actor: Librarian
Pre-Condition: Librarian is logged into the system and has the necessary
permissions.
Post-Condition: The new book is added to the library inventory.
Basic Flow:
1. User navigates to the 'Add New Book' section.
2. User enters the details of the new book (title, author, ISBN, etc.).
3. User clicks on the 'Add' button.
4. System validates the input and adds the book to the inventory.
Alternate Flow:
If the entered book details are incomplete or invalid, the system displays an
error message and prompts the librarian to correct the information.
GUI:
1.2 Use Case Name: Search for Books
Actor: User (Member or Librarian)
Pre-Condition: User is logged into the system.
Post-Condition: The search results are displayed based on the user's query.
Basic Flow:
1. User enters the search criteria (title, author, ISBN, etc.).
2. User clicks on the 'Search' button.
3. System retrieves and displays the search results.
Alternate Flow:
If no matching books are found, the system displays a message indicating that
no results were found.
GUI:

1.3 Use Case Name: Borrow Book

Actor: Member
 Pre-Condition: Member is logged into the system and has selected a book to
borrow.
Post-Condition: The book is marked as borrowed, and the member's borrowing
history is updated.
Basic Flow:
1. User searches for and selects the book to borrow.
2. User clicks on the 'Borrow' button.
3. System checks the availability of the book.
4. System marks it as the book borrowed and updates the member's
borrowing history, if the book is available.
Alternate Flow:
If the book is not available, the system displays a message indicating that the
book is currently unavailable for borrowing.
GUI:

1.4 Use Case Name: Return Book

Actor: Member
Pre-Condition: Member is logged into the system and has borrowed a book.
 Post-Condition: The book is marked as returned, and the member's borrowing
history is updated.
Basic Flow:
1. User navigates to the 'Return Book' section.
2. User selects the book to return.
3. User clicks on the 'Return' button.
4. System marks the book as returned and updates the member's borrowing
history.
Alternate Flow:
If the book is already marked as returned, the system displays a message
indicating that the book has already been returned.
GUI:

1.5 Use Case Name: Reserve Book

Actor: Member
 Pre-Condition: Member is logged into the system and the book is currently
unavailable.
Post-Condition: The book is reserved for the member once it becomes
available.
Basic Flow:
1. User searches for and selects the book to reserve.
2. User clicks on the 'Reserve' button.
3. System adds the book to the member's reservation list.
Alternate Flow:
If the member tries to reserve more books than the allowed limit, the system
displays a message indicating the limit and does not add the book to the
reservation list.
GUI:

1.6 Use Case Name: View Book Availability

Actor: Member or Librarian
Pre-Condition: User is logged into the system.
Post-Condition: The availability status of the book is displayed.
Basic Flow:
 1. User searches for and selects the book.
2. User clicks on the 'View Availability' button.
3. System displays the availability status of the book.
Alternate Flow:
If the book is not found in the system, the system displays a message indicating
that the book could not be found.
GUI:

1.7 Use Case Name: Manage Book Inventory

Actor: Librarian
Pre-Condition: Librarian is logged into the system and has the necessary
permissions.
Post-Condition: The book inventory is updated according to the librarian's
actions.
Basic Flow:
1. User navigates to the 'Manage Book Inventory' section.
 2. User selects the action to perform (add, edit, delete).
3. User enters the necessary details and clicks on the 'Save' button.
4. System updates the book inventory based on the librarian's actions.
Alternate Flow:
If the librarian tries to delete a book that is currently being borrowed by a
member, the system displays a message indicating that the book cannot be
deleted until it is returned.
GUI:

1.8 Use Case Name: View Borrowing History

Actor: Member
Pre-Condition: Member is logged into the system.
Post-Condition: The member's borrowing history is displayed.
Basic Flow:
1. User navigates to the 'View Borrowing History' section.
2. System retrieves and displays the member's borrowing history.
 Alternate Flow:
If the member has not borrowed any books, the system displays a message
indicating that the borrowing history is empty.
GUI:

1.9 Use Case Name: Manage User Accounts

Actor: Librarian
Pre-Condition: Librarian is logged into the system and has the necessary
permissions.
Post-Condition: The user account is updated according to the librarian's actions.
Basic Flow:
1. User navigates to the 'Manage User Accounts' section.
2. User selects the user account to manage.
3. User selects the action to perform (edit, delete).
4. User enters the necessary details and clicks on the 'Save' button.
5. System updates the user account based on the librarian's actions.
Alternate Flow:
 If the librarian tries to delete a user account that has borrowed books, the system
displays a message indicating that the user account cannot be deleted until all
borrowed books are returned.
GUI:

1.10 Use Case Name: Generate Reports

Actor: Librarian
Pre-Condition: Librarian is logged into the system and has the necessary
permissions.
Post-Condition: The report is generated based on the selected criteria.
Basic Flow:
1. User navigates to the 'Generate Reports' section.
2. User selects the type of report to generate.
3. User selects the criteria for the report (e.g., date range, book category).
4. User clicks on the 'Generate Report' button.
5. System generates and displays the report.
Alternate Flow:
If the librarian selects an invalid report type or criteria, the system displays a
message indicating the error.
GUI: