Dbms REPORT Final
Dbms REPORT Final
CERTIFICATE
This is to certify that the Mini Project work entitled “CROP MANAGEMENT SYSTEM” is a
bonafide work has been carried out by Mr. NISHANTHA K S (1BY20CS127) and Mr.
PRAMATH V BHAT (1BY20CS137), bonafide students of BMS Institute of Technology and
Management, Autonomous Institute Affiliated to VTU, in partial fulfillment for the award of
Bachelor of Engineering Degree in Department of Computer Science and Engineering during
the year 2022-23. It is certified that all corrections/suggestions indicated for Internal Assessment
have been incorporated in this report. The Mini project report has been approved as it satisfies the
academic requirements in respect of Mini project work for the B.E Degree.
The purpose of Crop Management System is to automate the existing manual system by the
help of computerized equipment and full-fledged computer software, fulfilling their requirements, so
that their valuable data/information can be stored for a longer period with easy accessing and
manipulation of the same. The required software and hardware are easily available and easy to work
with.
Crop Management System, as described above, can lead to error free, secure, reliable and fast
management system. It can assist the user to concentrate on their other activities rather to
concentrate on the record keeping. Thus, it will help organization in better utilization of resources.
The organization can maintain computerized records without redundant entries. That means that one
need not be distracted by information that is not relevant, while being able to reach the information.
Basically, the project describes how to manage for good performance and better services for the
clients.
Computers are extensively used in every industry today, primarily because of its reliability
and precision. Computers are able to process huge amounts of data at lightning speed, without
compromising in any way on the quality or reliability or accuracy of produced results.
With the use of this platform, it is possible to store the information about the crops which are
grown by the farmer and to ship it for the delivery, and customers can order the crops according to
their requirements. Also, this is used to maintain the record of crops distribution across the country.
For example, if the farmer from a particular region like Karnataka login to the portal and upload the
detail of the crops which he/she has been grown with the price of that crop. Then the admin can use
that data for data analytics of flora distribution in the world and also normal users who login as
customer can order the product whichever he/she wanted without need of the mediator. By this way
the platform act as two-way communication medium without the intervention of middle men in the
business.
Crop management system (AGROMAP) is a standard for handling, storing, and transmitting
information of crops which are open for sale. AGROMAP can be used to exchange the information
of the crops available in the market by the farmer to customer. Farmers will set the price for their
products with quantity available. And customer have the option to order the products according to
their need. This way AGROMAP helps in avoiding brokers in agriculture.
i
ACKNOWLEDGEMENT
We are happy to present this Mini project after completing it successfully. This project would not
have been possible without the guidance, assistance and suggestions of many individuals. I would
like to express my deep sense of gratitude and indebtedness to each and every one who has helped
me to make this project a success.
We heartily thank our Principal, Dr. MOHAN BABU G N, BMS Institute of Technology &
Management, Autonomous Institute Affiliated to VTU for his constant encouragement and
inspiration in taking up this Mini project.
We heartily thank our Head of the Department, Dr. Thippeswamy. G, Dept. of Computer Science
and Engineering, BMS Institute of Technology & Management, Autonomous Institute
Affiliated to VTU for his constant encouragement and inspiration in taking up this Mini project.
We gracefully thank our Project guide, Mrs. Ambika G.N, Assistant Professor, Dept. of Computer
Science and Engineering, for her encouragement and advice throughout the course of the Mini
Project work.
Special thanks to all the staff members of Computer Science Department for their help and kind co-
operation.
Lastly, we thank our parents and friends for their encouragement and support given to me in order to
finish this Mini Project work.
By,
NISHANTHA K S (1BY20CS127)
PRAMATH V BHAT (1BY20CS137)
ii
CONTENTS
Chapters Page no
Chapter 1: Introduction 01
1.1 Background 03
Chapter 4: Design 13
4.1 Entity-Relationship Diagram 14
4.2 Schema Diagram 15
Chapter 5: Implementation 17
5.1 Implementation with Screen shot 18
Chapter 7: References 26
III
CROP MANAGEMENT SYSTEM
CHAPTER 1
INTRODUCTION
The "Crop Management System" has been developed to override the problems prevailing in the
practicing manual system. This software is supported to eliminate and, in some cases, reduce the
hardships faced by this existing system. Moreover, this system is designed for the particular need of
the company to carry out operations in a smooth and effective manner. Crop management system is
used to manage the crops ordering without the interruption of mediator between the farmer and
customer. It can be used for analyzing the distribution flora among the country based on the region
where the crops come from. This way our project is going to reduce the record keeping work and
computerize farm maintaining system.
The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the user to
use this system. Thus, by this all it proves it is user-friendly. Crop Management System, as described
above, can lead to error free, secure, reliable and fast management system. It can assist the user to
concentrate on their other activities rather to concentrate on the record keeping. Thus, it will help
organization in better utilization of resources.
Every organization, whether big or small, has challenges to overcome and managing the information
of Crops, Farm, Insecticides, Equipment, Pesticides. Every Farm Management System has different
Farm needs. therefore, we design exclusive employee management systems that are adapted to your
managerial requirements. This is designed to assist in strategic planning, and will help you ensure
that your organization is equipped with the right level of information and details for your future
goals. Also, for those busy executive who are always on the go, our systems come with remote
access features, which will allow you to manage your workforce anytime, at all times. These systems
will ultimately allow you to better manage resources.
With this user-friendly application, it is possible for both farmers and customers to order the
products whichever they want with the beneficial price.
OBJECTIVE
The main objective of the Project on Crop Management System is to manage the details of Crops,
quantity, prices of product. It manages all the information about Farm, Cost Range, Pesticides,
quantity. The project is totally built at administrative end and thus only the administrator is
guaranteed the access. The purpose of the project is to build an application program to reduce the
manual work for managing the Farm, Crops, Cost Range, customer demand. It tracks all the details
about the Crops, price, demand etc.
FEATURES:
• Product and Component based
• Creating & Changing Issues at ease
• Query Issue List to any depth
• Reporting & Charting in more comprehensive way
• User Accounts to control the access and maintain security
• Simple Status & Resolution
• Multi-level Priorities & Severities.
• Targets & Milestones for guiding the programmers
• Attachments & Additional Comments for more information
• Robust database back-end
• Various level of reports available with a lot of filter criteria's
• It contains better storage capacity.
• Accuracy in work.
• Easy & fast retrieval of information.
• Well-designed reports.
PROPOSED SYSTEM:
The aim of proposed system is to develop a system of improved facilities. The proposed system can
overcome all the limitations of the existing system. The system provides proper security and reduces
the manual work.
• Security of data. Ensure data accuracies.
• Proper control of the higher officials.
• Minimize manual data entry.
• Minimum time needed for the various processing.
• Greater efficiency. Better service.
• User friendliness and interactive.
• Minimum time required.
CHAPTER 2
LITERATURE SURVEY
SINO Author/Association Publication
1 Manish Mahant, The application of Information and Communication
Abhishek Shukla, Sunil Technology (ICT) in agriculture is increasingly important.
Dixit, Dileshwer Patel,
E-Agriculture involves the conceptualization, design,
IEEE Research Paper development, evaluation and application of innovative ways
(2019) to use information and communication technologies (ICT) in
rural domain, with a primary focus on agriculture.
2 HavliCek, J. Vanek, V. The new ICT technologies are not only fast developed but, in
Lohr, E. Cervenkova, addition, are giving birth to newer systems and tools.
IEEE Research Paper The Internet network have become essential communication
(2020) tools in business processes recently.
3 Ludena R, D.A. Ahrary, Knowledge gap among the rural poor farmers is one of the
A. Horibe, N. key constraints to the growth of the overall agricultural
sector.
SPRINGER Research
Paper To overcome the above key constraint, Information and
(2021) Communication Technology (ICT) can be synthesized with
the Agricultural Technology.
5 Shabnam Sikandar The aim of this paper is to reveal the current situation
Mahat, Dr.Pallavi P. regarding the use of mobile phones as a mean of information
Jamsandekar, Dr. K.M. sharing by Cypriot farmers.
Nalavade
6 Maurya, B. Beg, M.R. Expert System technology can play a very important role in
Mukherjee, S. farming sector.
CHAPTER 3
Identification of need:
The old manual system was suffering from a series of drawbacks. Since whole of the system was to
be maintained with hands the process of keeping, maintaining and retrieving the information was
very tedious and lengthy. The records were never used to be in a systematic order. there used to be
lots of difficulties in associating any particular transaction with a particular context. If any
information was to be found it was required to go through the different registers, documents there
would never exist anything like report generation. There would always be unnecessary consumption
of time while entering records and retrieving records. One more problem was that it was very
difficult to find errors while entering the records. Once the records were entered it was very difficult
to update these records.
The reason behind it is that there is lot of information to be maintained and have to be kept in mind
while running the business. For this reason, we have provided features Present system is partially
automated (computerized), actually existing system is quite laborious as one has to enter same
information at three different places.
• Documents and reports that must be provided by the new system there can also be few
reports, which can help management in decision-making and cost controlling, but since the
reports do not get required attention, such kind of reports and information were also
identified and given required attention
• Details of the information needed for each document and report
• The required frequency and distribution for each document
• Probable sources of information for each document and report
• With the implementation of computerized system, the task of keeping records in an organized
manner will be solved. The greatest of all in the seal of information, which will be at the
click of the mouse. So, the proposed system h in saving the time in different operations and
making information flow easy going valuable reports.
In this phase, a logical system is built which fulfils the given requirements. Design phase of software
development deals with transforming the client’s requirements into a logically working system.
Normally, design is performed in the following in the following two steps.
1. Primary Design Phase: In this phase, the system is designed at block level. The blocks are created
on the basis of analysis done in the problem identification phase. Different blocks are created for
different functions emphasis is put on minimizing the information flow between blocks. Thus, all
activities which require more interaction are kept in one block.
2. Secondary Design Phase: In the secondary phase the detailed design of every block is performed.
HARDWARE REQUIREMENTS: -
• RAM – 128MB
SOFTWARE REQUIREMENTS: -
CHAPTER 4
DESIGN
INTRODUCTION
Design is the first step in the development phase for any techniques and principles for the purpose of
defining a device, a process, or system in sufficient detail to permit its physical realization.
Once the software requirements have been analyzed and specified the software design involves three
technical activities - design, coding, implementation, and testing that are required to build and verify
the software.
The design activities are of main importance in this phase because, in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing on the reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished software or
a system.
A database schema can be represented in a visual diagram, which shows the database object and
their relationship which represents the logical view of the database and how the relationships among
them are represented.
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to
unify the network and relational database views. Simply stated the ER model is a conceptual data
model that views the real world as entities and relationships. A basic component of the model is the
Entity-Relationship diagram which is used to visually represent data objects. For the database
designer, the utility of the ER model is:
• It maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.
• It is simple and easy to understand with a minimum of training. Therefore, the model can be
used by the database designer to communicate the design to the end-user.
The basic types of connectivity for relations are one-to-one, one-to-many, and many- to-many. A
one-to-one (1:1) relationship is when at most one instance of entity A is associated with one instance
of entity B. For example, "employees in the company are each assigned their own office. For each
employee, there exists a unique office and for each office, there exists a unique employee.
A one-to-many (1: N) relationship is when for one instance of entity A, there are zero, one, or many
instances of entity B, but for one instance of entity B, there is only one instance of entity A. An
example of a 1: N relationship is a department has many employees each employee is assigned to
one department.
A many-to-many (M: N) relationship, sometimes called non-specific, is when for one instance of
entity A, there are zero, one, or many instances of entity B and for one instance of entity B, there are
zero, one, or many instances of entity A. The connectivity of a relationship describes the mapping of
associated.
There is no standard for representing data objects in ER diagrams. Each modeling methodology uses
its own notation. The original notation used by Chen is widely used in academic texts and journals
but rarely seen in either CASE tools or publications by non- academics. Today, there are several
notations used, among the more common are Bachman, crow's foot, and IDEFIX.
All notational styles represent entities as rectangular boxes and relationships as lines connecting
boxes. Each style uses a special set of symbols to represent the cardinality of a connection. The
notation used in this document is from Martin. The symbols used for the basic ER constructs are:
• Entities are represented by labeled rectangles. The label is the name of the entity. Entity
names should be singular nouns.
• Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs
• Attributes, when included, are listed inside the entity rectangle. Attributes that are identifiers
are underlined. Attribute names should be singular nouns.
• The cardinality of many is represented by a line ending in a crow's foot. If the crow's foot is
omitted, the cardinality is one.
Data objects represented by labeled arrows and transformation are represented by circles also called
bubbles. DFD is presented in a hierarchical fashion i.e., the first data flow model represents the
system as a whole. Subsequent DFD refines the context diagram (level 0 DFD), providing increasing
details with each subsequent level.
The DFD enables the software engineer to develop models of the information domain & functional
domain at the same time. As the DFD is refined into greater levels of detail, the analyst performs an
implicit functional decomposition of the system.
At the same time, the DFD refinement results in a corresponding refinement of the data as it moves
through the process that embodies the applications. In a context-level DFD for the system, the
primary external entities produce information for use by the system and consume information
generated by the system. The labeled arrow represents data objects or object hierarchy.
CHAPTER 5
Adding Farmers and customers into website as users to communicate for crops.
Login by farmer’s credential to access farmer options further will take you into farmer’s account.
Here farmer can add his crops which he produced and details of remaining crops and also ordered
crops by customer.
After the produced crops are added by farmer we will get all details which are remaining.
Details of all crops ordered by customer are available to farmer in this option.
Customer can order required crops and will have all history of his orders.
Customer can add required quantity of crops into the cart based on available quantity he can order.
Option to view total crops,all registered farmers and registered customers and all order details.
All details of crops added by farmers can be viewed here further he has option to delete crops which
are out of stock.
Details of farmers who are registered,data of their location and contact number.
Details of customers who are registered,data of their location and contact number.
Quantity of crops ordered by customer and it’s total cost and also details about when it is ordered.
CHAPTER 6
Our project is only a humble venture to satisfy the needs to manage the project work. Several user-
friendly coding has also adopted. This package shall prove to be a powerful package in satisfying all
the requirements of the farming. The objective of software planning is to provide a frame work that
enables the manger to make reasonable estimates made within a limited time frame at the beginning
of the software project and should be updated regularly as the project progresses.
• A description of the background and context of the project and its relation to work already
done in the area.
• Made statement of the aims and objectives of the project
• The description of Purpose, Scope, and applicability
• We define the problem on which we are working in the project
• We describe the requirement Specifications of the system and the actions that can be done on
these things
• We understand the problem domain and produce a model of the system, which describes
operations that can be performed on the system
• We included features and operations in detail, including screen you
• We designed user interface and security issues related to system
• Finally, the system is implemented and tested according to test cases
Till now we have created a website which has sign in/up page where the user need to submit all the
details and according to it the site will respond. In this portal user can buy/sell his products without
mediation. For security each user will have user id and password. In future we are planning to host
this website in largescale with other implementations.
In a nutshell, it can be summarized that the future scope of the project circles around maintaining
information regarding:
The above-mentioned points are the enhancements which can be done to increase the applicability
and usage of this project. Here we can maintain the records of Farm and Crops. Also, as it can be
seen that now-a-days the players are versatile, i.e., so there is a scope for introducing a method to
maintain the Crop Management System. Enhancements can be done to maintain all the Farm, Crops,
Insecticides, Pesticides.
We have left all the options open so that if there is any other future requirement in the system by the
user for the enhancement of the system then it is possible to implement them. In the last we would
like to thanks all the persons involved in the development of the system directly or indirectly. We
hope that the project will serve its purpose for which it is develop there by underlining success of
process.
CHAPTER 7
REFERENCES
13. httpd.apache.org/docs/2.0/misc/tutorials.html