You are required to design a library system for Kent Institute. Assume that there are: two campuses – Sydney and Melbourne 300 VET level students 400 Higher Education students 20 professional staff...

Design of a system using OOP
Summary
A piece of software known as a li
ary management system is in charge of the fundamental administrative functions of a li
ary. Essential are systems for managing li
ary asset collections and interactions with customers. Li
ary management systems enable li
aries to keep track of members' subscriptions and profiles, as well as books and their checkouts.
Another aspect of li
ary management systems is maintaining 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 frequently used to model the precise conversion of models into programming code and to conceptually represent the static appearance of a software application. During software system design or development, class diagrams are frequently used. They are also used in data modeling. It is used to show classes, connections, interfaces, associations, and other things. A class in a class diagram is just the blueprint for an object. It only provides definitions and explanations for the numerous system objects 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.
· In addition to additional information like the rack number, each book will have a unique identification number that will make it easier to locate the book in person.
· A book may have multiple copies, and patrons should be able to reserve and bo
ow any one of them. A book item is the name given to each copy of a book.
· 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.
· Ten days should be the maximum amount of time a member can keep a book.
· The system states that penalties should be applied to books returned after the due date.
· Members ought to be able to reserve unread books.
· The system ought to be able to send notifications whenever the reserved books become accessible and whenever the book is not returned by the due date.
· Every member card and book will have a unique barcode. It will be possible for the technology to read barcodes on books and li
ary cards.
Use case diagram
There are three primary players in our system:
· Li
arian: primarily responsible for user, book, and book-related updates. The li
arian also has the ability to 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 modify, add, or remove a book or book item.
· Search catalog: to look up books by subject, author, title, or publication date.
· Register new account/cancel membership: to add a new member or remove an existing member from the group.
· 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 li
ary book that was given to a member.
Class diagram
The primary classes of our Li
ary Management System are as follows:
Li
ary: the most crucial element of the company for which this programme was created. It stands apart from other li
aries thanks to its location-specific "Name" and "Address."
Book: the fundamental skeleton of the system. Each book will have the ISBN, title, subject, publisher, etc.
BookItem: Each copy of a book will be treated as a separate record in our database, even if it contains multiple copies.All of the books' barcodes will be unique.In our database, each copy a person owns will be treated as a separate book item.All of the books' barcodes will be unique.
Account: There will be two distinct types of accounts in the system:a li
arian and a general member.
Li
aryCard: Each li
ary user will be issued a card that they can use as proof of identity when bo
owing or returning books.
BookReservation: is in charge of monitoring book product reservations.
BookLending: Limit the number of books bo
owed.
Catalog: Catalogs organize book lists according to a variety of criteria.Our system will make it easier to search across the four catalogs—Title, Author, Subject, and Publish-Date.
Fine: Computing and collecting li
ary fines from patrons will...