Future Farm Project Report

FUTURE FARM: ONLINE FARMING SOLUTIONS 1
DECLARATION
I, Ajay Cherian, do hereby declare that the project titled FUTURE FARM: ONLINE
FARMING SOLUTION is a record of work carried out under the guidance of Ms Donamol
Thomas, Assistant Professor, Department of Computer Applications, Christ College,
Puliyanmala as per the requirement of the curriculum of Bachelor of Computer Applications
program of Mahatma Gandhi University, Kottayam. Further, I also declare that this report has
not been submitted, full or part thereof, in any University / Institution for the award of any
Degree / Diploma.
Ajay Cherian (Reg: 170021093721)
DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

ACKNOWLEDGEMENT
The success of any project depends largely on the encouragement and guidelines of
many others. I would like to take this opportunity to express my gratitude to those people
who have been instrumental in the successful completion of this project.
First and foremost, I give all glory, honour and praise to God Almighty who gave me
wisdom and enabled me to complete the project successfully.
I also express sincere thanks, from the bottom of my heart, to my parents for their
encouragement and support in all my endeavours and especially in this project.
Words are inadequate to express my deep sense of gratitude to Rev. Dr. Alex Louis
CMI, Principal, Christ College, Puliyanmala for allowing me to utilize all the facilities of
our college and also for his encouragement.
I extend my sincere gratitude to Mr. Tony Mathews Panicker, Head of the

Department of Computer Science, Christ College, Puliyanmala who has been a constant
source of inspiration and without his tremendous help and support this project would not have
been materialized.
I own a particular debt of gratitude to my internal project guide, Ms. Jissa Maria
Jose, Department of Computer Science, Christ College, Puliyanmala for all the necessary
help and support that she has extend to me. Her valuable suggestions, corrections and the
sincere efforts to accomplish my project even under a tight time schedule were crucial in the
successful completion this project.
I extend my sincere thanks to all of our teachers and non-teaching staff of Christ
College, Puliyanmala for the knowledge they have imparted to me over the last two years.
I would also like to express my appreciation to all my friends for their comments, help
and support.

TABLE OF CONTENTS
1. Introduction……………..…………………………………………………………….06
1.1 Project overview……………………………………………………….07
2. System analysis……………………………………………………………………..08
2.1 Preliminary analysis…………………………………………………09
2.2 Existing system…………………………………………………………09
2.3 Proposed system……………………..……………………………….10
2.4 Feasibility study……………………………………………………….10
2.4.1 Economical feasibility…………….,.….…………..….12
2.4.2 Technical feasibility…………………………………..….13
2.4.3 Behavioural feasibility………………………………....14
2.4.4 Operational feasibility…………………………….......15
2.5 Advantages of proposed system………………………..……16
3. System specification……………………….…………………………………...17
3.1 Software specification……………………………………. 18
3.2 Hardware specification………………………………….. 18
3.3 About the developing tools...………………………… 19
4. System design………………………………………………………………………21
4.1 Architectural design…………………………….………… 25
4.2 Input design…………………………………….……………… 25
4.3 Modules and description…………………………………26
4.4 Output design…………………………………………………. 28
4.5 Database design……………………………………………… 28
4.6 User interface design……………………………………… 29
5. Database design…………………………………………………………………...30
5.1 Tables………………………………………………………….…….31
5.2 Data flow diagrams………………………………………… 33

6. System testing………………….……………………………………………………44
6.1 Unit Testing………………………………………………………46
6.2 Integration Testing……………………………………………47
6.3 Validation Testing…………………………………………… 48
6.4 System Testing…………………………….……………………49
6.5 User Acceptance Testing………………………………… 50
7. System implementation…………………………………………………………51
7.1 Implementation………………………………………………… 52
7.2 Problem statement………………………………………..……52
7.3 Problem description……………………………………………52
7.4 Feature of project………………………………………………. 52
8. Future enhancement……………………………………………………………… 53
10. Conclusion…………………………………………………………………………….55
11. Bibliography………………………………………………………………………….57
11. Appendix……………………………………………………………………………...59
a. Sample Screens…………………………………………………… 60
b. Coding……………………………………………………………….....66

ABSTRACT
The project named "Future Farm" is a website for agriculturists. The website provides
functions for Administrator, Farmer/User and Suppliers. This system has mainly four phases.
They are administrator side and the expert side, farmer side and general user side. The main
work will be done in the administrator side, still the user side is equally important because it
deals with what a visitor of the site sees when he/she enters the site. The administrator is the
charge of maintaining the contents of the site. Option are provided for him to perform the
operation regarding maintaining the contents of the site. He/she can view/delete/add the
contents
In this Project we are providing an interface to the farmers to interact with
farmers, clarify their doubts, view seasonal updates, view videos regarding crops and better
farming techniques, view market rates etc. We are providing and interface to the team to store
their data in order to conduct awareness events efficiently. Through this project they can
prepare schedule for the events, data needed in the events like videos regarding crops,
PowerPoint presentation on seasonal crops and their related documents. Before going to any
program in certain village they can be able to cross check the stuff needed in that event at any
point of time.

INTRODUCTION

1.1 PROJECT OVERVIEW
To solve a problem there are two ways. One is to appoint more employees and the other is
computerization. By analysing these situations first one is not effective. So we use second
option that is computerization that is our proposed system is a computerized system.
This system has developed to automate the future farm management processes. This includes
all online process, add crops, receive crops, add complaints, and add tips. Also can view
added tips and complaints by another frame we use login name and password for login in to
the FFMS. The user can enter only if the user name and password is match otherwise the user
cannot use it. Unregistered user can visit FFMS if they interested to continue to use, the
visitor first register in our system. Whenever a user logs-in it is checked whether he is
registered. Our system have mainly 3 users admin, farmer, byer. A valid user/farmer can add
crops, they can buy crop, add complaints, and also they can add tips. Byer can buy the crops
that are added by the farmer. If the buyer bye any crop then he get summary of his order. The
system has order tracking facility are included.
It should provide the user a warm welcome and make him feel comfortable in navigation
through the site. The user must be given necessary guidelines at every stage, so that even a
person with least computer literacy must be able to get information and see to it that he never
gets uneasy while looking for the information.
The master user of this system is the administrator who can login using a master password
and once a user is authenticated as the admin, he/she can access and modify information
stored in the database of the system.

SYSTEM ANALYSIS

2.1 PRELIMINARY ANALYSIS

The system analysis process is called the life cycle methodology, since it relates
significant phases in the life cycle of all business information systems: study, design,
development and operation. Analysis is a detailed study of the various operations performed
by a system and their relationships within and outside of the system. One aspect of analysis is
defining the boundaries of the system and determining whether or not a candidate system
should consider other related system. This is the major step among the software development.
System Analysis is a general term that refers to an orderly, structured process for identifying
and solving problems.
In order to design the proposed system, the requirements should be known and
arranged in such a way that the designing become easier. System Analysis is the process in
which the requirements for the proposed system is collected, corrected, and organized in an
effective manner. In System Analysis, the analyst collects the requirements from the Users
and carefully studies them. After that the skeleton-the structure and the way of development
is produced. Care must be taken while analysing the existing system as well as the proposed
system. Understand the needs and requirements is very important, because the proposed
system is evaluated based on the analysis phase. The system must satisfy the requirements in
the analysis phase. The requirements are fulfilled by computerized method.
2.2 EXISTING SYSTEM

The existing system made us to store information about the farm manually and crops
details are added by the admins and the user can only buy the crops. The user can view
an abstract details of the crops and he have to buy the crops without having a good idea
about the crops.
DISADVANTAGES OF EXISTING SYSTEM
 Communication and file handling is not easy.

 The searching process for the existing system is not possible.
 Frequent updating is not possible.
 The existing system is very time consuming.

2.3 PROPOSED SYSTEM
The proposed system is a dynamic user-friendly and interactive website. It should

provide the user a warm welcome and make him feel comfortable in navigation through
the site. The user must be given necessary guidelines at every stage, so that even a
person with least computer literacy must be able to get information and see to it that he
never gets uneasy while looking for the informant
Many modifications can be made to make the atmosphere user friendly. Fast retrieval
and data accuracy will be the major benefits of the proposed system. In proposed system
the user is provided with a set of menus, dialogues and enters screens, which are much
user friendly. Password protection facility is also incorporated to protect the system
from unauthorized access of data. A set of useful menus is provided in the menu in the
menu bar, which helps to carry out operations. User friendly shades are provided to give
the users that the application has a pleasant feeling.
The advantages of the proposed system are:
 The system avoids redundancy by the use of several type of validation that is the
system is enhanced
 Quick access and processing is the main advantage that forces as to implement
the proposed system.
 The main alteration between the existing system and the new automated system
lies in the specialty which reduces the time consumption in an appropriate
manner.
 Specification of the automated online system helps to accumulate all the details
of the farm transactions.
 This system helps to accumulate all the details of the customer, receiver, online
shopping, and inquiry of product in the farm department in the future farm.
 This software can be easily extended to any area since it is online.
 Less human effort.
 It is highly reliable and sec.

2.4 FEASIBILTY STUDY

System feasibility is a test or evaluation of the complete system plan. Such an
evaluation is necessary to define the application area along with the extend and capability to
provide the scope of computerization together with suggested output and input format and
potential benefits. Feasibility study is a proposal according to the workability, impact on the
organization, ability to meet user’s needs and efficient use of resources. The feasibility study
is conducted to determine if the proposed system is feasible or not. Feasibility analysis
evaluates the candidate systems and determines the best system that needs performance
requirements. The purpose of feasibility study is to investigate the present system, evaluate
the possible application of computer based methods, select a tentative system, evaluate the
cost and effectiveness of the proposed system, evaluate impact of the proposed system on
existing personnel and ascertain the need for new personnel. Feasibility is carried out to see if
the system is technically, economically and operationally feasible.
All projects are feasible when given unlimited resources and infinite time. It is both
necessary and prudent to evaluate the feasibility of a project at the earliest possible time. A
feasibility study is not warranted for systems in which economic justification is obvious,
technical risk is low, few legal problems are expected and no reasonable alternative exists.
An estimate is made of whether the identified user needs may be satisfied using current
software and hardware technologies. The study will decide if the proposed system will be
cost effective from the business point of view and if it can be developed in the given existing
budgetary constraints. The feasibility study should be relatively cheap and quick. The result
should inform the decision of whether to go ahead with a more detailed analysis.
Feasibility study may be documented as a separated report to higher officials of the

top-level management and can be included as an appendix to the system specification.
Feasibility and risk analysis is related in many ways. If there is more project risk then the
feasibility of producing the quality software is reduced.

Three key combinations are involved in the feasibility study:
 Economic Feasibility
 Technical Feasibility
 Behavioural Feasibility
 Operational Feasibility
2.4.1 ECONOMICAL FEASIBILITY
Economic analysis is the most frequently used method for evaluating the effectiveness of a
candidate system which is known as cost benefit analysis. In cost benefit analysis, the
benefits and savings that are expected from candidate systems compared with costs. If
benefits outweigh cost, then the decision is made to design and implement a system.
Otherwise further justifications or alterations in the proposed system will have to be made
if it has to be approved.
This project aims at reducing time, effort and cost. The system is developed under optimal
expenses with the hardware and software. The developed system is available free of cost.
Anybody can get the benefit of the system by simply using it as a service. There is no
additional cost for using or implementing the system. It can be used in windows based
system, and need not alter the current system configurations. This makes the system feasible
economically. Besides it is good economic to insist in such a kind of software from the
project manager’s point of view as the benefits over weighs the cost. The resources needed to
run the above project should be less in cost, easily available and highly reliable. This is a cost
effective project because of its accuracy, speed and user friendly nature.
2.4.2 TECHNICAL FEASIBILITY
 Does the necessary technology exist to do what is been suggested?

 Does the proposed equipment have the technical capacity for using the new system?
 Are there technical guarantees of accuracy, reliability and data security?

A study of function, performance and constraints may improve the ability to create an
acceptable system. Technical feasibility is frequently the most difficult area to achieve at the
stage of product engineering process.
Considering that are normally associated with the technical feasibility include Development
risk, Resource availability, Technology. Technical feasibility study deals with the hardware
as well as software requirements. The scope was whether the work for the project is done
with the current equipment and the existing software technology has to be examined in the
feasibility study. The outcome was found to be positive.
Project requirement system must be functional and multi user one should be based on specific
technology the system under study must be practical and platform independent. It should be
compactable with all kind of existing system in industry and should not provide any overhead
to user. Implementation of existing system does not require changing of the existing
configure of the system. The platform what is needed for development is easily available. So
the new system is technically feasible.
2.4.3 BEHAVIOURAL FEASIBILITY
An estimate should be made of how strong a reaction the user staff is likely to have toward
the development of a computerized system. It is common knowledge the computer
installations have something to do understandable that the introduction of a candidate system
requires special effort to educate, sell and train the staff on new ways of considering business.
The behaviour of the system plays an important role in the number of users accessing the
software. This is due to the fact that is a simple software is very easy and convenient to use.
Anyone with the basic knowledge of computer can easily use the system and get its benefits.
Additional training is not required to work with it. This means that the system is feasible
behaviourally.

2.4.4 OPERATIONAL FEASIBILITY
 Will the system be used if it developed and implemented?

 If there was sufficient support for the project from the management and from the
users.
 Have the users been involved in planning and development of the project.
 Will the system produce faulty result in any respect or area?
This application can be implemented in an organization because there is adequate support

from management and users. And application will be used by them since it doesn’t generate
poorer results or problems in any area. Therefore, the implementation of this application is
operationally feasible. Operational feasibility is concerned with human, organizational and
political aspects. The issues considered are the job changes that will be brought about, the
organizational structures that will be distributed and the new skills that will be required. The
operational feasibility of the proposed system is tested against organizational constraints, i.e.,
whether the company has adequate staff to implement the new system, will the employees
support the system or will they resist, whether there is management personnel with enough
data processing experience etc. The employees in the organization will have to alter their
work patterns and work in an atmosphere of change.
The present system is easily understandable. The maintenance and working of the new
system requires less human effort and is beneficiate to the organization. Our software is
based on the requirement specification given by the user and is user friendly, based on the
requirement specification given by users. The operation of this software is very simple.
2.5 ADVANTAGES OF THE PROPOSED SYSTEM

 The system excludes the use of paper work by managing all the book information
electronically.
 This web application allows the user to deal with the great ease of environment.
 It provide the functionality to complain.
 It saves human efforts and resources.
 Record editing facility.
 Automation.

SYSTEM SPECIFICATION

3.1 SOFTWARE SPECIFICATION

Operating System : Microsoft Windows 7 or Higher
Technology used : PHP version 5.2.5
Front end : HTML+ CSS
Back end : PHP
RDBMS : MySQL 5.0.1
3.2 HARDWARE SPECIFICATION
Processor : Intel Core 2 Duo

RAM : 2 GB or more
Hard disk drive : 320 MB
Keyboard : Standard 108
Monitor : Acer Soft Scree
Pointing device : mouse
Connectivity : Local internet or internet
3.3 ABOUT THE DEVELOPING TOOLS
HYPERTEXT PREPROCESSOR
PHP is a computer scripting language originally designed for producing dynamic web pages.
It is for sever side scripting but can be used from command line interface or in standalone
graphical applications. While PHP was originally created by Rasmus Lerdorf in 1995, the
main implementation of PHP is now produced by the PHP group and servers as the defector
standard for PHP as there is no formal specification. Released under PHP License, the free
software Foundation considers it to be free software.

PHP is a widely-used general purpose scripting language that is especially suited for web
development and can be embedded into HTML. It generally runs on a web server, taking
PHP codes as its input and creating web pages as output. It can be deployed on most web
servers and on almost every operating system and platform free of charge. PHP is installed on
more than 20 million website and 1 million web servers. It is also the most popular Apache
module among computers using Apache as web server. The most recent major release of PHP
was version 5.2.6 on May 1, 2008.
MICROSOFT SQL SERVER 2008
MySQL is a relational database management system (RDBMS) which is more than 11

million installations. The program runs as a server providing multi-user access to a number of
databases. MYSQL is owned and sponsored by a single for profit firm, the Swedish company
MySQL AB, now a subsidiary of sun Microsystems, which holds the copyright 10 most of
the codebase. The projects source code is available under terms of the GNU General Public
License, as well as under a variety of proprietary agreements.
Microsoft SQL Server 2008 provide following new features for database developers.
 Increase the precision of storing and managing DATE and TIME information.
 Store semi-structured and sparsely populated sets of data efficiently, using Sparse
Columns.
 New fully integrated Full-Text Indexes enable high-performance, scalable, and

manageable Full-Text Indexing.
 Create large User-Defined Types and User-Defined Aggregates greater than 8 KB.
 Pass large amounts of data easily to functions or procedures using new Table-
Value Parameters.
 Perform multiple operations efficiently with the new MERGE command.
 Model hierarchical data, such as org charts, or files and folders, using the new
Hierarchy Id data type.

 Build powerful location-aware applications, using SQL Server’s new standards-

compliant spatial data types and spatial indexing capabilities.
 Manage files and documents efficiently with full SQL Server security and
transaction support, using the powerful new FILESTREAM data type.
 Easily identify dependencies across objects and databases, using New

Dependency Management.
 Experience faster queries and reporting with Grouping Sets through powerful
ANSI standards-compliant extensions to the GROUP BY clause
 Experience efficient, high-performance data access, using new Filtered Indexes

for subsets of data.
ABOUT HTML+CSS
HTML, Hypertext Mark-up Language, gives content structure and meaning by defining
that content as, for example, headings, paragraphs, or images. CSS, or Cascading Style
Sheets, is a presentation language created to style the appearance of content—using, for
example, fonts or colours.
The two languages—HTML and CSS—are independent of one another and should
remain that way. CSS should not be written inside of an HTML document and vice
versa. As a rule, HTML will always represent content, and CSS will always represent
the appearance of that

SYSTEM DESIGN

4.0 SYSTEM DESIGN
Design phase is the phase in which the detailed design of the system selected in the study
phase is accomplished and the user oriented performance specifications is converted in to
technical specifications. The design of a system is correct if a system builds according to the
requirements of that system. The purpose of the design phase is to produce the current
designs. The normal procedure is to define the output required from the system based on the
user requirements. Once this is defined, in details, the input is worked back and appropriate
codes are designed for easy handling of various types of files. Design goes to logical and
physical system of development. Logical Design reviews present physical system, prepares
input and output specifications, make edit, security, control specifications and the detail of
the implementation. A software design is a meaningful engineering representation of some
software product that is to be built. A design can be traced to the customer's requirements and
can be assessed for quality against predefined criteria. In the software engineering context,
design focuses on four major areas of concern: data, architecture, interfaces and components.
The main aim of a system design is to identify the modules that should be in the system, and
the specification of these modules and how they interact with each other to produce the
desired results. Various design specification models are:
 Data design – Created by transforming the analysis information model (data dictionary
and ERD) into data structures required to implement the software. Part of the data
design may occur in conjunction with the design of software architecture. More detailed
data design occurs as each software component is designed.
 Architectural design - Defines the relationships among the major structural elements
of the software, the “design patterns” than can be used to achieve the requirements that
have been defined for the system, and the constraints that affect the way in which the
architectural patterns can be applied. It is derived from the system specification, the
analysis model, and the subsystem interactions defined in the analysis model (DFD).
 Interface design - Describes how the software elements communicate with each other,
with other systems, and with human users; the data flow and control flow diagrams
provide much of the necessary information required.

 Component-level design - Created by transforming the structural elements defined by

the software architecture into procedural descriptions of software components using
information obtained from the process specification (PSPEC), control specification
(CSPEC), and state transition diagram (STD). The Design Principles are: -
1. The design process should not suffer from tunnel vision – A good designer should
consider alternative approaches. Judging each based on the requirements of the problem,
the resources available to do the job and any other constraints.
2. The design should be traceable to the analysis model – because a single element of the
design model often traces to multiple requirements, it is necessary to have a means of
tracking how the requirements have been satisfied by the model.
3. The design should not reinvent the wheel – Systems are constructed using a set of design
patterns, many of which may have likely been encountered before. These patterns
should always be chosen as an alternative to reinvention. Time is short and resources are
limited! Design time should be invested in representing truly new ideas and integrating
those patterns that already exist.
4. The design should minimise intellectual distance between the software and the problem
as it exists in the real world – That is, the structure of the software design should
(whenever possible) mimic the structure of the problem domain.
5. The design should exhibit uniformity and integration – a design is uniform if it appears
that one person developed the whole thing. Rules of style and format should be defined
for a design team before design work begins. A design is integrated if care is taken in
defining interfaces between design components.
6. The design should be structured to degrade gently, even with bad data, events, or
operating conditions are encountered – Well-designed software should never “bomb”. It
should be designed to accommodate unusual circumstances, and if it must terminate
processing, do so in a graceful manner.

7. The design should be reviewed to minimize conceptual (semantic) errors – there is

sometimes the tendency to focus on minute details when the design is reviewed,
missing the forest for the trees. The designer team should ensure that major conceptual
elements of the design have been addressed before worrying about the syntax if the
design model.
8. Design is not coding, coding is not design – Even when detailed designs are created for
program components, and the level of abstraction of the design model is higher than
source code. The only design decisions made of the coding level address the small
implementation details that enable the procedural design to be coded.
9. The design should be structured to accommodate change.
10. The design should be assessed for quality as it is being created.
When these design principles are properly applied, the design exhibits both external
and internal quality factors. External quality factors are those factors that can readily be
observed by the user, (e.g. speed, reliability, correctness, usability). Internal quality factors
relate to the technical quality (which is important to the software engineer) more so the
quality of the design itself. To achieve internal quality factors, the designer must understand
basic design concepts.

4.1 ARCHITECTURAL DESIGN

Architectural design defines the relationship among the major structural elements.
Here the main objective is to develop a modular structure and represent the control
relationship between modules. In the AD phase, the software requirements are transformed
into definitions of software components and their interfaces, to establish the framework of the
software. This is done by examining the SRD and building a 'physical model' using
recognized software engineering methods. The physical model should describe the solution in
concrete, implementation terms. Just as the logical model produced in the SR phase structures
the problem and makes it manageable, the physical model does the same for the solution. The
physical model is used to produce a structured set of component specifications that are
consistent, coherent and complete. Each specification defines the functions, inputs and
outputs of the component.
While the architectural design is a responsibility of the developer, participants in the

AD phase also should include user representatives, systems engineers, hardware engineers
and operations personnel. In reviewing the architectural design, project management should
ensure that all parties are consulted, to minimize the risk of incompleteness and error.
4.2 INPUT DESIGN

Inaccurate input data are the most common cause of errors in data processing. Errors
entered by data entry operators can be controlled by input validation. Input design is the
process of converting user-oriented inputs to a computer-based format. Input design is a part
of an overall system design, which makes the system user friendly. The input design is the
link between the information system and the users. It comprises developing specifications
and those steps that are necessary to put transaction data into a usable form for processing
data entry. The activity of putting data into the computer for processing can be achieved by
instructing the computer to read data from a written or printed document or it can occur by
having people key data directly in to the system. The design of inputs focuses on controlling
the amount of inputs required, controlling errors, avoiding delay, avoiding extra steps and
keeping the process simple.

System analyst decides the following input design details:
 What data to input.
 What medium to use.
 How the data should be arranged or coded?
 The dialogue to guide the users in providing input.
 Methods for performing input validations and steps to follow when error occur.
The input screens are displayed in a way that the user can understand entries very
easily. Proper validation and controlling of input data will reduce the chance of errors. All
major operations are done only after checking the results of confirmation messages. This
makes the system more reliable and user friendly.
4.3 MODULES AND DESCRIPTION
There are four modules in our project
 Administrator
 Farmer
 Buyer
 Visitors
Module 1: Administrator
Administrator can do the following:
 Approve/Revoke user
 View queries
 Manage Blog
 Manage products
 Change password
 Log out

Module 2: Buyer
An approved supplier can do the following
 View/Buy products
 View/Comment/Like/Add Blog
 Update buyer profile
 Change password
 Give feedback
 Log Out
Module 3: Farmer
An Approved farmer can do the following
 View/Buy/Add/Manage Products
 View/Comment/Like/Add Blog
 Update profile
 Change password
 Give feedback
 Log out
Module 4: visitors
A general user can do the following
 View Market
 View Blog
 Give feedback
 Sign up
4.4 OUTPUT DESIGN

Output design generally refers to the results and information that are generated by the
system. For many end-users, output is the main reason for developing the system and the
basis on which they evaluate the usefulness of application. The objective of a system finds its
shape in terms of the output. The analysis of the objective of a system leads to determination
of outputs. Outputs of a system can take various forms.

The most common are reports, screens displays, printed form, graphical drawing etc. The
outputs also vary in terms of their contents, frequency, timing and format. The users of the
output, its purpose and sequence of details to be printed are all considered. The output from a
system is the justification for its existence. If the outputs are inadequate in any way, the
system itself is inadequate.
When designing output, the system analyst must accomplish things like, to determine what
information to be present, to decide whether to display or print the information and select the
output medium to distribute the output to intended recipients. External outputs are those,
whose destination will be outside the organization and which require special attention as the
project image of the organization. Internal outputs are those; whose destination is within the
organization. It is to be carefully designed, as they are the user’s main interface with the
system. Interactive outputs are those, which the user uses in communication directly with the
computer.
4.5 DATABASE DESIGN

Database design is the logical form of design of data storage in the form of records in a
particular structure. Records are organized in the form of tables with fields which are not
transparent to the normal user but it actually acts as the backbone of the system. Database is
a collection of data which helps the system to manage and store data. The software used to
store, manage and retrieve data from database is called database management system. Data
base management system builds some form of constraints like integrity constraints, i.e. the
primary key/ unique key and referential integrity which help to keep data structure storage
and access of data from tables efficiently and accurately and take necessary steps to
concurrent access of data and avoid redundancy of data in tables by normalization criterions.
4.6 USER INTERFACE DESIGN
Designing the visual composition and temporal behaviour of GUI is an important part
of software application programming in the area of human-computer interaction. Its goal is
to enhance the efficiency and ease of use for the underlying logical design of a
stored program, a design discipline known as usability. Methods of user-centred design are
used to ensure that the visual language introduced in the design is well tailored to the tasks.

DATABASE DESIGN

5.1 TABLES
SIGNUP
Sl.no Name Type Constraints
1 signup_id int(11) Primary Key
2 first_name varchar(25) Not Null
3 last_name varchar(25) Not Null
4 email varchar(25) Not Null
5 phone bigint(20) Not Null
6 address varchar(25) Not Null
7 gender varchar(25) Not Null
8 image varchar(25) Not Null
9 login_id int(11) Not Null
LOGIN
sl.no Name Type Constraints
1 login_id int(11) Primary Key
2 user_name varchar(25) Not Null
3 Password varchar(25) Not Null
4 Role varchar(25) Not Null
5 Status int(11) Not Null
Compliant
1 r_id int(11) Primary Key
2 c_id int(11) Not Null
4 Reply varchar(25) Not Null
5 Date Date Not Null

ORDER
sl.no Name Type Constraints
2 order_id int(11) Primary Key
3 order_date Date Not Null
4 crop_id int(11) Not Null
5 Quantity int(11) Not Null
6 Amount int(11) Not Null
Crop
1 crop_id Int(11) Primary Key
2 Image varchar(100) Not Null

3 Crop varchar(20) Not Null
4 category varchar(20) Not Null
5 Verity varchar(50) Not Null
6 Price int(11) Not Null
7 Kilos int(11) Not Null
8 features varchar(100) Not Null
9 Login_id int(11) Not Null
Contact
1 contact_id int(11) Primary Key
2 Name varchar(25) Not Null
3 Email varchar(25) Not Null
4 Phone bigint(20) Not Null
5 message varchar(225) Not Null

Comments
1 c_id int(11) Primary Key
2 blog_id int(11) Not Null
4 Comment varchar(225) Not Null
5 Date Date Not Null
Blog
1 blog_id int(11) Primary Key
3 Title varchar(25) Not Null
4 Image varchar(100) Not Null
5 Content varchar(225) Not Null
6 Likes int(11) Not Null
7 Comment int(11) Not Null
5.2 DATA FLOW DIAGRAMS

A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modelling its process aspects. Often they are a preliminary
step used to create an overview of the system which can later be elaborated. DFDs can also
be used for the visualization of data processing (structured design).
A DFD shows what kinds of information will be input to and output from the system,
where the data will come from and go to, and where the data will be stored. It does not show
information about the timing of processes or information about whether processes will
operate in sequence or in parallel. It is common practice to draw the context-level data flow
diagram first, which shows the interaction between the system and external agents which act
as data sources and data sinks. On the context diagram the system's interactions with the
outside world are modelled purely in terms of data flows across the system boundary.

The context diagram shows the entire system as a single process, and gives no clues as to its
internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows
some of the detail of the system being modelled. The Level 1 DFD shows how the system is
divided into sub-systems (processes), each of which deals with one or more of the data flows
to or from an external agent, and which together provide all of the functionality of the system
as a whole. It also identifies internal data stores that must be present in order for the system to
do its job, and shows the flow of data between the various parts of the system. Data flow
diagrams were proposed by Larry Constantine, the original developer of structured design,
based on Martin and Estrin's "data flow graph" model of computation.
The lower level diagrams are called ‘First Level DFDs’, ‘Second Level DFDs’, and so
on. Because the nature complexity of system varies, a specific number of levels of DFDs
cannot be fixed. Very complex data flow diagrams cause difficulty to understanding hem. On
the other hand, if they are under exploded, errors or mission could occur.
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 time.
 Choose meaningful names for data flow
 Draw all data flows around the outside of the diagram
To construct a Data Flow Diagram, we use certain symbols, each one has a
meaning. The various notations used to represent the DFD in Yourdon methodology are as
follows:
DATA FLOW
Data in a system move direction that is from origin to destination. The data flow is a
packet of data indicating the movements of data within the system. Data flow must be inputs
to or outputs from processes. They must contain data and all data flows should be labeled
indicating what data is flowing.

Data flow is represented as follows
PROCESS
The emphasis in a DFD is placed on processing. Processing transforms input to

outputs. They will do an action that is performed by people, machines, or computers on
incoming data flow to producing outgoing data flows. The details of the logic or procedures
are not shown in a DFD.
Process is represented as follows:
EXTERNAL ENTITIES
External entities are organizations, other information systems, departments or people

that represent a source or destination of transactions or data. External entities entity
represents any entity that supplies or receives information from the system but is not a part of
the system. Each entity is labeled with an appropriate name. Although it interacts with the
system, it is considered as external to the boundaries of the system.
External entity is represented as follows:

DATA STORE
Data store can be considered as the memory of the system. Any place that data
accumulate is the data store. Data flow diagrams do not specify the type of physical storage.
The data in the data store are stored or referenced by a process in the system. The data store
must have a label, which is placed between the two parallel lines, which should clearly
identify what the data store contains as a class object.
Data store is represented as follows:
Data flow
Level 0 (Context Diagram) DFD for Future farm
Level 1 DFD

Level 2 DFD for Blog
Level 2 DFD for Contact Us
Level 2 DFD for login

Level 2 DFD for logout
Level 2 DFD for market
Level 2 My products

Level 2 DFD for profile
Level 2 DFD for signup

SYSTEM TESTING

6.0 SYSTEM TESTING

Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly for the software. Testing is vital to the success of the system. Errors can be injected
at any stage during development. System testing makes a logical assumption that if all
the parts of the system are correct, the goal will be successfully achieved.
During testing, the program to be tested is executed with set of test data and
the output of the program for the test data is evaluated to determine if the program
is performing as expected. A series of testing are performed for the proposed system
before the system is ready for user acceptance testing. Another reason for system testing
is its utility as a user-oriented vehicle before implementation.
TYPES OF TESTING
The different types of testing are as follows:

 Unit Testing
 Integration Testing
 Validation Testing
 System Testing
 User Acceptance Testing
6.1 UNIT TESTING
In computer programming, unit testing is a method by which individual units of

source code, sets of one or more computer program modules together with associated
control data, usage procedures, and operating procedures, are tested to determine if they are
fit for use. Intuitively, one can view a unit as the smallest testable part of an application.

In procedural programming a unit could be an entire module but is more commonly an

individual function or procedure. In object-oriented programming a unit is often an entire
interface, such as a class, but could be an individual method. Unit tests are created by
programmers or occasionally by white box testers during the development process. Ideally,
each test case is independent from the others: substitutes like method stubs, mock objects,
fakes and test harnesses can be used to assist testing a module in isolation. Unit tests are
typically written and run by software developers to ensure that code meets its design and
behaves as intended. Its implementation can vary from being very manual (pencil and
paper) to being formalized as part of build automation. The goal of unit testing is to isolate
each part of the program and show that the individual parts are correct. A unit test provides
a strict, written contract that the piece of code must satisfy. As a result, it affords several
benefits.
6.2 INTEGRATION TESTING
Integration testing (sometimes called Integration and Testing, abbreviated "I&T") is

the phase in software testing in which individual software modules are combined and tested
as a group. It occurs after unit testing and before validation testing. Integration testing takes
as its input modules that have been unit tested, groups them in larger aggregates, applies
tests defined in an integration test plan to those aggregates, and delivers as its output the
integrated system ready for system testing.
The purpose of integration testing is to verify functional, performance, and reliability

requirements placed on major design items. These "design items", i.e. assemblages (or
groups of units), are exercised through their interfaces using Black box testing, success and
error cases being simulated via appropriate parameter and data inputs. Simulated usage of
shared data areas and inter-process communication is tested and individual subsystems are
exercised through their input interface. Test cases are constructed to test that all
components within assemblages interact correctly, for example across procedure calls or
process activations, and this is done after testing individual modules, i.e. unit testing. The
overall idea is a "building block" approach, in which verified assemblages are added to a
verified base which is then used to support the integration testing of further assemblages.

6.3 VALIDATION TESTING

Verification testing runs the system in a simulated environment using simulated data.
This simulated test is sometimes called alpha testing. This simulated test is primarily
looking for errors and motions regarding end user and decisions design specifications that
where specified in the earlier phases but not fulfilled during construction.
Validation refers to the process of using software in a live environment in order to

find errors. The feedback from the validation phase generally produces changes in the
software to deal with errors and failures that are uncovered. Than a set of user sites is
selected that puts the system in to use on a live basis. They are called beta tests. The beta
test suits use the system in day-to-day activities. They process live transactions and produce
normal system output. The system is live in every sense of the word; except that the users
are aware they are using a system that can fail. But the transactions that are entered and
persons using the system are real. Validation may continue for several months. During the
course of validating the system, failure may occur and the software will be changed.
Continued use may produce additional failures and need for still more changes.
6.4 SYSTEM TESTING

The code is tested at various levels in software testing. Unit, system and user
acceptance testing are often performed. This is a grey area as many different opinions exist
as to what the stages of testing are and how much, if any iteration occurs. Iteration is not
generally part of the waterfall model, but usually some occur at this stage. In the testing the
whole system is test one by one. Developers have to make sure their created programs will
work well in different environments. The traditional way of testing usually needs testers so
that the program will be exploited in different manner.
On the other hand, some software developers do not use testers for their program
rather developers get normal and intended users to test their program. They do not just
implement the program to everyone though, they implement the program in restricted
manner so that they can monitor to software’s performance and make the necessary
adjustments even before the software is released for general public.

The testing stage even expands to the idea of implementing the software in beta testing just
to make sure it can withstand multiple users at the same time.
6.5 USER ACCEPTANCE TESTING

User acceptance testing of the system is the key factor for the success of any system.
As we have created any easy interface it is easy to use. Only tough portion is the information
to be perfect and has only one kind of user that the administrator. The system under
consideration is tested for user acceptance by constantly keeping in touch with prospective
system at a time of the development and making change whenever required. This is done with
regard to the input screen design and output screen design.

SYSTEM IMPLEMENTATION

7.1 IMPLEMENTATION
Implementation includes placing the system into operation and providing the users
and operation personnel with the necessary documentation to use and maintain the new
system. Implementation includes all those activities that take place to convert from the old
system to the new. The new system may be totally new, replacing an existing system. Proper
implementation is essential to provide a reliable system to meet the organizational
requirements. Successful implementation may not guarantee improvement in the organization
using the new system, as well as, improper installation will prevent. There are four methods
for handling a system conversion. Parallel approach: The old system is operated with the new
system. Direct cut over method: The old system is replaced with the new system. Pilot
approach: Working version of the system is implemented in one part of the organization
based on the feedback, changes are made and the system is installed in the rest of the
organization by one of the other methods. Phase-in-method: Gradually implements the
system across all users. We have used the direct cut over method in our implementation.
7.2 PROBLEM STATEMENT

The project implements the functionalities of a social networking site in an easy and
user-friendly manner.
7.3 PROBLEM DESCRIPTION

There is wide variety of social networking sites. Our aim is to provide an
understanding about the working of a social networking site as a beginner.
7.4 FEATURES OF THE PROJECT

 The system employs GUI and is user friendly.
 The system is maximally maintainable and extensible.
 Less computer knowledge is required.

FUTURE ENHANCEMENT

8.0 FUTURE ENHANCEMENT
 Farm management store has many advantages and disadvantages. However the
advantages of the system that is helps to reach more time and less effort.
 The disadvantages includes the inaccurate results and information. In further we have
to overcome the following problem of this system.
• Expensive and time Consuming
• Accuracy of forecast
 The project “Future Farm” can be further enhanced to provide greater flexibility and
performance.
 We can modify the existing system by adding new features that are required in that
period.
 This system can be modified to a web based software so that, it can connect different
parts of an organization and make access easy.
 Considering this important factor, the system is designed in such a way that
provisions can be given for future enhancement without affecting the system presently
developed.
 Increase security.

CONCLUSION

9.0 CONCLUSION
This System has remained devoid of web technology, with most works being carried
out on a pen and paper basis. This traditional method is prone to delays and inefficiency. This
paper proposes to simplify and speed up the process of compliant registration and tracking.
With the advancement and incorporation of internet and web technology into the Indian
Police System, it will definitely boost up the proceedings. This paper aims to help the public
and the police officers alike.
We are attempted to develop a web application titled “Future Farm” that is easily
accessible, informative and helpful to all .It has been designed in such a way that is easy to
modify, can be updated efficiently and accurately. The forms are designed in a user-
friendly manner by providing messages and captions whenever necessary, so that the users
have no problem to overcome difficulties in data entry, validation, modification etc. The
system is designed in such a way that addition of new modules can be done in very simple
and efficient manner. The system is feasible enough for amendments and modifications
that may arrive in future.

BIBLIOGRAPHY

10.0 REFERENCES:
TEXT BOOKS
 PHP & MYSQL Web Development – by Luke Welling & Laura Thompson.
 PHP: A Beginner’s Guide – by Vikram Vaswani.
• Software Engineering: A Practitioner’s Approach, Seventh Edition: Roger S.

Pressman
• Database System Concepts: Fifth Edition, Avi Silberschatz,

Henry F. Korth, S. Sudarshan
• Advanced PHP Programming: George Schlossnagle, Pearson Education
• PHP and MYSQL Web Development- Luke Welling & Laura Thomson, Pearson
Education
• Beginning PHP5: 2005 edition-WROX publication.
WEB REFERENCE
• http://www.w3schools.com
• http://www.wikipedia.com

Future Farm Project Report

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

Future Farm Project Report

Uploaded by

Copyright:

Available Formats

FUTURE FARM: ONLINE FARMING SOLUTIONS 1

Ajay Cherian (Reg: 170021093721)

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

I extend my sincere gratitude to Mr. Tony Mathews Panicker, Head of the

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

1.1 PROJECT OVERVIEW

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

2.1 PRELIMINARY ANALYSIS

2.2 EXISTING SYSTEM

DISADVANTAGES OF EXISTING SYSTEM

 Communication and file handling is not easy.

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

2.3 PROPOSED SYSTEM

The proposed system is a dynamic user-friendly and interactive website. It should

The advantages of the proposed system are:

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

2.4 FEASIBILTY STUDY

Feasibility study may be documented as a separated report to higher officials of the

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

Three key combinations are involved in the feasibility study:

2.4.1 ECONOMICAL FEASIBILITY

2.4.2 TECHNICAL FEASIBILITY

 Does the necessary technology exist to do what is been suggested?

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

2.4.3 BEHAVIOURAL FEASIBILITY

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

2.4.4 OPERATIONAL FEASIBILITY

 Will the system be used if it developed and implemented?

This application can be implemented in an organization because there is adequate support

2.5 ADVANTAGES OF THE PROPOSED SYSTEM

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

3.1 SOFTWARE SPECIFICATION

Technology used : PHP version 5.2.5

Front end : HTML+ CSS

Back end : PHP

RDBMS : MySQL 5.0.1

3.2 HARDWARE SPECIFICATION

Processor : Intel Core 2 Duo

3.3 ABOUT THE DEVELOPING TOOLS

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

MICROSOFT SQL SERVER 2008

MySQL is a relational database management system (RDBMS) which is more than 11

 New fully integrated Full-Text Indexes enable high-performance, scalable, and

 Perform multiple operations efficiently with the new MERGE command.

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

 Build powerful location-aware applications, using SQL Server’s new standards-

 Easily identify dependencies across objects and databases, using New

 Experience efficient, high-performance data access, using new Filtered Indexes

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

4.0 SYSTEM DESIGN

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

 Component-level design - Created by transforming the structural elements defined by

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA

7. The design should be reviewed to minimize conceptual (semantic) errors – there is

9. The design should be structured to accommodate change.

10. The design should be assessed for quality as it is being created.

DEPARTMENT OF COMPUTER APPLICATIONS CHRIST COLLEGE, PULIYANMALA