Agri Farm Management System

Agri Farm management system 2019-2020
Chapter 1
INTRODUCTION
AGRI FARM MANAGEMENT SYSTEM, making and implementing of the
decision involved in organizing and operating a farm for maximum production and profit. Farm
management draws on agricultural economics for information on prices, markets, agricultural
policy, and economic institutions such as leasing and credit. It also draws on plant and animal
sciences for information on soils, seed, and fertilizer, on control of weeds, insects, and disease,
and on rations and breeding; on agricultural engineering for information on farm buildings,
machinery, irrigation, crop drying, drainage, and erosion control systems; and on psychology
and sociology for information on human behaviour. In making his decisions, a farm manager
thus integrates information from the biological, physical, and social sciences.
Because farms differ widely, the significant concern in farm management is the specific
individual farm; the plan most satisfactory for one farm may be most unsatisfactory for another.
Farm management problems range from those of the small, near-subsistence and family-
operated farms to those of large-scale commercial farms where trained managers use the latest
technological advances, and from farms administered by single proprietors to farms managed
by the state.
1.1 Objective
The name ‘agri farm’ indicates Intelligent Agriculture. ‘agri farm’ is a model farmer
management website application. This site helps the farmers to sell their agricultural produce
online and suggests best -in-practice farming processes. Hence, providing a wider market and
helping them to not restrict themselves to the local market. It helps the wholesalers and retailers
in buying produce from larger number of farmers. Thereby, enables the wholesalers and
retailers in expanding their business. It features online shopping for fertilizers, pesticides,
machinery & tools, etc. It helps the farmers to keep track of their agricultural production with
features such as virtual calendar, weather forecasting, etc. and enables them to hire labourers,
which in turn, will help the farm labourers to find small jobs by having a work profile in the
website. As a whole, ‘agri farm management system’ provides a concept of virtual agricultural
trade to its users.
Dept. of CSE, BGSIT page1

Chapter 2
EXISTING AND PROPOSED SYSTEM
2.1 EXISTING SYSTEM
In existing system farmer can sales product in agricultural produce market
committee(APMC).and farmer can take detail about agri products in APMCs. And buyer will
buy the products in different markets.
2.2 PROPOSED SYSTEM

The Farmer's condition today is very poor in India. There are many reasons for this
condition. One being the various diseases in the crops and other being the untimely changes in
the weather. Changes in the weather are natural and cannot be prevented but its impact can be
definitely reduced down. The proposed system agri farm offers a solution for this problem.
Agri farm management system offers location-based services to the farmers. It includes
weather forecasts, search for nearby farming related services, services for hiring laborers and
farming tool and much more. The system aims to reduce farmer's work load, ease his daily
work and thus ultimately increase the crop produce. Firebase is used for authentication and
real-time database which provides the facility of backend services. For getting nearby location,
the system uses standard zip-code database which provide latitude or longitude of zip-code and
other information. Further, the system is using web scraping technique to get data from
government website to our website.

Chapter 3
SOFTWARE AND HARDWARE SPECIFICATION
Requirement analysis for web application encompasses three major tasks:
formulation, requirements gathering and analysis modelling. During formulation, the basic
motivation and goals for the web application are identified, and the categories of users are
defined. In the requirements gathering phase, the content and functional requirements are listed,
and interaction scenarios written from end-user’s point-of-view are developed. This intent is to
establish a basic understanding of why the web application is built, who will use it, and what
problems it will solve for its users.
3.1 Software Requirements

Operating System : Windows 10.
User Interface : HTML, PHP, CSS, JAVA SCRIPT, BOOTSTRAP.
Database : MY SQL.
Application Server : XAMP Server.
3.2 Hardware Requirements

Processor : Any processor above 500 MHz
RAM : 4GB.
Hard Disk : 2GB free space.
Input Device : Keyboard, Mouse.
Output Device : Monitor.
System type : 32-bit or 64-bit operating system.

Chapter 4
SYSTEM DESIGN
 System Analysis:
The system analysis approach emphasises a closed look on all parts of the system. The analyst
must consider all the system elements, their inputs, outputs, control, feedback and the
environment when the system is being constructed.
 System Design:
The goal of system design phase is to produce a model or representation of the system, which
can be used to build the system. Here the emphasis is on translating the requirements of the
system into design specification.
1. Applicable Documents:
The document used in system design is Software Requirement Specification Document.
2. Functional Decomposition:
The system can be decomposed into functional components as follows.
The Components :-
 Registration component for customers, farmers and workers.
 Login component for customers, farmers, workers and administrators.
 Produce selling component for farmers.
 Agri farm Product selling component for administrator.
 Produce purchase request component for customers.
 Agri farm Product purchase component for farmers.
 Produce purchase approval component for farmers.
 Produce purchase report component for customer and administrator.
 Category, variety and item typesetting components for administrator.

4.1 Data Flow Diagram:

A data flow diagram is a graphical representation of the flow of data through an
information system. A data flow diagram can also be used for the visualization of the data
processing. It is common practice for a designer to draw a context level DFD.
It shows the interaction between the system and the outside entities. This context level DFD,
is then exploded to show more detail of the system being modelled.
A DFD represents flow of data through a system. Data flow diagrams are commonly
used during problem analysis. It views a system as a function that performs the input into the
desired output. A DFD shows movement of data through the different transformations or
processes in the system.
Data Flow diagrams can be used to provide the end users with the physical idea of
where the data they input ultimately has an effect upon the structure of whole system from
order to dispatch to restock how any system is developed can be determined through data flow
diagram. The appropriate register saved in database and maintained by appropriate authorities.
Shaping
management
customer Farmer
management management
Agri farm
management
system
Category worker
management management
Login
management
Fig4.1: Data Flow Diagram

Notations in DFD:
Symbol Description
The circle or bubble represents a process.

A process is named, and each process is
represented by a named circle.
The source or sink is represented as a

rectangular box. The source or sink is the
net originator or the consumer of the data
that flows in the system.
The arrow represents the flow of data

through the system. The labeled arrows
enter or leave the bubbles.
The database is represented with the

open box symbol.
4.2 Schema diagram

It formulates all the constraints that are to be applied on the data. The database
schema defines its entities and the relationship among them. It contains a descriptive detail of
the database, which can be depicted by the means of schema diagram.

Fig 4.2: Schema Diagram

4.3 ER-Diagram
The Entity-Relationship(ER) model was originally proposed by Peter in 1076 [Chen76]
as a way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually represent
data objects. Since Che wrote his paper the model has been extended and today it is commonly
used for database design for the database designer, the utility of the ER model.
Fig4.3: ER-diagram

2.purchase ER-diagram:
A
receives
purchase_request_id
request_date
purchase_request
customer_id
quantity
requires
purchase_order_id
purchase_order_time
purchase_order
purchase_order_date
generates
purchase_order_bill-id
purchase_order_bill purchase_order_id
paid_amt
Fig4.3: ER-diagram(A)

3.customer ER-diagram:
Fig4.3: ER-diagram(B)

4.workers ER-diagram:
Fig4.3:ER-diagram(C)

ER Notation
There is no standard for representing data objects in ER diagrams. Each modelling
methodology uses its own notations. The original notation used by Chen is widely used in
academic’s texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, where are a number of notation used, among the more common are
Bachman, crow’s foot, and ide fix.
All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in the document is from Martin. The symbols used for the basic
ER constructs are: Entities are represented by some labelled rectangles. The label is the name
of the entity. Entity names should be singular nouns.

Chapter 5
IMPLEMENTATION
5.1 FRONT END
PHP, which stands for “PHP: Hypertext Pre-processor” is a widely-used Open Source
general purpose scripting language that is especially suited for Web development and can be
embedded into HTML. Its syntax draws upon C, Java, and Perl, and is very to lean. The main
goal of language is to allow web developers to write dynamically generated web pages quickly,
but you can do much more with PHP.
5.2 Technology used for Implementation (PHP)
PHP:
PHP is a powerful language and the interpreter, whether included in a web server as a
module or executed as a separate CGI binary, is able to access files, execute commands and
open network connections on the server. These properties make anything run on a web server
insecure by default. PHP is designed specifically to be a more secure language for writing CGI
programs than Perl or C, and with correct selection of compile-time and runtime configuration
options, and proper coding practices, it can give you exactly the combination of freedom and
security you need. As there are many different ways of utilizing PHP, there are many
configuration options controlling its behaviour. A large selection of options guarantees you can
use PHP for a lot of purpose, but it also means there are combinations of these options and
server configurations that result in an insecure setup. The configuration flexibility of PHP is
equally rivalled by the code flexibility. PHP can be used to build complete server applications,
with all the power of a shell user, or it can be used for simple server/side includes with little
risk in a tightly controlled environment. How you build that environment, and how secure it
is, is largely up to the PHP developer.

5.3 Back End
Database:
A Database Management System (DBMS) is computer software designed for the
purpose of managing databases, a large set of structured data, and run operations on the data
requested by numerous users. Typical examples of DBMSs include Oracle, DB2, Microsoft
Access, Microsoft SQL Server, Firebird, PostgreSQL, MySQL, SQLite, FileMaker and Sybase
Adaptive Server Enterprise. DBMSs are typically used by Database administrators in the
creation of Database systems. Typical examples of DBMS use include accounting, human
resources and customer support systems. Originally found only in large companies with the
computer hardware needed to support large data sets, DBMSs have more recently emerged as
a fairly standard part of any company back office.
A DBMS is a complex set of software programs that controls the organization, storage,
management, and retrieval of data in a database.
SQL:
Structured Query Language (SQL) is the language used to manipulate relational databases.
SQL is tied very closely with the relational model.
• In the relational model, data is stored in structures called relations or tables.
SQL statements are issued for the purpose of:
• Data definition: Defining tables and structures in the database (DDL used to create, alter and
drop schema objects such as tables and indexes). • Data manipulation: Used to manipulate the
data within those schema objects (DML Inserting, Updating, Deleting the data, and Querying
the Database).
A schema is a collection of database objects that can include: tables, views, indexes and
sequences.

Chapter 6
TESTING
Testing is the major quality control measure used during software development. It is a
basic function to detect errors in the software. During the requirement analysis and design the
output of the document that is usually textual and non-executable after the coding phase the
computer programs are available that can be executed for testing purpose. This implies that
testing not only has to uncover errors introduce during the previous phase. The goal of testing
is to uncover requirement, design, coding errors in the program.
Testing determines whether the system appears to be working according to the

specifications. It is the phase where we try to break the system and we test the system with real
case scenarios at a point.
 Levels of Testing:
6.1 Unit Testing:
The unit testing of the source code has to be done for every individual unit of
module that was developing part of the system and some errors were found for every
turn and rectified. This form of testing was using to check for the behaviour signified
the working of the system in different environment as an independent functional unit.
6.2 Integration Testing:
From the individual parts to the cohesion of each part to make the system, there is need
to test the working between the assembled modules of the system. The modules are integrated
to make up the entire system. The testing process is concerned with finding errors that result
from unanticipated interaction between the sub-system and system component. It is also
concerned with validating the system meets its functional and non-functional requirement.
6.3 System Testing:

The requirement specification document that is the entire system is to be tested to see
whether it meets the requirement or not.

6.4 Test Reports:
 Test Unit: Admin Component

 Admin login:
Serial Condition
Test Data Expected Output Remarks
No. To be Tested
Alert the user to enter all
If any field in the Value of
1. the fields and then SUCCESSFUL
form is empty. form fields.
proceed.
Alert user that E-mail ID
2. If the E-mail ID
Email id, and password are not
and Password SUCCESSFUL
password matching and stay in
does not match.
the same page.
 Test Unit: Customer component

 Customer registration:
Serial Condition
No. To be Tested
Alert the user to enter
If any field in the Value of form
1. all the fields and then SUCCESSFUL
form is empty. fields.
proceed.
If customer name Alert the user to enter
contains other Customer only characters and
2. SUCCESSFUL
than Character name return to the same
values. page.
3.
If country is not Alert the user to select
country SUCCESSFUL
selected. a country.
4.
If state is not Alert the user to select
state SUCCESSFUL
selected. a state.

If PIN Code
5. contains other Alert the user to enter
Pin code SUCCESSFUL
than numeric only numeric values.
values.
If contact number
cntctnum SUCCESSFUL
values.
If mobile number
mblnum SUCCESSFUL
values.
Email id
8. Alert the user to enter a
If E-mail ID is
valid E-mail ID and SUCCESSFUL
invalid.
return to the same page.
If password Alert the user to enter

9. length is not Password a password of length
SUCCESSFUL
between 8 to 16 between 8 to 16
characters. characters.
If confirm
cpassword, Alert the user to enter
10. password and
password matching password and SUCCESSFUL
password does
confirm password.
not match.
If the customer Alert the user to select a
11. type is not Customer type customer type and SUCCESSFUL
selected. return to the same page.

 Customer login:
Serial Condition
No. To be Tested
proceed.
2. If the E-mail ID
password matching and stay in
does not match.
the same page.
 Test Unit: Worker component:

 Worker Registration:
Serial Condition
No. To be Tested
proceed.
If worker name Alert the user to enter
contains other only characters and
2. name SUCCESSFUL
than Character return to the same
values. page.
3.
country SUCCESSFUL
4.
state SUCCESSFUL
selected. a state.
5. If PIN Code Alert the user to enter

Pin code SUCCESSFUL
contains other only numeric values.

than numeric
values.
6. Login id Alert the user to enter a
If E-mail ID is
invalid.
If password Alert the user to enter
length is not Password a password of length
7. SUCCESSFUL
between 8 to 16 between 8 to 16
characters. characters.
If confirm
cpassword, Alert the user to enter
8. password and
password matching password and SUCCESSFUL
password does
confirm password.
not matc h.
If the expected
Alert the user to select a
salary contains
9. expected salary expected salary and SUCCESSFUL
other than
numeric values.
 Worker Login:
Serial Condition
No. To be Tested
proceed.
2. If the E-mail ID
password matching and stay in the
does not match.
same page.

 Test Unit: Seller Component

 Seller Registration:
Serial Condition
No. To be Tested
proceed.
If seller name Alert the user to enter
contains other only characters and
2. Seller name SUCCESSFUL
than Character return to the same
values. page.
3.
Country SUCCESSFUL
4.
State SUCCESSFUL
selected. a state.
If city is not Alert the user to select

5. city SUCCESSFUL
selected. a city.
If PIN Code
Pin code SUCCESSFUL
values.
If contact number
7. contains other Contact Alert the user to enter
SUCCESSFUL
than numeric number only numeric values.
values.
If mobile number
Mb number SUCCESSFUL
values.

Email id
Alert the user to enter a
9. If E-mail ID is
invalid.
If bank name
contains values
10. Bank name only characters for SUCCESSFUL
other than
Bank name.
characters.
If bank branch
name contains
11. branch only characters for bank SUCCESSFUL
values other than
branch name.
characters.
If bank account
number contains Bank ac
12. only numeric values for SUCCESSFUL
values other than number
bank account number.
numbers.
 Seller Login:
Serial Condition
No. To be Tested
proceed.
2. If the E-mail ID
password matching and stay in the
does not match.
same page.

 Test Unit: Variety Component

Serial Condition
No. To be Tested
If field in the form Value of form Alert the user to enter the
1. SUCCESSFUL
is empty. fields. fields and then proceed.
Alert the user to select a
If category is not
2. category category. SUCCESSFUL
selected.
If produce is not Alert the user to select a

3. produce SUCCESSFUL
selected. produce.
If variety contains Alert the user to enter
4. values other than variety only characters for SUCCESSFUL
characters. variety.
If image is not Alert the user to select
5. img SUCCESSFULS
selected. an image.
 Testing Unit: Selling Product Component

Serial Condition
No. To be Tested
proceed.
If category is not Alert the user to select a
2. category SUCCESSFUL
selected. category.
If product name
contains values Product
3. only characters for SUCCESSFUL
other than name
product name.
characters.
4. img1 SUCCESSFUL
selected. an image.

If cost contains Alert the user to enter

5. values other than cost only numeric values for SUCCESSFUL
numeric values. cost.
 Test Unit: Selling Product component

Serial Condition
No. To be Tested
proceed.
If seller name is Alert the user to select
2. seller name SUCCESSFUL
not selected. the name of the seller.
If category is not Alert the user to select
3. category SUCCESSFUL
selected the category.
If produce is not Alert the user to select
4. produce SUCCESSFUL
selected. the produce.
If variety is not Alert the user to select
5. variety SUCCESSFUL
selected. the variety.
6. img1 SUCCESSFUL
selected. an image.
If quantity contains Alert the user to enter

7. values other than quantity only numeric values for SUCCESSFUL
numeric values. quantity.
If the quantity type Alert the user to select a
8. Quantity type SUCCESSFUL
is not selected. quantity type.

Chapter 7
SNAPSHOTS
This section describes the screenshot of the “AGRO FARM MANAGEMENT SYSTEM”.
The snapshots are shown below for each module.
HOME PAGE
 This page displays information about “agri farm management system”.
 It contains different login and signup options.
Fig7.1: home page

BLOGS PAGE
 This page displays blogs based on agriculture.
Fig 7.2: blog page

NEWS
 This Page displays latest news on agriculture.
Fig7.3: news page

FARMERS KIT
 This page displays online shop for farming fertilizers, tools and equipment’s.
Fig7.4: farmer kit

FARMERS MARKET
 This page displays online shop for farm produces uploaded by farmers.
 It also contains location search to display farm produce of farmers of the given location.
Fig7.5: farmers market

HIRE PAGE
 This page displays farm labourers who have registered on the website in search of jobs.
 It also contains location search to display farm labourers of the given location.
Fig7.6: hire page

CONTACT US PAGE
 This page displays contact information of ‘agri farm’.
 It contains ‘Send Us A Message’ form for sending feedbacks and contacting the
administrator.
Fig7.7: contact us page

Customer registration page:

 When customer will fill all the blank, customer will registration to the “agri farm”.
Fig7.8: customer registration page
Customer login panel:

 It contains Register Now Link and Button to redirect user to the Registration Page, if the
user is not registered.
 This page displays Customer Login Form.
 It contains a Forgot Password Link.
Fig7.9: customer login panel

Farmer registration page:

 When farmer will fill all the blank, farmer will registration to the “agri farm”.
Fig7.10: farmer registration page
Farmer login panel:

 It contains Register Now Link and Button to redirect user to the Registration Page, if the
user is not registered.
 This page displays Farmer Login Form.
Fig7.11: farmer login panel

Worker registration page:

 When worker will fill all the blank, worker will registration to the “agri farm”.
Fig7.12: worker registration page
Worker login panel:

 This page contains a login form and Forgot Password link.
Fig7.13: worker login panel

Admin login panel:

 When Admin successfully logs in, the Admin Panel page is displayed:
Fig7.14: admin login panel
Admin home page:

 Dashboard: This page displays all the tables in the database with the total number of
records. View Customers: This page displays all the registered customers.
 View Product Billing Report: This page displays all the Farmer’s Kit products
purchase bills.
 View Produce Purchase Request: This page displays the purchase request sent for all
the farm produces by the farmers.
 View Produce Billing Report: This page displays the billing report for the farm
produces purchased.
Fig7.14: admin home page

CONCLUSION
The project “agri farm management system” is a man-made project and, therefore,
there may be mistakes and limitations. The ideas put up may be different. The terms and names
may be different. However, our sincere effort was to give the best. The advanced techniques
like sensor technology can be used in the future for measuring the quality of the product.

REFERENCES
 www.w3schools.com
 www.tutorialspoint.com
 www.stackoverflow.com
 www.highcharts.com
 Web Database Applications with PHP and MySQL By Hugh E. Williams, David Lane
 An integrated approach to Software Engineering by Pankaj Jalote

Agri Farm Management System

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Agri Farm Management System

Încărcat de

Drepturi de autor:

Formate disponibile

Agri Farm management system 2019-2020

Dept. of CSE, BGSIT page1

2.2 PROPOSED SYSTEM

Dept. of CSE, BGSIT page2

3.1 Software Requirements

User Interface : HTML, PHP, CSS, JAVA SCRIPT, BOOTSTRAP.

Application Server : XAMP Server.

3.2 Hardware Requirements

Hard Disk : 2GB free space.

Input Device : Keyboard, Mouse.

Output Device : Monitor.

System type : 32-bit or 64-bit operating system.

Dept. of CSE, BGSIT page3

Dept. of CSE, BGSIT page4

4.1 Data Flow Diagram:

Fig4.1: Data Flow Diagram

Dept. of CSE, BGSIT page5

The circle or bubble represents a process.

The source or sink is represented as a

The arrow represents the flow of data

The database is represented with the

4.2 Schema diagram

Dept. of CSE, BGSIT page6

Fig 4.2: Schema Diagram

Dept. of CSE, BGSIT page7

Dept. of CSE, BGSIT page8

Dept. of CSE, BGSIT page9

Dept. of CSE, BGSIT page10

Dept. of CSE, BGSIT page11

Dept. of CSE, BGSIT page12

5.2 Technology used for Implementation (PHP)

Dept. of CSE, BGSIT page13

5.3 Back End

• In the relational model, data is stored in structures called relations or tables.

SQL statements are issued for the purpose of:

Dept. of CSE, BGSIT page14

Testing determines whether the system appears to be working according to the

6.1 Unit Testing:

6.2 Integration Testing:

6.3 System Testing:

Dept. of CSE, BGSIT page15

6.4 Test Reports:

 Test Unit: Admin Component

 Test Unit: Customer component

Dept. of CSE, BGSIT page16

If password Alert the user to enter

Dept. of CSE, BGSIT page17

 Test Unit: Worker component:

5. If PIN Code Alert the user to enter

Dept. of CSE, BGSIT page18

Dept. of CSE, BGSIT page19

 Test Unit: Seller Component

If city is not Alert the user to select

Dept. of CSE, BGSIT page20

Dept. of CSE, BGSIT page21

 Test Unit: Variety Component

If produce is not Alert the user to select a

 Testing Unit: Selling Product Component

Dept. of CSE, BGSIT page22

If cost contains Alert the user to enter

 Test Unit: Selling Product component

If quantity contains Alert the user to enter

Dept. of CSE, BGSIT page23