Jordan University of Science and Technology

College of Computer Sciences & Information Technology

Smart Agri-
Guard

A project submitted
in partial fulfillment of the requirements for the degree of
Bachelor' in Software
Engineering

by
Mutasem Mustafa Al-Gharibeh (162289)
Batool Saber Abu Zaid (157902)
Osama Rad Al-Omari (161413)
Danial Ziad Yaseen (162683)
Naser Hani Mousa (164849)

Supervised by
Malik G. Qasaimeh

Committee Member Names

Committee Member’s First Name Middle Initial Last Name
Committee Member’s First Name Middle Initial Last Name
Month Year
Undertaking

This is to declare that the project entitled “Project Title” is an original work
done by undersigned, in partial fulfillment of the requirements for the degree “Bachelor
in Software Engineering” at Software Engineering Department, College of Computer
and Information Technology, Jordan University of Science and Technology.

All the analysis, design and system development have been accomplished by the
undersigned. Moreover, this project has not been submitted to any other college or
university.

Osama Rad Al-Omari

Naser Hani Mousa

Batool Saber Abu Zaid

Danial Ziad Yaseen

Mutasem Mustafa Al-Gharibeh

Note: sign across your name

3
ABSTRACT
This project presents a smart agriculture system designed specifically for

nursery management, aiming to monitor and improve plant health using

sensor technology and artificial intelligence (AI). The system collects real-

time environmental and soil data through ESP32-connected sensors and

analyzes it using an AI model to predict plant conditions and recommend

actions such as irrigation or fertilization. A mobile application built with

Flutter allows farmers and nursery managers to monitor plants, receive

alerts, and view historical trends. The backend, developed in [Link]

Core, provides secure data handling, AI integration, and role-based access

control. This solution is motivated by the need for efficient, localized

monitoring in greenhouses, especially where resources and expertise are

limited. The administrator of the system is the developer team, responsible

for managing users, plants, and greenhouses. The primary users are farmers

and managers within agricultural nurseries. The project demonstrates how

affordable, intelligent systems can enhance crop care and sustainability in

controlled environments.

4
Acknowledgment

We would like to express our deepest gratitude to everyone who

supported us throughout the development of this project.

First and foremost, we extend our sincere thanks to our supervisor,

Dr. Malik Qasaimeh, for his valuable guidance, continuous

encouragement, and insightful feedback throughout every stage of

this project.

We are also grateful to our instructors and the department staff for

providing us with the technical foundation and tools needed to

complete this work.

Special thanks go to our families and friends for their endless

support, patience, and motivation, which helped us stay focused

and committed.

Lastly, we would like to acknowledge our teammates for their

collaboration, dedication, and collective efforts that made this

project possible.

5
 CONTENT
Undertaking.....................................................................................................................2
ABSTRACT....................................................................................................................3
Acknowledgment.............................................................................................................4
CHAPTER 1: Project Overview, Vision, and Planning..................................................2
1.1 Problem Statement.................................................................................................2
1.2 Related Products....................................................................................................2
1.3 Product Vision.......................................................................................................2
1.4 Project Objectives and Milestones.........................................................................2
1.5 Risk Assessment and Mitigation...........................................................................3
CHAPTER 3: Product Features and Requirements.........................................................4
3.1 Functional Features................................................................................................4
3.2 Feature-to-Requirement Mapping.........................................................................5
CHAPTER 4: System Design and Deployment Overview..............................................6
4.1 System Architecture...............................................................................................6
4.2 Detailed Design (UML Models Based on Implementation)..................................6
4.3 Software Deployment............................................................................................6
CHAPTER 5: System Development and Implementation...............................................7
5.1 Core Implementation Progress..............................................................................7
5.2 Implemented and Planned Features.......................................................................7
5.3 Screenshots Evidence............................................................................................7
CHAPTER 6: Testing......................................................................................................8
6.1 Testing Overview...................................................................................................8
6.2 Sample Test Cases.................................................................................................8
6.3 Test reports............................................................................................................8
References........................................................................................................................9
Evaluation Criteria...........................................................................................................9
This template is designed to help students produce a concise and useful project
report that aligns with their actual implementation. Each section includes clear
instructions, expected content, and page/word guidelines.

Project Phases and Implementation Expectation:

This project is conducted over two consecutive courses (GP1 and GP2), each worth 3
credit hours.
 GP1 (Graduation Project 1) focuses on analysis, design, and partial
implementation of the core functional features of the system. Students must
submit working components that represent actual parts of the final product — not
a separate or disposable prototype.
 GP2 (Graduation Project 2) extends this work to full implementation,
integration, and testing.

All deliverables from GP1 must contribute directly to the final system submitted in GP2.

The document is expected to be 20-25 pages.

1
CHAPTER 1: Project Overview, Vision, and
Planning
✅ Tip: Keep it practical — describe what you will build, not general background or
theory. Expected length: 3 – 5 pages

1.1 Problem Statement

Greenhouse and nursery environments rely heavily on continuous

monitoring to ensure plants receive ideal conditions for growth. However,
most nurseries still depend on manual observation of critical factors such as
soil moisture, temperature, humidity, pH, and nutrient levels. Manual
monitoring is slow, inconsistent, and prone to human error. Farmers often
struggle to detect early signs of plant stress and cannot maintain accurate
historical data that supports better decision-making, The key issues
addressed by this project include:

 Inconsistent plant growth is due to variations in soil moisture,

temperature, humidity, and nutrient levels.
 Inefficient use of water and fertilizers, leading to waste, increased
costs, and environmental damage.
 Delayed detection of plant diseases and unfavorable conditions,
resulting in crop losses and financial setbacks.

1.2 Related Products

This project is inspired by several existing smart agriculture systems

designed to monitor plant and environmental conditions. Two well-
established systems relevant to greenhouse and nursery applications are
Arable and Phytech. Below is a summary of their key features:

[Link]
Arable is comprehensive crop intelligence device that provides multi-modal
environmental and plant-level data. It combines weather monitoring, plant

2
stress measurement, and predictive analytics into a single solar-powered
sensor.

Key Features:
 Measures rainfall, solar radiation, temperature, humidity, wind, and
leaf wetness.
 Includes a 5MP camera and 22-band spectrometer for canopy
analysis.
 Provides crop models, yield forecasts, and disease risk assessments.
 Integrated with a dashboard and mobile tools for data visualization.

Used in: Commercial agriculture, research institutions, and smart

greenhouses.

[Link]
Phytech is a plant-focused digital platform that monitors plant stress and
irrigation effectiveness using real-time data collected from physical plant
sensors.

Key Features:
 Uses dendrometers to track stem growth and detect water stress in
plants.
 Monitors irrigation components such as pressure, flow, and tank
levels.
 Sends real-time alerts for anomalies in irrigation performance.
 Delivers agronomic recommendations based on plant feedback and
environmental factors.

3
  Supports integration with irrigation automation systems.

Used in: Orchards, vineyards, and controlled greenhouse environments.

Project Differentiation:
While Arable and Phytech are powerful and well-established agricultural
monitoring systems, this project is uniquely tailored for nursery
environments with specific functional and design goals. The key
differentiators include:
1. Target Environment
 Unlike Arable and Phytech, which are optimized for large-scale
farms, orchards, or vineyards, this project is designed
specifically for agricultural nurseries and greenhouse-based
plant production.
 It focuses on individual plant monitoring, making it ideal for
nursery conditions where different plant types are grown in
controlled sections.
2. Role-Based Access and Plant Assignment
 This system features a role-based mobile application where
farmers only access and monitor plants assigned to them.
Managers oversee the entire greenhouse and all associated
plants. Administrators manage users, greenhouses and plant
data.
 This level of user-specific interaction is not a core feature of
Arable or Phytech.

4
 3. Integration of Specific Sensors
 The system uses a combination of temperature & humidity
(DHT22), soil moisture, pH, NPK, and light sensors — all of
which are selected to provide essential insight for nursery-level
decision-making.
 It supports flexible sensor integration with ESP32, allowing for
scalability and cost-effectiveness.

4. AI-Driven Predictions and Recommendations

 The project includes a machine learning model trained to
predict plant health status, recommend actions like irrigation or
fertilization based on historical and real-time data.

5. Expandable Design
 It is structured to expand over time, allowing for future
features like automation, drone integration, or centralized
dashboards.
1.3 Product Vision

Students should include:

● Proposed Solution:

he Smart Agri-Guard system provides an intelligent, data-driven solution

designed to modernize greenhouse plant monitoring in nurseries. Instead
of relying on inconsistent manual measurements, the system uses IoT
sensors connected to an ESP32 microcontroller to continuously collect
data on temperature, humidity, soil moisture, pH, and NPK levels. This
data is processed through a cloud-based backend and analyzed by a
machine learning model to generate real-time predictions about plant
health and recommendations for irrigation or fertilization. Through a
mobile application, users receive instant alerts and can easily monitor
plant conditions anytime.

● Target Users / Stakeholders:

The system mainly serves three stakeholder groups:

5
 1. Farmers (Nursery Workers): Monitor their assigned plants, receive
actionable alerts, and ensure each plant maintains optimal conditions.
2. Nursery Managers: Oversee all greenhouse operations, manage farmers,
monitor the overall health of plants, and analyze historical trends for
operational planning.
3. System Administrators: Maintain user accounts, greenhouses, and
overall system settings. In the project’s current phase, this role is managed
by the development team.

● Product Vision Statement:

Smart Agri-Guard helps farmers and nursery managers maintain optimal
plant health by providing intelligent real-time monitoring and AI-driven
recommendations.

● Value Proposition:
Smart Agri-Guard introduces an affordable, localized, and highly practical
approach to smart agriculture. It reduces water and fertilizer waste, detects
plant stress early using predictive analytics, and improves overall
productivity in nursery environments. Unlike expensive industrial
systems, the project uses cost-effective components and provides a
mobile-friendly, role-based interface tailored to local greenhouse needs.
This ensures accessibility for small and medium-sized nurseries that lack
advanced monitoring tools.

● Scope:
The system includes a mobile application (Flutter), a cloud backend
([Link] Core with RBAC), IoT sensors connected through ESP32, real-
time dashboards, push notifications, AI-based predictions, and trend
visualization.
Out of scope are advanced automated farming features such as automatic
irrigation/fertilization control, drone monitoring, and large-scale open-
field farm management.

● Related products:

Existing commercial solutions like Arable and Phytech offer advanced

environmental analytics but are costly and targeted at large agricultural
operations. Smart Agri-Guard differentiates itself by focusing specifically
on nursery greenhouses, providing essential monitoring, AI insights, and
role-based management at a significantly lower cost, making smart
agriculture more accessible to local users.

1.4 Project Objectives and Milestones

Students should:

6
  Present clear and measurable project objectives.
 Provide a development timeline that shows key milestones for Project 1
(analysis, design, development) and upcoming milestones for Project 2 (full
implementation, testing, final delivery).
 Use a Gantt chart or a simple milestone table. See example below:

Milestone Start End

Milestone Description Deliverable
ID Date Date
Problem analysis and Problem Statement
M1 Week 1 Week 2
literature review section

1.5 Risk Assessment and Mitigation

Risk
Description Impact Mitigation Strategy
ID
Hardware malfunction or Keep backup sensors, perform early
R1 sensor damage during High hardware testing, and verify
installation or testing connections before deployment
ESP32 losing internet
Implement retry logic, add local
connection or suffering
R2 Medium caching on ESP32, and ensure
unstable Wi-Fi in nursery
stable Wi-Fi placement
environments
Perform regular calibration,
Inaccurate readings from soil
compare readings with manual
R3 or environmental sensors due High
measurements, and integrate
to calibration issues
filtering algorithms
Limited dataset availability Collect additional sensor data,
R4 leading to low AI model Medium perform data augmentation, retrain
accuracy model iteratively
Delay in mobile or backend Allocate learning time, divide tasks
R5 development due to Medium across team members, and follow
unfamiliar frameworks supervisor guidance

7
CHAPTER 3: Product Features and

Requirements

3.1 Functional Features

Feature Priority Implementation

Feature Name Description
ID (H/M/L) Stage
Allows users (farmers,
User managers, admins) to
F1 Authentication & log in securely and High GP1
Role-Based Access access features based
on their assigned role.
Collects temperature,
humidity, soil
moisture, pH, and
Real-Time Sensor NPK readings through
F2 High GP1
Monitoring IoT sensors connected
to ESP32 and displays
them instantly in the
mobile app.
Uses machine learning
to analyze sensor data
Plant Health
and classify plant
F3 Prediction (AI High GP1
health (Healthy /
Model)
Moderate Stress / High
Stress).
Provides actionable
recommendations such
Smart as “Water the plant” or
F4 High GP1
Recommendations “Add fertilizer” based
on sensor data and AI
predictions.
Sends push
notifications when a
plant is in stress or
Alerts &
F5 when any High GP1
Notifications
environmental variable
exceeds safe
thresholds.
F6 Farmer View Allows farmers to High GP1
(Assigned Plants view only the plants
Only) assigned to them,

8
 including sensor
readings, trends, and
predictions.
Enables nursery
managers to monitor
Manager all greenhouse plants,
F7 Medium GP1
Dashboard view system-wide
stats, and analyze
trends.
Allows managers to
add, edit, delete, and
F8 Manage Farmers Medium GP1
assign farmers to
specific plants.
Admins can add plants,
update details, assign
F9 Manage Plants Medium GP1
sensors, and remove
entries when needed.
Admins can create and
manage multiple
Manage
F10 greenhouse units and Medium GP1
Greenhouses
organize plants
accordingly.
Visualizes key sensor
trends (temperature,
Trend Visualization
moisture, pH, etc.) for
F11 (Real-Time & Medium GP1
up to 1–2 months to
Recent History)
support decision-
making.
Supports retrieving and
Archived Trends
displaying historical
F12 (Long-Term Medium GP2
data for 2–12 months
Storage)
for deep analysis.
Enables
managers/admins to
export reports
F13 Report Generation Medium GP2
(PDF/CSV) for plants,
sensors, or greenhouse
performance.
Allows admins to
Sensor register, link, or
F14 Medium GP2
Management replace sensors as
needed.
Records important
System Logging & system events for
F15 Low GP2
Monitoring troubleshooting and
auditing.

9
3.2 Feature-to-Requirement Mapping

Feature Requirement
Requirement Description Priority
ID ID
The system shall allow users to log in using a
F1 FR-1 High
valid username and password.
The system shall restrict system access based
F1 FR-2 High
on user roles (Farmer, Manager, Admin).
The system shall log out users after a period of
F1 FR-3 Medium
inactivity.
Passwords shall be encrypted using industry-
F1 NFR-1 High
standard hashing.
Login response time shall not exceed 3 seconds
F1 NFR-2 Medium
under normal conditions.
The ESP32 shall collect sensor readings every
F2 FR-4 X seconds (temperature, humidity, soil High
moisture, pH, NPK).
The system shall store each sensor reading in
F2 FR-5 High
the backend.
The mobile application shall display real-time
F2 FR-6 High
readings.
Sensor data transmission delay shall not exceed
F2 NFR-3 Medium
5 seconds.
The system shall handle sudden spikes in data
F2 NFR-4 Medium
volume.
The system shall analyze sensor data using a
F3 FR-7 High
trained AI model.
The system shall classify plant health
F3 FR-8 High
(Healthy / Moderate Stress / High Stress).
Prediction results shall be generated within 3
F3 NFR-5 Medium
seconds.
Model accuracy shall exceed 85% on the
F3 NFR-6 Medium
validation dataset.
The system shall generate watering or
F4 FR-9 High
fertilization recommendations.
The system shall display recommendations in
F4 FR-10 High
the app.
Recommendations shall be generated within 3
F4 NFR-7 Medium
seconds.

10
F5 FR-11 The system shall send alerts for plant stress. High
The system shall send alerts for out-of-range
F5 FR-12 High
sensor values.
Notifications shall be delivered within 2
F5 NFR-8 Medium
seconds of trigger.
F6 FR-13 Farmers shall view only their assigned plants. High
The system shall display real-time data for
F6 FR-14 High
assigned plants.
F6 NFR-9 Page loading time shall not exceed 3 seconds. Medium
Managers shall view all plants in the
F7 FR-15 High
greenhouse.
Managers shall access greenhouse-wide
F7 FR-16 Medium
statistics.
Dashboard analytics must load within 4
F7 NFR-10 Medium
seconds.
F8 FR-17 Managers shall add, edit, or remove farmers. Medium
F8 FR-18 Managers shall assign farmers to plants. Medium
F9 FR-19 Admins shall add, edit, and delete plants. Medium
F9 FR-20 Admins shall assign sensors to each plant. Medium
Admins shall create and manage greenhouse
F10 FR-21 Medium
units.
Greenhouse data retrieval shall not exceed 3
F10 NFR-11 Medium
seconds.
The system shall display sensor trends for up to
F11 FR-22 Medium
2 months.
F11 FR-23 Users shall switch between sensor trend types. Medium
F11 NFR-12 Charts must load within 3 seconds. Medium
The system shall retrieve archived readings (2–
F12 FR-24 Medium
12 months).
Archived data retrieval shall not exceed 5
F12 NFR-13 Medium
seconds.
F13 FR-25 The system shall export PDF or CSV reports. Medium
F13 NFR-14 Reports shall be generated within 5 seconds. Medium
F14 FR-26 Admins shall register and replace sensors. Medium
Sensor registration shall complete in under 3
F14 NFR-15 Medium
seconds.
The system shall record important system
F15 FR-27 Low
events in logs.
Logs must be stored securely and accessible
F15 NFR-16 Low
only to admins.

11
CHAPTER 4: System Design and Deployment

Overview

Purpose: Show how your system is structured, how components interact, and how it will
be deployed. Expected length: 4 – 6 pages
4.1 System Architecture
Students should:
● Include one UML component or layered diagram showing:
o Main system layers (UI, business logic, database, etc.)
o Key connections between components
● Add a short paragraph (≈ 100 words) explaining the architecture choices.

4.2 Detailed Design (UML Models Based on Implementation)

Students should:
● Provide UML diagrams generated directly from the implemented code.
● Include the following:
Class Diagram (1 diagram):
● Generate using tools like IntelliJ, Visual Studio, or PlantUML.
● Must reflect the actual classes, attributes, and methods in your code.
● Remove unused or placeholder classes.
Sequence Diagrams (2-3 diagrams):
● Prepare one diagram per major feature.
● Show actual method calls and interactions among classes.
● Each diagram should match your implementation.
State Machine Diagram: (1-3 diagrams):
● Develop a state machine diagram for a key class or feature that involves
multiple states and transitions (e.g., order process, user session, game
state).
● Ensure the diagram reflects actual states and transitions from your
implemented code.
● Clearly label each state and transition with corresponding events, actions,
or conditions.

4.3 Software Deployment

Students should:
● Describe technologies and 3rd-party tools used in deployment.
● Present them in a table like this: (Update don’t use as is)
Component Technology Purpose
Front-End e.g., React, Angular, [Link] …
Back-End e.g., [Link], Django, …
Spring Boot, [Link]

12
 Component Technology Purpose
Database e.g., MySQL, PostgreSQL, …
MongoDB, Firebase
Dev Tools e.g., Github, Docker, VS …
Code, Jenkins, Postman

CHAPTER 5: System Development and

Implementation

Purpose:
Summarize the implemented and partially implemented components of the system.
Demonstrate how these components represent the foundation of the final product, not a
throwaway prototype. Expected length: 2 – 3 pages

✅ Tip: Focus on a few core features that demonstrate key functionality and technical
feasibility. Your prototype doesn’t need to be complete — it must prove that your
concept and architecture are viable.

5.1 Core Implementation Progress

Students should:

 Provide a short paragraph summarizing what has been developed so far.

 Provide the GitHub repository link(s) to their project code. Example GitHub
Repository: [Link]
 Ensure each feature or module has an associated README file or inline
documentation.
5.2 Implemented and Planned Features
Each implemented feature should be traced back to the functional requirements in
Chapter 3. Use a traceability table to demonstrate alignment.

Feature GitHub
Feature Name Related Requirement Implementation Status
ID Link
F1 Generate Report FR-01 Implemented [Link]
F2 User Login FR-02 Implemented [Link]
F3 Chat Groups FR-03 Partial [Link]
Admin
F4 FR-06 To-be-implemented-GP2 -
Dashboard
…

✅ Tip: Each implemented feature should correspond to a tested use case.

13
5.3 Screenshots Evidence
Screenshots should demonstrate the actual functionality developed during GP1 and must
directly relate to the features listed in Section 5.1. Only working parts of the system
should be shown—mockups or disconnected UI designs are not acceptable. [2-3 key
screenshots]

14
CHAPTER 6: Testing
Purpose: Demonstrate how the system was verified and validated to ensure that
implemented features meet requirements. Expected length: 1.5 – 2 pages

Note: Your testing should cover Implemented Features in GP1 but must cover all features
in GP2.

6.1 Testing Overview

Students should:

 Describe the purpose of testing in this phase.

 Identify what types of testing were performed: unit, integration, or UI testing.
 Explain the test scope (which modules or features were covered).
 List the tools and frameworks used during testing. For example:

Tool / Framework Purpose

JUnit Unit testing for Java backend
Postman API testing
Selenium UI testing for web prototype
PyTest Functional testing for Python scripts

6.2 Sample Test Cases

Provide at least 5–10 representative test cases covering implemented features.
Each case must include input, expected output, and a link or reference to code or
evidence.

Test
Expected Actual Evidence /
Case Feature Input Result
Output Output Link
ID
Valid Redirect to Dashboard [Github
TC-01 Login Pass
credentials dashboard loads Link]
Report Valid date Report Report [Github
TC-02 Pass
Generation range generated generated Link]
Chat Empty
Error Error
TC-03 Group group Pass [Screenshot]
message shown
Creation name

6.3 Test reports

Students should attach or link to:
 Test result files (logs, screenshots, CI/CD reports, or unit test output).
 Screenshots of API test results or execution traces.

15
References
List all frameworks, APIs, libraries, and research papers used.

Evaluation Criteria

This section is for outlining expected weight for each section in both GP1 & GP2:

GP1 GP2
Criterion Notes
Weight Weight

Problem Statement & Vision 15% 5% –

Features & Requirements 20% 10% –

Must align with implemented

Design & UML Models 20% 10%
system

Core Implementation GP1 must include core, non-

20% 45%
(Reusable Code & Demo) disposable components

Testing should cover Implemented

Testing 10% 20% Features in GP1 but must cover all
features in GP2.

Report Format & Clarity 15% 10% –

16