Scribd
Upload
33 views6 pages

Library Management System

Uploaded by

bsoombsoom
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
33 views6 pages

Library Management System

Uploaded by

bsoombsoom
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Library Management System

Presented by
Basma Gamal Mohammed

1
High Level Data Flow Diagram

2
Combined Use-Case Diagram

3
Books Database Design (ERD)

Borrowing Screen
4
We can use Figma to sketch up. Here are the fields expected to be in the Borrowing screen:

 Search Bar (for searching Keywords)


 Books Filtration Criteria
o Author
o Publisher
o Publication Year (from-to)
o Language
o Subject
 Books Listing Page with following Columns
o Book ID
o Book Title
o Author
o Subject
o Publication Year
o Book Status (including Number of copies available)
 Borrow Action for single or multiple books at the same (taking into consideration the business
rules for the maximum number of books to be borrowed and the current borrowed books)
 User can search for books using search bar or using the above filtration criteria or using both
and search results are displayed.
 Search results should be sorted alphabetically in descending order .

Use Case ID Borrow -Transaction-Use-Case-01


Primary Actor
Member
Preconditions
User membership is active and the book is available for borrowing
Main Flow
 User logs into their account.
 User searches for the book they wish to borrow
 The system checks the availability of the book.
 The system displays the Books Listing page.
 User selects the books to borrow.
 The system prompts the user to confirm the borrowing details (e.g., return date).
 User confirms the borrowing details.
 The system processes the transaction
 User receives confirmation with a due date for returning the item.
Postconditions
 The book status is updated.
 Number of books borrowed by this member increase by one.

Use Case

5
Epic and User Story

Epic Title Reporting Functionalities


Epic Description
As a Librarian, I want to generate detailed reports so that I can track data.
Acceptance Criteria
 Librarian can search or filter generated reports
 Librarian shall be able to export report to excel sheet.

User Story Title Fines Report


Description
As a Librarian, I want to generate detailed reports on fines issued (due to late returns
or lost books), so that I can track unpaid fines and send reminders to members.
Acceptance Criteria
 The report shall include the following details
o Member Full Name
o Borrowed Book Title
o Fine amount
o Return Due Date
o Payment Status
 Librarian can search or filter the report using the following criteria:
o Member Name
o Book Title
o Fine Amount (from-to)
o Return Due date (from -to)
o Payment Status
 The system allows generating fines reports for a specific time range.
 The system allows exporting report to excel sheet.

You might also like