Smart Irrigation System

See discussions, stats, and author profiles for this publication at: https://www.researchgate.
net/publication/338488146
Smart Irrigation System
Technical Report · May 2019

DOI: 10.13140/RG.2.2.28499.53286
CITATION READS
1 51,945
1 author:
Ayush Pandey
Islington College
2 PUBLICATIONS 3 CITATIONS
SEE PROFILE
All content following this page was uploaded by Ayush Pandey on 09 January 2020.
The user has requested enhancement of the downloaded file.

Module Code & Module Title
FC6P01NI- Final Year Project
Assessment Weightage & Type

50% Final Year Project Report
Year and Semester

2018-19 Autumn
Student Name: Ayush Pandey
London Met ID: 16033251
College ID:216053
Assignment Due Date: 8th May 2019
Assignment Submission Date: 8th May 2019
Word Count: 9345
Submitted to:
Ms. Suman Gupta (First Supervisor)
Mr. Akchayat Bikram Joshi (Second Supervisor)

Acknowledgement
Using this opportunity to express my gratitude to everyone who supported me in completing this
Final Year Project. On this occasion, I would like to thank, Miss Suman Gupta, who is my first
supervisor, without her I never thought I would be able to complete this project. From the choosing
of the topic till the finishing of the project she helped me in every way possible. I would like to
thank her and module leader for their valuable guidance, patience and the professional spirit.
Without them this project would not have been completed.
Mr. Akchayat Bikram Joshi, who is my second supervisor also helped in the developing of this
project. If he were to know that the group was not taking this task seriously, he would take some
time out from his busy schedule and guide us to the right track. Time to time he would remind us
about how important it is to write the report correctly. I am truly grateful for the guidance that
Akchayat sir has provided which has help me greatly in the completion of this project.
I would also would like to take this opportunity to thank my friends who helped me lot while doing
circuit designing and developing the final artifact and preparation of final documentation.
Abstract
The project presents the use of correct soil moisture sensors which helps to ease out the pain to
monitor and keep records about the changes in soil moisture. Using the Arduino Mega micro
controller with Light-Depended Resistor sensor, moisture sensor and temperature sensor,
temperature are measured and analyzed. The soil for a certain duration, provides information
related to the moisture status of the soil. The Arduino Mega will collect and process the data
received from the Sensors. When a threshold moisture level of the soil is reached, the water will
supply accordingly. This is essential because water must be provided to the plant at a particular
time for a good yield. This project is highly use for farmers, Nursery professionals by eradicating
traditional or manual method of irrigation system.
Contents
Chapter 1: Introduction ............................................................................................................................. 1
1.1 Current Scenario ......................................................................................................................... 3
1.2 Problem Domain ......................................................................................................................... 3
1.3 Aim & Objective ............................................................................................................................... 3
1.3.1 Aim .............................................................................................................................................. 3
1.3.2 Objective ..................................................................................................................................... 3
1.4 Structure of Report ..................................................................................................................... 4
1.4.1 Introduction ......................................................................................................................... 4
1.4.2 Background ................................................................................................................................ 4
1.4.3 Development ............................................................................................................................... 4
1.4.4 Testing and Analysis .................................................................................................................. 5
1.4.5 Conclusion .................................................................................................................................. 5
Chapter 2: Background .............................................................................................................................. 6
2.1 Survey ................................................................................................................................................ 6
2.2 Project Elaboration ........................................................................................................................... 6
2.2.1 Design Requirement ................................................................................................................... 7
2.3 End Users ..................................................................................................................................... 8
2.4 Necessity of the Project ............................................................................................................... 9
2.5 Understanding the Solution ........................................................................................................... 10
2.6 Similar System................................................................................................................................. 10
2.6.1 GSM based Agriculture Monitoring and Controlling System ............................................. 10
2.6.2 Plant Monitoring System ......................................................................................................... 10
2.6.3 Plant Moisture Monitoring System ........................................................................................ 11
2.6.4 Agriculture Monitoring System .............................................................................................. 11
2.7 Comparisons .................................................................................................................................... 12
2.7.1 Comparisons Table .................................................................................................................. 12
2.8 Review of Technical Aspect............................................................................................................ 13
Chapter 3: Development........................................................................................................................... 19
3.1 Considered Methodologies ............................................................................................................. 19
3.1.1 Extreme Programming Methodology..................................................................................... 19
3.1.2 Feature Driven Development Methodology ........................................................................... 20
3.1.3 Evolutionary Prototype Methodology .................................................................................... 22
3.1.4 Spiral Methodology .................................................................................................................. 23
3.1.5 Agile Methodology ................................................................................................................... 25
3.2 Selected Methodology ..................................................................................................................... 27
3.3 Stages................................................................................................................................................ 28
3.4 Code Development .......................................................................................................................... 29
Chapter 4: Testing and Analysis.............................................................................................................. 32
4.1 Unit Testing ..................................................................................................................................... 33
4.1.1 Test Case 01 .............................................................................................................................. 34
4.1.2 Test Case 02 .............................................................................................................................. 35
4.1.3 Test Case 03 .............................................................................................................................. 36
4.1.4 Test Case 04 .............................................................................................................................. 37
4.1.5 Test Case 05 .............................................................................................................................. 38
4.1.6 Test Case 06 .............................................................................................................................. 39
4.2 System Testing................................................................................................................................. 40
4.2.1 Test Case 07 .............................................................................................................................. 41
4.2.2 Test Case 08 .............................................................................................................................. 42
4.2.3 Test Case 09 .............................................................................................................................. 43
4.2.4 Test Case 10 .............................................................................................................................. 44
4.2.5 Test Case 11 .............................................................................................................................. 45
4.3 Critical Analysis .............................................................................................................................. 46
Chapter 5: Conclusion .............................................................................................................................. 47
5.1 Ethical Issues ................................................................................................................................... 48
5.2 Legal Issues ...................................................................................................................................... 48
5.3 Advantages of the Project............................................................................................................... 49
5.4 Limitation of the Project ................................................................................................................ 49
5.5 Further Work .................................................................................................................................. 50
Chapter 6: References .............................................................................................................................. 51
Chapter 7: Appendix ................................................................................................................................ 53
A. Pre-Survey ..................................................................................................................................... 53
B. Work Breakdown Structure ........................................................................................................ 57
C. Gantt Chart ................................................................................................................................... 57
D. Code of the system ........................................................................................................................ 58
E. Flowchart of the system ................................................................................................................ 61
F. Post Survey .................................................................................................................................... 62
Table of Figure
Figure 1: Agriculture Growth rate in last 12 year (Chaudhary, 2018) .................................................. 2
Figure 2: Result of Survey .......................................................................................................................... 8
Figure 3: Total water uses and per capita water resource ...................................................................... 9
Figure 4: Arduino ..................................................................................................................................... 13
Figure 5: Soil Moisture Sensor ................................................................................................................ 14
Figure 6: LDR ........................................................................................................................................... 15
Figure 7: Relay Module ............................................................................................................................ 15
Figure 8: Resistor ...................................................................................................................................... 16
Figure 9: Breadboard ............................................................................................................................... 16
Figure 10: Jumper wires .......................................................................................................................... 17
Figure 11: Extreme Programming Methodology ................................................................................... 19
Figure 12: The FDD project lifecycle ...................................................................................................... 21
Figure 13: Evolutionary Prototype Methodology .................................................................................. 22
Figure 14: Spiral Methodology ................................................................................................................ 24
Figure 15: Agile Methodology (A saksoft company, 2018) .................................................................... 25
Figure 16: Showing error in directory. ................................................................................................... 34
Figure 17: Successful while compiling the code. .................................................................................... 35
Figure 18: Value of moisture sensor ........................................................................................................ 36
Figure 19: Picture showing the part of the code..................................................................................... 37
Figure 20: Value of moisture sensor ........................................................................................................ 37
Figure 21: Showing the error of test case ............................................................................................... 38
Figure 22: Showing the value of test case ............................................................................................... 38
Figure 23: Value of delay to continue loop. ............................................................................................ 39
Figure 24: Showing the value of test case ............................................................................................... 39
Figure 25: Displaying the value of senor and condition of motor......................................................... 41
Figure 26: Displaying the value of senor and condition of motor......................................................... 42
Figure 27: Displaying the value of Moisture and LDR and condition of motor.................................. 43
Figure 28: Displaying the value of Moisture and Temperature and condition of motor. .................. 44
Figure 29: Displaying the value of LDR and Temperature and condition of motor. ......................... 45
Figure 30: Survey question 1 ................................................................................................................... 53
Figure 31: Survey Question 2................................................................................................................... 53
Figure 39: Survey Question 10................................................................................................................. 56
Figure 40: Work Breakdown Structure .................................................................................................. 57
Figure 41: Gantt Chart ............................................................................................................................. 57
Figure 42: Flowchart of System ............................................................................................................... 61
Figure 43: Post Survey 1........................................................................................................................... 62
Final Year Project (FC6PO1NI)
Chapter 1: Introduction
From massive agribusiness players like Cargill to small organic farmers, growers all over
the world are using the Internet of Things to reduce their consumption of water and
fertilizers, cut waste and improve the quality or yield of their products. Examples range
from tracking microclimates across cropland, to closely monitoring temperature changes
and humidity levels as perishable goods move from field to warehouse to store in order to
extend their shelf life and eliminate waste. California's recent historic drought forced many
growers to search for ways of using less water. Tech providers are helping them with tools
such as drone imagery and soil sensors, which measure real-time conditions. According to
The Nature Conservancy, such precision agriculture can enable farmers to cut water and
fertilizer use by up to 40 percent, without reducing yields. By improving the irrigation
efficiency in agricultural sector, this industry become more competitive and sustainable.
Also, in dry areas, where there is no sufficient rainfall, proper irrigation is not possible.
Hence by using this irrigation system by monitoring the moisture content of soil are can
meet the water requirements necessary for the field. To save effort of farmers, the important
considerations are water and time. In present condition, they need to wait until field is fully
watered. This restricts them to do other activities. This idea is not only meant for farmers
but also for watering the plants. In our present era, the farmers are irrigating their crops at
regular interval of time. The techniques they use will consume more water by creating
water logging and results in water wastage. This system that we designed will completely
eliminate the stress of manual Labour. Two types of soils have been tested and it will only
work when the soil condition is dry
Agriculture is the backbone of all developed countries. It uses 85% of available fresh water
resources worldwide and this percentage continues to be dominant in water consumption
because of population growth and increased food demand. Due to this efficient water
management is the major concern in many cropping systems in arid and semi-arid areas.
Arduino based plant communicator helps the farmer by checking the moisture of the soil
and if the moisture is below the level then automatic water is irrigated. Over irrigation
occurs because of poor distribution or management of waste water, chemical which lead to
water pollution. Under irrigation leads to increase soil salinity with consequent buildup of
Page | 1
L3N4 Ayush Pandey [16033251]
toxic salts on the soil surface in areas with high evaporation. To overcome these problems
and to reduce the man power plant communicator system has been used (S. Darshna, 2015).
Figure 1: Agriculture Growth rate in last 12 year (Chaudhary, 2018)
The above chart shows the growth of agriculture in Nepal with the growing rate traditional
irrigation has lots of limitation because they are operated manually. However, the modern
and automated tools like this simplify the everyday task which makes end product cost
effective and high production.
Page | 2
1.1 Current Scenario

Plant Communicator in content of the local market is a new concept. It has not yet been
introduced here. However, considering the international market, Plant Communicator is
very popular. There are many companies such as Kisan Group of Companies, GreenGold
Irrigation Private Limited, Balson Polyplast Private Limited all dedicated towards making
plant communicator targeting various trades such as fertilizers, organic fertilizers, sprinkler
irrigation system and more plant communicator with different feature such as monitoring
moisture, temperature and light and irrigating the plant if the moisture is below the level
(Patel, 2015).
1.2 Problem Domain

Internet of Things (IoT) in the context of Nepal is not quite affordable or available. Though
0there remains an eagerness for technology, this is largely due to the ignorance of the
emergence of those very technologies, lack in adapting to the pace of change and lack of
adequate budget with general population. This project targets the agriculture sector with
focus on making a cheaper and utility-based variant of the plant communicator in
alternative to those already existing in the international market.
1.3 Aim & Objective

1.3.1 Aim
The main aim of this project is to create plant communicator device based on Arduino
which help us to monitor moisture, temperature, light and irrigate if the moisture level is
below.
1.3.2 Objective
• Create a plant communicator device based on Arduino, Moisture, Temperature and
light sensor
• Use Arduino IDE for coding in Arduino device and various dependencies.
• Proper research for Arduino device and its circuit.
• Proper circuit design for the project.
• Proper testing and debugging of the device configuration.
• Create proper prototype of Plant Communicator.
Page | 3
• Conducting a survey regarding the project.

• Provide the proper value of Moisture, Temperature and Light.
• Research on various similar system.
1.4 Structure of Report

Here in this section it provides the information about the overall format of the report.
Various heading, sub-heading is there like Introduction, Background, Development,
Testing and Analysis and Conclusion. Below will be described accordingly,
1.4.1 Introduction
The first section of the report will be the introduction. This will contain several sub-
sections, as outlined. Various sub-headings like project description, current scenarios,
problem statement, aim and objectives are discussed. This is the main starting part of the
report so this will provide all the description about the project in every aspect.
1.4.2 Background
There should be some background information on the topic are. There will be
information regarding client, understanding the solutions, review of technical aspect and
similar system and overall comparisons of the project. Various sub-heading will define
various subjects. Here various feature of the project will be defined and understand the
solution of the client. After that there will be review of similar system and project where
system provide information about project which are in market but project gives which
were limited only in research paper. And at last comparison is done between others
system.
1.4.3 Development
Here should be some of the information about the development part. During the
development of the prototype which methodologies where used and which was suitable
will be described. During the time how, various stages were passed must be described
in this section. And one main thing is that the how the code was developed has to be
placed here in this section.
Page | 4
1.4.4 Testing and Analysis

Testing and Analysis is the section where the final prototype is tested in various type.
One is system testing where overall system is tested and another one is unit testing which
is done with single module. But in this report overall testing is done where everyone can
get brief description about system and unit testing. And at last overall analysis is done
to final prototype is done.
1.4.5 Conclusion
In this Conclusion section, whole report is sum up. At this part various issues like
ethical, social and legal issues will be discussed as well as advantages and limitations
also will be discussed.
Page | 5
Chapter 2: Background
2.1 Survey
As in this section the various survey that has been taken for the base decisions on objective
information and to compare the results. There we several questions which provides a
snapshot of the attitudes and behavior’s including thoughts, opinions and comments about
survey populations. And the feedbacks are much valuable to baseline to measure and
establish a benchmark from which to compare results over time. The various survey
questions and the answer are on the Appendix section.
2.2 Project Elaboration

The first prototype of the plant communicator would be able to deliver the moisture,
temperature and light of the soil. Farmer will be able to get the information about soil.
Overall after completion of the prototype additional feature as self-irrigation is added. Here
self-irrigation works when the sensed value goes beyond the threshold values set in the
program, the pump will be automatically switched ON/OFF by the relay circuit and it is
connected to the driver circuit which helps to switch the voltage. By using this system, the
farmer, agriculturist and nursery will be highly benefited because this system is cost
effective, easy to operate. Traditional or manual way of irrigation system will be time
consuming and more uses of water but this system will help user by self-irrigating, which
help to save time and save a lot of water.
Moisture Sensor
Temperature Sensor Motor

Arduino
ON/OFF
Light Sensor
Page | 6
2.2.1 Design Requirement

Connectivity
Internet connectivity was required to achieve remote access to the controller from around
the globe. It is intended that the end user will be able to control their irrigation system via
tablets, smartphones, and computers. Texas Instrument’s Beagle Bone Black (BBB) board
provides Ethernet or USB/Adapter Internet connectivity options.
Manual Operation
Manual operation of the controller was determined to be required. This would allow
control over the system without the need of a smart device and Internet connectivity.
Irrigation systems often require maintenance provided by system experts. Manual
operation gives these experts access to the system while minimizing security risks, as the
use of remote control to the system would require network access. Manual operation of
our controller would include one button to cycle through the zones and sixteen LEDs to
indicate zone operation. The button can be programmed to do whatever the software
designers need.
Installation
The only installation requirement associated with our design was that it be a replacement
of existing common controllers. Thus, being powered by a 24 V (AC) plug in transformer
and wired to corresponding zones. However, for the device to be used as a “Smart”
controller, it was required that it be connected to the Internet. This is achieved in two ways:
the first is Ethernet Connection and the second is USB Wi-Fi Adapter (range limited).
Assuming the user has Wi-Fi Internet and the controller is within a suitable range, the
controller is simply a replacement of most existing sprinkler controllers. If the controller
is out of Wi-Fi range the Ethernet connection must be used.
Page | 7
2.3 End Users

After, visiting the Mushroom farm it was found that there is problem in watering or
irrigation the water in mushroom plant where traditional way of irrigation system was still
running i.e. pouring water by themselves which consume more water than anything else.
So, to minimize the problem of irrigation and over consumption of water the concept of
“Plant Communicator” which will be beneficial to farmer. After that discussion with the
farmer of mushroom cultivator and the solution was on our hand with simple and easy
solution where got the idea to measure the moisture of spores and temperature and the light
of the room.
Figure 2: Result of Survey
The above data from pre-survey of project reveal the feedback of user towards the project.
Among the survey users 77.8% are positive towards project 22.2% are neutral. The
majority of the user are positive to the project.
Page | 8
2.4 Necessity of the Project

Day by day the population is increased which gives negative impact in water resources. As
below figure illustrates the per capita water use and per capita water resources. From the
below graph it is clear that the years passes per capita water use increases and per capita
water resources falls. So, it’s our duty to save the planet from water depletion and conserve
a single drop of water that being wasted unnecessary during the irrigation. While doing
this, water wastage will be more by water logging. So “Plant Communicator” system is
necessary to conserve water since the pump gets turn on and off automatically according
the condition of the program. One of the main objectives of this system is to remove human
is to remove control from filed for watering the plant and it is time saving (C. M. Devika
Karthika Bose, 2017).
Figure 3: Total water uses and per capita water resource
To talk about Internet of Things (IoT) is to be used in the field of agriculture this will help
in crop production. Internet of Things (IoT) won’t fix the problems related to irrigation but
if this can help in boosting crop production in one way or another way or another way and
can decrease human Labour to some extent. Involvement of technology in this filed might
make people attracted towards farming and might also remove their concept for it being as
low standard job.
Page | 9
2.5 Understanding the Solution

The main problem of the farmer was that they irrigate the mushroom spores manually or
traditionally so to overcome this problem, the proper solution for the problem was
developing a prototype which will water the plant itself and must be user friendly and cost
effective where farmer can use it and afford the system. After the study, of various project
and system it was found that various feature like checking the moisture, temperature and
LDR. Here the system is for mushroom farm so, to prepare a mushroom light temperature
and moisture are equally required. The system will help the farmer by checking the
moisture, temperature and LDR of the spores of the mushroom and water itself if the
moisture is below the farmer inputted and for temperature it will be controlled according
the farmer. This system is named as “Plant Communicator” which help the plant to
communicate whether the moisture, temperature and LDR is suitable for plant. After all
the feature the system, the prototype will be developed and tested accordingly. And the
final prototype will be checked according.
2.6 Similar System

2.6.1 GSM based Agriculture Monitoring and Controlling System
The main propose a farming environment observing framework for checking data
concerning an outside by using Wireless Sensor Network (WSN) innovation. The
proposed rural environment observing server framework gathers natural and soil data
on the outside through WSN-based ecological and soil sensor. This project uses
moisture and temperature sensor which help the field to control the water level and also
temperature. Here, they used wireless sensor network as GSM (Global System for
Mobile communication) (R.suresh, 2014)
2.6.2 Plant Monitoring System

The main purpose of this project is only just to monitor the moisture, light and
temperature of the plant. Here various sensor like moisture sensor is used to catch the
moisture of the soil whereas temperature sensor is used to take the temperature of the
plant as well as the nearer of the plant and at last the light sensor is used to take the data
of the light (Siddagangaiah, 2016).
Page | 10
2.6.3 Plant Moisture Monitoring System

The system timely monitors the moisture level of the soil. If at the time of monitoring it
comes to know that the moisture level of the soil is lower that recommended then it will
raise an audio-visual alert. An LED is used to give visual alarm and a Buzzer is used to
give audio alarm to the care taker of the plant. Thus, in this project with the help of a
simple combinational circuit and a sensor we can help save a plant by maintaining the
moisture level of the soil of the plant, thus keeping the plant healthy. This alert is then
received by the care tacker of the plant. When care taker waters the plant the alarm goes
off and the monitoring cycle continues (Nevon Project, 2015)
2.6.4 Agriculture Monitoring System

This system shows a smart agriculture monitoring system by using electronic device and
an android phone. This technology help landlord plantation to monitor and manage the
plant in order to increase the production and improvement of quality at various
agriculture sites. Here is different sensor like moisture and temperature sensor which
the value is stored in cloud. And the filed is controlled through the mobile application.
Mobile application which displays the data of the selected are and there will be option
to water itself user has to order, which will not much be applicable for the unknown and
uneducated cultivator (N. M. Z. Hashim, 2016).
Page | 11
2.7 Comparisons
In this section the evaluation is performed with the similar system and project. The first
project GSM based Agriculture Monitor and Controlling system here the GSM module
send the message to the user that moisture level is low please water the plant. So, this is
system is expensive because sending the message after and after will be expensive and
second project is Plant Monitoring System here in this project only plant is monitored no
any kind of irrigating facilities is available. Here this project checks only the moisture and
no any kind of facilities is not available so this is not much effective. The third project is
Plant Moisture Monitoring System is where the moisture is monitored and no other feature
is added. At last Agriculture Monitor System has same feature like other but additional
feature is it is control thorough mobile application where it gives the warning message to
the user, but in my project all kind of feature like monitoring moisture, temperature and
light is monitored and self-irrigating system is added where the plant will irrigate itself if
the moisture is below the level and the data of the temperature moisture and LDR values
are displayed accordingly.
2.7.1 Comparisons Table

System Moisture Temperature LDR Self-
Sensor Sensor irrigation
GSM based Agriculture Yes No No No
Monitoring and Controlling
System
Plant Monitoring System Yes Yes Yes No
Plant Moisture Monitoring Yes No No No

System
Agriculture Monitoring Yes Yes No Yes (User
System must
command)
Plant Communicator based on Yes Yes Yes Yes
Arduino
Page | 12
2.8 Review of Technical Aspect

Here in this section I am going to describe about the component like hardware and software
that are used in this project are as follow:
➢ Hardware
1. Arduino Mega:
The Arduino Mega 2560 is a microcontroller board based on the ATmega2560
(datasheet). It has 54 digital input/output pins (of which 15 can be used as PWM
outputs), 16 analog inputs, 4 UARTs (hardware serial ports), a 16 MHz crystal
oscillator, a USB connection, a power jack, an ICSP header, and a reset button. It
contains everything needed to support the microcontroller; simply connect it to a
computer with a USB cable or power it with a AC-to-DC adapter or battery to get
started. The Mega is compatible with most shields designed for the Arduino
Duemilanove or Diecimila. The Arduino Mega is a microcontroller board based on
the ATmega1280. In this project, I used analog pin A0 as an input as an input pin to
read data from LDR, pin 8 as an input pin to read data from soil moisture sensor and
pin 13 as an output to operate the water pump (Arduino , 2019)
Figure 4: Arduino
Page | 13
2. Soil moisture sensor: Soil moisture is difficult to define because it means different
things in different disciplines. For example, a farmer's concept of soil moisture is
different from that of a water resource manager or a weather forecaster. Generally,
however, soil moisture is the water that is held in the spaces between soil particles.
Surface soil moisture is the water that is in the upper 10 cm of soil, whereas root zone
soil moisture is the water that is available to plants, which is generally considered to be
in the upper 200 cm of soil. Soil moisture sensor used to measure the water content of
the spores. Soil moisture sensor has two probes, are responsible for the flow of current
in the soil which result help to identify resistance value to measure the moisture level
of the spores.
Figure 5: Soil Moisture Sensor
Why to measure soil moisture?
It is common landscape practice to supplement rainfall with the use of an irrigation

system to keep plants looking their best. Many systems are automatic: the more
complex units are connected to a climate-based electronic controller and run when
weather and evapotranspiration data dictate; the simpler ones run a set schedule linked
only to a time clock. Either of these systems may apply more water than is necessary
to maintain a healthy landscape. For a clear picture of when and how much to water
plantings, agricultural managers have long relied on soil moisture measurements;
landscape professionals can do the same to maximize irrigation efficiency in landscape
and turf plantings (Arnold, 1999).
Page | 14
3. Light-dependent resistor (LDR): Light dependent resistors, LDRs or photoresistors

are often used in circuits where it is necessary to detect the presence or the level of
light. They can be described by a variety of names from light dependent resistor, LDR,
photoresistor, or even photo cell, photocell or photoconductor. Although other devices
such as photodiodes or photo-transistor can also be used, LDRs or photoresistors are a
particularly convenient electronics component to use. They provide large change in
resistance for changes in light level LDR is also known as the photoresistor. LDR are
light sensitive device which are used to identify the presence and absence of the light
intensity. LDR resistance value increases whenever it exposed to less or low intensity
of light (dark light).
Figure 6: LDR
4. Relay module: Relay is electromechanically switch which is operated by a relatively.

small amount of electric current which can control the switching activity of the large
electric current operating devices. Arduino Uno is not able to control high value of
voltage and current.
Figure 7: Relay Module
Page | 15
5. Water Pump: As to pump water 12-volt submersible pump for this project which has
18-watt motor that can lift water up to 1.7 meters. This pump should be operated only
when it is submerged completely in the water for better results, for that we need to
keep water in the bucket because if water pump will be operated without water than it
will get damaged.
6. Resistor: The resistor is a passive electrical component to create resistance in the flow
of electric current. In almost all electrical networks and electronic circuits they can be
found. The resistance is measured in ohms. An ohm is the resistance that occurs when
a current of one ampere passes through a resistor with a one volt drop across its
terminals. The current is proportional to the voltage across the terminal ends. The
breadboard is a connection board used for prototyping of electronics projects. This
project requires the 10-k resistor with the Light dependent resistor for better results.
Figure 8: Resistor
7. Breadboard: A breadboard is a solderless device for temporary prototype with

electronics and test circuit designs. Most electronic components in electronic circuits
can be interconnected by inserting their leads or terminals into the holes and then
making connections through wires where appropriate. The breadboard has strips of
metal underneath the board and connect the holes on the top of the board. A breadboard
is an inexpensive, easy-to-use piece of hardware for wiring electrical circuits.
Breadboards acquired their name because they are similar in shape to cutting boards
used for cutting unsliced bread.
Figure 9: Breadboard
Page | 16
8. Jumper wires: Jumper wires are simply wire that have connector pins at each end,
allowing them to be used to connect two points to each other without soldering. Jumper
wires are typically used with breadboards and other prototyping tools in order to make
it easy to change a circuit as needed. Though jumper wires come in a variety of colors,
the colors don’t actually mean anything. This means that a red jumper wire is
technically the same as a black one. But the colors can be used to your advantage in
order to differentiate between types of connections, such as ground or power. For this
project two varieties of jumper wires were use Male to Male and Female to male.
Figure 10: Jumper wires
➢ Software
Arduino Integrated Development Environment (IDE): Arduino is an open-source

prototyping platform based on easy-to-use hardware and software. The Arduino Integrated
Development Environment - or Arduino Software (IDE) - contains a text editor for writing
code, a message area, a text console, a toolbar with buttons for common functions and a
series of menus. It connects to the Arduino and Genuino hardware to upload programs and
communicate with them. Programs written using Arduino Software (IDE) are called
sketches. These sketches are written in the text editor and are saved with the file extension
ino. The editor has features for cutting/pasting and for searching/replacing text. The
message area gives feedback while saving and exporting and also displays errors. The
console displays text output by the Arduino Software (IDE), including complete error
messages and other information. The bottom right-hand corner of the window displays the
configured board and serial port. The toolbar buttons allow you to verify and upload
Page | 17
programs, create, open, and save sketches, and open the serial monitor. Verify Checks your
code for errors compiling it. Upload Compiles your code and uploads it to the configured
board (Sravya, 2018)
Page | 18
Chapter 3: Development
3.1 Considered Methodologies
Numerous development methodologies based upon the System Development Life Cycle
(SDLC) model have been developed over the past Ranging from traditional development
methodologies such as the spiral methodology to modern techniques such as the
evolutionary prototype methodology some of the methods considered for this project are:
3.1.1 Extreme Programming Methodology

Extreme Programming methodology is a software development methodology which is
intended to improve software quality and responsiveness to changing customer
requirement. Extreme Programming improves a software in five essential ways;
communication, simplicity, feedbacks, respect and courage. They get feedback by
testing their software starting on day one. XP is a used for creating projects within an
unsteady environment. It provides the developers the flexibility of change. XP targets
to lower the cost of the change in the requirement. Like the traditional waterfall
methodology, the start and the end point of XP methodology is fixed but can be
improvised if necessary. Extreme programming methodology is widely used in
situations where the customers are not sure of the feature (Wells, 2013).
Figure 11: Extreme Programming Methodology
Page | 19
Advantages
• Time can be saved because it focuses on the delivery time of final product.
• This methodology is extremely simple and code can be improved at any moment.
• The whole process is visible and accountable.
• It contributes increasing employee satisfaction and retention.
Disadvantages
• Extreme Programming Methodology focuses on the code rather than on design.

• It does not measure code quality assurance.
3.1.2 Feature Driven Development Methodology

Feature driven development is a process that provides businesses with feature-rich
systems that should help them control their ever-evolving nature. Feature-driven design
is an iterative and incremental software development a process that follows the
principles of the agile manifesto. As we know FDD has five main activities that are
performed iteratively. The chosen practices are all client-based. This means that the
developers focus on the features that their client’s value and find important for their
business. On top of that, these features help the developers handle each step of the
planning stage of the project development. The first is Develop an Overall Model,
where we must identify and understand the fundamental of the domain, second step is
to Build a Features List where we will create group them into related sets and subjects.
Third one is Plan by Feature where identification of feature set owners. And Design by
Feature and Build by Feature are exactly what you’d expect, they include tasks such as
detailed modeling, programming, testing and packaging of the system. (Ambler, 2014)
Page | 20
Figure 12: The FDD project lifecycle
Advantages
• Lads to move to large projects and obtain repeatable success.

• Practicing the five processes helps to bring new staff in short time.
• Risk reduction via iteration of design and build in small chucks.
• Costing the project by feature leads to great accuracy.
Disadvantages
• Not as powerful on smaller projects.

• High reliance on chief programmer.
• No written documentation.
Page | 21
3.1.3 Evolutionary Prototype Methodology

Evolutionary prototype is an approach to system development where an initial prototype is
produced and redefined a number of stages to the final system. Evolutionary prototype is a
life-cycle model in which the system is developed in increments so that it can readily be
modified in response to end-users and customer-feedbacks. This prototyping scheme
differs from the rapid or throwaway prototyping, in that the developer begins with the
best understood requirements; whereas in rapid prototyping, the developer implements
the least understood requirements. Furthermore, the first prototype need not be built
quickly. Note that evolutionary prototyping is similar to incremental development in that
parts of the system may be inspected or delivered to the customer throughout the software
life cycle model. The objective of evolutionary prototyping is to deliver a working system
to end-users. The development starts with those requirements which are best understood.
This methodology allows rapid delivery and deployment of the system, where user
engagement with the system. This methodology has ability to address risk early in the
project and series of increments developed in the system are delivered to the customer
(Digvijay, 2018).
Figure 13: Evolutionary Prototype Methodology
Page | 22
Advantages
• This methodology can be used when requirement is not specific.

• The user can experiment with the system to improve the requirement
Disadvantages
• There is high risk in using.

• Strong management is required to handle.
• It requires high cost and time.
• This methodology is not very useful in most projects.
3.1.4 Spiral Methodology

The Spiral model combines the idea of iterative development with the systematic,
controlled aspect of the waterfall model. This Spiral Model is a combination of iterative
development process model and sequential linear development model. Spiral model is
a combination of sequential and prototype model. This model is best used for large
projects which involves continuous enhancements. There are specific activities which
are done in one iteration (spiral) where the output is a small prototype of the large
software. The same activities are then repeated for all the spirals till the entire software
is build. The Spiral Model has four phases: Identification, Design, Construct or Build
and Evaluation and Risk Analysis. Here we can change the requirement, allows
extensive use of prototype, requirement can be captured more accurately, user can see
the system in early. Spiral Methodology development can be divided into smaller parts
and the risky part can be developed earlier which helps in better risk management.
(Tutorials Point, 2018)
Page | 23
Figure 14: Spiral Methodology
Advantage
• This methodology is good for large projects.

• It requires strong approval and documentation control.
• Additional feature can be added at any later date.
• It is suitable for high risk projects.
Disadvantages
• It can be costly model to use.

• This model doesn’t work well for small projects.
• It is hard to define objectives.
• It is not suitable for low risk projects.
Page | 24
3.1.5 Agile Methodology

Agile development model is also a type of Incremental model. Software is developed
in incremental, rapid cycles. This results in small incremental releases with each release
building on previous functionality. Each release is thoroughly tested to ensure software
quality is maintained. It is used for time critical applications. This methodology is used,
when new changes are needed to be added. The freedom agile gives to change is very
important. To implement a new feature the developers, need to lose only the work of a
few days, or even only hours and implement it. Here both system developers and
stakeholders alike, find they also get more freedom of time and options than if the
software was developed in a more rigid sequential way. Having options gives them the
ability to leave important decision until more or better data or even entire hosting
programs are available; meaning the project can continue to move forward without fear
of reaching a sudden standstill.
Figure 15: Agile Methodology (A saksoft company, 2018)
Page | 25
Advantage
• This methodology satisfies the customer by rapid, continuous delivery of useful

software.
• Face-to-face conversation between business people and developers.
• Helps in working software is delivered frequently.
• Helps in continuing attention technical excellence and good design.
• Accepts late changes in requirement of the project.
• Regular adaptation to changing circumstances
Disadvantages
• There is lack of emphasis on necessary designing and documentation.

• The project can easily get taken off if the customer representative is not clear
about final outcome.
• Only higher level of programmers is capable of taking decision required during
the development process.
Page | 26
3.2 Selected Methodology

After careful consideration of all mentioned development methodologies it is thought that
this project will be better suited with the evolutionary prototype methodology. It provides
a strong foundation for the system to progress upon and is easy to understand. It features
rigid and linear development stages with distinct goals for each stage. Requirement
gathering and feasibility study are easy to perform using the evolutionary prototype
methodology. Changes on the original design can also be enforced upon easily with no
major loss. The evolutionary prototype methodology defines to obtain the feedbacks of the
client or the targeted audiences regularly. It provides the developer with the chance to
analyze the results of the development early and frequently.
Reason for choosing the evolutionary prototyping methodologies:
The most needed functionality will be produced first, thereby solving the user’s basic
needs.
This model establishes user engagement with the system. This increases the chances of
producing a system that meets the user’s requirement and also more likely to have users
commit to the user of the system.
Here we will list out the initial requirement of the client and start to create a prototype
where we will redefine the requirement of the client. At third all the requirement will be
described in full detail while creating each milestone and at last final solution based on
prototype development is developed.
Reason for not choosing the other methodologies:
Extreme Programming is focused on the coding rather than one design. This methodology
does not measure code quality assurance.
Spiral model can costly to use. Does not work for small project. This methodology is hard
to define objective, verifiable milestones and is not suitable for low risk projects.
Agile method does not focus on design and development. Only senior people are capable
of taking decisions for required in development process.
Page | 27
Feature Driven Development methodology is not powerful on smaller project. This has no
written documentation.
3.3 Stages
Evolutionary prototyping is a software development method where the developer or
development team first constructs a prototype. After receiving initial feedback from the
customer, subsequent prototypes are produced, each with additional functionality or
improvements, until the final product emerges. As to talk about the stages according to
the methodology are:
Develop abstract specification where all the requirement has to be collected from client.
After meeting with client some of the feature like checking moisture of the soil,
temperature and light of the room and displaying the result were only discussed.
Building prototype system where the prototype has to present to the client with their
requirement feature. Their feature was not much valuable to the money which they have
invested to build this prototype.
Use prototype system where the prototype is finally tested. After testing the prototype by
the client was not much happy so he gave me suggestion to add some more feature like
self-irrigation system was to add to the prototype. And the final prototype was given for
testing to the client and the client was happy after adding the feature of self-irrigation. Here
to self-irrigation two condition is applied if the moisture is low and enough light is passing
then self-irrigation is done. Second condition was if the moisture is low and room is dark
then no irrigation is done
Delivery system where the final prototype was finalized and the complete prototype was
delivered that helped the farmer which of them were happy to see some new technology in
their farm which help them to save time and less consumptions of water.
Page | 28
3.4 Code Development

This is the main phase of methodology. All the development of the project is carried out in
this phase. Also, Technical development and programming is also carried out in this phase.
Some of the activities conducted in this phase are:
❖ Various library was downloaded which can perform its task.
❖ To get the value from sensor various pin number were inputted.
❖ To run the motor there which help Relay Module to run the motor.
❖ Various data were printed through the print section in the code.
❖ Code commenting was performed for making the source code easier for human to
understand.
Below there will be the definition of the code with the source code:
#include <dht.h>
#define WATERPUMP 12 //pump connected to pin 13
#define SENSOR A1 //soil sensor digital pin connected to pin 8
#define LDR A0//light dependent resistor is connected to A0
#define PORTNUMBER 9600 // opens serial port, sets data rate to 9600 bps
#define DHT11_PIN 7
dht DHT;
Above code shows, that the library was used for the temperature and humidity sensor.
Various pin number was inputted to get the values from the sensor and at last the library
was called for the proper placement of the code.
void setup()
{
Serial.begin(PORTNUMBER);
pinMode(WATERPUMP,OUTPUT); //Set pin 12 as OUTPUT pin
pinMode(SENSOR,INPUT); //Set pin 8 as input pin, to receive data from Soil moisture
sensor.
pinMode(LDR,INPUT);
pinMode(DHT11_PIN,INPUT);
digitalWrite(WATERPUMP,LOW);//pump should be off initally
}
Page | 29
Above code section describes, the value of pin number. This code helps the Arduino board
to get the value of the sensor and reads the value. The condition of the motor is also given
output pin and input pin. Output pin helps the board to give the instruction whether to on
motor or off. Input pin is used for the valuation of the sensors.
void loop()
{
int val = analogRead(SENSOR); //stores the value received from Soil moisture sensor in
variable val
int LDRValue=analogRead(LDR);//stores the value received from LDR in variable
LDRValue
int XYZ = DHT.read11(DHT11_PIN);
if(LDRValue <= 400)
{
// if its dark then doesn't matter whether moisture is low or high, pump should be off
Serial.print("its dark, so the pump will be off.");
Serial.print("\n LDR value is: ");
Serial.println(LDRValue);//Print LDR value
Serial.print("moisture value is: ");
Serial.print("Temperature = ");
Serial.println(DHT.temperature);
Serial.println(val);//print soil moisture sensor value
digitalWrite(WATERPUMP,HIGH);//pump will off
return;
}
Above code section helps the board to recognize the value of the sensor. There is a condition
for checking the value of light. If the light of the room is below the condition then the pump
be off and above the condition then the pump will be on. And after all there is a print section
which help the board to display the value in the running environment of the Arduino IDE
monitor section.
Page | 30
if( val <= 300)

{
Serial.print("its not dark and moisture is LOW so pump should turn off,");
Serial.println(LDRValue);//print LDR value
digitalWrite(WATERPUMP,HIGH); //pump goes on
}
else
{
Serial.print("its not dark and moisture is HIGH so pump will be on.");
Serial.println(LDRValue);//print LDR value
digitalWrite(WATERPUMP,LOW);//and pump goes off
}
Here, the value of moisture is checked according the condition of the light. Here if the
moisture is below the condition then the relay module switches on which help the motor to
irrigate the filed. If the moisture is above the condition then the motor will not start. And
after all these print section helps to print the value of moisture, temperature and light.
Page | 31
Chapter 4: Testing and Analysis

Here in this section there will be various test case which were done during finalizing the
prototype. Testing is done to evaluate the system. It is performed on the basis of the output
carried out by the system. Different test cases such as Unit and System testing with different
sub heading have done with specific objective and the end results.
Page | 32
4.1 Unit Testing
No of Test Cases Objective
1 Checking if all the libraries are working properly or

not.
2 Checking all the library are running according to

requirement.
3 Checking if the moisture value is being detected in

Analog or Digital.
4 To display the value of moisture sensor in analog

value.
5 Checking if the Temperature value is correct or not.
6 To check the value of temperature is accurate.
Page | 33
4.1.1 Test Case 01

Test Case 01
Objective Checking if all the libraries are working properly or not.
Expected Results While compiling the code no library related error should be
shown.
Actual Results Showed a file from library was missing.
Analysis IDE showed that temperature sensor library was missing

even. After that the proper solution was to download the
library of temperature sensor named as “dht.h”.
Further Notes (If any) After installing the library of the temperature sensor, the
program was successfully running.
Proof: Proof of the testing can be found below.
Figure 16: Showing error in directory.
Page | 34
4.1.2 Test Case 02

Test Case 02
Objective Checking all the library are running according to requirement.
Expected Results While compiling the code the code must run successfully.
Actual Results Compiling the code was done successfully.
Analysis IDE showed that temperature sensor library was missing even.
After that the proper solution was to download the library of
temperature sensor named as “dht.h”.
Further Notes (If any) After installing the library of the temperature sensor, the
program was successfully running.
Proof: Proof of the testing can be found below in screenshot.
Figure 17: Successful while compiling the code.
Page | 35
4.1.3 Test Case 03

Test Case 03
Objective Checking if the moisture value is being detected in
Analog or Digital.
Expected Results While monitoring the moisture sensor value must be in
analog.
Actual Results Showed a value in digital (0 and 1)
Analysis The value was shown in digital due the error in code and
in the pin of the sensor.
Proof: Test was successful and proof of the testing can be found
below in screenshot.
Figure 18: Value of moisture sensor
Page | 36
4.1.4 Test Case 04

Test Case 04
Objective To display the value of moisture sensor in analog value.
Expected Results While monitoring the moisture sensor value must be in

analog.
Actual Results According to objective the value of moisture is displayed
in analog value.
Analysis The value of moisture is shown in analog so that help the
user will be able to know the exact value of moisture.
Proof: Proof of the testing can be shown in screenshot.
Figure 19: Picture showing the part of the code.
Figure 20: Value of moisture sensor
Page | 37
4.1.5 Test Case 05

Test Case 05
Objective Checking if the Temperature value is correct or not.
Expected Results While monitoring the temperature the value must show in
positive.
Actual Results Showed a value in negative i.e. -99.9 Celsius.
Analysis After proper study of the code there was found that missing
of the time to continue the loop.
Figure 21: Showing the error of test case
Figure 22: Showing the value of test case
Page | 38
4.1.6 Test Case 06

Test Case 06
Objective To check the value of temperature is accurate.
Expected Results While monitoring the temperature the value must show in
positive.
Actual Results The output of the temperature sensor is displayed in
positive value.
Analysis After the correcting the value of delay in the code helped
us to give the value n the positive form.
Figure 23: Value of delay to continue loop.
Figure 24: Showing the value of test case
Page | 39
4.2 System Testing

Number of Test case Objective
7 To monitor the values and turn on the motor under required

conditions.
8 To monitor the values and turn off motor under the required
conditions.
9 To monitor the Moisture and Light Dependent Resistor (LDR) with
motor condition.
10 To monitor the Temperature and Moisture value with motor

condition.
11 To monitor the Temperature and Light-Dependent Resistor (LDR)

with motor condition.
Page | 40
4.2.1 Test Case 07

Test Case 07
Objective To monitor the values and turn on the motor under
required conditions.
Expected Results While monitoring the values of sensor the values was
correct and the motor must be on as condition.
Actual Results The result was as expected.
Analysis The value that is sensed by sensor are displayed and

the motor is on as according to the condition.
Figure 25: Displaying the value of senor and condition of motor.
Page | 41
4.2.2 Test Case 08

Test Case 08
Objective To monitor the values and turn off the motor under
required conditions.
Expected Results While monitoring the values of sensor the values was
correct and the motor must be off as condition.
Analysis The value that is sensed by sensor are displayed and the
motor is off as according to the condition.
Figure 26: Displaying the value of senor and condition of motor.
Page | 42
4.2.3 Test Case 09

Test Case 09
Objective To monitor the Moisture and Light Dependent
Resistor (LDR) with motor condition
Expected Results While monitoring Moisture and LDR the values was
correct and the condition of motor must display.
Analysis The value that is sensed by Moisture and LDR and the
condition of the motor is displayed in the Arduino
IDE.
Figure 27: Displaying the value of Moisture and LDR and condition of motor.
Page | 43
4.2.4 Test Case 10

Test Case 10
Objective To monitor the Temperature and Moisture value with
motor condition.
Expected Results While monitoring Moisture and Temperature the values
was correct and the condition of motor must display.
Analysis The value that is sensed by Moisture and Temperature and

the condition of the motor is displayed in the Arduino IDE.
Figure 28: Displaying the value of Moisture and Temperature and condition of motor.
Page | 44
4.2.5 Test Case 11

Test Case 11
Objective To monitor the Temperature and Light-Dependent
Resistor (LDR) with motor condition.
Expected Results While monitoring Light Dependent Resistor and
Temperature the values was correct and the condition of
motor must display.
Analysis The value that is sensed by Light-Dependent Resistor

(LDR) and Temperature and the condition of the motor is
displayed in the Arduino IDE.
Figure 29: Displaying the value of LDR and Temperature and condition of motor.
Page | 45
4.3 Critical Analysis

Finally, after performing the various different type of testing cases the successful “Plant
Communicator” was developed as expected on aims and objective. The various testing cases
was performed which made the system suitable and appropriate for using it in on real-time
scenario. Some of the evaluation concluded from testing cases are:
• The system was able to achieve the Temperature before and after the operation of the
system.
• The system was able to communicate with the moisture to make sure it fulfills the
requirement of irrigation.
• The comparison with similar system proved that the system is capable for market use.
• The farmers, agriculturist, nursery will be highly benefited with the system because it is
cost effective, easy to operate and user friendly.
Page | 46
Chapter 5: Conclusion
Irrigation is the vital component for economic in any developing countries like Nepal. Over the
years, professionals involved in irrigation implemented manual method of irrigation. The manual
method has lots of drawbacks and is quite unreliable for irrigation of big areas. Irrigation has direct
impact on cost and production of final product. This system aims to eradicate the tractional manual
method of irrigation which needs to be improved over the time. Moreover, the problem domain
explains the requirement of plant communicator and irrigation systems that can be used by farmers
and flower Nursery professionals. This testing phases of the project justifies that this project can
be used in a real time farming environment. Also, the project was developed after studying the
market requirement which makes it extremely suitable in the context of present scenarios. The post
survey result provides that the system is useful in real time scenario and end users are interested
in using this system.
Page | 47
5.1 Ethical Issues

With the development of wireless technology physical objectives can be connected together
on the internet. There are many new risks and vulnerabilities risen from transferring data
between different electronic devices, many of them are belong to ethics issues. Massive amount
of data provided by the various sensor are beyond the ethics of the users. If the value of sensor
shows the wrong value then it will beyond the ethics.
5.2 Legal Issues

This project was created with an intended to be used for good work. Even if this project is good
this system can be used for various illegal activities like weed farming, Cocaine plant farming,
etc. with little modification in the code. Using this system for such illegal activities violates
the law of Nepal Government and consequences of such activities are punished according to
law.
Page | 48
5.3 Advantages of the Project

This project targets the farmer, cultivator and nursery which help them a lot. “Plant
Communicator” offers a variety of advantages over traditional irrigation system. As to talk about
the advantages of the project, firstly there is soil moisture sensor which allows for water use only
when and where needed which help in conservation of water. Generally speaking, traditional
watering method can waste as much as 50% of the water used due to inefficiencies in irrigation,
evaporations and overheating. After that the data are real-time data where farmer can visualize
water level and moisture of spores in real time. “Plant Communicator” system uses sensor for real
time data to inform watering routines and modify watering schedules to improve efficiencies.
Automating process in irrigation can reduce resources consumption, human error and overall costs
which help the farmer to lower the operation costs. This will result in energy conservation and it
is one of the great solutions for water depletion and water scarcity. The machine- to- machine
interaction provides better efficiency; hence accurate results can be obtained fast. This result in
saving valuable time. Instead of repeating the same task every day, it enables people to do other
creative jobs. This project helps the farmer to increase the productivity by providing the required
amount of water. At last this system help to reduce soil erosion and nutrient leaching. This project
is feasible and cost-effective for optimizing water resources for agricultural production. This
project allows cultivation in places with water scarcity thereby improving sustainability. It proves
that the wastage of water can be reduced. I conclude that this system is very easy to implement.
Here user should visualize his soil’s moisture content from time to time and check whether the
water level is sufficient or not. “Plant Communicator” displays the values of the water level in
Arduino IDE monitor system for the user so that user can operate them anytime.
5.4 Limitation of the Project

As to talk about the limitations of the project, this system work under the condition of light.
there will be two condition if the light is above the required value moisture performs its task,
but if the light is under the required system then the moisture does not perform its task. This
system targets small projects like mushroom farm and indoor farm so, if the farmers try to
implement in big farm some error may occurs. This system does not receive local weather which
determine when a landscape should water.
Page | 49
5.5 Further Work

The performance of the system can be further improved in term of the operating speed, memory
capacity and instruction cycle period of the microcontroller by using another high-end
controller. The number of channels can be increased to interface a greater number of sensors
which is possible by using advanced versions of controllers. The system can be modified with
the use of a data logger and a graphical LCD panel or using ThingsSpeak API to show the
measured sensor data over a period of time. this device can be made to perform better by
providing the power supply with the help of renewable sources. Time bound administration of
fertilizer, insecticides and pesticides can be introduced. A water meter can be installed to
estimate the amount of water used for irrigation and thus giving a cost estimation and a solenoid
valve can be used for varying then volume of water flow.
Page | 50
Chapter 6: References
A saksoft company, 2018. The Importance of Different Agile Methodologies Included in Agile Manifesto.
[Online]
Available at: https://www.360logica.com/blog/the-importance-of-different-agile-methodologies-included-
in-agile-manifesto/
[Accessed 12 April 2019].
Ambler, S. W., 2014. Agile Modeling. [Online]

Available at: http://www.agilemodeling.com/essays/fdd.htm
[Accessed 08 01 2019].
Arduino , 2019. Arduino cc. [Online]

Available at: https://www.arduino.cc/en/Main/arduinoBoardMega/
[Accessed 16 03 2019].
Arnold, J. E., 1999. weathermsfc. [Online]

Available at: https://weather.msfc.nasa.gov/landprocess/
[Accessed 25 03 2019].
Bullibabu, R., 2015. See discussions, stats, and author profiles for this publication at: https:/GSM based
Agriculture Monitoring and Controlling System, Guntur: ResearchGate.
C. M. Devika Karthika Bose, S. V., 2017. Automatic plant irrigation system using Arduino.
Thiruvananthapuram, IEEE.
Chaudhary, D., 2018. AGRICULTURAL POLICIES AND RURAL DEVELOPMENT IN NEPAL.

Research Nepal Journal of Development Studies, 1(2), pp. 34-46.
Digvijay, 2018. Evolutionary Prototyping in Software Development , Kathmandu: CSIT Notes.
ICT International, 2018. ICT International. [Online]

Available at: http://www.ictinternational.com/casestudies/soil-moisture-measurement-instrumentation/
[Accessed 24 03 2019].
N. M. Z. Hashim, S. R. M. M. Z. A. A. A. A. S. A. S. J. N. R. M., 2016. AGRICULTURE MONITORING

SYSTE. Centre for Telecommunication Research and Innovation, 77(1), pp. 53-59.
Page | 51
Nevon Project, 2015. Nevon Project. [Online]

Available at: http://nevonprojects.com/plant-moisture-monitoring-system/
[Accessed 05 01 2019].
Patel, A., 2015. Irrigation in India – Focus on some serious issues, India: India Microfinance.
R.suresh, S. K. T. N., 2014. GSM based Automated Irrigation Control using Raingun Irrigation System.
International Journal of Advanced Research in Computer and Communication Engineering , 3(2), pp.
5654-5657.
S. Darshna, T. ,. S. M. A. S. D., 2015. Smart Irrigation System. IOSR Journal of Electronics and
Communication Engineering (IOSR-JECE) , 10(03), pp. 32-36.
Siddagangaiah, S., 2016. A Novel Approach to IoT Based Plant Health Monitoring System. International
Research Journal of Engineering and Technology (IRJET, 03(11), pp. 880-885.
Sravya, P. R. &. G., 2018. IOT Based Smart Irrigation System. International Journal of Research, 05(12),
pp. 1016-1021.
Tutorials Point, 2018. Tutorialspoint. [Online]

Available at: https://www.tutorialspoint.com/sdlc/sdlc_spiral_model.htm
[Accessed 08 01 2019].
Wells, D., 2013. Extreme Programming. [Online]

Available at: http://www.extremeprogramming.org/
[Accessed 09 01 2019].
Page | 52
Chapter 7: Appendix
A. Pre-Survey
1. Can our plant water itself?
Figure 30: Survey question 1
2. Do you think Different varieties of plant requires different amount of

water?
Figure 31: Survey Question 2
Page | 53
3. How much water will impact in plant growth?
4. What do you think about plant communicator?
5. Why should I use Plant Communicator?
Page | 54
6. Do you face problem in Traditional or Manual method of Irrigation?
7. Do you think plant communicator will be beneficial?
8. Do you think it will save water as well as time?
Page | 55
9. Do you think it will remove the traditional or manual method of irrigation?
10. Which one will be the appropriate cost for the implementation?
Page | 56
B. Work Breakdown Structure
Figure 40: Work Breakdown Structure
C. Gantt Chart
Figure 41: Gantt Chart
Page | 57
D. Code of the system

#include <dht.h>
#define WATERPUMP 12 //pump connected to pin 13
#define SENSOR A1 //soil sensor digital pin connected to pin 8
#define LDR A0//light dependent resistor is connected to A0
#define PORTNUMBER 9600 // opens serial port, sets data rate to 9600 bps
#define DHT11_PIN 7
dht DHT;
void setup()
Serial.begin(PORTNUMBER);
pinMode(WATERPUMP,OUTPUT); //Set pin 12 as OUTPUT pin
pinMode(SENSOR,INPUT); //Set pin 8 as input pin, to receive data from Soil moisture
sensor.
pinMode(LDR,INPUT);
pinMode(DHT11_PIN,INPUT);
digitalWrite(WATERPUMP,LOW);//pump should be off initally
void loop()
Page | 58
int val = analogRead(SENSOR); //stores the value received from Soil moisture sensor in
variable val//
int LDRValue=analogRead(LDR); //stores the value received from LDR in

variable LDRValue//
int XYZ = DHT.read11(DHT11_PIN);
if(LDRValue <= 400)
// if its dark then doesn't matter whether moisture is low or high, pump should be off
Serial.print("its dark, so the pump will be off.");
Serial.println(LDRValue); //Print LDR value
digitalWrite(WATERPUMP,HIGH); //pump will off
return;
if( val <= 300)
Serial.print("its not dark and moisture is LOW so pump should turn off,");
Page | 59
Serial.println(LDRValue); //print LDR value
digitalWrite(WATERPUMP,HIGH); //pump goes on
else
Serial.print("its not dark and moisture is HIGH so pump will be on.");
Serial.println(LDRValue); //print LDR value
Serial.println(val); //print soil moisture sensor value
digitalWrite(WATERPUMP,LOW); //and pump goes off
delay (2000); //Wait for few second and then continue the loop.
Page | 60
E. Flowchart of the system
Figure 42: Flowchart of System
Page | 61
F. Post Survey
In this section, the system or prototype was tested by various professionals. They used this
system for some days and the feedback of the system was given by the professionals.
Various questions were presented to the professionals which helped us to know the
betterment of the project in real time scenario. The various questions and the review of the
question are given below:
1. Will it be beneficial to farmers?
Figure 43: Post Survey 1
2. Do you think it will save water?
Page | 62
3. How reliable is this system?
4. Will it remove traditional or manual method of irrigation after its implementation?
Page | 63
5. Is this project fulfilling its aim and objective?
6. Rate this system
Page | 64
View publication stats

Smart Irrigation System

Uploaded by

Document Information

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

Smart Irrigation System

Uploaded by

Copyright:

Available Formats

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

Smart Irrigation System

Technical Report · May 2019

The user has requested enhancement of the downloaded file.

Assessment Weightage & Type

Year and Semester

Ms. Suman Gupta (First Supervisor)

Mr. Akchayat Bikram Joshi (Second Supervisor)

Figure 1: Agriculture Growth rate in last 12 year (Chaudhary, 2018)

1.1 Current Scenario

1.2 Problem Domain

1.3 Aim & Objective

• Conducting a survey regarding the project.

1.4 Structure of Report

1.4.4 Testing and Analysis

2.2 Project Elaboration

Temperature Sensor Motor

2.2.1 Design Requirement

2.3 End Users

Figure 2: Result of Survey

2.4 Necessity of the Project

Figure 3: Total water uses and per capita water resource

2.5 Understanding the Solution

2.6 Similar System

2.6.2 Plant Monitoring System

2.6.3 Plant Moisture Monitoring System

2.6.4 Agriculture Monitoring System

2.7.1 Comparisons Table

Plant Moisture Monitoring Yes No No No

2.8 Review of Technical Aspect

Figure 5: Soil Moisture Sensor

Why to measure soil moisture?

It is common landscape practice to supplement rainfall with the use of an irrigation

3. Light-dependent resistor (LDR): Light dependent resistors, LDRs or photoresistors

4. Relay module: Relay is electromechanically switch which is operated by a relatively.

Figure 7: Relay Module

7. Breadboard: A breadboard is a solderless device for temporary prototype with

Figure 10: Jumper wires

Arduino Integrated Development Environment (IDE): Arduino is an open-source

3.1.1 Extreme Programming Methodology

Figure 11: Extreme Programming Methodology

• Extreme Programming Methodology focuses on the code rather than on design.

3.1.2 Feature Driven Development Methodology

Figure 12: The FDD project lifecycle

• Lads to move to large projects and obtain repeatable success.

• Not as powerful on smaller projects.

3.1.3 Evolutionary Prototype Methodology

Figure 13: Evolutionary Prototype Methodology

• This methodology can be used when requirement is not specific.

• There is high risk in using.

3.1.4 Spiral Methodology

Figure 14: Spiral Methodology

• This methodology is good for large projects.

• It can be costly model to use.

3.1.5 Agile Methodology

Figure 15: Agile Methodology (A saksoft company, 2018)

• This methodology satisfies the customer by rapid, continuous delivery of useful

• There is lack of emphasis on necessary designing and documentation.

3.2 Selected Methodology

Reason for choosing the evolutionary prototyping methodologies:

Reason for not choosing the other methodologies:

3.4 Code Development

if( val <= 300)

Chapter 4: Testing and Analysis