Project Group Member Name:

1)Auti Prajwal Auti (PRN: 1102006934)

2) Mavale Yash Balasaheb (PRN: 1102006982)
 A

Project Report on

“Krushi-Market”
Submitted in Partial fulfilment for the award of the degree of

“T.Y. B.Sc. (Computer Science)”

Submitted To:
1) Auti Prajwal Vilas (PRN:1102006934 )
2) Mavale Yash Balasaheb (PRN: 1102006982)

As

Savitribai Phule Pune University, Pune

Academic Year 2022-2023
 Department of Computer Science
This is to certify that
Auti Prajwal Vilas
Mavale Yash Balasaheb
Students of T. Y. B.Sc. (Computer Science)
Has completed the project titled
“Krushi-Market”

As per laid down by the Savitribai Phule Pune University, Pune during
Academic Year 2022-23

Internal Examiner External Examiner Project Guide

HOD Principal
Prof. Kale A B. Dr. Shelar U.B.
 Acknowledgement

I would like to take this opportunity to express my heartfelt thanks,

To my guide of computer science Prof. Kale A. B. for his esteemed guidance And encouragement,
especially through difficult times.
His suggestions broaden my version and guided me to succeed in this work.
I am also very grateful for his guidance and comments while designing part of my project and learnt
many things under his leadership. I would like to take this opportunity to express my heartfelt thanks to
Also, I would like to thanks all my teaching and Non-teaching staff of our BCS department specially
Miss Usha mam and Prof. Maniyar. S. A. for their encouragement and suggestions. My sincere
thanks
to all my friends, who helped me directly or indirectly in completing of this project work. I would like
to
express my appreciation for the wonderful experience while the completion of this
project work.
Kale.Amol28@gmail.com
Submitted By :- Mr. Auti Prajwal Vilas
Mr. Mavale Yash Balasaheb
 Table of Contents
Sr. No Title Page No.
1 Abstract of Project 1

Introduction 1

1.1 Motivation 2
1.2 Problem statement 2
1.3 Purpose/Objective and goals 3

1.4 literature survey 3

1.5 Project scope and Limitations 4

2 System Analysis 5

2.1 Existing systems 5

2.2 Scope and Limitations of existing systems 6
2.3 Project perspective,features 7
2.4 Stakeholders 8
2.5 Requirement Analysis - 9
2.5.1 Functional requirements 9
2.5.2 Performance requirements 10
2.5.3 Security requirements 11
3 System Desing 13
3.1 Design constrains 13
3.2 System Model: Using OOSE 14
3.3 Data Model 17
3.4 User Interface 18
4 Implementation details 26
4.1 Software Specification 26
4.2 Hardware Specification 26
5 Outputs and Reports Testing 27
5.1 Test Plan 27
5.2 Black Box Testing 28
5.3 White Box Testing 32
5.4 Result 35
6 Conclusion and Recommendations 35
7 Future Scope 36
8 Reference and Bibilography 36
 ABSTRACT
Agriculture derives its importance from the fact that it has vital supply and demand links
with the manufacturing sector. During the past five years agriculture sector has witnessed spectacular
advances in the production and productivity of food grains, oilseeds, commercial crops, fruits,
vegetables, food grains, poultry and dairy.
Online Marketing much more than effect agriculture department and In India, the organized
marketing of agricultural commodities has been promoted through a network of regulated markets.
The advent of regulated markets has helped in mitigating the market handicaps of
producers/sellers at the wholesale assembling level. But the rural periodic markets in general and the
tribal markets in particular, remained out of its developmental ambit.

Keywords – User documentation, Searching, Confirmation, farmer.

INTRODUCTION
Farming is the Prime Occupation in India in spite of this, today the people
involved in farming belongs to the lower class and is in deep poverty. The Advanced techniques
and the Automated machines which are leading the world to new heights, is been lagging when
it is concerned to farming, either the lack of awareness of the advanced facilities or the
unavailability leads to the poverty in farming. Even after all the hard work and the production
done by the farmers, in today’s market the farmers are cheated by the Agents, leading to the
poverty. Agro-marketing would make all the things automatic which make easier serving as a
best solution to all the problems.

Farmer’s Krushi-Market will serve as a way for the farmers to sell their products
across the country just with some basic knowledge about how to use the website. The site will
guide the farmers in all the aspects. Getting availed to the required information related to the
markets and different products can be made possible through the SMS facility. Farmers Krushi-
Market is the web application that will help the farmers to perform the agro-marketing leading
to achievesuccess and increase in their standard of living. TheMarketing facility would allow
the farmers to have aview of the bills created and the related information intheir accounts.

An Authorized-agent would serve as away for the farmers to sell their products in
the market.The Centralized market committee will have control onthe Agents through business

1
activities review. In rural area,the SMS facility would give the required market information where
internet cannot be availed. Government will put forward the new schemes for the farmers.
Compensation will be provided for thefarmers in case of any loss to the production due to some natural
calamities. Unique interface will be provided for applying and viewing the schemes in the website.

1.1 Motivation
Krushi marketing still continues to be in a bad shape in rural India. In the absence of
sound marketing facilities, the farmers have to depend upon local traders and middlemen
for the disposal of their farm produce which is sold at throw-away price.
The status of farmers in India is such that they buys everything in retail and sells their produce
inwholesale. With different Agricultural Product Market Committee (APMC) acts in different
states, lack of clarity on the prices set by these agencies, high lobbying capacity of the
middlemen has resulted in exploitation of farmers and crops not fetching the right price.
Due to short shelf life of fruits and vegetables and other products, there is a high requirement of
cold storages and warehouses to have a stable price and quantity across the year. With very few
and poorly managed warehouses, the government lacks the main tool for controlling inflation
and also giving a fair price to the harvest. Such uncertainties discourage farming.
In current competitive scenario every business establishment needs quality processes to increase
their efficiency as well as improve their productivity. It is of vital importance that manual, time
consuming & monotonous operations are automated so as to streamline the working of
anorganization. Since, the existing system takes more time and manpower for processing. It is
keeping in mind this business philosophy that we propose a Farmer’s Krushi-Market.
Considering the above scenario faced by farmers we have designed this web portal so that farmers
will be able to market their product without the involvement of middlemen or any third party. Our
system will deal with all aspects of farmer’s products

1.2 Problem Statement

“You are to design and implement a krushi market that should accept farmer and
traders communication of data for subsequent processing. The system should prepare pay cheque and
cash, cradit ledger, and maintain data on a sequential krushi file. Non-statutory deductions such as
quality. The year-to-date total should contain earnings and union dues”
To accomplish these tasks, we had to meet with the client to find out exactly what
the program is meant to do. Here are the sub stories that we were able to get from the client:

2
1.3Propose ,Scope of the System:
• This social site can provide separate login id and admin can handle to server side data easily.
• Farmer can send information and photos number of businessman.
• Businessman checks that number of client’s data and choice that’s product and send to rate list.
• Farmer can see number of rate list for our products then he also decide to sale that our product.
• The system is mainly developed for chief engineers Taking care of non-technical users. The overall
structures, Methods with proper design will be useful for the user of all Levels designing is created in
user friendly manner, which can be operated without any problems.
• The system is flexible because all the coding and Specification are taken care in such manner that
future up Gradation of the system can be possible. This project use to Manage database where the
modification and complexity Arises.
As now, complex data is becoming one of the parts of Database this project is helpful.
System takes care of the people who logged in and the modification they have done, so that there is no
mishandling of database.

1.4 literature survey

Significant research has been done on the agriculture market and various studies in
journals about the agricultural sector. Making a distinct platform for farmers helps them to share some
information about agriculture. Technology is existing everywhere from well equipped cities to a small
village in the current generation. So there are no difficulties in using the technology to move into this e-
commerce field. In the study, we got to know that the majority of the farmers are not getting enough
profits for their crops.
All the intermediate market strategies doing all these losses to the hard-working farmers. Despite all
the hard work and patience to grow the crops, farmers play a crucial role in the agricultural life cycle
but still they are facing a lot of issues to get profit due to their bad circumstances. In India two-third of
the one billion population relies on agricultural entities. Now the country is not matching the
requirements for agriculture.
The farming sector has to formulate with the rise in the market to do such increments
there should be unique development that has to be done. That is the new techniques and technology
should be used to build modern farming in a high yield manner. A lot of countries are doing their
research on technologies to use them in farming, in the process, they are achieving good outcomes.
With the spread technology, agricultural system connections between regions become easy and they
can easily get the information they are seeking. The modern IT(Information Technology)
infrastructure simplifies the integration in the network. We can useinformation technology in an
enormous amount in the agricultural sector.
From planting saplings to harvesting the present advances in information technology
help us to adopt new automated ways in farming. All of this resulted in that information technology is
very much beneficial in all the techniques carried out in the farm management system. After harvesting,
there is the main struggle to begin selling the product, every farmer wants to sell their product for
profits. To analyse the cost in different markets the IT Services are more helpful to farmers. Most of the
public are aware of smartphones and their usage which will help to go with the technology.

3
The website we are making is simple in design and easy to understand the interface of the website.
Technology has advanced to a high level and farmers have the option of using mobile phones in rural
regions effectively. We publish the information from the (IFFCO) which is a multi-state cooperative
society in India on our website.

1.5 Project scope and Limitations

Scope
The scope of the Farmer Krushi-Market System includes the development of an online platform that
connects farmers with potential buyers, facilitating the sale and purchase of agricultural products. The
system aims to provide a convenient and efficient marketplace for farmers to sell their produce directly
to consumers, eliminating intermediaries and improving profitability.
 The key features and functionalities of the Farmer Krushi-Market System may include:

 Farmer Registration: Farmers can register on the platform, providing necessary details such as
contact information, location, and types of products they offer.

 Product Listings: Farmers can create listings for their agricultural products, including details
like product description, quantity, quality, pricing, and availability.

 Search and Filter: Buyers can search for specific products or browse through different
categories using search and filtering options.

 Ordering and Payments: Buyers can place orders for desired products and make payments
securely through integrated payment gateways.

 Ratings and Reviews: Buyers can provide feedback and ratings for the products and services
received, helping to build trust and reputation for the farmers.

 Messaging and Notifications: The system should facilitate communication between farmers and
buyers through messaging features. It should also send notifications for order status updates,
new product listings, and other relevant information.

 Analytics and Reporting: The system can generate reports and analytics to provide insights into
sales, product demand, and other relevant metrics to help farmers make informed decisions.

Limitations
While the Farmer Krushi-Market System aims to provide a comprehensive solution for connecting
farmers and buyers, there are certain limitations to consider:

4
  Geographical Coverage: The system may initially focus on a specific region or country, limiting
the availability of the platform to farmers and buyers within that particular area.

 Language and Localization: The system may be designed to support a specific language or a set
of languages, potentially limiting accessibility for users who do not speak or understand the
supported languages.

 Internet Connectivity: The system relies on internet connectivity for farmers and buyers to
access and use the platform. Limited or unreliable internet access in certain rural areas may pose
challenges for users.

 Trust and Verification: The system may face challenges in ensuring the authenticity and
reliability of farmers and their products. Implementing robust verification processes and buyer
reviews can help mitigate this limitation.

 Delivery Logistics: The system does not handle the physical logistics of delivering the products
from farmers to buyers. It is the responsibility of the parties involved to arrange for
transportation and delivery.

 Technical Support: While the system may provide user guides and documentation, it may not
offer round-the-clock technical support, which could impact user experience and issue
resolution.

 These scope and limitations provide a general overview of what can be expected from a Farmer
Krushi-Market System. It is essential to further refine the scope and limitations based on
specific project requirements, resources, and constraints

System Analysis
1.4 Existing System:
 In the existing system all transactions, dealings of products, purchasing of products were
done manually which is time consuming.
 Reports are prepared manually as and when needed. Maintaining of reports is
tedious task
 To buy any product user has to collect information about it either by visiting the shop or
by asking people which is better.
 There is no computer system for handling payments. All calculations are performed
manually which may not always be accurate. Maintaining records is difficult.

5
  Any internet user can use this existing website to search for any kind of products, select
particular product from wide range of products.
 Once they make up their mind to purchase any particular thing they can place an order
and make payment through net banking.
 The existing Farmer’s Krushi-Market website is static which makes it less interactive. It has a
database connectivity. The home page, farmer interface,admin interface and the user interface has
been prepared.
 The system information updates according to the changes in technology and store
products.
 Master maintenance is done by admin who is responsible for every updation required in
the system.
 In this system, the producer can update , sell and check details about their products
accordingly. They can put information about their products which are to be displayed in
the website
 Buyer can avail benefits of the user friendly web based system in choosing products
available and buying them. Moreover the buyer can contact admin in case of faulty
products.

2.2 Scope and Limitations of existing systems

Scope of Existing Systems:
1. Product Listing and Search: Existing systems provide a platform for farmers to list their
products, including details such as type, quantity, quality, and pricing. Buyers can search and
browse through these listings to find the desired products.

2. Communication and Negotiation: These systems typically enable communication between

buyers and sellers, allowing them to negotiate terms, discuss product specifications, and finalize
transactions.

3. Order Placement and Tracking: Buyers can place orders for the selected products, specifying
quantity, delivery details, and payment preferences. Some systems may offer order tracking
features to monitor the status of the shipment.

4. Payment Integration: Integration with payment gateways allows secure online transactions,
providing convenience and trust to both buyers and sellers. Common payment options include
credit/debit cards, mobile wallets, and online banking.

5. Review and Rating: Many systems include a feedback mechanism where buyers can rate and
review the products and sellers. This feature helps build trust and transparency within the Krushi-
Market .

6
 Limitations of Existing Systems:
1. Limited Geographic Coverage: Some existing systems may have limited reach, focusing on
specific regions or countries. This can restrict the availability of products and limit the user base.

2. Limited Product Variety: The range of agricultural products available on existing systems can
be limited, depending on the participation of farmers and the focus of the platform. It may be
challenging to find niche or specialized products.

3. Trust and Quality Assurance: Ensuring the quality and authenticity of the listed products can be
challenging for existing systems. Verification processes may be absent or insufficient, leading to
potential issues with product quality or misrepresentation.

4. Logistics and Delivery Challenges: Coordinating logistics and delivery can be complex,
especially in rural or remote areas. Existing systems may face limitations in providing efficient
and reliable delivery services, impacting customer satisfaction.

5. Language and Technical Barriers: Language barriers can pose challenges for farmers and buyers
who are not fluent in the platform's language. Moreover, technical barriers, such as limited internet
connectivity or limited access to electronic devices, may hinder adoption in certain regions.

6. Limited Ancillary Services: Existing systems may lack additional services important for farm
Krushi-Market s, such as real-time market data, advisory services, or post-harvest support. These
services can add value and enhance the overall experience for users.

7. Market Dynamics and Price Fluctuations: The volatile nature of agricultural markets, including
price fluctuations and supply-demand dynamics, can pose challenges for existing systems in
maintaining up-to-date pricing information and managing stock availability.

2.3 Project perspective,features

1. User Registration and Profiles: Users can create accounts and profiles on the platform, providing
necessary information such as contact details, location, and preferences.

2. Product Listing and Management: Farmers can list their products on the platform, including
details like product type, quantity, quality, pricing, and available delivery options. They can also
manage their listings, update stock availability, and make modifications as needed.

3. Search and Filter Functionality: Buyers can search for specific products or browse through
categories using search and filter options. This feature helps users find relevant products based on their
requirements.

7
4. Communication and Negotiation: The system facilitates communication between buyers and
sellers, allowing them to discuss product details, negotiate terms, and ask questions. Features like
messaging or chat functionality enable direct interaction.

5. Order Placement and Management: Buyers can place orders for the selected products, specifying
the desired quantity, delivery address, and preferred payment method. The system records and manages
these orders, providing order tracking and status updates.

6. Payment Integration: The system integrates with secure payment gateways, enabling online
transactions. Users can make payments using various methods, such as credit/debit cards, mobile
wallets, or online banking.

7. Review and Rating System: Users can provide feedback by rating and reviewing the products and
sellers. This feature helps build trust and credibility within the Krushi-Market and assists other buyers
in making informed decisions.

8. Delivery and Logistics Management: The system can include features to manage delivery logistics,
including coordination with shipping providers, tracking shipments, and updating delivery statuses.
This ensures efficient and timely delivery of products.

9. Analytics and Reporting: The system may offer analytics and reporting tools to provide insights
into sales trends, product performance, user activity, and other relevant data. This information can help
users make informed business decisions.

10. Notifications and Alerts: The system can send notifications and alerts to users regarding order
updates, product availability, special offers, or any other relevant information.

2.4 Stakeholders

1. Farmers: Farmers are key stakeholders as they list and sell their agricultural products on the Krushi-
Market platform. They rely on the system to reach a wider customer base, showcase their products, and
manage their sales and orders.
2. Buyers: Buyers, including individuals, retailers, or wholesalers, are important stakeholders as they
use the Krushi-Market system to browse and purchase agricultural products directly from farmers. They
benefit from a wider selection of products, convenient purchasing options, and potentially lower prices.

8
3. Payment Gateway Providers: Payment gateway providers play a crucial role as stakeholders in
farm Krushi-Market systems. They handle the secure processing of online transactions, ensuring that
payments from buyers reach the farmers' accounts.
4. Shipping and Logistics Partners: Shipping and logistics partners collaborate with the Krushi-
Market system to facilitate the delivery of agricultural products from farmers to buyers. They handle
transportation, packaging, and tracking of shipments to ensure timely and efficient delivery.
5. Regulatory Authorities: Regulatory authorities, such as agricultural departments, food safety
agencies, or trade commissions, may have an interest in farm Krushi-Market systems to monitor
compliance with regulations, quality standards, and fair trade practices.
6. Consumer Advocacy Groups: Consumer advocacy groups are stakeholders who may monitor the
Krushi-Market system to ensure transparency, fair pricing, and quality standards for agricultural
products. They may provide feedback or raise concerns about any perceived issues related to consumer
rights.

7. Financial Institutions: Financial institutions, such as banks or payment service providers, have a
stake in the Krushi-Market system as they handle financial transactions, facilitate secure payments, and
ensure financial integrity.
8. Technology Providers: Technology providers, including software developers, hosting companies, or
cloud service providers, play a vital role in developing and maintaining the Krushi-Market system
infrastructure, ensuring its stability, scalability, and security.
9. Government Agencies: Government agencies involved in agricultural development, rural
empowerment, or digital initiatives may be stakeholders in the farm Krushi-Market project system.
They may provide support, funding, or regulatory guidance to promote the adoption and success of the
system.
10. Industry Associations: Agricultural or farmer associations, industry trade groups, or cooperatives
can be stakeholders in a farm Krushi-Market system. They may support the system's adoption, advocate
for the interests of farmers and buyers, and provide guidance on industry best practices.

2.5 Requirement Analysis -

2.5.1 Functional Requirements:

Interviews:

Analyst use interviews to collect information from individual or from groups. The
respondence is generally current users of the existing system or new users of the proposed
system. The respondence may be manger or employees who provide data for the proposed

9
 system or who will be affectedby it. Interviews are not always the best source for collecting the
informationbecause of the time required for interviews.
Despondence and analyst converse during an interview. Interview provides
opportunities for gathering information from respondence.The interview is the best method for
producing quality information like opinions,policies and subjective description of activities and
problems. This method of fact-finding is helpful for gathering information from individuals
who do not communicate effectively in writing or who may not have time to complete
questioning. Interviews allow analysts to discover areas of misunderstanding, unrealistic
expectations and indications of resistance tothe proposed system.

Interviews can be of two types:

 Structured
 Unstructured
Using question and answer format, analyst wants to acquire general information
about the system. This format encourages respondent to share their feeling, ideas etc. Structure
interviews use standardized question, in either an open response or close response format. The
unstructured, allows respondent top answer in their own words. Whereas a structure interview
uses a set of prescribed answers. The success of an interview depends on the skill of the
interviewer and on the preparation for the interview. Analyst alsoneed to the sensitive to the
kind of difficulties that some respondents create during interviews and know how to deal with
the problems.

Observation:

Observation allows analyst to get information, which they cannotobtain by, any other
fact finding technique. Through the observation analyst can obtain the first hand information
about how activities are carried out. This method is most useful when the analyst need to
actually observe how documents are handled, how processes are carried out and whether
specified steps are actually followed or not.

2.5.2 Performance requirements

Performance requirements for a farm Krushi-Market project system are crucial to ensure its efficiency,
reliability, and scalability. Here are some key performance requirements to consider:

10
1. Response Time: The system should have low response times to ensure quick loading of web pages,
product listings, and search results. Users expect a smooth and responsive browsing experience to
efficiently navigate the platform.

2. Scalability: The system should be designed to handle increasing user traffic and growing product
listings. It should have the ability to scale horizontally or vertically to accommodate a larger number of
users and data without compromising performance.

3. Concurrent User Support: The system should be able to handle a significant number of concurrent
users accessing the platform simultaneously. It should not experience performance degradation or
downtime due to high user loads.

4. Search Performance: The search functionality should be fast and efficient, enabling users to
quickly find relevant products based on various criteria such as product type, location, or price range.
The search algorithms and indexing mechanisms should be optimized for speed and accuracy.

5. Order Processing Speed: The system should process orders promptly, ensuring quick confirmation
and providing real-time order updates to both buyers and sellers. This helps in maintaining a seamless
buying and selling experience.

6. Payment Processing: Payment transactions should be processed securely and swiftly, with minimal
latency. Integration with reliable payment gateways and ensuring adherence to industry-standard
security protocols are important for smooth payment processing.

7. System Availability and Reliability: The system should have high availability, minimizing
downtime or disruptions. This requires robust server infrastructure, backup mechanisms, and fault
tolerance measures to ensure uninterrupted access to the platform.

8. Data Integrity and Security: The system should ensure the integrity and security of user data,
including personal information, transaction details, and communication within the platform. Data
encryption, secure protocols, and compliance with privacy regulations are essential to maintain user
trust.

11
2.5.2 Security requirements
1. User Authentication and Authorization: The system should implement secure user authentication
mechanisms, such as strong passwords, multi-factor authentication, or biometric authentication, to
ensure that only authorized users can access the platform and perform relevant actions based on their
roles and privileges.
2. Secure Communication: All communication between users and the system should be encrypted
using industry-standard protocols (e.g., SSL/TLS) to protect sensitive information from unauthorized
access or interception.
3. Data Privacy: The system should adhere to privacy regulations, such as GDPR or CCPA, and
implement measures to protect user privacy. This includes obtaining user consent for data collection
and processing, providing clear privacy policies, and limiting access to user data to authorized
personnel.
4. Secure Payment Processing: The system should integrate with reputable and secure payment
gateways that comply with Payment Card Industry Data Security Standard (PCI DSS) requirements.
This ensures that financial transactions are handled securely and sensitive payment information is
protected.
5. Protection against Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF): The
system should implement measures to prevent common web application vulnerabilities like XSS and
CSRF attacks. This involves input validation, output encoding, and implementing CSRF tokens to
prevent unauthorized actions.
6. Secure Database Management: The system's database should be protected against unauthorized
access, and sensitive data should be encrypted at rest. Regular database backups should be performed to
prevent data loss in case of a security incident or system failure.
7. Regular Security Audits and Penetration Testing: The system should undergo regular security
audits and penetration testing to identify vulnerabilities and weaknesses. This helps ensure that
appropriate security measures are in place and that any identified vulnerabilities are promptly
addressed.
8. Secure Third-Party Integrations: If the system integrates with third-party services or APIs, proper
security assessments and due diligence should be conducted to ensure the security of data exchanged
between the system and these external entities.

12
3.System Design
3.1 Design constrains
1. Technology Constraints: The choice of technology stack and frameworks may be constrained by
factors such as budget, available expertise, existing infrastructure, or compatibility requirements with
other systems or platforms.

2. Compatibility: The system may need to be compatible with various devices and platforms,
including desktop computers, mobile devices (iOS and Android), and different web browsers. It should
be designed and developed to provide a consistent user experience across these platforms.

3. Network Connectivity: The system should be able to handle variations in network connectivity, as
users may access the platform with different internet speeds or in areas with limited connectivity. The
design should optimize for efficient data transmission and minimize the impact of intermittent or slow
connections.

4. Limited Resources: The system should be designed to operate efficiently with limited resources,
such as memory, processing power, or storage capacity. This is particularly important for users with
older devices or in regions where hardware resources may be constrained.

5. Compliance and Legal Requirements: The system should comply with relevant legal and
regulatory requirements, such as data protection laws, privacy regulations, or industry-specific
standards. These constraints may impact data handling, storage, and security practices.

6. Localization and Internationalization: The system may need to support multiple languages,
regional preferences, and localized features to cater to users from different geographical regions. This
includes considerations for language translations, date/time formats, and currency conversions.

7. Usability and User Experience: The system should be designed with a focus on usability and
providing a positive user experience. This includes intuitive navigation, clear and concise interface
design, and efficient workflows that minimize user effort and promote user engagement.

8. Integration with Existing Systems: If the Krushi-Market system needs to integrate with existing
systems, such as inventory management, accounting, or shipping systems.

13
3.2 System Model: Using OOSE
To provide a system model for the farm Krushi-Market project system using Object-Oriented Software
Engineering (OOSE), we can employ the Unified Modeling Language (UML) to represent the various
components and their interactions. Here's an example of a simplified system model:

1. Class Diagram:

14
2. Use Case Diagram:

3. Sequence Diagram:
The sequence diagram illustrates the interactions between different objects or components during a
specific scenario or use case. For example, a sequence diagram can depict the steps involved in placing
an order, including user authentication, product selection, payment processing, and order confirmation.

15
4. Activity Diagram:

16
3.3 Data Model
+------------------+ +------------------+ +---------------------+
| User | | Product | | Order |
+------------------+ +------------------+ +---------------------+
| id (PK) | | id (PK) | | id (PK) |
| username | | name | | product_id (FK) |
| password | | description | | buyer_id (FK) |
| email | | price | | quantity |
| role | | quantity | | address |
| contact | | seller_id (FK)| | status |
+------------------+ +------------------+ +---------------------+

+------------------+
| Payment |
+------------------+
| id (PK) |
| order_id (FK) |
| amount |
| payment_date |
+------------------+

17
3.4 User Interface

1.Farmer site

Home Page

Login and Registration Page for (Farmer)

18
Home Page

19
 My product

Add New product

20
Farmer Profile

21
1.Buyer site
First Page

Login and Registration Page for (Farmer)

22
Home Page

23
Add To Cart

My Cart

24
Buyer Profile

25
4.Implementation details
4.1 Software Specification

 Technologies : php, java script,css,html

 Database : Microsoft Office Access2007

 Operating System : Windows 7,10,11

 Application Software : JDK1.7, Net bean 8.1, xampp

4.2 Software Specification

 Processor : Intel P-IV or above

 RAM : 1GB or Higher

 HDD : Minimum 5GB Free Space on HDD

26
5. Outputs and Reports Testing
5.1 Test Plan
1. Introduction:
- Provide an overview of the farm Krushi-Market system.
- Define the objectives and scope of the testing.

2. Test Objectives:
- Identify the key objectives of the testing phase.
- Specify the desired outcomes and deliverables.

3. Test Strategy:
- Define the overall approach to testing, including the test levels and types to be conducted.
- Identify the resources required for testing, such as test environments, test data, and tools.
- Specify any third-party systems or services that need to be integrated and tested.

4. Test Environment:
- Describe the required test environment, including hardware, software, and network configurations.
- Specify any test data or test databases needed for the testing process.

5. Test Deliverables:
- List the expected deliverables from the testing phase, such as test plans, test cases, and defect
reports.
- Specify the format and documentation standards for the deliverables.

6. Test Phases and Activities:

a. Requirements Analysis:
- Review the system requirements and identify any ambiguities or inconsistencies.
- Ensure that the requirements are testable and can be translated into test cases.

27
b. Test Planning:
- Define the test objectives, scope, and test coverage.
- Identify the test levels, test types, and entry/exit criteria.
- Develop a detailed test schedule and allocate resources accordingly.
c. Test Case Design:
- Identify the test scenarios and develop test cases.
- Ensure that the test cases cover all functional and non-functional requirements.
- Include positive and negative test scenarios, boundary value analysis, and equivalence
partitioning.
d. Test Execution:
- Execute the test cases based on the defined test scenarios.
- Record the test results, including any deviations or defects found.
- Log any issues encountered during the testing process.
e. Defect Management:
- Track and manage the defects found during testing.
- Prioritize and categorize the defects based on severity and impact.
- Monitor the resolution process and verify the fixes.
f. Test Reporting:
- Generate test reports summarizing the test activities, results, and metrics.
- Provide a detailed analysis of the test coverage and the system's quality.
- Include recommendations for improvement or further testing, if applicable.
7. Test Execution Schedule:
- Define the timeline for test execution, including specific dates for each test phase.
- Consider any dependencies or constraints that may affect the schedule.

8. Risks and Mitigation:

- Identify potential risks and issues that may impact the testing process.
- Develop contingency plans and mitigation strategies to address the identified risks.
9. Roles and Responsibilities:
- Define the roles and responsibilities of the testing team members.
- Identify the key stakeholders and their involvement in the testing process.

28
10. Approval and Sign-off:
- Specify the criteria for test completion and sign-off.
- Define the approval process for accepting the test results and closing the testing phase.
11. Test Closure:
- Summarize the overall testing process.
- Provide a final assessment of the system's quality and readiness for production.
- Identify any open issues or recommendations for future improvements.

5.2 Black Box Testing

1. Functional Testing:
- Test the registration process by entering valid and invalid user
information, verifying that new user accounts are created correctly.
- Test the login functionality with valid and invalid credentials, ensuring
that users can log in successfully and receive appropriate error messages for
invalid login attempts.
- Test the product listing and search features by entering different
keywords, verifying that the search results display accurate and relevant
products.
2. User Interface Testing:
- Test the layout and navigation of the user interface to ensure it is intuitive
and user-friendly.

2. User Interface Testing:

- Test the layout and navigation of the user interface to ensure it is intuitive
and user-friendly.
- Verify that all buttons, links, and forms are working correctly and perform
the intended actions.
- Test the responsiveness of the user interface on different devices and
screen sizes.
3. Usability Testing:
- Conduct user testing to evaluate the ease of use and overall user
experience of the system.
- Gather feedback from users on the clarity of instructions, intuitiveness of
workflows, and accessibility of features.

4. Transaction Testing:

29
 - Test the shopping cart functionality by adding products, adjusting
quantities, and verifying that the total cost is calculated accurately.
- Test the checkout process, including entering shipping details and
selecting payment methods, to ensure a smooth transaction flow.
- Verify that users receive proper order confirmations and invoices after
completing a purchase.
5. Security Testing:
- Test the system for vulnerabilities such as SQL injection, cross-site
scripting (XSS), and cross-site request forgery (CSRF) attacks.
- Verify that user authentication and authorization mechanisms are working
correctly.
- Test for proper encryption and protection of sensitive information, such as
user passwords and payment details.
6. Error Handling Testing:
- Test the system's response to invalid inputs and error conditions, verifying
that appropriate error messages are displayed.
- Validate that error messages are clear, informative, and user-friendly.
- Test the system's ability to gracefully handle exceptions and recover from
errors.
7. Performance Testing:
- Test the system's performance under expected user loads to ensure it can
handle concurrent users and transactions.
- Measure response times for various operations and validate that they meet
the specified requirements.
- Conduct stress testing to determine the system's maximum capacity and
identify any performance bottlenecks.
8. Localization Testing:
- Test the system's support for multiple languages and verify that translations
are accurate and contextually appropriate.
- Validate that date/time formats, currency symbols, and other regional
preferences are displayed correctly based on the selected language.
9. Compliance Testing:
- Test the system for compliance with relevant regulations and standards,
such as data privacy regulations or accessibility guidelines.
- Verify that the system meets the specified compliance requirements

30
 5.2 White Box Testing

1. Unit Testing:

- Test individual components or modules of the system, such as functions or methods, to ensure
they produce the expected outputs for various inputs.
- Verify that edge cases and boundary conditions are handled correctly.
- Use techniques such as code coverage analysis to ensure that all code paths are tested.

2. Integration Testing:
- Test the interaction between different modules or components of the system to ensure they work
together as expected.
- Verify that data is correctly passed between modules and that communication channels are
properly established.
- Test for proper error handling and exception handling during integration.

3. Database Testing:

- Test the database operations, such as data insertion, retrieval, and modification, to ensure they are
performed accurately.
- Verify that database queries and transactions are executed correctly and efficiently.
- Test for proper handling of concurrent database operations and data consistency.

4. Security Testing:

- Test the system's vulnerability to security threats, such as SQL injection, cross-site scripting (XSS),
or cross-site request forgery (CSRF).

- Verify that sensitive information, such as user credentials or payment details, are properly
encrypted and protected.

- Test for proper authentication and authorization mechanisms to ensure that only authorized users
have access to sensitive functionalities.

5. Performance Testing:

- Test the system's performance under various load conditions to ensure it can handle the expected
number of concurrent users and transactions.

31
 - Verify that response times and system resources meet the specified requirements.
- Conduct stress testing to determine the system's limits and identify any performance bottlenecks.

6. Error Handling and Exception Testing:

- Test the system's response to exceptional scenarios, such as invalid inputs, unexpected errors, or
system failures.
- Verify that appropriate error messages or exception handling mechanisms are in place to provide
meaningful feedback to users.
- Test error recovery and ensure the system returns to a stable state after encountering errors.

7. Code Review and Static Analysis:

- Conduct code reviews to identify potential coding issues, such as code smells, anti-patterns, or
violations of coding standards.
- Use static code analysis tools to identify potential bugs, security vulnerabilities, or performance
issues in the codebase.
- Review error logs and debug information to identify and fix any runtime errors or exceptions.

8. Regression Testing:

- Perform regression testing to ensure that system changes or bug fixes do not introduce new issues
or impact existing functionalities.
- Re-run previously executed tests to verify that the system behaves as expected after modifications.

5.4 Result
Date: [24/3/2023]
Tester: [Auti Prajwal]

1. Introduction:
The purpose of this testing report is to provide an overview of the testing activities conducted on the
Krushi-Market System. The testing was performed to evaluate the system's functionality, usability,
security, and performance.

2. Testing Objectives:

32
 - To verify that all the required features and functionalities of the Farm Krushi-Market System are
implemented correctly.
- To identify and report any defects or issues encountered during the testing process.
- To ensure that the system meets the specified requirements and performs as expected.

3. Test Environment:
- Operating System: [Windows 11]
- Browser: [Microsoft edge]
- Hardware: [RAM]
- Test Data: [24/3/2023]

4. Test Coverage:
The testing activities covered the following areas:
- User registration and login functionality
- Product listing and search
- Shopping cart and checkout process
- Security and access control
- Error handling and exception scenarios
- Performance under various load conditions
- Compatibility with different browsers and devices

5. Test Results:
Test the registration process by entering valid and invalid user information, verifying that new user
accounts are created correctly.
- Test the login functionality with valid and invalid credentials, ensuring that
users can log in successfully and receive appropriate error messages for
invalid login attempts.
- Test the product listing and search features by entering different
keywords, verifying that the search results display accurate and relevant
products.

User Interface Testing:

33
 - Test the layout and navigation of the user interface to ensure it is intuitive
and user-friendly.
- Verify that all buttons, links, and forms are working correctly and perform
the intended actions.
- Test the responsiveness of the user interface on different devices and
screen sizes.

- Security Testing:
- Test the system for vulnerabilities such as SQL injection, cross-site
scripting (XSS), and cross-site request forgery (CSRF) attacks.
- Verify that user authentication and authorization mechanisms are working
correctly.
- Test for proper encryption and protection of sensitive information, such as
user passwords and payment details.
- Performance Testing:
- Test the system's performance under expected user loads to ensure it can
handle concurrent users and transactions.
- Measure response times for various operations and validate that they meet
the specified requirements.
- Conduct stress testing to determine the system's maximum capacity and
identify any performance bottlenecks.
- Compatibility Testing:
Test the system for compliance with relevant regulations and standards, such
as data privacy regulations or accessibility guidelines.
- Verify that the system meets the specified compliance requirements.

- Error Handling Testing:

- Test the system's response to invalid inputs and error conditions, verifying
that appropriate error messages are displayed.
- Validate that error messages are clear, informative, and user-friendly.
- Test the system's ability to gracefully handle exceptions and recover from
errors.

7. Recommendations:
Based on the testing results, the following recommendations are made:
- Address and fix the identified defects before the system is deployed to production.

34
 - Conduct additional testing in specific areas where issues or limitations were found.
- Consider user feedback and make necessary improvements to enhance the user experience.
- Implement any suggested security enhancements to ensure data protection and system integriy.

9. Approval:
This testing report requires approval from the relevant stakeholders before proceeding with the
system deployment or further testing.

[Prajwal Auti,
Mavale Yash]
[Student]
[1/5/2023]

CONCLUSION:
Online Marketing much more than effect agriculture department and In India,
the organized marketing of agricultural commodities has been promoted through a network of
regulated markets. The advent of regulated markets has helped in mitigating the market
handicaps of producers/sellers at the wholesale assembling level. But the rural periodic
markets in general and the tribalmarkets in particular, remained out of its developmental
ambit

35
 Feature Assesment
The following are the future scope of the website:
The addition of Face detection system can be added.

The more attractive views can be created.

More changes as per owner’s requirements can be added.
More strong security can be given.
The software can be modified for large scale use.
More addition the project can used Microsoft Access databaseConnectivity.
We will try to alerts the market by farmer and trader about newschemes and
about various offers.

REFFERENCES

Websites:

www.google.com
https://www.programmableweb.com
https://codebun.com
https://www.researchgate.net
https://github.com
www.wikipedia.com
www.w3schools.com

36