Solution
Amar Kumar answered on
Oct 04 2022
Design of a system using OOP
Summary
A piece of software known as a li
ary management system takes care of a li
ary's essential administrative tasks. Li
aries must have systems in place to monitor customer interactions and asset collections. Li
aries may use li
ary management systems to keep track of patrons' profiles, subscriptions, and the books they bo
ow and when they return them.
Another function of li
ary management systems is to maintain the database used to track bo
owed books and their due dates.
Introduction
The fundamental building block of object-oriented modeling frequently depicts the various system objects, their properties, their various functions, and their interactions. These individual parts are refe
ed to as "class diagrams."
Class diagrams are widely used to conceptually represent the static look of a software application and to model the precise conversion of models into programming code.
Class diagrams are frequently used in software system design and development. They are also utilized in the modeling of data. It shows connections, classes, affiliations, interfaces, and other things. A class in a class diagram is just the blueprint for an object. It merely provides descriptions of the various system components and their interactions.
Background
System Requirements
· The following set of requirements will receive special attention as we develop the li
ary management system:
· The title, author, subject, and publication date of a book ought to be searchable by any li
ary patron.
· Each book will have a unique identification number that, in addition to additional information like the rack number, will make it simpler to locate the book in person.
· Customers ought to be able to reserve and bo
ow any one of the multiple copies of a book. Each book copy is refe
ed to as a book item.
· Details like who bo
owed a particular book and which volumes a given li
ary patron has on loan should be accessible by the system.
· A member should not be allowed to keep a book longer than ten days.
· The system specifies that late returns of books should result in fines.
· Unread books need to be available for members to reserve.
· When reserved books become available and when a book is not returned by the due date, the system should be able to notify users.
· Each membership card and book will have its own unique barcode. Barcodes on li
ary cards and books will be readable by the technology.
Use case diagram
There are three primary players in our system:
· Li
arian: primarily accountable for updates that affect users, books, and books. Additionally, the li
arian can lend, hold, and receive books.
· Member: Members have access to the catalog, which they can use to check out, reserve, renew, and return books.
· System: principally in charge of notifying customers of cancellations, late bookings, and other issues.
The following is a list of the most common applications for the Li
ary Management System:
· Add/Remove/Edit book: to change, add, or take away from a book or book item.
· Search catalog: to search for books by title, author, subject matter, or publication date.
· Register new account/cancel membership: to either add a new member to the group or remove an existing member.
· Check-out book: to get a book from the li
ary to bo
ow.
· Reserve book: to reserve a book that is not yet available for purchase.
· Renew a book: to bo
ow a previously checked-out book again.
· Return a book: to return a member-given book from the li
ary.
Class diagram
The following are our Li
ary Management System's primary classes:
Li
ary: the most important part of the business for which this program was made. Because its "Name" and "Address" are specific to the location, it stands out from other li
aries.
Book: the system's fundamental skeleton. The ISBN, title, subject, publisher, and other details will be on each book.
Book Item: Each copy of a book will be treated...