CONTRACT FARMING

Abstract
The Contract Farming is purely a web application. Now a days, farmers lead
their lives with the critical situations. However, if they have interest in farming
but they didn’t have land or money. It leads to unemployment. Contract
Farming is a web application which provides the information about the land
owners to the farmers who are willing to do farming. One can register for giving
contract to the Tenant farmers, and also register who are interested for farming.
The land owners can give their land and also supply the inputs like seeds,
manures, fertilizers, and equipments etc for farming. When Tenant farmers
register into our website, his details will be sent to admin for verification to
verify whether he is eligible for Tenant farming or not. If he is eligible then he
can send requests for Tenant farming and he can select or choose the land based
on their locality. Land owner send an agreement to the tenant farmer, once
tenant farmer accepts the agreement then he can start farming. Then they share
the profit as the percentage (Percentage which is mentioned in agreement). This
application will keep track of all the input details which are given by the land
owner to the tenants.

The existing system is only an offline system and it also taking money from the
farmers and need not provide any inputs to the farmers.

The proposed system is an online system and is beneficial to the farmers who
are unemployed, they can earn money without any investment.

OBJECTIVE
1. The aim of the contract farming is to deliver the information to the farmers
and provide the employment.

2. To provide the service to the people nearby local.

3. For this unemployment rate will decreases some.

PLAN OF ACTION
First we need to build a module for user authentication and also the other
modules and next we go for testing.
Modules Description:

This system provides its best in automating the details maintenance of

Land owners, Tenant farmers etc... It is the software which is used to provide
the service to the people who are unemployed. This project is based on linear
sequential (Water fall) model.

Modules:

This project is divided into different modules like:

1. Admin: admin is a person who is responsible for maintaining

total application. Admin can login into the system and can
manage the land owners and Tenant Farmers. He is the person who can
verify about land owners and tenant farmers whether they are really
tenant farmers or not or land owners or not. He can see the comments and
feedbacks sent by the owners and farmers and also he can send reply to
them
2. Land Owners: land owners are the users who can provide the land or farm
to the tenant farmers. He will see the requests sent by the Tenant farmers
and if they okey with that request then they will send a agreement to the
farmers. And once agreement is done then he will send inputs for the
farming tot the Tenant owners
3. Tenant farmers: He is a person or user who can take the farm for
farming. When Tenant farmers register into our website, his details will
be sent to admin for verification to verify whether he is eligible for
Tenant farming or not. If he is eligible then he can send requests for
Tenant farming and he can select or choose the land based on their
locality. Once the agreement is done with land owner, he can ask for
inputs. And share the money after cropping done.
FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS:

Functional Requirements:

 The system has login credentials(User Id & Password)

 Admin can login to the system.
 Store details of Land owners, Tenant farmers.
 The details like name, phone, address.
 Once the tenant farmer is logon to the system his details can send to the
verification state.
 The tenant farmer can select or choose the land.
 If he is eligible, admin can provide details of land owners.
 Tenant farmers can send request to the land owners.
 Land owner sends the agreement to the farmer.
 Accepts the agreement and he can start farming.
 Share the profit as percentage.
 Admin will keep track of all the input details which are given by the land
owner to the tenants.

Non-functional requirements:

Here, are some examples of non-functional requirement:

 Tenant farmer can send requests to the owner only after verification is
done by the admin.
 Land owners land details will be available in website only after
verification is done by the admin.

 Every unsuccessful attempt by a user to access our website shall be

recorded on an audit trail.
  This website is capable enough to handle 20 million users with affecting
its performance
 This software is portable. So moving from one OS to other OS does not
create any problem.

SYSTEM ANALYSIS

Hardware & Software Requirements:

Software Requirements:

 Web Presentation : HTML, CSS

 Client – side Scripting : JavaScript
 Programming Language : Java
 Web based Technologies : Servlets, JSP
 Database Connectivity : JDBC
 Java Version : JDK1.8
 Backend Database : Mysql
 Operating System : Windows
 Web Server : Tomcat
 Browser : IE/Mozilla/Chrome

Hardware Requirements (minimum):

 Pentium processor : 233 MHZ

 RAM Capacity : 2GB
 Hard Disk : 250GB
 Keyboard : 108 Standard
 Mouse : Optical
 Monitor : 15’’ Color Monitor
FEASIBILITY STUDY

Primarily whether a project that was initiated by somebody has to be

considered for further development or not will be decided through preliminary
investigation. As part of this investigation, feasibility analysis of the project is
conducted. When the outcome of this feasibility analysis is fine, then request for
the project is approved .This study will be done in these three areas: operational,
technical, and economical. Let us consider each area in brief.

Technical Feasibility

This test focuses on the feasibility of technical environment required for

the development and implementation of the project. First we have to verify
whether the necessary technology exists or can be acquired to undertake the
project. If any technical shortcomings are noted, the project is not feasible. If
such technology exists, we’ve to check whether the technical equipment can
handle the data required to use the proposed system. If the proposed project
involves networking, we’ve to examine whether the proposed system provide
adequate response to the requests irrespective of the location and users. Also,
the technical guarantees of accuracy, reliability, ease of access, and data
security should be considered and the expandability of the project is to be
tested.

Economic Feasibility

As part of this, the costs and benefits associated with the proposed system
are compared and the project is economically feasible only if tangible or
imaginable benefits overweight costs.

The proposed system will minimize the time and effort involved in
maintaining registers, books and file. This results in cost savings. Since the
necessary hardware and software are already are available. The system
development costs will be significantly low. So the proposed system will be
economically feasible.

Operational Feasibility

There is sufficient support for the project from the organization. The
proposed system is acceptable to the users. So the proposed system is
operationally feasible.

REQURIEMENTS ANALYSIS

The requirement phase basically consists of three activities:

 Requirement Analysis

 Requirement specification

 Requirement Validation

Requirement Analysis
Requirement Analysis is a software engineering task that bridges the gap
between system level software allocation and software design. It provides the
system engineer to specify software function and performance and indicates
software interface with the other system elements and establish constraints that
software must meet.

The basic aim of this stage is top obtain a clear picture of the needs and
requirement of the end-user and also the organization. Analysis involves
interaction between the clients and analyst.

Usually analysts research a problem from any questions asked and

reading existing documents. The analysts have to uncover the real needs of the
user even if they don’t know them clearly. During analysis it is essential that a
complete and consistent set of specifications emerge for the system. Here it is
essential to resolve the contradictions that could emerge from information got
from various parties.
This is essential to ensure that the final specifications are consistent. It may be
divided into 5 areas of effort

 Problem recognition

 Evaluation and synthesis

 Modeling

 Specification
 Each requirement analysis method had a unique point of view. However
all analysis methods are related by a set of operational principles. They
are

 The information domain of the problem must be represented and

understood

 The functions that the software is to perform must be defined

 The behavior of the software as a consequence of external events must be
defined

 The models that depict information, function and behavior must be

partitioned in hierarchical or layered fashion

 The analysis process must move from essential information to

implementation detail.

REQUIREMENT SPECIFICATION

Specification Principles:

Software Requirements Specification plays an important role in creating

quality software solutions. Specification is basically a representation process.
Requirements are represented in a manner that ultimately leads to successful
software implementation.

Requirements may be specified in a variety of ways. However there are some

guidelines worth following: -

 Representation format and content should be relevant to the

problem
  Information contained within the specification should be nested
 Diagrams and other notational forms should be restricted in
number and consistent in use.
 Representations should be revisable.

Software Requirements Specifications:

The software requirements specification is produced at the culmination

of the analysis task. The function and performance allocated to the software as
a part of system engineering are refined by establishing a complete information
description, a detailed functional and behavioural description, and indication of
performance requirements and design constraints, appropriate validation criteria
and other data pertinent to requirements. An outline of the Software
Requirements Specification:

Database Design
inputs_to_tenant
Column Type Null Default Links to Comments MIME

input_id (Primary) int(11) No

land_id int(11) Yes NULL land_details -> land_id

input_name varchar(50) No

input_quantity varchar(50) No

input_date date No
admin
Column Type Null Default Links to Comments MIME

admin_id (Primary) varchar(50) No

name varchar(100) No

address varchar(150) No

phone bigint(20) No

email varchar(100) Yes NULL

pinno int(11) No

gender varchar(10) No

aadharid varchar(10) No

comments
Column Type Null Default Links to Comments MIME

comm_id (Primary) int(11) No

comment varchar(200) No

tenant_farmer ->
given_by varchar(50) No
tenant_farmer_id

institute_reply varchar(200) No

date_of_comment date No

feedback
Column Type Null Default Links to Comments MIME

feedback_id (Primary) int(11) No

feedback int(200) No

given_by varchar(50) Yes NULL tenant_farmer ->

 tenant_farmer_id

institute_reply varchar(200) No

date_of_feedback date No

land_agreement
Column Type Null Default Links to Comments MIME

agreement_id (Primary) int(11) No

land_id int(11) Yes NULL land_details -> land_id

owner_percentage int(11) No

tenant_percentage int(11) No

landowner_id varchar(50) No

howmany_days_tocomplete int(11) No

land_details
Column Type Null Default Links to Comments MIME

land_id (Primary) int(11) No

land_size varchar(50) No

place_of_land varchar(50) No

status varchar(15) No

landowner_id varchar(50) No land_owner -> landowner_id

land_owner
Column Type Null Default Links to Comments MIME

landowner_id (Primary) varchar(50) No

name varchar(100) No
address varchar(150) No

phone bigint(20) No

email varchar(100) Yes NULL

pinno int(11) No

gender varchar(10) No

aadharid varchar(10) No

login
Column Type Null Default Links to Comments MIME

userid (Primary) varchar(50) No land_owner -> landowner_id

password varchar(50) No

desig varchar(50) No

status varchar(10) No

tenant_farmer
Column Type Null Default Links to Comments MIME

tenant_farmer_id (Primary) varchar(50) No

name varchar(100) No

address varchar(150) No

phone bigint(20) No

email varchar(100) Yes NULL

pinno int(11) No

gender varchar(10) No

aadharid varchar(10) No
tenant_farmer_requests
Column Type Null Default Links to Comments MIME

req_id (Primary) varchar(50) No

land_id int(11) No

tenant_farmer ->
tenant_farmer_id varchar(50) No
tenant_farmer_id

E-R Diagram

Data Flow Diagram

DFD Context level diagram

Data Flow Diagram of Contract Farming

UML DIAGRAMS

Land Owner Use-Case Diagram

register

login

provides land details

provide agreement to tenant

farmers

LandOwner

send inputs for farming

close contract with tenant

logout
Tenant Farmer Use_Case diagram

register

login

View land/farm details

Send Request for farming

Tenant Farmer
Accept agreement

take inputs
ask for inputs for farming

close contract with tenant

logout
Admin Use case diagram

login

view land owners and tenant

farmers

accepts registration after

verification

admin

can block owners or tenants

generate reports
logout

Activity Diagram of Land Owner

 Land Owner Activity Diagram

InActive

register

admin
verification

if admin verification done and success

Active
State

login

login check

entered into
session

provide land view tenant provide agreement to send inputs for close contract
details requests tenant farmers farming with tenant

logout
Activity diagram of Tenant Farmer

InActive

register

AdminVerification

ActiveState

login

invalid login
logincheck

entered into
session

view land/form send request ask for inputs take inputs close contract
details for farming for farming with tenant

logout

Admin Activity Diagram

 Inactive
state

check uid/pwd

Active
State

enters into
new session

view land view tenant verify details and accepts block owners generate
owners farmers owners and tenants or tenants reports

logout
Sequence Diagram of LandOwner

Land Owner contract Database

farming app
enter uid/pwd

login check

display landowner Home page

provide land details

land details stored in

land details stored successfully

ask to view tenant requests

cmd to get request from database

gets the tenant requests

display tenant request

accepts request

success

send agreement to tenant

stored in database

succes

agreement sent successfully

send inputs to tenants

store in database

success

sent successfully

close contract with tenant

status updated to close

success

contract closed

logout

session closed

logged out successfully

Collaboration Diagram of land owner

1: enter uid/pwd
4: provide land details
7: ask to view tenant requests
Land 11: accepts request
Owner 13: send agreement to tenant
17: send inputs to tenants
21: close contract with tenant
25: logout 2: login check
26: session closed

3: display landowner Home page

6: land details stored successfully
10: display tenant request
12: success
16: agreement sent successfully contract
20: sent successfully farming app
24: contract closed
27: logged out successfully

9: gets the tenant requests

15: succes
19: success
23: success

5: land details stored in

8: cmd to get request from database
14: stored in database
18: store in database
22: status updated to close

Databas
e
Sequence diagram of Tenant Farmer

tenant farmer cotract farming Database

web-app

enter userid/password

login check

tenant farmer home page

ask to view land farm details

commad to get land details

return land details

display to tenant

send request for farming

request will be stored in

success

successfully sent to

ask to see the agreement

command to get agreement

return agreement details

display agreement

acccept/reject agreement

sent to database

success

successfully accepted/rejected

logout

close session

logged out successfully

Collaboration Diagram for Tenant Farmer

1: enter userid/password
4: ask to view land farm details
8: send request for farming
tenant 12: ask to see the agreement
farmer 16: acccept/reject agreement 2: login check
20: logout 21: close session

3: tenant farmer home page

7: display to tenant
11: successfully sent to cotract farming
15: display agreement web-app
19: successfully accepted/rejected
22: logged out successfully

6: return land details

10: success
14: return agreement details
18: success

5: commad to get land details

9: request will be stored in
13: command to get agreement
17: sent to database

Databas
e
Admin Sequence diagram

admin contract farming Database

application
enter userid/pass...

login check

admin home page will be displayed

view tenants and land owners

cmd to get tenenats and owners details

return details

tenants and owner details displayed

validate/verify whether he is correct or not

update verification details

success

accepted/rejected

block tenant farmer/land owner who are active

cmd to block/unblock active members

success

blocked successfully

generate reports

cmd to get reports

return data

reports displayed

logout

session closed

logged out successfully

Admin collaboration diagram

1: enter userid/password
admin 4: view tenants and land owners
8: validate/verify whether he is correct or not
12: block tenant farmer/land owner who are active
16: generate reports
20: logout
2: login check
21: session closed

3: admin home page will be displayed

7: tenants and owner details displayed
11: accepted/rejected
15: blocked successfully
19: reports displayed contract farming
22: logged out successfully application

6: return details
10: success
14: success
18: return data

5: cmd to get tenenats and owners details

9: update verification details
13: cmd to block/unblock active members
17: cmd to get reports

Databas
e
 Data Flow Diagrams

Land Owner DFD:

Tenant Farmer DFD:

Admin DFD