Scribd
Upload
737 views7 pages

Library Management System Design Guide

The document describes requirements, diagrams, and activities for a library management system. It includes use case and class diagrams showing actors like librarians and members, and classes like books, book items, accounts, and library cards. It also provides activity diagrams for checking out, returning, and renewing books, with steps like verifying due dates and collecting fines. The goal is to design a system to manage book and member data and checkouts.

Uploaded by

chuchu
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
737 views7 pages

Library Management System Design Guide

The document describes requirements, diagrams, and activities for a library management system. It includes use case and class diagrams showing actors like librarians and members, and classes like books, book items, accounts, and library cards. It also provides activity diagrams for checking out, returning, and renewing books, with steps like verifying due dates and collecting fines. The goal is to design a system to manage book and member data and checkouts.

Uploaded by

chuchu
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
  • System Requirements
  • Use Case Description
  • Class Diagram
  • Class Details
  • Activity Diagram

Design a Library Management System

 System Requirements
 Use case diagram
 Class diagram
 Activity diagrams

System Requirements

A Library Management System is a software built to handle the primary housekeeping functions
of a library. Libraries rely on library management systems to manage asset collections as well as
relationships with their members. Library management systems help libraries keep track of the
books and their checkouts, as well as members’ subscriptions and profiles.

Library management systems also involve maintaining the database for entering new books and
recording books that have been borrowed with their respective due dates.

We will focus on the following set of requirements while designing the Library Management
System:

1. Any library member should be able to search books by their title, author, subject category
as well by the publication date.
2. Each book will have a unique identification number and other details including a rack
number which will help to physically locate the book.
3. There could be more than one copy of a book, and library members should be able to
check-out and reserve any copy. We will call each copy of a book, a book item.
4. The system should be able to retrieve information like who took a particular book or what
are the books checked-out by a specific library member.
5. There should be a maximum limit (5) on how many books a member can check-out.
6. There should be a maximum limit (10) on how many days a member can keep a book.
7. The system should be able to collect fines for books returned after the due date.
8. Members should be able to reserve books that are not currently available.
9. The system should be able to send notifications whenever the reserved books become
available, as well as when the book is not returned within the due date.
10. Each book and member card will have a unique barcode. The system will be able to read
barcodes from books and members’ library cards.

Use case diagram

We have three main actors in our system:

 Librarian: Mainly responsible for adding and modifying books, book items, and users.
The Librarian can also issue, reserve, and return book items.
 Member: All members can search the catalog, as well as check-out, reserve, renew, and
return a book.
 System: Mainly responsible for sending notifications for overdue books, canceled
reservations, etc.

Here are the top use cases of the Library Management System:

 Add/Remove/Edit book: To add, remove or modify a book or book item.


 Search catalog: To search books by title, author, subject or publication date.
 Register new account/cancel membership: To add a new member or cancel the
membership of an existing member.
 Check-out book: To borrow a book from the library.
 Reserve book: To reserve a book which is not currently available.
 Renew a book: To reborrow an already checked-out book.
 Return a book: To return a book to the library which was issued to a member.

Use case diagram


Class diagram

Here are the main classes of our Library Management System:

 Library: The central part of the organization for which this software has been designed.
It has attributes like ‘Name’ to distinguish it from any other libraries and ‘Address’ to
describe its location.
 Book: The basic building block of the system. Every book will have ISBN, Title,
Subject, Publishers, etc.
 BookItem: Any book can have multiple copies, each copy will be considered a book
item in our system. Each book item will have a unique barcode.
 Account: We will have two types of accounts in the system, one will be a general
member, and the other will be a librarian.
 LibraryCard: Each library user will be issued a library card, which will be used to
identify users while issuing or returning books.
 BookReservation: Responsible for managing reservations against book items.
 BookLending: Manage the checking-out of book items.
 Catalog: Catalogs contain list of books sorted on certain criteria. Our system will support
searching through four catalogs: Title, Author, Subject, and Publish-date.
 Fine: This class will be responsible for calculating and collecting fines from library
members.
 Author: This class will encapsulate a book author.
 Rack: Books will be placed on racks. Each rack will be identified by a rack number and
will have a location identifier to describe the physical location of the rack in the library.
 Notification: This class will take care of sending notifications to library members.

Class diagram for Library Management System


Activity Diagram

Check-out a book: Any library member or librarian can perform this activity. Here are the set of

steps to check-out a book:

Return a book: Any library member or librarian can perform this activity. The system will
collect fines from members if they return books after the due date. Here are the steps for
returning a book:

Renew a book: While renewing (re-issuing) a book, the system will check for fines and see if
any other member has not reserved the same book, in that case the book item cannot be renewed.

Here are the different steps for renewing a book:

Code--Finally implement the code by the selected language.

Common questions

Powered by AI

The 'Fine' class manages the process of calculating and collecting fines for overdue books. When a book is returned past its due date, the system automatically computes the fine based on the number of overdue days and the set fine policy. This ensures accountability, as the fine calculation is automated, and the collection is integrated with the book return process, minimizing manual oversight .

Efficient handling of overdue book notifications can be achieved through automated scheduling and batching processes using the 'Notification' class. This class can integrate with calendars and email systems to send out timely alerts. It may use machine learning algorithms to optimize the timing and frequency of notifications based on user response history. This not only ensures timely alerts but also aims to improve response rates by adapting to user behavior patterns .

The 'BookItem' class represents each physical copy of a book, which is pivotal for system operations as it allows multiple copies of a book to exist simultaneously, each with a unique barcode. This facilitates precise tracking of each book copy's location, availability, and status. Including 'BookItem' helps differentiate between multiple copies of the same book and supports functionality like accurate checkouts, returns, and reserves, thereby improving inventory management .

The 'Catalog' class supports search functionality by organizing books into searchable categories based on title, author, subject, and publication date. This categorization allows users to execute detailed queries and receive refined search results, enabling efficient discovery of books matching specific criteria. The catalog's database backend structures the information to provide quick access and integration with user interfaces, thereby enhancing the search experience across digital and physical assets .

Challenges in managing book reservations include ensuring accurate reservation records, avoiding double bookings for the same copy, and managing reservation priority or waitlists. The 'BookReservation' class addresses these by maintaining reservation details specific to each book item, tracking reservation queues, and integrating with notification systems to alert members when books become available. This systematic approach minimizes conflicts and ensures equitable access to book items .

In the use case diagram, the librarian primarily manages the addition, modification, and removal of books and users. They are also responsible for issuing, reserving, and returning book items. Members, on the other hand, are generally involved in using the catalog to search for books, checking out, reserving, renewing, and returning books. The system supports these tasks by handling notifications for overdue books and reservations .

The 'Check-out a Book' activity involves both librarians and members, but with differing interactions. Librarians might have admin-level permissions to override certain limits or manage user accounts, whereas members follow a direct protocol of selecting, scanning, and confirming book items for checkout. Steps such as accessing member accounts, verifying identity through barcodes, and checking book availability remain common, along with system notifications about due dates and conditions .

Key system requirements include the ability for members to search books by title, author, subject, and publication date, manage book checkouts and reserves, and track membership details. Each book has a unique identification number and rack location. The system must allow multiple copies of a book to be checked out or reserved. A maximum of 5 books can be checked out per member, and the return period is limited to 10 days, with fines collected for late returns. Reservations can be made on unavailable books, and notifications must be sent for due and overdue items. The system interacts with unique barcodes for books and member cards to facilitate these functions .

Unique identification and traceability in the system are ensured through barcodes assigned to each book item and member card. For books, the unique identification number and rack number alongside the book’s barcode help in tracking each item’s location and status. For members, their library card's unique barcode ties directly to personal borrowing records. This design supports robust tracking and accountability for both book transactions and membership activity .

A maximum limit of 5 check-outs per member and a return period of 10 days promotes fair distribution and availability of library resources, preventing monopoly by a few members. This policy ensures a consistent flow of book circulation, reducing the chances of books being inaccessible due to long-term checkouts. Consequently, it streamlines the reservation and notification system, thus enhancing operational efficiency by better balancing between user demand and resource availability .

Design a Library Management System  System Requirements (https://www.educative.io/courses/grokking-the-object-oriented-desig
 System: Mainly responsible for sending notifications for overdue books, canceled reservations, etc. Here are the top use c
Class diagram Here are the main classes of our Library Management System:  Library:
 LibraryCard: Each library user will be issued a library card, which will be used to identify users while issuing or return
Activity Diagram Check-out a book: Any library member or librarian can perform thi

You might also like