CHAPTER I: INTRODUCTION 4

1.1 Introduction....................................................................................................................................4

1.3 Objectives of the Project.................................................................................................................4

1.4 Scope of the Project........................................................................................................................4

1.5 Methodology/Procedure..................................................................................................................4

1.7 Project Framework........................................................................................................................4

1.8 Data and Information.....................................................................................................................5

1.9 Primary Source of Data..................................................................................................................5

1.10 Secondary Source of Data.............................................................................................................5

1.11 Tools Used......................................................................................................................................5

1.12 Testing............................................................................................................................................6

1.12.1 Unit Testing.................................................................................................................................6

1.12.2 Integration Testing.....................................................................................................................6

1.12.3 System Testing............................................................................................................................6

CHAPTER II: TASK AND ACTIVITIES PERFORMED 7

2.1 System Analysis...............................................................................................................................7

2.3 Problem Analysis.............................................................................................................................7

2.3.1 Design and Development Problem..............................................................................................7

2.4 Feasibility Analysis..........................................................................................................................8

2.4.1 Economical Analysis.....................................................................................................................8

2.4.2 Software Analysis.........................................................................................................................8

2.4.3 Data Conversion...........................................................................................................................8

1
2.4.4 Operational Feasibility.................................................................................................................8

2.5 Use case Diagram............................................................................................................................9

2.6 Sequence Diagram...........................................................................................................................9

2.7 Activity Diagram...........................................................................................................................11

2.9 ER Diagram...................................................................................................................................12

2.10 Gantt Chart..................................................................................................................................13

2.12 Findings........................................................................................................................................14

2.12.1 Application’s Output................................................................................................................14

2.12.1.1 Backend..................................................................................................................................14

2.12.1.2 Frontend.................................................................................................................................14

List of Figure

Figure 1: Use Case Diagram.....................................................................................................................9

Figure 2:Sequence Diagram..................................................................................................................10
Figure 3: Activity Diagram.....................................................................................................................11
Figure 4: ER Diagram.............................................................................................................................12
Figure 5: Gantt Chart.............................................................................................................................13
Figure 6: Farmer/ Buyer Login...............................................................................................................14
Figure 7: Member Login........................................................................................................................15
Figure 8 Home Page..............................................................................................................................15
Figure 9: Member Log out.....................................................................................................................16

2
3
 CHAPTER I: INTRODUCTION

1.1 Introduction
Agro Culture is the farmer system where they can plan, monitor and analyze the activity of the farmers
production system. It manages farmer operation with one system and organizes data in one place. It
helps smart farmers become even smarter. This creates in partnership with growers and buyers. It
inspire farmer to produce and buyers to consume fresh goods.

Agro Culture System will make better connection among Farmers and Buyers ensure quality food.
Standardize and increase efficiency of agro culture process.

1.3 Objectives of the Project

The specific objectives of the project include:

 To provide qualitative foods to the buyers.

 Implementing an automated/online agro culture system.

 To inspire farmer to produce quality goods and supply to the buyers.

 Eco-friendly farming system.

1.4 Scope of the Project

It is focused on studying the existing system of agro culture in and to make sure that the peoples are
getting quality fresh goods. This is also will produce:

 Less effort and less labor intensive, as the primary cost and focus primary on creating,
managing, and running a secure quality food supply.

 Increasing number of buyers as individuals will find it easier and more convenient to buy
goods.

 Easy management.

1.5 Methodology/Procedure
4
  For the development of project the designing of database was done on PHPMYADMIN, back
end was coded in basic PHP and for frontend we used the same basic PHP codes.

 Software methodologies are concerned with the process of creating software – not so much the
technical side but the organizational aspects. Several software development approaches have
been used since the origin of information technology.

1.7 Project Framework

A framework is a standardized set of concepts, practices, and criteria for dealing with a common type
of problem, which can be used as a reference to help us approach and resolve new problems of a
similar nature.

The aim of framework is to provide a common structure so that developers don’t have to redo it from
scratch and can reuse the code provided. In this way, frameworks allows us to cut out much of the
work and save a lot of time

1.8 Data and Information

Data collection plays an important role in a projects succession and also it plays an inevitable role in
the timely completion of the project. The data in the project includes contact information of the clients
and their respective feedbacks/complaints which is stored in a database. To assure safety, only the
admin has proper access to the information provided by the clients.

1.9 Primary Source of Data

Primary data are the first hand data. The necessary information was collected from day to day
observation, problems, instructions of supervisor. Queries and personal discussion with the staff of the
organization.

 Observation of working environment

 Informal discussion and interaction with the staff of the library department

1.10 Secondary Source of Data

The Secondary sources of data were collected in order to achieve the real and fact data as far as
available. The major sources of secondary data are as follows:

 Annual reports of the concerned organization

 Related websites

1.11 Tools Used

 Xampp:
5
 o Apache:
 (Application Server) Apache , often referred to as Server, is an open-source
Java Servlet Container developed by the Apache Software Foundation.
o MySqlServer:
 It handles larege databases much faster than existing solutions.
 It consists of multi-threaded SQL server that supports different back ends,
several different client programs and libraries, administrative tools, and
application programming interfaces (APIs)
 Its connectivity, speed, and security make MySQL Server highly suited for
accessing databases on the Internet.
 Sublime Text 3.1.1- Sublime Text is a sophisticated text editor for code, markup and prose.
You'll love the slick user interface, extraordinary features and amazing performance.
 Web browsers: Google Chrome,Mozilla Firefox, Opera and Internet Explorer.
 Git Hub: GitHub Inc. is a web-based hosting service for version control using Git. It is mostly
used for computer code. It offers all of the distributed version control and source code
management functionality of Git as well as adding its own features.

1.12 Testing
Testing is evaluation of the software against requirements gathered from users and system
specifications. Testing identifies important defects, flaws, or an error in the application code that must
be fixed .It also assesses the feature of a system. Testing assesses the quality of the product.

1.12.1 Unit Testing

Unit testing refers to the testing certain functions and areas of the code. It gives the ability to verify that
all the functions work as expected. Eventually, it helps to identify failures in the algorithms as well as
logic to help improve the quality of the code that composes a certain function.

1.12.2 Integration Testing

Integration testing is basically a logical extension of unit testing. In simple words, two tested units are
combined into a component and the interface between them is tested. It identifies problems that occur
when different units are combined The different modules of this project have undergone integration
testing while being merged.

1.12.3 System Testing

System testing tests the behavior of whole system as defined by the scope of the development project.
It might include tests based on risks as well as requirement specifications, business process, use cases
or other high level descriptions of system behavior, interactions with the operating systems and system
resources. It is most often the final test performed to verify that the system meets the specification and
its objectives. System testing has been performed at the completion of each feature and is still taking
place to make improvements on the existing system.

6
 CHAPTER II: TASK AND ACTIVITIES PERFORMED

2.1 System Analysis

System Analysis is a detailed study of the various operations performed by a system and their
relationships within and outside of the system. Here the key question is- why all problems exist in the
present system? What must be done to solve the problem? Analysis begins when a user or manager
begins a study of the program using existing system. During analysis, data collected on the various
files, decision points and transactions handled by the present system. The commonly used tools in the
system are Data Flow Diagram etc. Training, experience and common sense are required for collection
of relevant information needed to develop the system. The success of the system depends largely on
how clearly the problem is defined, thoroughly investigated and properly carried out through the
choice of solution. A good analysis model should provide not only the mechanisms of problem
understanding but also the frame work of the solution. Thus it should be studied thoroughly by
collecting data about the system. Then the proposed system should be analyzed thoroughly in
accordance with the needs. System analysis can be categorized into four parts.
 System planning and initial investigation
 Information Gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis.
In our existing system the recording of user’s information is done manually, So taking more time for
searching the information of the users. Another major disadvantage is that preparing the list of
members that viewed any user’s information takes more time. So, after conducting the feasibility study
I decided to make the agro culture System to be computerized.

2.3 Problem Analysis

It is related with the accessing the detailed information of a user and a candidate. So, I have initiated
this project with simple requirements regarding the user and candidate information. Some of the
problems for designing and developing this project are discussed below:

2.3.1 Design and Development Problem

 Problem in running XAMPP.

7
  To debug the error during the development.
 To show a relationship between entity.
 Minor error with database table.

2.4 Feasibility Analysis

A feasibility analysis is conducted once the problem is clearly understood. The purpose of the study is
to determine whether the problem is worth solving. It is an analysis and evaluation of a proposed
project to determine if it is technically feasible, feasible with the estimated cost and profitable.

2.4.1 Economical Analysis

The economic feasibility of a system is used to evaluate the benefits achieved from and the costs
incurred for the project or system. This is done by a process called cost benefit analysis.  It provides
tangible and intangible benefits like reduction in cost, more flexibility, faster activities, proper database
management, etc.

The application is medium scale application and is economically feasible for us to accomplish it. This
involves cost benefits analysis. Thus there is no problem of high cost and cost benefits analysis.

2.4.2 Software Analysis

● Consumes a long-time for development of web application.
● Research and analysis cost to determine the actual need in real world.
● Implementation of application in the server and cost associated with the space in server.

2.4.3 Data Conversion

Another cost associated while implementing this web application is the data conversion. The
previously used software database must be stored and backup such that there will be no loss in
implementing a new web application which consumes time as well as money.

2.4.4 Operational Feasibility

The system is operational feasible as the system can be operate by normal users with basic computer
skills without any additional trainings. We have developed this system with the willingness and ability
to create, manage and operate the system which is easy for the end users to operate it.

8
2.5 Use case Diagram

Figure 1: Use Case Diagram

Above figure represents Use Case Diagram of the project and is a useful technique for identifying,
clarifying, and organizing system requirements. It describes how a user uses a system to accomplish a
particular goal. Use cases help ensure that the correct system is developed by capturing the
requirements from the user's point of view.

2.6 Sequence Diagram

A sequence diagram is a type of interaction diagram because it describes how—and in what order—a
group of objects works together. A sequence diagram specifically focuses on lifelines, or the processes
and objects that live simultaneously, and the messages exchanged between them to perform a function
before the lifeline ends.

9
 Figure 2:Sequence Diagram
Above diagram represents Sequence Diagram of the project which is a type of interaction diagram
because it describes how—and in what order—a group of objects works together. A sequence diagram
specifically focuses on lifelines, or the processes and objects that live simultaneously, and the
messages exchanged between them to perform a function before the lifeline ends.

10
2.7 Activity Diagram

Figure 3: Activity Diagram

Above diagram describes the flow of control of a system. The flow can be sequential, concurrent or
branched showing the overall functions of the system.

11
2.9 ER Diagram

Figure 4: ER Diagram
ER diagram show all the relationships between entity sets stored in the database. It illustrates the
logical structure of the database. It helps to visualize how data is connected in general ways.

12
2.10 Gantt Chart

Figure 5: Gantt Chart

A Gantt chart illustrates how the project will run. It communicates with the client and shows them the
expected date of project completion. It helps you assess how long a project should take, determine the
resources needed, and plan the order in which you'll complete task.

13
2.12 Findings
After a series of testing and debugging, the project was ready for projection and is believed that it will
achieve the goals that it is designed to get, which is to vote in ease.

2.12.1 Application’s Output

2.12.1.1 Backend

Figure 6: Farmer/ Buyer Login

2.12.1.2 Frontend

14
Figure 7: Member Login

Figure 8 Home Page

15
Figure 9: Member Log out

16