TABLE OF CONTENTS

CONTENTS PAGE NO:

1. INTRODUCTION 1
1.1 System Overview 2
1.2 Objectives of the System 3

2. SYSTEM ANALYSIS 4
2.1 Existing System 6
2.2 Drawbacks of Existing System 6
2.3 Requirement Analysis 6
2.4 Feasibility Study 7
2.5 Proposed System 9
2.6 Advantage of Proposed system 11

3. SYSTEM SPECIFICATIONS 12
3.1 Hardware Specification 13
3.2 Software Specification 13

4. SYSTEM DESIGN 16
4.1 Input Design 17
4.2 Output Design 18
4.3 Database Design 19
 4.4 Data Flow Diagram 20
4.5 UML Design 23
4.6 Code Design 26

5. SYSTEM TESTING 29
5.1 Unit Testing 30
5.2 Code Testing 31
5.3 Integration Testing 31
5.4 Validation Testing 31
5.5 Output Testing 31
5.6 User Acceptance Testing 32

6. SYSTEM MAINTENANCE 36

8. CONCLUSION 39

9. FUTURE ENHANCEMENTS 41

10. APPENDIX 43
I. Screen Shots 44
II. Database Design 49
III. Data Flow Diagrams
IV. UML Diagrams
11. BIBLIOGRAPHY
INTRODUCTION
 1. INTRODUCTION
1.1 System Overview

GREEN FARM is envisaged to make available relevant information and

services to the farming community and private sector through the use of
information and communication technologies, to supplement the
existing delivery channels provided for by the department .GREEN
FARM is an endeavor in this direction to create one step for meeting all
informational needs relating to Agriculture of a farmer. With this
Farmer will not be required to sift through maze of websites created for
specific purposes.

Once in the GREEN FARM a farmer will be able to get all relevant
information on specific subjects around his village/block /district or
state. This information will be delivered in the form of text, SMS. These
levels can be easily reached through the Map of India placed on the
Home page. Farmers will also be able to ask specific queries by the
module specially developed for the purpose.

1.2 Objectives of the Proposed System

The main objective of the project is to design and develop a website to
make available relevant information and services to the farming
community and private sector.
SYSTEM ANALYSIS
2. SYSTEM ANALYSIS
2.1 System Analysis
System analysis refers to an orderly structured process for identifying and solving
problem using computer. It is the most important part of system development. It is
the process of gathering and interpreting facts, diagnosing problems and using the
information to recommend improvement to the system. As a part of the system
analysis, the existing system of GREEN FARM was studied thoroughly and all
the aspects were identified accordingly.

2.2 Existing System

Kissan Kerala is a Govt. of Kerala initiative project. It undertakes activities among
farmers to promote scientific methods of cultivation plant protection etc. and also it
includes the details of high yielding varieties of seeds, seedlings, planting materials
and plant protection chemicals to farmers.

2.3 Drawbacks of Existing System

 It is less user-friendly.
 It is a time consuming process
 Updations are not done properly
 The query section is not available

2.4 Requirement Analysis

Requirement analysis is the first technical step in the software
engineering process. It is at this point that a general statement of software scope is
refined into a concrete specification that becomes a foundation for all the software
engineering activities that follow. Analysis must focus on the informational,
functional and behavioral domains of a problem. To better understand what is
required, models are created, the problem is partitioned, and representation that
depict the essence of requirements and later, implementation detail, are developed.

 Introducing the system by giving a control to existing system.

 This system helps the user to register& access data very fast.

 Implementing new technology.

2.5 Feasibility Study

The prime objective of feasibility study is to ensure that the problem
is worth to be solved. At the stage a cost benefit analysis is performed to
ascertain that the benefits from the system will over rule the cost associated with
the whole analysis, design and development of the new system. An important
outcome of the preliminary investigation determining whether the system
required is feasible.
Feasibility study is a test of proposed system regarding its efficiency,
impact on the organization, ability to meet the needs of users and effective use
of resources. Thus, when a new project is proposed, it normally goes through a
feasibility study before it is approved for development.
All the projects are given unlimited resources and infinite time
.Feasibility and risk analysis are related in many ways .If project risk is great,
the feasibility of producing the quality software is reduced. There are four
aspects in the feasibility study portion of preliminary investigation.
1. Economical Feasibility
2. Technical Feasibility
3. Behavioral Feasibility
4. Operational Feasibility
 Economical Feasibility

Here an evaluation of development cost weighted against the ultimate income

or benefit from the developed system. The cost for the development of the
project has been evaluated and we want to check that the cost doesn’t exceed
beneficial cost the system. Economic and financial analysis is used for
evaluating the effectiveness of the candidate system. This project also
undergone economical feasibility study and found that it is feasible, because of
open source platform.

Technical Feasibility

The system must be evaluated from the technical view point first.
The assessment of this feasibility must be based on an outline design of the
system requirements in terms of input, output, programs, procedure and staff
having identified outline system, the investigation must go on to suggest the type
of equipment, required method of running the system. The technical feasibility
study deals with the hardware as well as software requirements. This system has
been developed using PHP, a popular open source scripting language and
Database used is mysql. So this system is technically feasible.

Behavioral Feasibility
The determination of any violation of any rules or liability hat could
result from the development of the system is behavioral feasibility. There is no
barrier for implementing the system. The system also helps to access the
information immediately as need arises. This provides user friendliness and
simple and no additional effort is needed to train the users.
Operational feasibility

This analysis involves how it will work when it is installed and the assessment of
political and managerial environment in which it is implemented. People are
inherently resistant to change and computers have been known to facilitate change.
The new proposed system is very much useful to the users and there for it will
accept broad audience from around the world. User doesn’t need any technical
knowledge to operate this application like any other android applications.

2.6 Proposed System

The proposed GREEN FARM system is going to be an automated one using PHP
and MY SQL server. The system is supposed to do various functionalities such as
checking the availability of seeds, fertilizers and also the saplings. The checking
will be based on the under district. Up-to-date market details will be available
through this system. The program schedule of different programs that are
conducting at different places will be updated accordingly. Interested users can
also register for the program. The applications of various schemes and the related
information’s will be available. And also a query section which clears the doubt of
the users is included in this system
Module description:
 Admin Module:
Admin has the privileges to modify different activities that are included in
the system.

 Admin is responsible for updating the availability of various items such

as seeds, fertilizers and planting materials.
 Day to day updating of the market details is done by the admin.
  Program schedules and details of the different applications is the
responsibility of the admin
 Different queries and doubts which are asked by the user are answered by
the admin.
 User Module:

 The user can check the availability of the seeds, fertilizers, planting
materials according to the district.
 The details of the various program schedules, market details and also
different application details can be viewed.
 Different queries and doubts can be asked by the user to expert and
also different queries and their replies can be viewed
 Staff Module:

 Day to day updating of the market details.

 Management of program schedule and other applications.
 Different queries and doubts which are asked by the user are answered by
the staff.
 Reply to queries and complaints.
 Staff can edit profile

2.7 Drawbacks of Existing System

 The system does not support any video session.

 There is no messaging facility available.
 Online selling of the products is not included
SYSTEM SPECIFICATIONS
3 .SYSTEM SPECIFICATIONS
3.1 Hardware Specification:
The selection of hardware configuration is a very important task related to
the software development. The processor should be powerful to handle entire
operations. The minimum hardware requirement of the running system is as
follows:

 Processor : Intel Core i3

 Memory : 4GB RAM
 Hard disk : 500GB
 Key board : Standard Windows keyboard
 Mouse : 3-Button Mouse
 Monitor : 1366 * 768 Resolution Color LCD Monitor

3.2 Software Specifications

The major element in building a system is the selection of compactable
software. The software requirement of the system on which the project was
developed is as follows:

 Development Platform : windows XP/7/8/10

 Front-End : HTML,PHP
 Front-End& Back End Tool : xampp-win32-1.8.3
 Scripts :Java script
 Database : My SQL
 Documentation : Microsoft Word 2007
SOFTWARE DESCRIPTION
Front End
PHP
PHP is a general purpose server-side scripting language originally designed for
Web development to produce dynamic Web pages. It is one of the first developed
server-side scripting languages to be embedded into an HTML source document
rather than calling an external file to process data.

The code is interpreted by a Web server with a PHP processor module which
generates the resulting Web page. It also has evolved to include a common-line
interface capability and can be used in stand-alone graphical applications. PHP can
be deployed on most Web servers and also as a standalone shell on almost every
operating system and platform free of charge.

Any PHP code in a requested file is executed by the PHP runtime, usually to create
dynamic Webpage content or dynamic images used on Websites or elsewhere. It
can also be used for command-line scripting and client-side biographical user
interface (GUI) applications. PHP can be deployed on most web servers, many
operating systems and platforms, and can be used with many relational database
management systems (RDBMS). I t is available free of charge and the PHP group
provides the complete source code for users to build, customize and extend for
their own use.

Instead of lots of commands to output HTML, PHP pages contain HTML with
embedded code that does “something”. The PHP code is enclosed in special start
and end processing instructions <?php and ?> that allows you to jump into and out
of “PHP mode”.
What distinguishes PHP from something like client side JavaScript is that code is
executed on the server, generating HTML which is then sent to the client. The
client would receive the results of running that script, but would not know what the
underlying code was. You can configure your web server to process all your
HTML files with PHP, and then there’s really no way that users can tell what you
have up your sleeve.

Features of PHP

• Cost is low

• PHP is open source software

• PHP is easy to learn

• PHP is embedded within HTML

Advantages of PHP Programming

PHP programming which had a humble beginning has now turned to be a

major player in software development. It was successful in a humble beginning has
now turned to be a major player in software development. It was successful in
launching fast and simple scripting language that could work seamlessly with
many other components.

The execution speed of a web application is very important as it cannot afford to

slow down the rest of the machine, either. PHP integrates well with other software,
especially under UNIX. It can be very fast, because it is a thin wrapper around
many operating system calls.

PHP offers various security levels which can be set in the .ini file to defend the
system from attacks of users, both as programmers and as surfers. Another
important advantage of PHP is its simplicity. Even HTML coders can integrate
PHP programming straight into their pages.

Further Advantages of PHP Programming include:

• Ease of writing interface to other libraries

• Several HTTP server interface.

• Large amount of database interface like MYSQL, MS SQL, Oracle, Informix and
Posture SQL etc.

• PHP programming is similar to C/Javascript and java.

• PHP is extendible.

• PHP will run on almost any platform

• The PHP extension and Add-on-Repository.

• PHP is open source.

 Back End
MySQL
MySQL ("My Sequel") is an open-source relational database
management system (RDBMS); in July 2013, it was the world's most widely used
RDBMS, and the most widely used open-source client server model RDBMS. It is
named after co-founder Michael Widenius's daughter, My. The SQL acronym
stands for Structured Query Language. The MySQL development project has made
its source code available under the terms of the GNU General Public License, as
well as under a variety of proprietary agreements. MySQL was owned and
sponsored by a single for-profit firm, the Swedish company MySQL AB, now
owned by Oracle Corporation. For proprietary use, several paid editions are
available, and offer additional functionality.
MySQL is a popular choice of database for use in web applications, and is a central
component of the widely used LAMP open source web application software stack
(and other "AMP" stacks). LAMP is an acronym for Linux, Apache, MySQL,
Perl/PHP/Python." Free-software-open source projects that require a full-featured
database management system often use MySQL. Applications that use the MySQL
database.
Include: TYPO3,MODx, Joomla, WordPress, phpBB, MyBB,Drupal and other
software. MySQL is also used in many high-profile, large-scale websites, including
Google (though not for searches), Facebook, Twitter, Flickr, and youtube.
SYSTEM DESIGN
4 .SYSTEM DESIGN
4.1 Fundamental Design Concepts of System
The most creative and challenging phase of the system
lifecycle is the system design. The term design describes a final system and the
process by which it is developed. It refers to the technical specifications that will
be applied in implementing the candidate system. In system design, we move from
the logical to physical aspects of the lifecycle.
The first step is to determine how the output is to be produced and in
which format. The input data and master files have to be designed at the next step
and finally the impact of the candidate system on the user and organization are
documented and evaluated by the management. After identifying the problem and
the limitations of the existing system, a detailed design of the proposed system is
conducted.
Design is the phase that indicates the final system. It is the solution,
the translation of requirements into ways of meeting them. In this phase the
following elements were designed namely dataflow, data stores, processes,
procedures. Firstly logical design was done where the outputs, inputs, databases
and the procedures were formulated in a manner that meet the project
requirements. After logical design physical construction of the system is done.

4.2 Input Design

In the input design, user-oriented inputs are converted into a computer
based system format. It also includes determining the record media, method of
input, speed of capture and entry on to the screen. Online data entry accepts
commands and data through a keyboard. The major approach to input design is the
menu and the prompt design. In each alternative, the user’s options are predefined.
The data flow diagram indicates logical data flow, data stores, source and
destination. Input data are collected and organized into a group of similar data.
Once identified input media are selected for processing.
In this application, importance is given to develop Graphical User Interface
(GUI), which is an important factor in developing efficient and user-friendly
application. For inputting user data, attractive forms are designed. User can also
select desired options from the menu, which provides all possible facilities. Also
the important input format is designed in such a way that accidental errors are
avoided. The user has to input only just the minimum data required, which also
helps in avoiding the errors that the users may make. Accurate designing of the
input format is very important in developing efficient software. The goal or input
design is to make entry as easy, logical and free from errors.

4.3 Output Design

In the output design, the emphasis is on producing the information
requested or displaying the output on the LCD display of PC.
As the outputs are the most important source of information to the
user, better design should improve the system’s relation and also should help
indecision-making. The output device’s capability, print capability, response time
requirements etc should also be considered form design elaborates the way output
is presented and layout available for capturing information. It’s very helpful to
produce the clear, accurate and speedy information for end users.
4.4 Database Design
In designing a database application you must set up not only the
program’s routines for maximum performance, but you must pay attention also to
the physical layout of the data storage.
A good data base design does the following:
1. Provides minimum search times when locating specific records.
2. Stores in efficient manner possible to keep database from growing large.
3. Make data updates as easy as possible.
4. Is flexible enough to allow inclusion of new functions required of program.
Data normalization is the process of eliminating redundant data within a database.
Taking data normalization fully results in each piece of information in a database appearing only once,
although that’s always not practical.
The objectives of database are accuracy and integrity, successful recovery from
failure, privacy and security of data and good overall performance database is a collection of interrelated
data stored with minimum redundancy to serve many users quick inexpensive and flexible for users.

Database
A database is similar to a data file in that it is a storage place for data. Like a
data file, a database does not present information directly to a user: the user runs an
application that accesses data from the database and presents it to the user in an
understandable format.
Database systems are more powerful than data files. The data is more highly
organized. In a well designed database, there are no duplicate pieces of data that
the user or application has to update at the same time. Related piecesof data are
grouped together in a single structure or record, and relationships can be defined
between these structures and records.
When working with data files, an application must be coded to work with
the specific structure of each data file. In contrast, a database contains a catalog
that applications use to determine how data is organized. Generic database
applications can use the catalog to present users with data from different databases
dynamically, without being tied to a specific data format.
A database typically has two components: the files holding the physical
database and the database management system (DBMS) software that applications
use to access data. The DBMS is responsible for enforcing the database structure,
including
1. Maintaining the relationships between data in the database
2. Ensuring that data is stored correctly, and that the rules defining data
Relationships are not violated.
3. Recovering all data to point of known consistency in case of system.

4.5 Data Flow Diagram

A Data Flow Diagram (DFD) is a diagram that describes the flow of data
and the processes that change data throughout a system. It’s a structured analysis
and design tool that can be used for flowcharting in place of or in association with
information. Oriented and process oriented system flowcharts. When analysts
prepare the Data Flow Diagram, they specify the user needs at a level of detail that
virtually determines the information flow into and out of the system and the
required data resources. This network is constructed by using a set of symbols that
do not imply physical implementations. The Data Flow Diagram reviews the
current physical system, prepares input and output specification, specifies the
implementation plan etc.
Four basic symbols are used to construct data flow diagrams. They are
symbols that represent data source, data flows, and data transformations and data
storage. The points at which data are transformed are represented by enclosed
figures, usually circles, which are called nodes.
 Data flow diagram symbols:-

- Source or Destination of data

- Data Flow

- Process

- Storage

Steps to Construct Data Flow Diagrams:

Four steps are commonly used to construct a DFD
 Process should be named and numbered for easy reference. Each name
should be representative of the process.
 The destination of flow is from top to bottom and from left to right.
 When a process is exploded in to lower level details they are numbered.
 The names of data stores, sources and destinations are written in capital
letters.
Rules for constructing a Data Flow Diagram:
 Arrows should not cross each other.
 Squares, circles and files must bear names.
 Decomposed data flow squares and circles can have same names.
 Draw all data flow around the outside of the diagram.
Context Diagram
The context diagram is the most abstract data flow representation of a
system. It represents the entire system as a single bubble. This bubble is labeled
according to the main function of the system. The various external entities with the
system interact and the data flows occurring between the system and the external
entities are also represented. The data input to the system and the data output from
the system are represented as incoming and outgoing arrows. These data flow
arrows should be annotated with the corresponding data names. The name context
diagram is well justified because it represents the context in which the system is to
exist, i.e. the external entities who would interact with the system and the specific
data items they would be supplying to the system and the data items they would be
receiving from the system. The context diagram is also called the Level 0 DFD.

4.6 UML Design

The Unified Modelling Language (UML) is used to specify, visualize,
modify, construct and document the artefacts of an object-oriented software
intensive system under development. UML offers a standard way to visualize
systems architectural blue prints.

 Use Case Diagram

A use case diagram in the Unified Modelling Language (UML) is a type
of behavioural diagram defined by and created from a Use-case analysis. Its
purpose is to present a graphical overview of the functionality provided by a
system in terms of actors, their goals (represented as use cases), and any
dependencies between those use cases. The main purpose of a use case diagram is
to show what system functions are performed for which actor. Roles of the actors
in the system can be depicted. The symbols are:

Use case

Association
 Actor

 Activity Diagram
Activity diagrams are graphical representations of workflows of
stepwiseactivities and actions with support for choice, iteration and concurrency.
In the Unified Modelling Language, activity diagrams can be used to describe the
business and operational step-by-step workflows of components in a system. An
activity diagram shows the overall flow of control.
Initial node

Final node

Decision node

Control Flow

Activity

Fork

Join

Fork is a black bar with one flow going into it and several leaving it.
This denotes the beginning of parallel activity. Join is a black bar with several
flows entering it and one leaving it. All flows going into the join must reach it
before processing may continue. This denotes the end of parallel processing.
4.7 Code Design
The coding step transfers a detailed design of representation of
software into a programming language realization. All the software engineering
steps that have been presented up to this step are directed towards a final objective.
Coding is a process that transforms design into a programming language. The
translation process begins when a compiler accepts the source code as input and
produces machine dependent object code as output. Compiler output is further
translated into machine code. Building the application refers to the coding step in
software engineering process. The language used in this project is php as front end
and MYSQL as backend .
SYSTEM TESTING
5.SYSTEM TESTING
5.1 System Testing
System testing is a critical aspect of Software Quality Assurance and
represents the ultimate review of specification, design and coding. Testing is a
process of executing a program with the intent of finding an error. A good test is
one that has a probability of finding an as yet undiscovered error. The purpose of
testing is to identify and correct bugs in the developed system. Nothing is complete
without testing. Testing is the vital to the success of the system.

The entire testing process can be divided into different phases:

 Unit testing
 Integration testing
 Validation testing
 Output testing

Unit Testing
It focuses efforts on the smallest unit of software design. This is known as
module testing. Each unit is tested separately for errors and defects found are
corrected. The modules are tested separately. In database management, the data
and design of tables are tested separately for errors. The test is carried out during
programming stage itself. In this step, each module is found to be working
satisfactory as regards to the expected output for the module. There are some
validation checks for the fields.
Integration Testing
Integration testing is a systematic approach for constructing the program
structure, while at the same time constructing test to uncover errors associated
within the interface. The objective is to take unit tested modules and builds
program structure. All the modules are combined and tested as a whole.

Validation Testing
Validation testing can be defined in many ways, but a simple definition is
that validation succeeds when the software functions in a manner that can
reasonable expected by the client. That means the input we are entering to the
system “Project Scheduling” will be checked whether the entered input is valid or
not.

Output Testing
After performing validation testing, the next step is output testing of the
proposed system could be useful if it does not produce the required output in the
specific format. Here the output format is considered in two ways. One is on screen
and another one is in printed format. All the reports which are generating will be
tested.
SYSTEM IMPLEMENTATION
6. SYSTEM IMPLEMENTATION
6.1 System Implementation
Implementation referred to conversion of a new system design to an
operation alone. It also deals with training of operators. An implementation plan
is to be made before starting the actual implementation of the system.
Implementation is the stage where the theoretical design is converted into a
working system.
Implementation includes all those activities that take place to convert
from the old system to the new one. The new system may be totally new,
replacing an existing manual or automated system or it may be major
modification to an existing system. Proper implementation is essential to
provide a reliable system to meet requirements.
This web application consists of very friendly graphical user
interfaces and implementation is a very simple process in this system.

Implementation Plan

The implementation plan includes a description of all the activities

that must occur to implement the new system and to put into operation. It identifies
the personnel responsible for the activities and prepares time chart for
implementing the system. The implementation plan consists of the following steps:
 List all files required for implementation
 Identify all data required to build new files during the implementation.
 List all new documents and procedures that go into the new system.
Education and Training
The implementation of the proposed system includes the training of
system operators. Training the system operators includes not only instructions in
how to use the equipment, but also in how to diagnose malfunctions and in what
steps to take when they occur. So proper training should be provided to the system
operators. No training is complete without familiarizing users with simple system
maintenance activities. Since the proposed system is developed in a GUI, training
will be comparatively easy than systems is developed in a non GUI. There are
different types of training. We can select off-site to give depth knowledge to the
system operators.
Success of the system depends on the way in which it is operated and
used. Nowadays android applications become very common in all levels of people
so this application doesn’t need any training or education programs for
implementing this application.
MAINTENANCE
7. MAINTENANCE
7.1 Maintenance
After a system is successfully implemented, it should be maintained in
a proper manner. System maintenance is an important aspect in the software
development life cycle. The need for system maintenance is for it to make
adaptable to the changes in the system environment. There may be social,
technical and other environmental changes, which affects a system, which is
being implemented.
Software product enhancements may involve providing new
functional capabilities, improving user displays and mode of interaction,
upgrading the performance characteristics of the system. So only through proper
system maintenance procedures, the system can be adapted to cope up with
these changes. Software maintenance is of course, far more than “finding
mistakes”. We may define maintenance by describing four activities that are
undertaken to after a program is released for use. The first maintenance activity
occurs because it is unreasonable to assume that software testing will uncover all
latent errors in the large program, errors will occur and be reported to the
developer. The process that includes the diagnosis and correction of one or more
an error is called corrective maintenance.
The second activity that contributes to a definition of maintenance
occurs because of the rapid change that is encouraged in every aspect of
computing. Therefore, adaptive maintenance is an activity that modifies
software to properly interfere with a changing environment is both necessary
and commonplace.
 The third activity that may be applied to a definition of maintenance
occurs when a software package is successful. As the software is used,
recommendations for new capabilities, modifications to existing functions, and
general enhancements are received from users. To satisfy requests in this
category, perceptive maintenance is performed. This activity accounts for the
majority of efforts expended on software maintenance.
The fourth maintenance activity occurs when software is changed to
improve future maintainability or reliability, or provide a better basis for future
enhancements. Often called preventive maintenance, this activity is
characterized by reverse engineering and re-engineering techniques. Software
maintenance activities can be classified into:

 Corrective Maintenance
 Adaptive Maintenance
 Perfective Maintenance
 Preventive Maintenance
CONCLUSION
8.CONCLUSION

8.1 Conclusion
The project entitled “‘GREEN FARM’” has been proposed to be implementing
for helping the farmers to the better usage of technologies and for gathering useful
information’s. It is an integrated multimodal delivery of agriculture information
system which provides several dynamic and useful information’s and advisory
services for farming community across Kerala. As the ‘GREEN FARM’is a user
friendly it will definitely help the farmers for the better production of crops.
FUTURE ENHANCEMENT
9. FUTURE ENHANCEMENTS
9.1 Future Enhancements
This application is developed in such a way that any further
enhancement can be done with ease. Our main objective is to build a complete
online booking along with admin control.
Suggestions for future enhancement:
 Feedback
 Online billing
APPENDIX
SCREEN SHOTS
DATABASE DESIGN
 TABLES:
Table 1:Login

FIELD NAME DATA TYPE CONSTRAINTS DESCRITION

User name Varchar(20) Primary key User name of

admin

password Varchar(20) Not null Password of

admin

Table 2:User registration

Kkj
Table 3:Staff registration

FIELD DATA TYPE CONSTRAINTS DESCRIPTION

NAME

staf_id Int(10) Primary key Staff id

Name Varchar(20) Not null Name of staff

Address Varchar(20) Not null Address o staff

Mobile Int(10) Not null Mobile no. of staff

Adhar Varchar(20) Not null Adhar no. of staff

Quaification Varchar(20) Not null Qualificatn of staff

email Varchar(20) Not null E-mail id of staff

Username Varchar(20) Not null User name of staff

password Varchar(20) Not null Password of staff

 Table 4:Category

FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

Cat_id Int(20) Primary key Category id

Cat_name Varchar(20) Not null Category name

Table 5:Product

FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

P_id Int(20) Primary key Pk of prduct table

Cat_id Int(20) Foreign key Pk of category

table

P_name Varchar(20) Not null Product name

Qty Int(20) Not null Quantity of

product

Centre of Varchar(20) Not null Product

availability availability

Month Date Not null Coresonding

month

Cost Int(10) Not null Cost of product

 Table 6:Market details

FIELD NAME DATA TYPE CONSTRAINTS DESCRIPTION

m_id Int(20) Primary key Market details id

Product Varchar(20) Not null Name of the prouct

Price today Int(10) Not null Product prize of today

Price yesterday Int(10) Not null Product prize of yesterday

Table 7:Query

FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

Q_id Int(20) Primary key Query id

User_id Varchar(20) Foreign key Pk of user registration

Name Varchar(20) Not null Heading of query

Query Text Not null Query portion

Reply Text Not null Repply to the queries

Date Date Not null Corresonding date

Table 8:Notification

FIELD DATA TYPE CONSTRAINT DESCRIPTION

NAME

N_id Int Primary key Notification id

N_name Varchar(20) Not null Title of notification

Desc Varchar(150) Not null descrition

Date Date Not null Program date

time Time Not null Program time

Table 9:Schemes

FIELD DATATYPE CONSTRAINTS DESCRIPTION

NAME

S_id Int(10) Primary key Scheme id

User_id Int(10) Foreign key Pk of user

registration

Bank Varchar(20) Not null Bank name

Branch Varchar(20) Not null Branch name

A/C no Int(20) Not null Account no

Schem Varchar(20) Not null Desription of

details schema

Date Date Not null Apply date

 Table 10:Booking

FIELD NAME DATATYPE DESCRIPTION DESCRIPTION

B_id Int(10) Primary key Booking id

User_id Int(10) Foreign key Pk of user registration

name Varchar(30) Not null Machine name

Agri_purpose Varchar(30) Not null Agricuture purpose

Delivary_date Date Not null Machine delivery date

From_time Time Not null From time of delivery

To_time Time Not null To time of delivery

Amount Int(10) Not null amount

Place Varchar(30) Not null User place

Table 11:Cart

FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

C_id Int(20) Primary key Cart id

P_id Int(20) Foreign key product id

P_name Varchar(20) Roduct name

 Table 12:Stock

FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

S_id Int(20) Primary key Stock id

P_id Int(20) Foreign key Product id

Cat_id Int(20) Foreign key Category id

Quaty Int(20) Not null Quatity of product

Price Int(20) Not null Price of product

Table 13:BILL

FIELD NAME DATA TYPE CONSTRAINTS DESCRIPTION

B_id Int(20) Primary key Bill id

User_id Int(20) Foreign key Pk of user registration

C_id Int(20) Foreign key Cart id

Bill_no Int(20) Not null Bill number

amount Int(20) Not null Total amount

P_name Varchar(20) Not null Product name

Date date Not null date

DATA FLOW DIAGRAM
LEVEL 0 (Context level)

request request
GREEN FARM
USER ADMIN
response
response

request response

STAFF
LEVEL 1 (ADMIN)
LEVEL 1(USER)
LEVEL 1 (STAFF)
LEVEL 2 (USER)
UML DIAGRAMS
BIBLIOGRAPHY
11 BIBLIOGRAPHY

Webliography :
1. www.stackoverflow.com
2. www.youtube.com
3. www.w3schools.com
4. www.wikipedia.org