Fyp4033 Fyp1

UNIVERSITI POLY-TECH MALAYSIA
BOARDING SCHOOL LOCKER LOCK
MUHAMMAD ZAFRAN BIN MOHD ZUHAIRI
BACHELOR OF INFORMATION
TECHNOLOGY (HONS) IN CYBER
SECURITY
MUHAMMAD ZAFRAN BIN MOHD ZUHAIRI Boarding School Locker Lock
UNIVERSITY POLY-TECH MALAYSIA

Faculty of Computing & Multimedia
BOARDING SCHOOL LOCKER LOCK
MUHAMMAD ZAFRAN BIN MOHD ZUHAIRI

AM2111010674
FYP4033
NOVEMBER 2023
FYP4033 Page 3 of 54
Declaration of Originality
This project is all my own work and has not been copied in part or in whole from any other source
except where duly acknowledged. As such, all use of previously published work (from books,
journals, magazines, internet, etc.) has been acknowledged within the main report to an item in
the References or Bibliography lists.
I also agree that an electronic copy of this project may be stored and used for the purposes of
plagiarism prevention and detection.
Copyright Acknowledgement
I acknowledge that the copyright of this project and report belongs to Universiti Poly-Tech
Malaysia.
Signed: Date:
Office Stamp
Abstract
This project is called Boarding School Locker Lock. This project is a response to stealing cases inside
boarding schools in Malaysia. Most of the stealing cases are related to student’s locker break-ins. To help
to decrease the stealing cases in boarding schools, an RFID lock is suitable to be implemented in school.
It’s more practical for the students and for the school to maintain security for student’s belongings and
helps the school manages stealing cases. This project implements an RFID lock to either student lockers,
wardrobes, cabinets, or any space for students place their belongings. This project also have IoT features
to have a user friendly way to manage the locks and the RFID tags or cards. It have to keep in mind that
the school staff like the wardens of the school have the control of the lock system rather than the students.
Table of Contents
[This table is constructed automatically by Word, by collecting items set in Heading 1, 2 or 3 style. To
update the table, double-click, right-click on it and select “Update Field” > “Update entire table”.]
1. Introduction ..................................................................................................... 13
1.1 Project Background ................................................................................................. 13
1.2 Problem Statements ................................................................................................ 13
1.2.1 The amount of stealing in boarding school is not decreasing. ...........................13
1.2.2 The students are helpless to make sure their belongings are safe. ..................14
1.2.3 The wardens lack control and access of student’s lockers. ..............................14
1.3 Project Objectives ....................................................................................................14
1.3.1 To develop a Radio Frequency Identification Based Lock .................................14
1.3.2 To provide a good lock for the school locker ......................................................14
1.3.3 To provide a web-based system and an app that helps the warden access and view events of
the lock. ...........................................................................................................................15
1.4 Scope and Target User ............................................................................................15
1.4.1 Project Scope ......................................................................................................15
1.4.2 Product Scope .....................................................................................................15
1.4.3 Target User ......................................................................................................... 16
1.5 Overview of This Report ..........................................................................................16
2 Investigation / Literature Review ................................................................... 17
2.1 Introduction to Radio Frequency Identification (RFID) ....................................... 17
2.1.1 Radio Frequency Identification (RFID) lock ........................................................18
2.1.2 Arduino ................................................................................................................ 18
2.1.3 Arduino RFID ...................................................................................................... 19
2.2 Existing Project ........................................................................................................ 19
2.2.1 RFID Door Lock System ..................................................................................... 19
2.2.1.1Board used for the project .................................................................................................... 20
2.2.2 Smart door lock using RFID & ESP32 ................................................................21
2.2.3 Iot Smart Door Lock System Using NodeMCU ESP8266 ..................................23
2.3 Comparison .............................................................................................................. 24
2.4 Discussion ................................................................................................................ 25
2.5 Conclusion ................................................................................................................25
3 Methodology ....................................................................................................26
3.1 Introduction .............................................................................................................. 26
3.2 Agile Methodology ................................................................................................... 26
3.3 Phases in Agile Methodology .................................................................................27
3.3.1 Planning Phase ................................................................................................... 27
3.3.2 Design Phase ......................................................................................................27
3.3.3 Development Phase ............................................................................................27
3.3.4 Testing Phase ..................................................................................................... 28
3.3.5 Deployment Phase ..............................................................................................28
3.3.6 Review Phase ..................................................................................................... 28
3.4 Conclusion ................................................................................................................29
4 Requirements .................................................................................................. 29
4.1 Introduction .............................................................................................................. 30
4.2 Data Gathering Technique ...................................................................................... 30
4.2.1 Questionnaire .....................................................................................................................30
4.3 Functional Requirement ..........................................................................................31
4.4 Non-Function Requirement .....................................................................................31
4.5 Software Requirement .............................................................................................32
4.5.1 GitHub ................................................................................................................................ 33
4.5.2 Arduino IDE ........................................................................................................................33
4.5.3 Blynk ...................................................................................................................................33
4.6 Hardware Requirement ............................................................................................34
4.7 Conclusion ................................................................................................................34
5 Analysis ........................................................................................................... 34
5.1 Introduction .............................................................................................................. 35
5.2 Data Gathering Analysis ......................................................................................... 35
I. Question 1 ..................................................................................................................................35
5.3 Use Case Model ........................................................................................................40
5.3.1 Administrator Use Case Diagram ...................................................................................... 40
5.3.2 Student Use Case Diagram ............................................................................................... 41
5.4 Flowchart .................................................................................................................. 42
5.5 BPMN (Business Process Modelling Notation) .................................................... 43
5.6 Conclusion ................................................................................................................43
6 Design .............................................................................................................. 44
7 Implementation ............................................................................................... 44
8 Testing ............................................................................................................. 45
9 Project Management .......................................................................................46
9.1 Project Schedule ...................................................................................................... 46
9.2 Risk Management .....................................................................................................46
9.3 Quality Management ................................................................................................ 46
10 Conclusions .................................................................................................... 46
10.1 Achievements ..................................................................................................... 47
10.2 Future Work ........................................................................................................ 47
10.3 Project Evaluation .............................................................................................. 47
Appendix A – Requirements Specification Document .........................................48
Appendix B – User Manual ..................................................................................... 49
References ............................................................................................................... 50
List of Figures
Figure 2.1 Radio Frequency Identification ………………………………… ……………….. 16

Figure 2.2: Arduino ………………………………… ……………………………………………. 17
Figure 2.3: RFID Door Lock System ………………………………… ………………………… 18
Figure 2.4: Arduino Uno ………………………………… ………………………………………. 19
Figure 2.5: Smart door lock using RFID & ESP32………………………………… ………… 20
Figure 2.6: ESP32………………………………… ……………………………………………….. 21
Figure 2.7: Iot Smart Door Lock System………………………………… ……………………. 22
Figure 2.8: NodeMCU ESP8266………………………………… ……………………………….. 22
Figure 3.1: Agile Methodology Diagram ………………………………… ……………………. 25
Figure 4.1: GitHub………………………………… ……………………………………………….. 32

Figure 4.2: Arduino IDE………………………………… …………………………………………. 32
Figure 4.3: Blynk ………………………………… ………………………………………………… 33
Figure 5.1: Question 1 Response ………………………………… …………………………….. 34

Figure 5.10: Question 10 Response ………………………………… ………………………….. 37
Figure 5.14: Administrator Use Case Diagram ………………………………… ………………39
Figure 5.15: Student Use Case Diagram………………………………… ……………………….40
Figure 5.16: Flowchart ………………………………… ……………………………………………41
Figure 5.17: BPMN………………………………… …………………………………………………42
List of Tables
Table 2.1 Comparison of Existing Projects ………………………………………… 24
Table 4.1 Functional Requirements ………………………………………………….. 31

Table 4.2 Non-Functional Requirements ……………………………………………. 32
Acknowledgements
My sincere gratitude goes out to everyone who made it possible for me to finish my final year project. My
supervisor, Madam Shamshillah binti Kamarzaman, and coordinator, Madam Noraliza binti Azizan,
deserve a special thank you for their stimulating suggestions and encouragement that greatly aided me in
organising my project, particularly in writing this project documentation. In addition, I would like to express
my gratitude to my family for their vital assistance in granting me permission to use all tools and supplies
needed to finish creating "Boarding School Locker Lock." My parents deserve special recognition for
helping me begin this final year project. Lastly, I would like to express my gratitude to my friends and
classmates who helped me with my final year project by motivating me throughout the semester and
offering their suggestions and opinions regarding the task of building the project.
1. Introduction
An introduction of a project explains what the project is about. Introduction helps readers to get a full
understanding of why the project is being made, how the project is going to finish, where is this project
going to be implemented and who is this project intended users.
1.1 Project Background

The Boarding School Locker Lock is a lock that uses Radio Frequency Identification technology that
can help schools have a safer and more secure method of storing personal belongings for school
students. This project will be mainly focused on boarding schools since student lockers are most
common in boarding schools. But this Radio Frequency Identification (RFID) based lock can be
implemented into almost anything such as doors, small gates, cabinets and more. The Boarding
School Locker lock prevents bad actors getting into other students’ lockers and possibly stealing or
taking belongings without permission or access. A school should have a secure way of making their
students feel safe with their belongings. Especially for boarding schools since most boarding schools
require all students to stay at their hostel or dormitory until the end of their school period of each year.
1.2 Problem Statements

A problem statement is a concise description of the problem or issues a project seeks to address. The
problem statement identifies the current state, the desired future state and any gaps between the two.
(Jamie Birt, 2023).
1.2.1 The amount of stealing in boarding school is not decreasing.

The first problem statement is the student is unable to do much to protect their belongings. Because of
that, the bad actor will continue to break into student’s personal lockers and steal or take without
permission. Resulting to the victims of the stealing always must watch out for their belongings and feel
worried every time they’re not around their belongings. Another reason that could adding to the problem of
stealing or breaking into student lockers is the bad actors keep getting away with their misbehaviour and
thus nothing stopping the bad actors to do it again.
1.2.2 The students are helpless to make sure their belongings are safe.
The second problem statement is the student are hopeless to keep their belongings safe. In school, the
students are advised to keep their personal belongings some place safe like inside their personal locker,
cabinet or even wardrobe. Usually there is a place on their safe place to put a lock on and the student
must provide their own lock. Most of the time, students won’t bother to buy a reliable lock because they do
not have much money or even the lock placement is specific on what kind of lock to use. Therefore, the
students don’t have much choice and thus hopeless to make their lockers secure.
1.2.3 The wardens lack control and access of student’s lockers.

The third problem statement is whenever a stealing has occurred, the wardens that in charge of watching
the student dorms during school hours are not always aware of any stealing happening. The wardens do
not have details or aware if a student’s locker has been opened without permission by a bad actor. Other
than that, sometimes the wardens want to do a spot-check on several student’s lockers, but the wardens
can’t open it right away because of the keys to the locker are with the students. Because of this spot-
checks always ends up meaningless and unsuccessful if trying to find unallowed or stolen items.
1.3 Project Objectives

Project objectives are goals that need to achieve to successfully finish the project. Project objectives
identified based on problem statements that are defined for the project. Project objectives purpose are
also to solve the problem statements by defining several methods or ideas of solving the problems.
1.3.1 To develop a Radio Frequency Identification Based Lock

The first objective is to develop a Radio Frequency Identification Based Lock. In this project, the use of an
electronic locker system can become a factor of decreasing the number of stealing and locker break ins in
the school. The electronic locker system will be utilized with Radio Frequency Identification (RFID). By
doing this, students won’t have to rely on traditional or conventional keys anymore or even pad locks. The
locks cannot be opened unless the person opening it is using the access key or forcefully open it. The way
the electronic RFID lock works is each lock have one or a few access keys or tags which are also known
as RFID tags that are unique to each lock. One lock device could have three unique RFID tag that can
only use that specific lock only. If the lock tries to detect a card that is unauthorized, it will deny access or
even alert the owner of the lock. Basically, an RFID based lock is a better and more secure way to protect
a student’s locker.
1.3.2 To provide a good lock for the school locker

The second objective is to provide a good lock that sturdy and can withstand some force. The problem
with conventional locks is it is easy to break it or lock picking it if one is experienced enough in it. To solve
this problem, a lock that is strong and unable to creatively opened like lock picked will be used. A solenoid
lock is a good lock to use since it is powered by electricity to open and close it rather than do it manually.
The lock uses reliable material that it can withstand some force.
1.3.3 To provide a web-based system and an app that helps the warden access and view
events of the lock.
The third objective is to provide a web-based system and an app that helps the warden or administrator
access and view events of the lock. Having full control of the lock is a must for the wardens or
administrators. To make that happen, the administrators have spare RFID tags to access the locks. By
doing that, a spot-check routine of the student locker will have more effect. Additionally, having spare
RFID tags could help students access their own locker in case they lost their original RFID tag. To avoid
any exploit of the RFID tags, the administrator can disable cards that are not in use remotely. That way,
only one card will be in use to access the lock. Furthermore, the administrator can view events of the lock
that had happened. Every activity of the lock opening, closing, denying access and the time of occurrence
will be recorded and be able to read by the administrator or warden.
1.4 Scope and Target User

Scope refers to the combined objectives and requirements needed to complete a project. The term is often
used in project management as well as in consulting. (Mitchell Grant, 2021). The group of people who the
project activities are intended to reach and who stand to benefit the most from the project's outcomes are
referred to as the "main target audience." These could be demographic subgroups, professional
categories, body or organisation types, business actors, etc. (Life Cyclamen, 2020).
1.4.1 Project Scope

The scope of this project is at a school or a boarding school. More specifically a school that have Wi-Fi
availability throughout the whole school area or at least at the school’s hostel or dormitory to reach some
user requirements for this project. The school also need to have either a locker, wardrobe or a cabinet that
stores personal belongings for the students.
1.4.2 Product Scope

There are several product scopes in this project. The first one is the product can register multiple users for
one lock. Each user will be registered together with own unique RFID tag. The second product scope is
the product have user interface for enabling and disabling RFID tags. Since there are going to be several
users and RFID tags that will be registered for one singular lock, having a user interface for enabling and
disabling RFID tags will be a useful way of having security of the lock. Additionally, the user interface also
will display events of the lock every time it is opened, closed, denied unauthorized access and the timeline
of the events. The most important product scope is the product need Wi-Fi compatibility. This is because
the previous product scopes user internet connection to function properly.
1.4.3 Target User

The target users of this project are mainly be situated in school. The main user of this project is the
students at the school. The wardens of the school that are usually in charge of monitoring student
activities during curfew are also a target user and their role in this project is like an administrator for the
RFID lock system. Teachers can also be a target user and have a role of an administrator like the wardens
if need to.
1.5 Overview of This Report

The Boarding School Locker Lock project addresses the security concerns related to personal belongings
in boarding schools by introducing an innovative solution utilizing Radio Frequency Identification (RFID)
technology. The primary focus is on developing a secure lock system for student lockers, with the potential
for broader applications such as doors, gates, and cabinets within the school environment.
2 Investigation / Literature Review

A literature review is a type of academic writing that, when presented in context, demonstrates the author's
knowledge and comprehension of the academic literature on a particular subject. Because a literature
review also involves a critical assessment of the sources, it is referred to as such rather than a literature
report. It is both a writing process and a method of evaluating the literature. (The University of Edinburgh,
2023).
2.1 Introduction to Radio Frequency Identification (RFID)
Figure 2.1: Radio Frequency Identification
An example of a planned innovation is Radio Frequency Identification (RFID), which uses radio waves to
identify things, retain metadata, and control singular focus on computers or other devices. When an RFID
reader is connected to an Internet terminal, it may identify, monitor, and display the articles that have
labels attached to them inclusively, subsequently, and gradually, as needed. The so-called Internet of
Things (IOT) looks like this. The invention known as radio frequency identification (RFID) uses
electromagnetic wave communication to exchange data between a terminal and an electronic label
attached to an object in order to identify and track the object. (Sapna Yadav, Pratibha Jha, 2019). A
microchip, a powered antenna, and a scanner are used in conjunction with radio frequency identification.
Its commercial applications began in the 1970s, but in recent years, it has grown more widely available.
Information reading and storing technology has advanced, making it more accessible and adaptable. It is
employed in a number of business and industrial settings, such as monitoring the flow of goods via a
supply chain or the inventory of things that are checked out of libraries. (Adam Hayes, 2023).
2.1.1 Radio Frequency Identification (RFID) lock
An RFID door lock is a kind of electronic lock that can be unlocked with RFID-enabled credentials, such as
key fobs or cards. RFID technology is used by many industries. For instance, companies may provide
keycards to every worker so they can enter specific offices or rooms in the building. There are several
options available to you when it comes to RFID door lock installation. You can use metal keys in addition
to RFID credentials for certain RFID door locks that are compatible with current deadbolts. Some RFID
locks only require electronic credentials and completely replace the deadbolt. (Dejan, 2018). Doors
leading to apartments or other common areas such as fitness centres or coworking spaces on a
residential property may have RFID locks installed. Commercial properties can also use RFID systems.
For example, a company might provide keycards to every worker so they can enter specific offices or
rooms in the building. (Ferdison Cayetano, 2014).
2.1.2 Arduino
Figure 2.2: Arduino
The open-source electronics platform Arduino is built on user-friendly hardware and software. Arduino
boards are capable of reading inputs, such as a light from a sensor, a finger pressing a button, or a
tweet, and translating them into outputs, such as starting a motor, turning on an LED, or posting content
to the internet. By sending a set of instructions to the microcontroller on the board, you can instruct your
board on what to do. You use the Arduino Software (IDE), based on Processing, and the Arduino
programming language, which is based on Wiring, to accomplish this. Thousands of different projects
and applications have used Arduino because of its easy-to-use interface. Beginners will find the Arduino
software easy to use, but experienced users will find it sufficiently flexible. It functions on Linux,
Windows, and Mac. It is used by educators and students to construct inexpensive scientific apparatuses,
demonstrate chemistry and physics concepts, and begin learning robotics and programming. At the
Ivrea Interaction Design Institute, Arduino was created as a simple tool for quick prototyping that was
intended for students without any prior experience with electronics or programming. Since its
introduction to a larger audience, the Arduino board has evolved to meet new demands and overcome
obstacles, moving beyond basic 8-bit boards to include products for wearables, 3D printing, embedded
environments, and Internet of Things applications. (Arduino, 2018)
2.1.3 Arduino RFID
Arduino RFID (Radio-Frequency Identification) refers to the integration of RFID technology with Arduino
microcontroller platforms for various applications. RFID is a technology that uses wireless communication
to identify and track objects, people, or animals using RFID tags or cards. When combined with Arduino,
RFID technology becomes a powerful tool for creating interactive and secure electronic systems. Arduino
RFID projects are diverse and can be adapted for various purposes, offering a versatile and accessible
way to incorporate RFID technology into electronic systems. Additionally, the Arduino community provides
ample resources, tutorials, and example codes for those interested in implementing RFID solutions with
Arduino.
2.2 Existing Project

This section discuss about existing projects that are similar to this current project to have an idea of how
the projects should work, the method, functionality and useful features.
2.2.1 RFID Door Lock System
Figure 2.3: RFID Door Lock System
This project is a DIY project that is made by a name of SriTu Hobby based on their website and YouTube
channel. The person made a step-by-step instruction of how to make an RFID door lock using Arduino
with minimal cost. A RFID module is mainly used for the project. The lock itself of the project operates
automatically using a servo motor and a manual door lock. According to SriTu Hobby (2021), When power
ON this door lock, the servo motor activates and pushes the door lock forward. Also displayed as
“Welcome, put your card” on the LCD. Then when the RFID tag is moved closer to the RFID reader, it is
scanned. In that case, it is displayed as “scanning” on the LCD. Then, if the RFID tag is correct, the servo
motor is activated, and the door lock is pulled back. The LCD shows “Door is Open”. When the RFID tag
is moved closer to the RFID reader again, if it gets the correct tag, the servo motor will push the lock
forward. Displays “Door is locked” on LCD. If a wrong RFID tag is used according to the program, it will be
displayed as “Wrong card” on the LCD.
2.2.1.1Board used for the project
Figure 2.4: Arduino Uno
The board used for this project is the Arduino Uno. A microcontroller board called Arduino Uno is built
around the ATmega328P. It features a 16 MHz ceramic resonator (CSTCE16M0V53-R0), 6 analogue
inputs, 14 digital input/output pins (six of which can be used as PWM outputs), a USB port, a power jack,
an ICSP header, and a reset button. It comes with everything required to support the microcontroller; all
you need to do is power it with a battery or an AC-to-DC adapter or connect it to a computer via a USB
cable to get going. (Arduino, 2022).
2.2.2 Smart door lock using RFID & ESP32
Figure 2.5: Smart door lock using RFID & ESP32
This project is made by a person named Sachin and he posts videos about electronic projects on his
YouTube channel called “techiesms” and have a website about his projects for the public to learn. In this
project, Sachin made a smart door lock that uses RFID technology together with a keypad. Additionally,
the project also records attendances of each people accessing the lock by detecting their unique
authorized RFID tag. The time of this project had published was during the Covid-19 where social
distancing and avoiding physical contact was a must. Originally the “techiesms” company uses a
fingerprint type security lock to access their building. But since time has change that time, they decide to
change it to RFID technology which helps minimize physical contact of skin on the door lock system.
Furthermore, this project can read and save the details of the RFID cards, user of the RFID cards and the
time of the lock been accessed and save it into a Google Sheet to make it into an attendance system. The
way the developer make the lock system able to save details of the lock activities is he uses an app called
IFTTT implement the webhook in the project to have a connection between the lock system and the IFTTT
app. This project required Wi-Fi connection to make it function properly.
Figure 2.6: ESP32
The board used in this project is ESP32. The low-cost, low-power ESP32 system on a chip (SoC) series,
developed by Espressif Systems, has dual-mode Bluetooth and Wi-Fi capabilities! The chips ESP32-
D0WDQ6 (and ESP32-D0WD), ESP32-D2WD, ESP32-S0WD, and the system in package (SiP) ESP32-
PICO-D4 are all part of the ESP32 family. Its core is a Tensilica Xtensa LX6 microprocessor, which can
run at up to 240 MHz and be either dual- or single-core. With integrated antenna switches, RF balun,
power amplifier, low noise receiver amplifier, filters, and power management modules, ESP32 is a highly
integrated device. ESP32 is a power-saving technology that is designed for wearable electronics, mobile
devices, and Internet of Things applications. It achieves extremely low power consumption by using
features like dynamic power scaling, multiple power modes, and fine resolution clock gating. (ESP32.net,
2017).
2.2.3 Iot Smart Door Lock System Using NodeMCU ESP8266
Figure 2.7: Iot Smart Door Lock System
In this project, the developer made a door lock system with IoT features that have remote access controls
of the RFID tags and can do live monitoring or view events of the lock based on the user or the RFID tag
that tried to access the lock. The method that the developer used to have the remote access and live
monitoring, or view events is the developer used an app called Blynk. The developer made a user
interface using Blynk that can enable and disable the authorized RFID tags. In the project, the developer
registered three users and three RFID tags for each user in the Blynk app. After registering the users, the
developer demonstrates that the Blynk app can disable and enable every RFID card for the lock and the
disabled RFID tags cannot access the lock until it enabled again. This project required Wi-Fi connection to
make it function properly.
Figure 2.8: NodeMCU ESP8266
According to Random Nerd Tutorials (2015), the ESP8266 is a low-cost Wi-Fi chip developed by Espressif
Systems. It can be used as a standalone device, or as a UART to Wi-Fi adaptor to allow other
microcontrollers to connect to a Wi-Fi network. For example, you can connect an ESP8266 to an Arduino
to add Wi-Fi capabilities to your Arduino board. The most practical application is using it as a standalone
device. With the ESP8266, you can control inputs and outputs as you would do with an Arduino, but with
Wi-Fi capabilities. This means you can bring your projects online, which is great for home automation and
internet of things applications.
2.3 Comparison
Table 2.1: Comparison of Existing Project
RFID Door Lock RFID Based Smart Door RFID IoT Smart RFID Door
System Lock Using ESP32 Lock System Using
NodeMCU ESP8266
Type of board used Arduino Uno Board ESP32 Development Board Node MCU ESP8266
Display Yes (LCD) Yes (OLED Display) No
Keypad No Yes No
Type Of Lock A normal sliding door Solenoid Lock – 12v Solenoid Lock – 12v
lock tied to with a metal
wire to a servo motor
Power Used With a laptop 12V 1A Adapter plug to a 3.7V 18650 Battery
electrical outlet
Live No Yes Yes

Monitoring/Record
Events
Can grant and disable No No Yes
an RFID tag remotely
Need to use Wifi No Can Can

connection to
operate?
Additional features or No This project uses IFTTT to  This project uses Blynk to
software record and monitor activities of implement a remote
the lock and save it to a google access and disable and
sheet. enabling card for one lock.
 Additionally it provides a
user interface for an Admin
to configure the
necessities of the Blynk
web app and application.
 Also, can view events of
the lock.
2.4 Discussion
The criteria comparison of RFID Door Lock System, Smart Door Lock Using ESP32 and RFID IoT Smart
RFID Door Lock System Using NodeMCU ESP8266 is shown in Table 2.1. The purpose of this discussion
is to determine existing project function is most appropriate and suitable for implementation in this project.
The RFID IoT Smart RFID Door Lock System Using NodeMCU ESP8266 is an existing project that is a
good fit for the current project. The first reason is the RFID IoT Smart RFID Door Lock System Using
NodeMCU ESP8266 is the cheapest and give enough features and requirements to make suitable for a
school. Although the ESP32 board as indicated in Table 2.1 is better, powerful and have more features
than the ESP8266, it is already good enough and a cheaper option to use and since this project doesn’t
require complicated procedures or step to develop and launch it. A display won’t be necessarily a feature
since it only for display and based on this project, the lock system only will have one primary user thus this
project won’t use any display and it can also be a target to vandalise at school by a bad actor. Another
feature that is not included for this project is a keypad. This is because a keypad can be exploited in the
environment of a school especially when this project is for a student’s locker. A keypad can be physically
seen by many people even when trying to hide their password input. When that happens, bad actors can
try to open or access the lock easily thus making the lock system does not secure anymore and failing to
reach a user requirement and objectives of this project. As for the lock that will be in use, a Solenoid Lock
is a good lock for this project as shown at Table2.1. Solenoids are basically electromagnets: they are
made of a big coil of copper wire with an armature (a slug of metal) in the middle. When the coil is
energized, the slug is pulled into the centre of the coil. This makes the solenoid able to pull from one
end. This solenoid in particular is nice and strong and has a slug with a slanted cut and a good mounting
bracket. It's basically an electronic lock, designed for a basic cabinet or safe or door (Synacorp, n.d). Four
3.7V 18650 Battery will be used for powering the lock system which is enough to make sure the system
keeps running for a decent amount of time. Like the RFID IoT Smart RFID Door Lock System Using
NodeMCU ESP8266 project, the Blynk app will be in use because of the feature that the app can make an
user interface, register users, edit users and able to view events of the lock activities as shown on Table
2.1.
2.5 Conclusion
This chapter describes how each defined project's relevant systems and security elements are examined.
It also contains a comparison of the criteria used in three current projects. It may be possible to improve
the functionality of the related current project linked to the upcoming development by making reference to
these three projects. The goal of this project is to improve community management and give users a safe
environment.
3 Methodology
Methodology is a body of methods, rules, and postulates employed by a discipline and as well as a
particular procedure or set of procedures. Methodology is basically a system of ways of doing, teaching, or
studying something.
3.1 Introduction
A methodology is an assemblage of procedures, rules, practises, processes, and techniques. Project
management methodologies are defined and rigorous, typically comprising a sequence of actions and
tasks for every stage of the project's life cycle. They have established methods that clearly outline the next
actions to take, the reasoning behind each action, and the proper way to complete each project stage.
(Alexandra Cote, 2023). Bowling (2002) explains that methodology is the complete structure of the
research study; the size and sample methods, the practices and techniques utilized to collect data and the
process to analyse data.
3.2 Agile Methodology
Figure 3.1: Agile Methodology Diagram
The agile methodology is a framework for project management that divides work into multiple, flexible
stages, or sprints. Iterative methodology is what the Agile framework uses. Teams review and analyse
their performance at the end of each sprint to identify areas for improvement and modify their plan for the
following sprint. The development of applications and other software often makes use of agile project
management. This is due to the fact that software is always evolving, and product requirements must
adapt accordingly. This makes linear project management techniques, such as the waterfall model, less
successful. (Sarah Laoyan, 2022).
3.3 Phases in Agile Methodology
Within this project, the agile methodology process comprises six phases: plan, design, development,
testing, deploy and review. The following provides a detailed discussion of each phase within the context
of the current project.
3.3.1 Planning Phase

The agile software development lifecycle begins with planning. In this stage, the stakeholders and project
team collaborate to establish the project's requirements, prioritise its features, and define its scope.
Because it lays the groundwork for the entire project and guarantees that everyone is on the same page
and working towards the same objectives, planning is essential. (Ficus Technologies, 2023).
During the planning phase, the Boarding School Locker lock will be planned out based on the
requirements of this current project. Several of the plans are to analyse the user and system requirements
for this project, do research on existing systems that are similar to this project and distribute a
questionnaire to the public not specific to certain groups to gain data for the project’s requirements. The
target user, system requirements and the problem statements as well as objectives of the current project
will be identified after all the information from the research and questionnaire has gathered.
3.3.2 Design Phase

The project's architecture, user interface, and database design are created during the design phase. Since
it lays the groundwork for the development phase, the design phase is essential to the project's success.
In this stage, the group has to make sure that the design satisfies the project specifications, can be scaled
up or down, and can be implemented on schedule. (Ficus Technologies, 2023).
For the design phase, by using Use Case and Flow Chart diagram the flow of the system and the process
of this project can be seen clearly. Other than that, the circuit diagram will be design as well to have a
clear view of how the Boarding School Locker Lock device will look like. The design of the shell of the
device will also be designed to protect the circuits and important hardware from damage or natural wear.
Furthermore, the user interface of this project will also be designed with Blynk app that consists of two
tabs, Access Control tab which have buttons that disable and enables each RFID tags for one lock. The
second tab is for View Events tabs which the user can view the events of the lock activities.
3.3.3 Development Phase

The building is the second step of a traditional Agile process model. In the building or design process, the
Agile development team creates input functions & prepares the system for start testing. (Bitbytesoft, 2022).
For the development phase, the hardware that required to make this project will be bought first. After
achieving all of the hardware requirements, The Boarding School Locker Lock will begin by physically
install and connect all of the wires to reach functionality of the project and power it on. After everything has
been install perfectly, the Boarding School Locker Lock device will be plug to a laptop or a computer. The
programming and coding will be done with the laptop using Arduino IDE software. All of the functionality
and behaviour of the device will depend on how the coding is done. The RFID tags will also have to be
defined in the coding authorize the RFID tags to access the lock. Connection between the device and the
Blynk app will also be defined and code in using Arduino IDE. After all of the coding and programming has
finished, the codes have to upload to the board used in this project.
3.3.4 Testing Phase

The project team tests the software during the testing phase to make sure it is error-free and satisfies the
acceptance criteria. Unit, integration, and system testing are all part of the testing phase. Together, the
team must find solutions for any bugs and problems found during testing. (Ficus Technologies, 2023).
In testing phase, the Boarding School Locker Lock functions will undergo multiple tests to check and
identify if there are any possible error of the lock function and behaviour. The first step is to make sure that
the RFID tags is detected and can open and closes the lock. After that will be registering and editing
user’s name if the Blynk app and make sure that the app follows the changes then try to access the lock
again. After the behaviour of the lock is flawless, enabling and disabling the RFID tags is tested. Several
RFID tags will be enabled and disabled. If the RFID tag is enabled, the RFID tag can access the lock and
if it is disabled then the lock denied access of the RFID tag. Lastly, the last test is to monitor the View
Events tab and make sure every activity of the lock will be displayed through the View Events tab in the
Blynk app. At the same time of all the testing, the battery will also be monitored to make sure that the
battery can power the device throughout the whole testing phase.
3.3.5 Deployment Phase

The Agile delivery is the fourth step of the software development workflow. After performing a series of
testing, user training, enhancing system functionalities developers team release the software. (Bitbytesoft,
2022).
For the deployment phase, the Boarding School Locker will be deployed for user to test it. For that to
happen firstly, the lock device needs to be screwed on to a locker, cabinet or even a wardrobe to reach
the project scope and suits certain requirements.
3.3.6 Review Phase

The last phase in the agile development process is review. In this step, client and user feedback is
gathered to determine the results and whether the software is functional and works. In summary, this is
the phase of application retirement, which involves ongoing software review and upgrades. (Bitbytesoft,
2022).
After the Boarding School Locker Lock has been deployed to the target user and had been used as
instructed by the developer, the developer will visit the intended project environment and gather feedback
and reviews. The Administrator will oversee monitor the Boarding School Locker Lock device at the project
environment and gather reviews and feedback from other users if any unintended occurrence or difficulties
of the device happened during the deployment phase. Any changes or update to the device either
physically or virtually will be based on the reviews and feedback from users.
3.4 Conclusion
Agile methodology was selected for this project because of its openness, ability to integrate feedback, and
emphasis on quality control. Agile improves project control and flexibility by allowing for constant feedback
and working in short bursts, which allows it to adjust to last-minute changes. Small sprints of the Agile
methodology, in contrast to other approaches, minimise the time and expense of revisions. Agile
methodology is preferred by dynamic organisations due to its unparalleled flexibility and reduced risk in
project development. Agile also guarantees continuous user participation in decision-making, which
increases user retention. In contrast to traditional methods, which restrict user influence during the
planning phase and thereby reduce overall flexibility, this user-centric approach stands out. Agile makes
sure the finished product meets user expectations by maintaining user engagement and making
adjustments in response to their feedback.
4 Requirements
A requirement is a state or a capability that a solution or component of a solution must have in order to
satisfy a formal document such as a contract, standard, specification, or other formal document. In order
to begin the process of developing the solution, business requirements are first drafted as requirements.
(Surbhi Manhot, 2017)
4.1 Introduction
The set of precise, quantifiable, and testable qualities that a software system needs to have in order to
satisfy the needs of its users is referred to as software development requirements. A requirement is a
condition or capability that a user needs to solve a problem or accomplish an objective, a requirement that
a system or system component must meet or possess to satisfy a contract, standard, specification, or
other formally imposed document, and a documented representation of a condition or capability as in 1 or
2. These definitions are provided by the IEEE Standard Glossary of Software Engineering Terminology.
(Rikkei, 2023)
4.2 Data Gathering Technique

Getting information requires a time-consuming process called data collection. To obtain real-time insights
into a specific problem or workflow process, a data gathering approach is used. By collecting and
analysing data, the study enables developers to make better decisions, which improves the system's
overall performance.
4.2.1 Questionnaire
A questionnaire is a research instrument that consists of a set of questions or other types of prompts that
aims to collect information from a respondent. A research questionnaire is typically a mix of close-ended
questions and open-ended questions. (Adi Bhat, n.d)
For this project, the first method of collecting data from individuals or groups that are not specifically
mentioned will be a questionnaire. For this project, a questionnaire form will be created using Google
Form, a Google feature. Without the need to distribute printed forms, Google Form can be used to create
a digital questionnaire that can be shared with the general public. This is going to be very helpful as it will
cut down on the time and expense of this project. There are 13 questions total across the two sections of
the questionnaire. Respondents who have attended boarding schools are asked to fill out Section A, and
those who have never attended boarding school are asked to fill out Section B. The goal is to have 50
respondents complete the questionnaire. Ensuring that user requirements for the upcoming system are
met is the goal. Responses from the respondent will be automatically saved in a Google Form associated
with their Google account, allowing for analysis of the responses.
4.2.2 Existing System Project

The project's second method of gathering data is the Existing System Project. Three previous projects that
are comparable to the one being examined will be examined. Examining the advantages of current
projects by figuring out how they work and offering assistance in developing a better version or in a more
advantageous setting based on the current project, then applying that to the current project. The purpose
of the inspections is to see how the system operates, what procedures are followed, and how the current
project functions.
4.3 Functional Requirement

Functional requirements outline the functions that a software system and its parts must perform. These
specifications outline the features that the software must have in addition to the inputs and anticipated
results for each function. Calculations, data processing, data manipulation, and other specialised
functionalities that specify what the software should be able to do are examples of functional requirements.
(Rikkei, 2023).
Table 4.1: Functional Requirement

Functions Result
User Authentication The RFID card authenticate user based on RFID card information to permit access.
RFID Card Compatibility The system supports a specified range of RFID cards or fobs for user identification.
Access Control The lock should have the ability to control access to the locker, cabinet, or wardrobe.
Battery Monitoring The project has a feature to monitor battery levels by using Blynk app.
Tamper Detection The system can detect and log attempts to tamper or manipulate the lock using the Blynk
app.
Remote Management The system has a capability for remote management of the RFID lock system. An Admin
can update information of the RFID tags using the Blynk app. The Admin also can
deactivate user accounts and RFID cards.
User-friendly Interface The system has a user-friendly interface for the Admin to use all of the system features.
Auto-locking The system can automatically relock after 5 seconds to enhance security.
Mechanism
4.4 Non-Function Requirement

Non-functional requirements specify the desired level of performance for the software system, as opposed
to its precise actions. These specifications outline the software system's quality attributes, including
dependability, performance, security, and usability. Non-functional requirements specify the qualities of
the software, just as functional requirements specify its functions. Non-functional requirements determine
a system's general characteristics rather than particular use cases, which makes the difference between
development success and failure. (Rikkei, 2023).
Table 4.2: Non-Functional Requirement

Functions Result
Performance  The system has a response time within acceptable range to ensure swift access of the lock.
 The RFID scanner is efficient and not cause delays. The RFID scanner can detect the RFID
cards with 1 second.
Reliability  The RFID lock can be used for a long period of time more than a month.
Usability  The system has a user-friendly interface that there’s no need for extensive use training.
Cost  The RFID lock is within a reasonable cost. The hardware and software used is cheap and
affordable. The cost for installation, maintenance and operational costs are also really
cheap. Batteries of the lock are the only things that need to change and buy every now and
then.
4.5 Software Requirement

The software requirements are description of features and functionalities of the target system.
Requirements convey the expectations of users from the software product. The requirements can be
obvious or hidden, known, or unknown, expected, or unexpected from client’s point of view.
4.5.1 GitHub
Figure 4.1: GitHub
GitHub is a platform for online software development. It is employed for software project collaboration,
tracking, and archiving. It facilitates the sharing of code files and facilitates developer collaboration on
open-source projects. In addition, developers can freely network, collaborate, and pitch their work on
GitHub, which doubles as a social networking platform. Users of GitHub can create coding projects,
upload files, and create accounts. (Jamie Juviler, 2022).
4.5.2 Arduino IDE
Figure 4.2: Arduino IDE
Writing and uploading code to the Arduino boards is done via the open-source Arduino IDE software. The
IDE programme works with a variety of operating systems, including Linux, Mac OS X, and Windows. The
programming languages C and C++ are supported by it. IDE refers to the Integrated Development
Environment in this context. (javaTpoint, n.d).
4.5.3 Blynk
Figure 4.3: Blynk
Using Blynk, an Internet of Things platform for iOS and Android smartphones, users can control Arduino,
Raspberry Pi, and NodeMCU remotely. With the help of this application, a graphical user interface (HMI)
can be created by gathering and supplying the correct address on the available widgets. The Internet of
Things was the target market for Blynk. It has many cool features, including remote hardware control,
sensor data display, data storage, data visualisation, and much more. (Syufrijal, n.d).
4.6 Hardware Requirement
Asus (Laptop)
AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 2.00 GHz (GPU &CPU)
12.0 GB (11.0 GB usable) (total laptop storage)
Windows 10 Home (Laptop Operating System)
NodeMCU ESP8266
RFID MFRC-522 Module
12V Solenoid Door Lock
Green LED
Few jumper wires
3.7V 18650 Battery
3.7V 18650 Battery holder
LM2596 Buck Converter
Buzzer
4.7 Conclusion
Project failures are typically primarily caused by problems with requirement collection and management. A
poorly defined requirement set can result in scope creep, budget overruns, delays in projects, and a
system that is of poor quality and does not meet user and safety requirements. In order to guarantee that
the objectives of product development are fulfilled, requirements management is vital. By keeping an eye
on requirements changes, requirements management provides a way to stop mistakes.
5 Analysis
Analysis is a detailed examination of anything complex in order to understand it’s nature or to determine
its essential features.
5.1 Introduction
Data Analysis is the process of systematically applying statistical and/or logical techniques to describe and
illustrate, condense and recap, and evaluate data. According to Shamoo and Resnik (2003) various
analytic procedures “provide a way of drawing inductive inferences from data and distinguishing the signal
(the phenomenon of interest) from the noise (statistical fluctuations) present in the data”.
5.2 Data Gathering Analysis

I. Question 1
Figure 5.1: Question 1 Response

II. Question 2
III. Question 3
IV. Question 4
V. Question 5
VI. Question 6
VII. Question 7
VIII. Question 8
IX. Question 9
X. Question 10
XI. Question 11
XII. Question 12
XIII. Question 13
5.3 Use Case Model

A use case is a concept that describes how a system can be used to accomplish particular tasks or goals.
It is used in software development, product design, and related fields. It describes how users or actors
interact with the system to accomplish a particular goal. (Nicky Daly, 2022).
5.3.1 Administrator Use Case Diagram
Figure 5.14: Administrator Use Case Diagram
The use case diagram in figure 5.14 represents the administrator that is involved in the system and how it
interacts with the system. In figure 5.14, the administrator can sign up and log in using the Blynk app to
start of the system. After the administrator successfully sign up and log in their Blynk account, the
administrator can start registering students with their RFID cards. The administrator also can monitor the
lock by viewing events of the lock activities in the Blynk app. Administrators have control of access cards
that is authenticated with the lock. The administrator can deactivate and activate RFID cards remotely by
connecting the Blynk app with the lock. Of course, the administrator can access the lock with their own
RFID card. Lastly, the administrator provides spare RFID tags in case of the original RFID is unable to use
or lost.
5.3.2 Student Use Case Diagram
Figure 5.15: Student Use Case Diagram
The use case diagram in figure 5.15 represents the students that is involved in the system and how it
interacts with the system. Firstly, the student can register into the Blynk app by letting the administrator do
it for them. As the main user of the system, the students can access the lock and the student only have
one access card at a time to access the lock system.
5.4 Flowchart
A flowchart is a graphic representation of a process or workflow that shows the decisions, steps, and
sequences. The most basic type of process map is a basic flowchart, though there are many varieties
available. It's an effective tool that can be used for process planning, visualisation, documentation, and
improvement in a variety of fields. (Team Asana, 2023)
Figure 5.16: Flowchart
5.5 BPMN (Business Process Modelling Notation)
A flowchart is a diagram that illustrates the choices, actions, and sequences in a process or workflow. A
simple flowchart is the most fundamental kind of process map, though there are numerous variations. It's a
useful tool that can be applied to many different fields for process planning, improvement, documentation,
and visualisation.
Figure 5.17: BPMN
5.6 Conclusion
This chapter presents and uses pie charts to illustrate the findings from the data gathered through the
questionnaire. Next, for better understanding, this chapter also uses a BPNM diagram, a flow chart, and a
use case to illustrate a thorough system flow. The gathered information will serve as a guide during the
development stages. This guarantees that the project satisfies user expectations and is in line with user
requirements.
6 Design
[ Here you should describe the system architecture and include some appropriate design diagram(s).
Detailed design specifications belong to the appendices (on the CD), but you could explain here any novel
or interesting features of your design. You could also have a subsection on the user interface design,
highlighting any HCI issues covered in the design (but not simply regurgitating HCI theory).]
7 Implementation
[ Describe here the implementation and any associated issues, eg platform, languages and tools used, etc.
Did you start by building and evaluating an early prototype? Did you apply an “iterative” approach? What
is the current status of the system at the time of submission? Have you already deployed the system, or
have devised a deployment strategy?]
8 Testing
[ Never mind the theory of black-box and white-box testing, what we really want to know is why you chose
a particular strategy, what areas you decided to test and how, what your test plan looks like and how well
it worked out. Did you involve the client and/or end-users?]
9 Project Management
[ The subsections shown below are only one possible structure for this section covering the conduct of the
project. ]
9.1 Project Schedule
[ This could include the work breakdown structure, Gantt chart, and comments about how well you
managed to keep to the original plan, or what adjustments were necessary. ]
9.2 Risk Management
[ Risk identification, analysis and mitigation plan. Did any risk actually materialise? ]
9.3 Quality Management
[ Standards adopted, techniques used to review progress and evaluate outcomes, etc. ]
10 Conclusions
[ Optional introduction]
10.1 Achievements
[ Comment on what you have achieved in terms of product or other results, with reference to the original
project objectives.]
10.2 Future Work
[ Outline possible enhancements or extensions to the product, or further work needed to address
outstanding issues, etc.]
10.3 Project Evaluation
[ A reflective and critical appraisal of your performance, problems encountered and how they were
resolved, lessons learnt, what could have been done better or differently, etc. If you have a lot to say you
could make this into a separate top-level section.]
Appendix A – Requirements Specification Document
[ You may include here the agreed list of requirements signed off by the client. Remember that any
appendices included with the main report count towards the 12,000 word limit, but ancillary materials on
the CD are outside this limit. If the requirements document is too big, put it separately on the CD rather
than as an appendix to the report. ]
You can include questionnaire and Turnitin result here.
Appendix B – User Manual
[ Include this if it’s fairly short and you feel it helps the reader understand the product without having to
look for this information on the CD. ]
References
Admin (2022). IoT Smart RFID Door Lock System Using NodeMCU ESP8266. [online] IoT Projects Ideas.
Available at: https://iotprojectsideas.com/iot-smart-rfid-door-lock-system-using-nodemcu-esp8266/.
Aimsler, S. and Shea, S. (n.d.). What is RFID and how does it work? [online] IoT Agenda. Available at:
https://www.techtarget.com/iotagenda/definition/RFID-radio-frequency-
identification#:~:text=RFID%20(radio%20frequency%20identification)%20is.
Aisyah, S., Ali, Y., Saharja, K., Suhendra, S. and Sani, A. (2022). SMART DOOR LOCK SYSTEM
DEVELOPMENT PROTOTYPE USING RFID TECHNOLOGY ID-12. Jurnal Riset Informatika, 4(4),
pp.379–384. doi:https://doi.org/10.34288/jri.v4i4.433.
ARDUINO (2021). Arduino Uno Rev3. [online] Arduino Official Store. Available at:
https://store.arduino.cc/products/arduino-uno-rev3.
Arduino (2018). Arduino - Introduction. [online] Arduino.cc. Available at:

https://www.arduino.cc/en/guide/introduction.
Arduino Official Store. (n.d.). NodeMCU ESP8266. [online] Available at:

https://store.arduino.cc/products/nodemcu-esp8266 [Accessed 27 Nov. 2023].
Bhat, A. (2018). Questionnaire: Definition, Examples, Design and Types | QuestionPro. [online]
QuestionPro. Available at: https://www.questionpro.com/blog/what-is-a-questionnaire/.
Birt, J. (2023). What Is a Problem Statement: Definition and Example. [online] Indeed Career Guide.
Available at: https://www.indeed.com/career-advice/career-development/what-is-a-problem-statement.
Bitbytesoft (2022). The Phases Of Agile Software Development Life Cycle & Workflow And Project
Management. [online] Bitbytesoft. Available at: https://bitbytesoft.com/phases-of-agile-software-
development-life-cycle/#:~:text=After%20performing%20a%20series%20of [Accessed 27 Nov. 2023].
Cayetano, F. (2022). RFID Door Lock: The 3 Best Locks & How They Work. [online] Video Intercom
System for Apartment Buildings | ButterflyMX. Available at: https://butterflymx.com/blog/rfid-door-lock/.
Cote, A. (2019). Project Management Methods, Methodologies, and Frameworks. [online] Paymo.
Available at: https://www.paymoapp.com/blog/project-management-methodologies/.
Daly, N. (2022). What Is a Use Case & How To Write One | Wrike. [online] www.wrike.com. Available at:
https://www.wrike.com/blog/what-is-a-use-case/.
Dejan (2017). How RFID Works and How To Make an Arduino based RFID Door Lock. [online]
HowToMechatronics. Available at: https://howtomechatronics.com/tutorials/arduino/rfid-works-make-
arduino-based-rfid-door-lock/.
Elsevier (2022). What is a Problem Statement? With Examples | Author Services Blog. [online] Elsevier
Author Services - Articles. Available at: https://scientific-publishing.webshop.elsevier.com/research-
process/what-problem-statement-examples/#:~:text=A%20problem%20statement%20is%20an.
Ficus Technologies (2023). Agile Software Development Lifecycle Phases. [online] www.linkedin.com.
Available at: https://www.linkedin.com/pulse/agile-software-development-lifecycle-phases-ficus-
technologies.
Grant, M. (2019). Scope. [online] Investopedia. Available at:

https://www.investopedia.com/terms/s/scope.asp.
Hayes, A. (2020). Radio Frequency Identification (RFID). [online] Investopedia. Available at:
https://www.investopedia.com/terms/r/radio-frequency-identification-
rfid.asp#:~:text=Radio%20Frequency%20Identification%20(RFID)%20is.
Hobby, S. (2021a). How to make a RFID door lock with Arduino | Step by step instructions. [online] SriTu
Hobby. Available at: https://srituhobby.com/how-to-make-a-rfid-door-lock-with-arduino/.
Hobby, S. (2021b). RFID door lock access control system | How to make an RFID door lock system using
Arduino. [online] www.youtube.com. Available at: https://www.youtube.com/watch?v=GOO84CGBPz8.
Hobby, S. (2023). How to make an RFID door lock system using an Arduino Nano board #sritu_hobby
#arduinoproject. [online] www.youtube.com. Available at:
https://www.youtube.com/watch?v=JQAskBAoUQs [Accessed 27 Nov. 2023].
Iot Project Ideas (2022). IoT Smart RFID Door Lock System Using NodeMCU ESP8266. [online]
www.youtube.com. Available at: https://www.youtube.com/watch?v=qh5cWS76N78 [Accessed 27 Nov.
2023].
Juviler, J. (2022). What Is GitHub? (And What Is It Used For?). [online] blog.hubspot.com. Available at:
https://blog.hubspot.com/website/what-is-github-used-for#what-github.
Kim Seong Chan and Ryu Keun Kwan (2014). Electronic rfid locker to improve the conveniennce of
storage. typeset.io. [online] Available at: https://typeset.io/papers/electronic-rfid-locker-to-improve-the-
conveniennce-of-4yqiao8nms [Accessed 27 Nov. 2023].
Laoyan, S. (2022). What Is Agile Methodology? (A Beginner’s Guide). [online] Asana. Available at:
https://asana.com/resources/agile-methodology.
Last Minute Engineers (2018). What is RFID? How It Works? Interface RC522 RFID Module with Arduino.
[online] Last Minute Engineers. Available at: https://lastminuteengineers.com/how-rfid-works-rc522-
arduino-tutorial/.
Lifecyclamen. (2020). How to write a LIFE Proposal: Stakeholders and Target Audience. [online] Available
at: https://lifecyclamen.com.cy/en/how-to-write-a-life-proposal-stakeholders-and-target-
audience/#:~:text=The%20term%20%E2%80%9CMain%20target%20audience.
Lucidchart (2019). What Is a Flowchart. [online] Lucidchart.com. Available at:

https://www.lucidchart.com/pages/what-is-a-flowchart-tutorial.
Make-It.ca. (n.d.). NodeMCU ESP8266 Specifications, Overview and Setting Up. [online] Available at:
https://www.make-it.ca/nodemcu-details-specifications/.
Media’s, E., Syufrijal and Rif’an, M. (2019). Internet of Things (IoT): BLYNK Framework for Smart Home.
KnE Social Sciences, 3(12), p.579. doi:https://doi.org/10.18502/kss.v3i12.4128.
Nguyen, T. (2023). Complete Guide to Software Development Requirements. [online] Trusted IT

Outsourcing Provider. Available at: https://rikkeisoft.com/blog/software-development-requirements/.
Nursing Essay (2020). The Definition Of Methodology. [online] NursingAnswers.net. Available at:
https://nursinganswers.net/essays/the-definition-of-methodology-nursing-essay.php.
ori.hhs.gov. (n.d.). Data Analysis. [online] Available at:

https://ori.hhs.gov/education/products/n_illinois_u/datamanagement/datopic.html#:~:text=Data%20Analysi
s%20is%20the%20process.
Synacorp Technologies Sdn. Bhd. (1310487-K). (n.d.). 12VDC Solenoid Door Lock. [online] Available at:
http://synacorp.my/v3/en/appliances/497-12vdc-solenoid-door-lock.html.
techiesms (2020a). IoT Door Lock using RFID with Online Attendance | IoT Projects | ESP32 projects.
[online] www.youtube.com. Available at: https://www.youtube.com/watch?v=RVa0zpzpeR8&list=PLZ-
IJSW0hGRyLyEh855mv7R7lmVZEC9Bo&index=3 [Accessed 27 Nov. 2023].
techiesms (2020b). Smart door Lock using RFID & ESP32 - techiesms. [online] techiesms. Available at:
https://techiesms.com/smart-door-lock-using-rfid-esp32/ [Accessed 27 Nov. 2023].
The University of Edinburgh (2023). Literature review. [online] The University of Edinburgh. Available at:
https://www.ed.ac.uk/institute-academic-development/study-hub/learning-resources/literature-
review#:~:text=A%20literature%20review%20is%20a.
www.javatpoint.com. (n.d.). Arduino IDE - JavaTpoint. [online] Available at:

https://www.javatpoint.com/arduino-ide.
UPTM – FINAL YEAR PROJECT – FORMAT (SUMMARY)
COVER PAGE FORMAT
Most-front Cover Top Margin 4 cm

(hard binding) Bottom Margin 4 cm
Left Margin 3.2 cm
Right Margin 3.2 cm
UNIVERSITI POLY-TECH MALAYSIA ARIAL BOLD 20
First Line on page
Project Title ARIAL BOLD 20
Centre of Page
Student’s Full Name ARIAL BOLD 20
Last Line on page
Inside Cover (2
nd
Top Margin 4 cm
Page) Bottom Margin 4 cm
Left Margin 3.2 cm
Right Margin 3.2 cm
UNIVERSITI POLY-TECH MALAYSIA ARIAL BOLD 18
First Line on page
Faculty of Computing & Multimedia ARIAL BOLD 15
Second Line on
page
Spacing ARIAL BOLD 18
Single
Project Title ARIAL BOLD 16
Centre of Page
Student’s Full Name ARIAL BOLD 16
College ID Number
Spacing ARIAL BOLD 16
Single
FYP4013/FYP4033/FYP4074/IMF402
MONTH AND YEAR COMPLETED ARIAL BOLD 16
[Choose your course code] Last two lines
Content Top Margin 1”

Bottom Margin 1.2”
Left Margin (this margin is wide, for binding 1.52”
requirements)
Right Margin 1.2”
Font/Size (Heading) Arial/16-point/Bold
Font/Size (Sub heading) Arial/14-point/Bold
Font/Size (Content) Arial/11-point
Spacing 1.5
Alignment Justify
Text in Table/ Figure and Table labels Arial 10-point
Side Cover Student Id 11 point
YEAR COMPLETED

Fyp4033 Fyp1

Uploaded by

Copyright:

Available Formats

You might also like

Fyp4033 Fyp1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fyp4033 Fyp1

Uploaded by

Copyright:

Available Formats

UNIVERSITI POLY-TECH MALAYSIA

BOARDING SCHOOL LOCKER LOCK

MUHAMMAD ZAFRAN BIN MOHD ZUHAIRI

UNIVERSITY POLY-TECH MALAYSIA

BOARDING SCHOOL LOCKER LOCK

MUHAMMAD ZAFRAN BIN MOHD ZUHAIRI

Figure 2.1 Radio Frequency Identification ………………………………… ……………….. 16

Figure 3.1: Agile Methodology Diagram ………………………………… ……………………. 25

Figure 4.1: GitHub………………………………… ……………………………………………….. 32

Figure 5.1: Question 1 Response ………………………………… …………………………….. 34

Table 2.1 Comparison of Existing Projects ………………………………………… 24

Table 4.1 Functional Requirements ………………………………………………….. 31

1.1 Project Background

1.2 Problem Statements

1.2.1 The amount of stealing in boarding school is not decreasing.

1.2.3 The wardens lack control and access of student’s lockers.

1.3 Project Objectives

1.3.1 To develop a Radio Frequency Identification Based Lock

1.3.2 To provide a good lock for the school locker

1.4 Scope and Target User

1.4.1 Project Scope

1.4.2 Product Scope

1.4.3 Target User

1.5 Overview of This Report

2 Investigation / Literature Review

2.1 Introduction to Radio Frequency Identification (RFID)

Figure 2.1: Radio Frequency Identification

Figure 2.2: Arduino

2.2 Existing Project

2.2.1 RFID Door Lock System

Figure 2.3: RFID Door Lock System

Figure 2.4: Arduino Uno

Figure 2.5: Smart door lock using RFID & ESP32

Figure 2.6: ESP32

Figure 2.7: Iot Smart Door Lock System

2.2.3.1Board used for the project

Figure 2.8: NodeMCU ESP8266

Display Yes (LCD) Yes (OLED Display) No

Live No Yes Yes

Need to use Wifi No Can Can

3.2 Agile Methodology

Figure 3.1: Agile Methodology Diagram

3.3.1 Planning Phase

3.3.2 Design Phase

3.3.3 Development Phase

3.3.4 Testing Phase

3.3.5 Deployment Phase

3.3.6 Review Phase

4.2 Data Gathering Technique

4.2.2 Existing System Project

4.3 Functional Requirement

Table 4.1: Functional Requirement

4.4 Non-Function Requirement

Table 4.2: Non-Functional Requirement

4.5 Software Requirement

Figure 4.1: GitHub

4.5.2 Arduino IDE

Figure 4.2: Arduino IDE