Slide 13: Let’s now discuss the Methodology of the research study, it describes the process of

creating a Scan & Go Self-Service Lending Machine for borrowing books and a Drop & Go
dropbox system for returning books. This serves as a template for each module that the
researchers would develop for the proposed project. During the Covid-19 epidemic, this paper
attempts to have a specified and complicated solution procedure for book borrowing and
returning, as we follow the school's Safety Health Guidelines and Protocols.

Slide 14: In the requiremtent Analysis it has 3 subsection which are Theoretical Consideration ,

Software Requirements, and Hardware Requiremtmesnt

Slide 15: The researchers have gathered information on the project's requirements, such as sprint
plans with specific targets, application framework, code reviews, automated testing, bug task
tracking, as well as software and hardware requirements.
Researchers will evaluate and review end-user proposals and perform user testing prior to
production of the final project product to include changes to code and system design. This will
help identify the needs of the intended users and thus give researchers a clearer view of how to
start the process by creating a more efficient way to borrow and return books in less time during
pandemic period. It will also give researchers a clear and focused view of the system's design
including its hardware and software components.
Slide 16: The researcher decided to use web programming languages like Hypertext Preprocessor
(PHP) for getting data in database, HyperText Markup Language (HTML) and Cascading Style
Sheets (CSS) to give structure or for the design of the web page, Javascript for system
development of the project, and Python for the micocomputer, Raspberry Pi. The researchers
decided to use MySQL as a database to store all the information necessary for the operation of
the Scan&Go and Drop&Go recommender systems.

Slide 17: The researcher utilizing the The Agile Development Lifecycle Model, it will use for
implementation of the proposed system concept and structure, which will help researchers
adapt to the current configuration and improve the proposed system recommendations based
on customer requirements for our system. It has been modeled to take an iterative approach to
provide a final version containing all required functionality. For the proposed product, the
researchers will use Agile method to build the system to obtain the final product that
corresponds to the user's needs. It will take a long time to complete it as it will go through three
(3) iterations before the full product is available for the project. Changes in design plans during
system development are rare due to the complexity of the technology and user needs. Design
and construction can proceed almost simultaneously, testing various alternatives desirable from
a user and researcher perspective, thus eliminating the need for extensive system modification.
The iterative steps will help the researchers develop an end product that best meets the user's
needs, as well as provide the user with a well-built lending machine and automated return drop
box system next The researchers gathered information through an interview with AdZU
librarians about the current state of AdZU libraries and how they continue to deliver alternative
means for students, faculty and staff during the borrowing process and book returns during and
before the pandemic. After assessing the responses of the librarians, we will be able to identify
areas of interest for both users and library staff. The interview helps to gain insight into the
scope and process of the entire project, anticipated issues, opportunities, and guidance that
enabled the project by providing the best solution to the problem. during and after the pandemic
and also Several tests based on the lending and returning functions were designed to establish
that the Lending Machine and Returning DropBox system met the project's objectives. The
Lending Machine and automated DropBox system were to be put through Alpha and Beta tests
for this project.

Slide 18: The hardware requirements for Scan & Go first is the
Computer
It includes a machine (computer) that can access the internet or server. A computer for the
lending machine which serves as the access to the system. The computer specification will be
as follows:
OS: Microsoft Windows 7/8/10 (32 bit or 64-bit)
RAM: 4 GB RAM minimum, 8 GB RAM recommended;
CPU: Intel(R) Core (TM) i5 processor
HDD: 2 GB of available disk space minimum, 4 GB recommended

Next is RFID Reader

The Scan & Go will be supplied by a USB RFID contactless proximity smart card reader that
works with any RFID/NFC card without the need for a driver and operates at 13.56MHz.

Next is Receipt Printer

Thermal printer will be used for the printing of the receipt since text or images are created from
the heat of the thermal printhead in seconds. It will help in reducing the time for the borrowing
process.

Slide 19: The hardware requirements for the Drop & Go are Raspberry Pi
The Drop&Go system will be operated by a Raspberry Pi microcomputer. Its main objective is to
operate as a tiny computer for the dropbox system to work.
Model: Raspberry PI 4 B (8GB)
CPU: 1.5-GHz, 4-core Broadcom BCM2711 (Cortex-A72)
RAM: 8GB
Wireless: 802.11ac / Bluetooth 5.0
I/O Ports: 2x USB 3.0, 2x USB 2.0, 1x Gigabit Ethernet, 2x micro HDMI
And last is the RFID Card Reader
The Drop&Go dropbox will be operated by a USB RFID contactless proximity smart card reader
that works with any RFID/NFC card without the need for a driver and operates at 13.56MHz.

Slide 40: the overview of the data and relationship between the users and the admin from the
Scan&GO and Drop&Go system. Users, students and staff, are required to provide identifcation
cards while the admins are required to provide their credentials, username and password.
The data relationship between the user and the systems, Scan&Go and Drop&Go, is that users
will scan their ID to the system to validate if the user is registered. Users will also provide the
information of the book to the system for both process of borrowing and returning through
scanning the book tags. The book details will be provided to the users as well as a receipt by
the system.
The data relationship between the admin and the system is that they will input their credentials,
username and password, to validate if the user is an admin of the system. As the admin has the
function to monitor the borrow and return logs, all the information from the borrowing and
returning process of all users will be provided.

Slide 41: here in the level 0 diagram it illustrates the basic overview process of the proposed
system. The flow of the system will start at the authorized User and the Manage Borrow Books.
the user will provide the ID, name and the book code through scanning which will be then
processed and transmitted to the database of the system. After the database receives the
information, Generate Borrow Receipt will provide the user with the checkout receipt.
The next process and relationship is of the data from the students to the Manage Borrow Books
to the Admin. After the user’s information, and book code/s as well as the information of the
borrow date and due date of the book/s is provided the information will be transmitted as borrow
logs to the admin. The admin can now monitor the borrow logs.
For the returning process, borrowed books will go through a scanning process as they are
deposited into the dropbox, the information of the scanned book will be transmitted as return
logs to the admin. The return logs and borrow logs will be compared by the admin to check if the
user has incured fines. The admin will then update the user’s account accordingly; user’s
without any incured fines will get a cleared updated book detail; user’s with incured fines will get
an updated book details with the fine for each book.
Slide 41: The data model of the system has six entities – Users, Borrow-Return Logs, Admin,
Payment, Books, and RFID.
The Users have a one (and only one) relationship with the Borrow-Return Logs since users can
only have one record per borrowing of books. Also the Borrow-Return Logs has a zero or many
relationship to the users, since students will have no record or borrow return logs until they will
borrow a book. Users can have many book return logs since users can borrow multiple times.
From Book-Return Logs there is a zero or many relationship to the Admin since the admin is the
one who manages all the data including the borrow and return logs in the library database
system. From the Admin there is a one (and only one) relationship to the Payment since the
payment can only occurs ones per user log, and a one (and only one) relationship between the
Payments and the Admin since the payment or receipt will only be provided once, to clear the
name of the user for overdue return. A Payment has one (and only one) relationship with the
Users since the users can only pay once per transaction, and a zero or many relationship
between the Users and Payments, since the users can have none or multiple overdue return
and need to pay multiple times for the overdue books fines. From the Users it has a one to
many relationship with the Books since users can have at least one book or have mutltiple
books for borrowing, and a one (and only one) relationship from Books to Users since a book
can only be borrowed by one user at a time. A book has zero or many relationship with the
RFID since the book can have zero RFID and a many RFID tags for the books. There is a one
(and only one) relationship between RFID and the books since only one rfid tags can be
provided per book.

Slide 42: Under System Design In this section, the researchers will discuss each function of the
different software modules and submodules. It is divided into two parts – Scan&Go and
Drop&Go system modules.

Slide 43: Here its show the general flowchart of the Scan & Go System, next I will discuss each
of the module of the Scan & Go system
Slide 44: first we have The Scan ID module is designed to ensure that the user is enrolled or
validated to proceed to accessing the Scan&Go system. The user starts with scanning the ID, it
will then check from the database of the system if the user is enrolled or validated, if the user is
not validated an error message will be shown, else it will proceed to the home module of the
proposed system which consist of the borrow

Slide 45: we have the The User Account module will show the user’s existing borrow logs from
the database. It is design to show the user the borrowed date, the date for returning the books,
and it also includes the fines of the user if the user exceeded its due date.

Slide 46: Under the borrow module it consist of three submodules – first the scan book second
the show booklist, and lastly is the checkout module.
Slide: 47: in the Scan Book module it is designed to scan the RFID tags of each book and get
the book information from the system’s database. The flow for the scanning of books will starts
from the user with the RFID tagged books to be scanned, the user will now scan the books to
borrow, a condition from the system is set to know if the book tag is registered in to the system,
if the books is registered it will now provide the book information from the database to the user.
If the user is done with scanning the books, the user will now proceeds to the show list module.
Slide: 48 next is the Show Book List module it is designed to provide the list of books that have
been scanned and show the information of each book from scanning, to check if it’s already the
correct books that the user wanted to borrow. Then if the books are all correctly listed the user
will now proceeds to Checkout module, if not the user can go back to Scan Book module.
Slide 49: The user is first asked to scan the ID for check out, if the identity of the user matches
the data from the Scan ID module before entering in to the system, it will now store the scanned
books into the database under the user’s account and it will then prints out the book information
including the date borrowed and the return date of the books as a receipt.
Slide 50: we have now the general flowchart of the Drop & Go system, next I will discuss each
of the module of the Drop & Go system.
Slide 51: The Drop&Go is designed to be an automated system purposely for returning of book
through a book drop. It is designed to identify and recognize books with RFID tags regsitered in
to the system before proceeding in to the admin module. The Drop box module is design to
proceed to notifcation module if the set limit capacity for the dropbox is met.
Slide 52: The flow of the Notification module start with the book’s tag being scanned, every book
scan will add one to the total numer of book scanned. Once the number of book scanned
reaches the set maximum capacity, it will now transmit the information to the librarian that the
dropbox is already full and the books are ready to be picked up. After getting the books in the
dropbox, the librarian will now press the button available in the Rpi to set the book count back to
zero.
Slide 53: The Admin module also starts with the book’s tag being scanned, then it will update to
the library system the number of books being returned including the book information. The
module will be updated with the books borrow log and return log from the system’s database.
The logs will then be compared by the admin, librarian, and calculate the fines if there are any.
Then the admin will now update the user account w/ accumulated fines that the user incurred
and store it into the system database.
Slide 54: The last section of the Methodology is the testing and validation. The purpose of Alpha
tests is to assess the product's quality and ensure Beta readiness. .
For the scan id module test The researcher will have to create two (2) dummy accounts for
the ID scanning, one is a validated user and the other one is unvalidated. To do this, the
researcher will have two (2) ID’s assigning different account on each card, with those IDs the
researcher will use it to scan into the machine.
For the user account test the reasearchers will create validated accounts with preregistered
borrow logs. To consider this test a success, upon accessing the user account module the
system should be able to show all existing borrow logs.
For the borrow module test the researchers will create a validated account, to proceed to the
borrow module of the system. The system should be able to successfully show the borrow
button and successfully proceeds to the scanning of book module after selecting the button.
For the Scan book module test the researcher will scan the unregistered and registered
tagged books. To consider this test success all registered tags must be read by the system
while unregistered tags will be ignored.
For the List of book module test the researchers will scan multiple books. To consider this
test a success the system must be able to get all the books information of each scanned book
tag from the system’s database and output it.
For the Checkout module test the researchers will scan unregistered ID or a different ID from
the one that the researchers used for entering into the system, to see if the system will proceeds
to checking out the books. It is expected to only recognized the ID that is a match from the ID
used for accessing the system, else the system will not go through the Checkout module.
Slide 55: We have now the system testing for the Drop & go System
For the dropbox module test To do this the researchers will have twenty (20) books, where
ten (10) have registered tags, five (5) unregistered tags, and five (5) untagged books. To ensure
this test is a success the dropbox system must be able to recognize all of the ten (10) registered
tags and ignore the five (5) unregistered tags and five (5) untagged books.
For the notification module test the researchers will set the maximum capacity of the dropbox
and use registered books to drop inside the drop box. The module is expected to successfully
count the number of books that have been returned through the dropbox then notify the admin
that the dropbox is full through the library system.
For the Admin Module test the researchers will drop ten (10) registered book to test if the
Drop&Go system will output the book information, borrow log and return log, to the library
system.

Slide 56: After the alpha testing is completed, beta testing will begin. Because the system
requires privacy between the user and the respondent, ten people will be requested to
participate as users and one librarian as admin for the testing. Respondents would be asked to
repeat the researchers' tests and give a rating of the system based on their personal
experiences and suggestions.

Slide 57: The last but not the list the validation of result,All modules must work and process
according to their purpose also the Scan&Go and Drop&Go must be able to solve each of the
component problems.