Pbl Project Ce
Pbl Project Ce
CERTIFICATE
This is to certify that the project-based seminar report entitled
“AGRICULTURE FARM MANAGEMENT SYSTEM” being submitted by Vikas Salunke ,
Shubham Supalakar is a record of bonafide work carried out by her/his under the
supervision and guidance of Prof. Varsha Raule in fulfillment of their requirement for SE
(Computer Engineering)–2019 course of Savitribai Phule Pune University, Pune in the
academic year 2024-2025.
EXTERNAL PRINCIPAL
Acknowledgement
We express our sincere thanks to all those who have provided us the valuable
guidance towards the successful completion of this system as a part of syllabus for the
bachelor‘s course. We express our sincere gratitude towards our co-operative department for
providing us with altheas valuable assistance and equipment for the system development.
We hereby take this opportunity to sincerely thank Prof. Varsha Raule for her valuable
guidance, inspiration, whole hearted involvement during every stage of this project and his
experience, perception through professional knowledge which made it possible for us in
successfully realizing the concept
We also thankful to Prof. Vishal Puranik HOD C.E. - PGMCOE, Wagholi for
his his constant enlightenment, support and motivation which has been highly instrumental
in successful completion of our project.
We are extremely thankful to Principal – PG Moze COE, Wagholi for his
encouragement and providing us the opportunity and facilities to carry out this work.
Finally, we like to express our deep sense of gratitude towards our parents, friends and well-
wishers who were always there for suggestions and help.
1. Introduction
1
1.1 System Introduction
1.2 Problem Statement
1.3 Motivation
1.4 Objectives
2. Design Specifications
3
1.1 Introduction about ER Diagram
1.2 Introduction about Relational Model
1.3 Data Requirements
3. ER Diagram
4. Relational Diagram
5. Database Creation
6. Conclusion
7. References
CHAPTER 1
INTRODUCTION
The Agriculture Farm Management System (AFMS) is an innovative software solution designed to
streamline and optimize farm operations, enhancing productivity and sustainability in the agricultural sector.
This system integrates various aspects of farm management, including crop planning, resource allocation,
irrigation scheduling, pest and disease monitoring, and yield forecasting. By leveraging data-driven insights
and real-time analytics, AFMS empowers farmers to make informed decisions, reduce operational costs, and
maximize crop yields. The system is built to be user-friendly, accommodating both tech-savvy individuals
and those with limited digital literacy, ensuring accessibility across diverse farming communities.
The primary users of the Agriculture Farm Management System include farmers, agronomists, farm
managers, agricultural consultants, and researchers. Farmers benefit from tools that assist in crop
management, resource optimization, and financial tracking. Agronomists and consultants use the system for
data analysis, recommending best practices for soil health, pest control, and crop rotation. Farm managers
utilize AFMS for scheduling, monitoring field activities, and managing labor efficiently. Additionally,
agricultural researchers apply the system to study trends, analyze environmental impacts, and develop
sustainable farming techniques. The application areas of AFMS are vast, spanning commercial farms,
smallholder farms, agribusinesses, and agricultural research institutions, making it a versatile tool in the
modern agricultural landscape.
1.2 Problem Statement
The traditional methods of farm management often rely on manual processes, leading to inefficiencies, poor
resource utilization, and limited data-driven decision-making. Farmers face challenges in tracking crop
performance, managing resources effectively, monitoring pest and disease outbreaks, and optimizing
irrigation schedules, which can result in reduced yields and increased operational costs. Additionally, the
lack of real-time data and analytical tools hinders the ability to respond quickly to changing environmental
conditions and market demands. The Agriculture Farm Management System aims to address these issues by
providing an integrated, data-driven platform that enhances productivity, improves resource management,
and supports sustainable agricultural practices.
1.3 Motivation
The motivation behind developing the Agriculture Farm Management System stems from the growing need
to modernize farming practices and address the challenges faced by farmers in managing their operations
efficiently. Traditional farming methods often lack the integration of technology, leading to suboptimal
resource use, inconsistent crop yields, and increased vulnerability to environmental factors. Our aim is to
empower farmers with a user-friendly, data-driven platform that enhances decision-making, optimizes
resource allocation, and promotes sustainable agricultural practices. By leveraging technology, we seek to
improve productivity, reduce costs, and support the long-term viability of farms, ultimately contributing to
food security and agricultural resilience in the face of global challenges.
1.4 Objectives
1.Efficient Farm Planning & Management – Provide tools for farmers to plan and manage their farm
activities, including crop rotation, soil health monitoring, and resource allocation.
2. Automation & Data-Driven Decisions – Use data analytics and automation to optimize irrigation,
fertilization, and pest control, improving productivity and reducing costs.
3. Inventory & Resource Tracking – Keep records of seeds, fertilizers, pesticides, and equipment to ensure
efficient usage and timely replenishment.
4. Financial Management & Reporting – Track farm expenses, revenue, and profits with financial reports,
helping farmers make informed financial decisions.
5 .Weather & Market Insights – Integrate real-time weather forecasts and market price trends to help
farmers make strategic planting and selling decisions.
6.Sustainability & Compliance – Promote eco-friendly farming practices and ensure compliance with
agricultural regulations for sustainable farm operations.
CHAPTER 2
DESIGN SPECIFICATION
2.1 Introduction about ER Diagram
An Entity Relationship Diagram (ERD) is a conceptual blueprint of a database that represents the
structure and organization of data. It visually displays entities (objects or things in the system), their
attributes (properties), and the relationships between those entities. ER diagrams are widely used during
the database design phase of system development to ensure that the data is logically organized and
efficiently accessible.
In an ERD:
Entities are usually drawn as rectangles and represent real-world objects (e.g., Farmer, Buyer,
Product).
Attributes are represented as ovals and are connected to their respective entities (e.g., farmer name,
product price).
Relationships are shown with diamonds and illustrate how entities are associated with each other
(e.g., a Buyer "places" an Order).
The Relational Model is a fundamental concept in database management that organizes data into relations,
commonly known as tables. Each table consists of rows and columns, where:
The relational model is based on mathematical set theory and first-order predicate logic, which makes it
highly structured, consistent, and easy to query using Structured Query Language (SQL).
Primary Keys: Unique identifiers for each row in a table (e.g., fid for Farmer, pid for Product).
Foreign Keys: Attributes that link one table to another, establishing relationships (e.g., fid in the
fproduct table refers to the farmer table).
Data Integrity: Enforced through constraints like NOT NULL, UNIQUE, and FOREIGN KEY.
Normalization: Process of organizing data to minimize redundancy and dependency.
In the context of the agriculture e-commerce system, the relational model translates the ER diagram into a
working database by:
A farm management system requires a comprehensive and well-structured database to support its core
operations, decision-making, and reporting capabilities. The system must be able to store and manage
diverse types of data related to various stakeholders and activities within the agricultural environment. This
includes maintaining detailed records of farmers, including their personal details, land information, and the
types of crops or livestock they manage. It should also track resources such as equipment, fertilizers,
pesticides, and labor used during farming activities. The system must support data for crop planning,
including sowing dates, growth cycles, irrigation schedules, and expected harvest periods. Additionally,
inventory management is essential for keeping track of input stock levels and produce outputs. Financial
data is also crucial — the system should handle expenses, income, sales records, and transactions with
buyers or suppliers. If the system includes a marketplace or customer interaction, buyer information,
orders, and feedback should also be recorded. Finally, the system should enable report generation,
analysis, and alerts for better decision-making, helping farmers optimize productivity and sustainability.
INT: Used for numerical identifiers such as farmer ID (fid), buyer ID (bid), product ID (pid), etc.
VARCHAR: Used for strings such as names, usernames, email addresses, and mobile numbers.
TEXT: Used for long-form content like blog posts or user comments.
BOOLEAN: Used for status fields such as factive or bactive, indicating if a user is active.
DATE/TIMESTAMP: Used for tracking time-based data like blog creation time and comment
timestamps
2.3.2 Entities in ER Diagram
Entities are objects or concepts within the system that have a distinct existence and need to be represented in
the database. Here are some of the main entities in an Online Agricultural Product Store:
1. Customer
o Represents a user who shops through the online agricultural store.
o Includes attributes such as: First Name, Last Name, Mobile No, Address, DOB.
2. Payment
o Represents the payment method used by the customer.
o Includes attributes like: Debit/Credit, Net Banking, Cash on Delivery, UPI.
3. Product Cart
o Represents a temporary storage for products selected by the customer.
o Includes attributes such as: Delivery Address, Edit Item, Save for Later.
4. Product
o Represents a specific item available for sale in the store.
o Includes attributes like: Product Name, Quantity, Total Price.
5. Agricultural Product Information/Catalog
o Represents the master catalog of all available products.
o Includes attributes such as: Product ID, Product Name, Price.
6. Online Agricultural Product Store
o Represents the overall system where the customer logs in and purchases products.
o Connected to other entities such as Product Catalog and Customer.
Attributes describe the properties or characteristics of an entity. Below are some examples of attributes
associated with various entities in the Online Agricultural Product Store:
1. Customer
o First Name
o Last Name
o Mobile No
o Address
o DOB
2. Payment
o Debit/Credit
o Net Banking
o Cash on Delivery
o UPI
3. Product Cart
o Delivery Address
o Edit Item
o Save for Later
4. Product
o Product Name
o Quantity
o Total Price
5. Agricultural Product Information/Catalog
o Product ID (Primary Key)
o Product Name
o Price
2.3.4 Types of Relation in ER Diagram
Relationships illustrate how entities are connected in the system. Here are the main types of relations in the
Online Agricultural Product Store ER Diagram:
1. Login
o A customer logs in to the Online Agricultural Product Store.
o Relationship between: Customer and Online Store
2. Does
o Represents the action where a customer makes a payment.
o Relationship between: Customer and Payment
3. Proceeds
o A successful payment results in a cart being generated or updated.
o Relationship between: Payment and Product Cart
4. Adds To
o A product is added to a customer’s cart.
o Relationship between: Product and Product Cart
5. Adding
o Represents products being added into the product catalog.
o Relationship between: Agricultural Product Catalog and Product
6. Has
o Indicates that the Online Store contains a product catalog.
o Relationship between: Online Agricultural Product Store and Product Catalog
Functional dependencies indicate how one attribute or a set of attributes uniquely determines another. Here
are the key dependencies in the system:
6. Internal documents and annual reports from agro and transport service organizations.