Project Report

on

E-COMMERCE: KisaanKart
In partial fulfillment of requirements for the degree

of
BACHELOR OF TECHNOLOGY
IN

INFORMATION TECHNOLOGY

Submitted by:

AAKASH CHOUDAHRY [170100BTIT01412]

MALIK DRYFRUITWALA [1710DMBIT01537]
HARSH CHOUDHARY [1710DMBIT01530]
DEVANSH JAIN [1710DMBIT01530]

Under the guidance of

PROF. RANI SINGH

PROF. ISHA CHOPRA

SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE

SHRI VAISHNAV INSTITUTE OF INFORMATIN TECHNOLOGY
DEPARTMENT OF INFORMATION TECHNOLOGY

JULY-DEC 2021
i
 SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE
SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

DECLARATION

We h e r e d e c l a r e t h a t work w h i c h is b e i n g presented in t h e project e n t i t l e d

― Ecommerce: KisaanKart in partial fulfillment of degree of Bachelor of Technology in
Information Technology is an authentic record of our work carried out under the supervision
and guidance of Mrs. Rani Singh and Mrs. Isha Chopra, Asst. Professor of Information
Technology. The matter embodied in this project has not been submitted for the award of any
other degree.

DATE: 04/12/21
AAKASH CHOUDHARY
MALIK DRYFRUITWALA
HARSH CHOUDHARY
DEVANSH JAIN

ii
 SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE
SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

PROJECT APPROVAL SHEET

Following team has done the appropriate work related to the ―Ecommerce: KisaanKart in partial
fulfillment for the award of Bachelor of Technology in Information Technology of ―SHRI
VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY‖ and is being submitted to
SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE.

Team:
1. Akash Choudhary
2. Harsh Choudhary
3. Malik Dryfruitwala
4. Devansh Jain

Internal Examiner External Examiner

Date: 04/12/21

iii
 SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA, INDORE
SHRI VAISHNAV INSTITUTE OF INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that Mr. Akash Choudhary, Mr. Harsh Choudhary, Mr. Malik
Dryfruitwala and Mr. Devansh Jain working in a team have satisfactorily completed
the project entitled ―Ecommerce Website: KisaanKart under the guidance of Mrs. Rani
Singh and Mrs. Isha Chopra in the partial fulfillment of the degree of Bachelor of Technology in
Information Technology awarded by SHRI VAISHNAV INSTITUTE OF INFORMATION
TECHNOLOGY affiliated to SHRI VAISHNAV
VIDYAPEETH VISHWAVIDYALAYA, INDORE during the academic year July2021-Dec
2021.

Prof. Rani Singh

Prof. Isha Chopra Prof. Manish Kumar
Project Guide Project Coordinator

Dr. Jigyasu Dubey

Head, Department of Information Technology
iv
 ACKNOWLEDGEMENT

We are grateful to a number of persons for their advice and support during the time of complete
our project work. First and foremost, our thanks goes to Dr. Jigyasu Dubey Head of the
Department of Information Technology and Prof. Rani Singh and Prof. Isha Chopra the
mentor of our project for providing us valuable support and necessary help whenever required
and also helping us explore new technologies by the help of their technical expertise. His
direction, supervision and constructive criticism were indeed the source of inspiration for us.

We would also like to express our sincere gratitude towards our Director Dr. Anand Rajavat
for providing us valuable support.

We are really indebted to Prof. Manish Kumar, project coordinator for helping us in each
aspect of our academics activities. We also owe our sincere thanks to all the faculty members of
Information Technology Department who have always been helpful.

We forward our sincere thanks to all teaching and non-teaching staff of Information
Technology department, SVVV Indore for providing necessary information and there kind co-
operation.

We would like to thanks our parents and family members, our classmates and our friends for
their motivation and there valuable suggestion during the project. Last, but not the least, we
thank all those people, who have helped us directly or indirectly in accomplishing this work. It
has been a privilege to study at SHRI VAISHNAV VIDYAPEETH VISHWAVIDYALAYA,
INDORE.

v
ABSTRACT

Organic food products and other organic ingredients are grown without the use of pesticides,
synthetic fertilizers, sewage sludge, or ionizing radiation. Conventional fruits and vegetables
are often sprayed with pesticides. When you buy such fruits and vegetables, these stubborn
chemicals remain on the food. The second big difference between conventional and
organic food is that many conventional foods are genetically modified or contain genetically
modified organisms. Organic food is not easily available in the market. There are only some
particular shops where organic food is available. E-commerce is a process of doing business
through computer network. Online shopping is a form of electronic shopping store where the
buyer is directly online to the seller’s computer usually via the internet. To overcome the
difficulty of organic food shopping. We have proposed a best online organic store which
provides organic foods by just sitting at home and follows E-commerce mode of shopping.
This system has two modules namely, Admin and Customers. Admin has authority to add
organic food list on the website, view products uploaded, view customers and view the
customer’s order. Customers can register and login using credentials. Customers has
authority to view products, desire products and can add to cart and do payment for it, they can
view their previous order history and also can track their order.

vi
❖ Modules:

The system comprises of 2 major modules with their sub-modules as follows:

1. Admin:

• Login: Admin can login in his personal account using id and password.
• Add Organic Food: Admin can add Organic food.
• View Product: Amin can also add organic food products.
• View User: Admin can view all information about the user.
• View Users order: Admin can view users order.

2. User:

• View Products: User can view products.

• Add products to cart: User can add product to the cart.
• View Order history: User can view their previously purchase history.
• Track order: User can track his order.

vii
 TABLE OF FIGURES
Figure No. Figure Caption Page No.

1 Admin Module 3

2 Manage Order Module 4

3 Manage Item Module 4

4 User Module 4

5 Flow of Module 5
Frameworks
6 Use Case Diagram 17

7 Conceptual Level Class 18

Diagram
8 0 Level Data Flow Diagram 20

9 1 Level Data Flow Diagram 21

10 2 Level Data Flow Diagram 22

11 ER Diagram 24

12 Detailed Class Diagram 27

13 Sequence Diagram 30

14 Collaboration Diagram 32

15 Activity Diagram for User 34

16 Activity Diagram for 35

Admin
17 Component Diagram 37

18 Deployment Diagram 38

19-23 Test cases 39-41

24-35 Implementation Images 42-47

vii
 TABLE OF CONTENT

Content Page No.

Declaration ii

Project Approval Sheet iii

Certificate iv

Acknowledgment v

Abstract vi

List of Figures vii

CHAPTER 1: INTRODUCTION 1-6

1.1 Introduction 1

1.2 Problem Statement 1

1.3 Need for the proper system 2

1.4 Objective 2

1.5 Modules of the system 3

1.6 Scope 6

CHAPTER 2: LITERATURE SURVEY 7-10

2.1 Existing System 8

2.2 Proposed System 8

2.3 Feasibility Study 9

2.3.1Technical feasibility 9

2.3.2 Economical feasibility 10

2.3.3 Operational feasibility 10

CHAPTER 3: REQUIREMENT ANALYSIS 11-14

3.1 Method used for Requirement analysis 11

3.2 Data Requirements 11

3.3 Functional Requirements 12

viii
3.4 Non functional Requirements 12

3.5 System Specification 14

3.5.1 Hardware Specification 14

3.5.2 Software Specification 14

CHAPTER 4: DESIGN 15-23

4.1 Software Requirements Specification 15

4.1.1 Glossary 15

4.1.2 Use Case Model 16

4.2 Conceptual level class diagram 17

4.4 Data Flow diagram 19

4.5 Database Design (ER Diagram) 23

CHAPTER 5: SYSTEM MODELING 25-47

5.1 Detailed Class Diagram 25

5.2 Interaction Diagram 28

5.2.1 Sequence Diagram 28

5.2.2 Collaboration Diagram 30

5.4 Activity Diagram 32

5.6 Component Diagram 36-38

Deployment Diagram

5.7 Test Plans and Implementation Images 39

CHAPTER 6: CONCULSION & FUTURE WORK 48-49

6.1 Limitation of Project 48

6.2 Future Enhancement 49

CHAPTER 7: BIBLIOGRAPHY & REFERENCES 50

ix
 1. INTRODUCTION

1.1 Introduction

KisaanKart is a form of ecommerce that allows consumers to directly buy fresh food staffs or
produce from a farmer over the internet. Kisaankart evokes the physical analogy of buying
produce like it is done in a local market. The largest online retailing corporations are e-Bay
and Amazon.com, both of which are based in the US. These giant online shops have with time
been able to add to their sales the ability to sell fresh food and other home products through
the internet

Online markets have been a thing that has come to stay with the society of today since most
financial transactions can be attained online. Internet access has vastly grown across the India
today and has given rise to interconnectivity even to the remotest areas in the world. This
generally means it is possible to be at any location and reach any other location in the world
without stepping a foot out of your premises. This takes multi-tasking to another level since
you can be in a meeting and visit a market located several kilometres away at the same time.
This has made businesses to grow without spending as much as they would have if they had to
build another branch of their business in another location.

However, this phenomenon has not caught in the Indian business society, hence it has given
rise to the topic of this project. KissanKart is a website that will be used to sell and buy
produce that can be commonly found in any local market. In our markets, farmers reach out to
their customers who are present in the market at a particular time.

When a customer walks up to buy a bunch of bananas from a fruit seller, the customers is
asked how much she wants to buy, she is served and then the customer walks away. The seller
at this point has no record of the customer and this means no way of getting feedback from the
customer which goes a long way to grow business. This website will be designed to increase
profits by extending services and produce to a different customer base by means of online
advertisement which cuts across many borders of our world.

This website will hold a lot information that will increase the profits of business at a little cost.
In reaching out to various customers over the internet, the concept is aimed at penetrating a
fractions of our Indian population who are generally pre-occupied with activities which makes
it impossible for them to step out of their daily activities to purchase their needs. It is also
aimed to provide a source of income to many job seekers who may be interested in setting up
their own business over the internet.

1
The Website will have these basic functions:

Customer Information.
Catalogue of items sold or available in the shop.
Hold client shopping preference in a database.
Interface for customer support or relations.
Delivery capabilities.
.

Background to study

Farmers in local markets currently have a traditional system of shopping where customers are
expected to walk to the displayed items to make purchases at that particular time.

This leaves these farmers at the mercy of undecided customers who are normally moved by
the competitive pricing of other shops.

Customers who are loyal to the particular sellers are the ones who tend to stay for years with
unwavering attachment to such sellers. Most sellers in the marketplaces do not have a database
of customers who visit. Customers basically walk-ins just buy what they need and they are
gone.

There is a simple work flow of acquiring various products from the wholesalers, working out
prices, displaying produce on the shelves, receiving money, bagging bought items and finally
watch the customer walk away without out any interaction. This leaves no room for feedback
from the customer on the shopping experience. Whether it was good or bad it will never be
known until an unhappy customer willingly comes out to complain.

With popular trends and demands the concept of the Internet as the way forward to increase
profit margins, companies new and old are creating websites here and there. The significance
for retailers to having a website is that a website is informational and transactional in nature.
As the website can be used for advertising and direct marketing; sales; customer support and
public relations.

With seasonal events and holidays, the Internet has become a tool for a quick and stress-free
method of shopping. Allowing retailers to cash in the profit from another useful shopping
channel.

2
 1.2 Problem Statement

• Most markets in India are so crowded and disorganized so much that is it hard for
customers to locate items want. Before one even arriving at the market, the hustle of
queuing in traffic causes so much stress that when a customer reaches the market, there
is little or no energy to roam the lengths and breadth of the market for items.

• Aside this, sellers in the market can but sell what they have in the market rather than sell
what customers actually want. This usually leaves customers unsatisfied with produce
they find. There is no way to announce to the public that there are shortages of produce
at particular times and so price hikes are expected or price reduction in order to clear
excess in the market.

• The circulation of information is one of the best thing today’s society. However,
information about local markets are not circulating as it should.

3
 1.3 Need for the Proper System
Collecting the information from various research papers and other sources.
We analyzed that many farmers want to sell their products but they have
concern with the middle-man in the mandi. Sometimes people do not know
specific information about particular crops items as well as seller is not
technically skilled. Farmers does not compare prices with different
shopkeeper and there is no facility for online payment only cash may
consume.

So, in this case KisaanKart platform where farmers and street vendors can
directly sell their products to the customers and big companies and make
payment easily. Customer service is extremely important. We want each
customer to have a pleasant shopping experience, and it is the intention of our
staff to answer questions with expertise and to offer advice when we feel it is
needed.

Retain customers to generate repeat purchases and make referrals. Continue to

expand daily sales by adding to the variety of products we sell.
Communication with our customers through creative advertising. Customers
can buy from their home. Customers can view a large number of plants
available in a mandi. When an admin decides to check out the order, then
information including the buyer’s name, address and billing instruction is
record in system for future references.

1.4 Objectives

The aim of this project it to give information about the content of any kisan mandi to
anyone who so wants to check current prices of available products, order products,
spend less time in the market and shopping centers to reduce the stress and hustle of
shopping and finding of customers.

The Objectives of using an kisaankart are to:

• Provide accessible information about products to customers who have are cut off
by distance of other constrains but need to shop or window shop.
4
• To minimize the difficulty of business owners from finding customers and
reducing the cost of advertisement which are paid to most radio and television
stations who genuinely allocate smallest of their broadcast time to such broadcast.
• Eliminate the unwanted patrol of window shoppers who take up space in various
shops and markets. This goes a long way to reduce human traffic in our markets.
• Extremely minimize the losses due to shoplifting and cost associated with security.

Following is some of the key features of our system, which distinguishes it from
others:

▪ Display all the available categories of products on the home page.

▪ We can further explore the items of all the categories present.
▪ Admin has the authority to add new particulars to the items list whenever needed.
▪ Permission to the administrator to remove items, anytime.
▪ Allows the admin to modify the price of each item, whenever required or felt like.
▪ Admin has the authority to update the description of each item.
▪ Permission to the admin to view information about each customer who
checkouts the items list.
▪ Provides facilities to client to contact anytime to the customer care service.

5
1.5 Modules of the System
This project mainly divided into two modules:

A) Admin module: -

1. Admin first log in himself in the website without registering.

2. He can view the order which can be added to cart from the customer side.
3. He can send order confirmation message to the customer and also if any
plant wants to add the website then he can update the information.
4. Admin can also update in calendar that which plant will be suitable to buy in
which season.
5. Admin can add and remove the plant cards as per availability

B) User module:-

1. User can log in himself in the website.

2. He can select the plant item and purchase the plant by comparing prices
with different shop keeper.
3. Purchased plant details will be added to the cart.
4. He can pay amount on cash on delivery.
5. He can view the calendar.
6. If any complaint about the product then he can give the feedback by calling.

Figure: 1 Admin Module

6
Figure: 2 Manage Order Module

Figure :3 Manage Items Module

Figure: 4 Users Module

7
Figure: 5 Representation of Flow of Modules

8
 1.6 Scope

The KisaanKart platform is to increase the profit margin of farmers and conveniently grant access to
products of farmers available in the mandi to the potential customers. KisaanKart market will be
made up various parts which include:

• Product catalog. An organization of the products will be made for clear navigation of the site
which will mean it will be browseable by all

• Product attributes. Customers need to what product they need before logging on to make a
purchase. Attributes are generally accepted as a must: product name, category, description, price,
and photo / image of the product.

• Check out. The eCommerce checkout needs to provide a way to take payment, append relevant
taxes (if necessary), compute shipping and handling costs, provide a sub-total of the amount due,
collect billing and shipping information from the customer.

• Reporting & order tracking. Some stores have a way to track the status of the order through the
fulfillment and shipping stages.

• Security is vital. The website will be encrypted with HTTPS, at a minimum to ensure losses are
not made.

9
 2. LITERATURE REVIEW
Shopping online has never been so easy. With the flourishing numbers of online
businesses, people nowadays have various choices to do their shopping. Big
companies such as amazon.com have introduced many values added features to
help the farmers and consumers to decide what to shop for. With features such
as price comparison, product photos and user reviews, consumers can shop
easily and smartly without even going to the stores and having such a hard time
looking for the products they want.
All they have to do are just browse for the product they want on the website and
within a few mouse clicks they have them. Such simplicity is what makes online
shopping appealing for consumers and farmers. The question is, why do many
people still decline to shop online? Well, for most people, privacy and security
issues are their concerns. Hence, here I will discuss customers’ perception of
privacy and security issues, the reality of such issues and ways to avoid those
issues, all based on some trustworthy sources I have found. Also, in our systems
transacting business online does not go so well in the country.

10
 2.1 Existing System
The current system for farmers is to visit the mandi and sell their
products available middleman on their price and their quantity of
will. And customer get that product after multiplying the price 2-3
times.

1. It is less user-friendly.
2. Farmers must go to mandi and select middleman
3. It is difficult to identify the required product.
4. Description of the product limited.
5. It is a time-consuming process
6. Not in reach of distant users.
7. Price get doubled when it reaches the end consumers

2.2 Proposed System

The proposed system is a website that will collect information about

customers who wish to buy or check prices of items from the market. Aside
this, the website is proposed to be an extension of the market to farmers who
find it difficult to arrive at the mandi which are located in busy business
districts of most cities. This system is geared at easing the shopping stress of
most farmers who have to hustle from shed to shed in the scorching sun just
to sell stuff in the crowded market.

This proposed system should be able to give analysis of customer shopping

preference which will assist in predictive behavior and shopping trends of
customers. Customer management is possible because a restricted access will
be put on the website to force whoever is interested in shopping to registers
with a valid national identification as a measure to prevent fraudsters from
going unidentified.

This will be the customer database that will be secured on an encrypted server
11
which will hold vital information like the transaction details between sellers
in the markets and customers.
Customers can easily be picked out for special promotions based on their
shopping history. This will also help customers to keep track of expenses
made in time past. Customer satisfaction is ensured on this proposed system.
Questionnaires will be provided to customers to review services rendered to
them over the online market to evaluate sellers who were up to the task of
reaching or surpassing the expectations of customers.

12
This is will be rated and displayed against the sellers’ username. This is also to put a
check on sellers who are fraudsters who receive payments and never deliver, can be
made available to reward their consistence. This will make the shopping experience very
personal to all. Reaching further at a little cost is made possible by the implementation
of this system since the website can be reached by all in any location.

For instance if a hotel X, lives in M.P and needs a brand of oats, he can simply logon to
the website, check it out if its available or not rather than driving all the way to Punjab
which is typically packed with traffic.

The website will function in this manner:

• Customer Account registration.
• Products and pricing display.
• Customer relation is possible.
• Draw the supermarkets closer to customers
• Elimination of long queues in shopping halls.
• Unlimited profit potentials
• It never closes down.
Above all, the proposed system should grant access to transactions over the
internet using the various payment This would allow a lot of business to
grow beyond the borders of markets and penetrate the international market.

13
 2.3 Feasibility Study
Feasibility is defined as the practical extent to which a project can be
performed successfully. To evaluate feasibility, a feasibility study is
performed, which determines whether the solution considered to accomplish
the requirements is practical and workable in the software. Information such as
resource availability, cost estimation for software development, benefits of the
software to the organization after it is developed and cost to be incurred on its
maintenance are considered during the feasibility study. The objective of the
feasibility study is to establish the reasons for developing the software that is
acceptable to users, adaptable to change and conformable to established
standards.

Types of Feasibility

Various types of feasibility that are commonly considered include technical

feasibility, operational feasibility, and economic feasibility

2.3.1 Technical Feasibility

It is a measure of the how practical solutions are and whether the technology is
already available within the organization. If the technology is not available to
the firm, technical feasibility also looks at whether it can be acquired.
Technical feasibility centers around the existing system and to what extent its
support can be extended to the proposed system. This project is technically
feasible and to maximum extent the existing systems support the proposed
system.

Our project is a web-based application. The main technology that are associated are:

MERN STACK
1. MONGODB
2. EXPRESS.JS
3. REACT.JS
4. NODE.JS
All of these technologies are freely available and technical skills are manageable.

14
2.3.2 Economic Feasibility
It is a measure of how well the system will work in the organization. It is also a
measure of how people feel about the system/project. In this project the user
feels that the system is very user friendly this project developed is worth and
solution to the problem will work successfully.

2.3.3 Operational Feasibility

It is a measure of the cost-effective of a project or solutions. It is a measure of
whether a solution will pay for itself or how profitable a solution will be , this
is often called a cost- benefit analysis.

So, it‘s clear that project has the required operational feasibility.

15
 3. REQUIREMENTS ANALYSIS

3.1 Method used for Requirement analysis

For requirement analysis we have used UML diagrams and Data flow
diagrams. UML is a modeling standard primarily used for specification,
development, visualization and documenting of software system. To capture
important business process and artifacts UML provides objects like

• Use Case
• Object
• Activity
• Class
• Sequence
• Collaboration

There are 14 UML diagrams that help with modelling like the use case
diagram, interaction diagram, class diagram, component diagram, sequence
diagram, etc. UML models are important in the IT segment as it becomes the
medium of communication between all stakeholders. A UML-based business
model can be a direct input to a requirements tool. A UML diagram can be of
two type's Behavioral model and Structural model. A behavioral model tries to
give information about what the system do while a structural model will give
what is the system consist of.

Data flow diagrams show how data is processed by a system in terms of inputs
and outputs. Components of data flow diagram includes

• Process
• Flow
• Store
• Terminator

A logical data flow diagram shows system's activities while a physical data
flow diagram shows a system's infrastructure. A data flow diagram can be
designed early in the requirement elicitation process of the analysis phase
within the SDLC (System Development Life Cycle) to define the project
scope. For easy analyzing a data flow diagram can be drilled down into its sub-
16
processes known as "levelled DFD".

3.2 Data Requirements

• Details of users.
• Details of Product
• Details of product that currently are in need.
• Details of product which are currently available.
• Details of person who purchased the product.
• User:
a. Name
b. Email Id
d. Phone number
d. Address

3.3 Functional Requirement

This section provides requirement overview of the system. Various functional
modules that can be implemented by the system will be -

1. Login
Customer logins to the system by entering valid email id and one time
password for the shopping

2. Changes to Cart
Changes to cart means the customer after login can make order or cancel order
of the product from the shopping cart.

3. Payment
For customer there is a secured bill is generated and he can pay cash on delivery.

4. Logout
After the product will be ordered by the customer he will logged out.

5. Report Generation
After the product is being ordered it is being reported to the admin and user
gets the notification that his order is being placed.

6. Manage Products
The administrator can add product, delete product and view product.

7. Manage Orders
The administrator can view orders and delete orders.
17
3.4 Non-Functional Requirements
1. Efficiency Requirement
When an online KisaanKart management application implemented customer
can purchase product in an efficient manner.

2. Reliability Requirement
The system should provide a reliable environment to both customers and owner. All
orders
should be reaching at the admin without any errors.

3. Usability Requirement
The website is designed for user friendly environment and ease of use.

4. Implementation Requirement
Implementation of the system using html, css and in front end with jsp as back
end and it will be used for database connectivity. And the database part is
developed by mysql. Responsive web designing is used for making the website
compatible for any type of screen.

5. Availability Requirement
The system should be available at all times, meaning the user can access it
using a web browser, only restricted by the down time of the server on which
the system runs. Also in case of a hardware failure or database corruption,
backups of the database should be retrieved from the server and saved by the
administrator. Then the service will be restarted. It means 24*7 availability.

6. Maintainability
A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a re-initialization
of the program will be done. Also the software design is being done with
modularity in mind so that maintainability can be done efficiently.

7. Portability
The application is HTML and scripting language based. So the end-user part is
fully portable and any system using any web browser should be able to use the
features of the system, including any hardware platform that is available or
will be available in the future. An end-user is use this system on any OS; either
it is Windows or Linux.
The system shall run on PC, Laptops, and PDA etc.
18
8. Interface Requirement
Various interfaces for the product could be-
1. Login Page
2. There will be a screen displaying information about product that the shop having.
3. If the customers select the buy button then another screen of shopping cart
will be opened.
4. After product is being placed it will report to the admin along with the details of
product.

8.1 Hardware Interface

The System must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system. As for e.g. Modem,
WAN – LAN, Ethernet Cross- Cable.

8.2 Software Interface

The system require Data Base also for the store the any transaction of the
system like MYSQL etc. system also require DNS(domain name space) for the
naming on the internet. At the last user need web browser for interact with the
system.

9. Performance Requirement
There is no performance requirement in this system because the server request
and response is depended on the end user internet connection.

10. Design Constrain

The system shall be built using a standard web page development tool that
conforms to Microsoft ‘s GUI standards like HTML etc.

19
20
3.5 System Specification
The system consists of two parts. A web application which can provide the
online shopping service and an application for the customer to access the web
service from his Smartphone. Web application should be able to help the
customer for selecting his item and to help the owner in managing the orders
from the customers

3.5.1 Software Specifications

For Website:
• MERN Stack
For Software Product:

● Operating System: Windows XP/ Windows 7/ Linux

● Software: Heruko

● Postman

3.5.2 Hardware Specification

● Processor Name: Dual Core
● Processor Speed: 3.2 GHz
● RAM: 2 GB
● Hard Disk Capacity: 80 GB
● Display Device: 14‘ to 19‘ InchMonitor
● Keyboard Type: PS2 or USB
● Mouse Type: PS2 or USB

21
 4. DESIGN

4.1 Software Requirements Specification

The Software Requirements Specification is designed to document and
describe the agreement between the customer and the developer regarding the
specification of the software product requested. Its primary purpose is to
provide a clear and descriptive
―statement of user requirements‖ that can be used as a reference in further
development of the software system. This document is broken into a number of
sections used to logically separate the software requirements into easily
referenced parts.

This Software Requirements Specification aims to describe the Functionality,

External Interfaces, Attributes and Design Constraints imposed on
Implementation of the software system described throughout the rest of the
document. Throughout the description of the software system, the language
and terminology used should unambiguous and consistent throughout the
document.

4.1.1 Glossary

• SRS – Software Requirement Specification

• User- Customer who can order plants.
• Admin- Owner of the Ecommerce Website: KisaanKart manager who manages
it.
• Home- Place where all the plants and supplements are present.
• Items- Plants items and supplements to be sell.
• Orders- Items which are ordered by user.
• Calendar- Gives description of which plant is suitable for which season.

4.1.2 Supplementary Specifications

• Performance Requirements: In order to maintain an acceptable speed at

maximum number of uploads allowed from a particular customer as any
number of users can access to the system at any time. Also, the connections to
the servers will be based on the attributes of the user like his location and
server will be working 24X7 times.

• Technical Issues: This system will work on client-server architecture. It will

require an internet server and which will be able to run PHP application. The
22
system should support some commonly used browser such as IE, Mozilla
Firefox, chrome etc.

• Interface Requirement: Various interfaces for the product could be

1. Login Page
2. There will be a screen displaying information about product that the shop having.
3. If the customers select the buy button then another screen of shopping cart
will be opened.
4. After product is being placed it will report to the admin along with the details of
product.

• Hardware Interface
The System must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system. As for e.g.
Modem, WAN – LAN, Ethernet Cross-Cable.

• Software Interface
The system require Data Base also for the store the any transaction of
the system like MYSQL etc. system also require DNS(domain name
space) for the naming on the internet. At the last user need web browser
for interact with the system.

23
4.1.3 Use Case Model

A UML use case diagram is the primary form of system/software

requirements for a new software program underdeveloped. Use cases specify
the expected behavior (what), and not the exact method of making it happen
(how). Use cases once specified can be denoted both textual and visual
representation (i.e. use case diagram). A key concept of use case modeling is
that it helps us design a system from the end user's perspective. It is an
effective technique for communicating system behavior in the user's terms by
specifying all externally visible system behavior.

Only static behaviour is not sufficient to model a system rather dynamic

behaviour is more important than static behaviour. In UML, there are five
diagrams available to model the dynamic nature and use case diagram is one of
them. Now as we have to discuss that the use case diagram is dynamic in
nature, there should be some internal or external factors for making the
interaction.

The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four
diagrams (activity, sequence, collaboration, and State chart) also have the same
purpose.

Use case diagrams are used to gather the requirements of a system including
internal and external influences. These requirements are mostly design
requirements. Hence, when a system is analyzed to gather its functionalities,
use cases are prepared and actors are identified.

24
 Figure: 6 Use Case Diagram

4.2 Conceptual Level Class Diagram

Domain models are solution-independent descriptions of a problem domain
produced in the analysis phase of a software engineering project. The term
―conceptual model‖ is often used as a synonym of ―domain model‖. A domain
model may include both descriptions of the domain‘s state structure (in
conceptual information models) and descriptions of its processes (in
conceptual process models). They are solution-independent, or ‗computation-
independent‘, in the sense that they are not concerned with making any system
design choices or with other computational issues. Rather, they focus on the
perspective and language of the subject matter experts for the domain under
consideration.

25
In the design phase, first a platform-independent design model, as a general
computational solution to the given software engineering problem, is
developed on the basis of the domain model. The same domain model can
potentially be used to produce a number of (even radically) different design
models representing different design choices. Then, by taking into
consideration a number of implementation issues ranging from architectural
styles, nonfunctional quality criteria to be maximized (e.g., performance,
adaptability) and target technology platforms, one or more platform-specific
implementation models are derived from the design model.

• A conceptual model captures the important concepts and relationships in some

domain.

• Concepts are represented by classes, while relationships are represented by

associations.

• Packages represent groups of related classes and associations.

• Objects represent specific instances of classes.

Figure: 7 Conceptual Level Class Diagram

26
4.3 Data flow Diagram
DFD graphically representing the functions, or processes, which capture,
manipulate, store, and distribute data between a system and its
environment and between components of a system. The visual
representation makes it a good communication tool between User and
System designer. Structure of DFD allows starting from a broad overview
and expands it to a hierarchy of detailed diagrams. DFD has often been
used due to the following reasons:

• Logical information flow of the system

• Determination of physical system construction requirements
• Simplicity of notation
• Establishment of manual and automated systems requirements

The following observations about DFDs are essential:

1. All names should be unique. This makes it easier to refer to elements in the DFD.
2. Remember that DFD is not a flow chart. Arrows is a flow chart that
represents the order of events; arrows in DFD represents flowing data. A DFD
does not involve any order of events.
3. Suppress logical decisions. If we ever have the urge to draw a diamond-
shaped box in a DFD, suppress that urge! A diamond-shaped box is used in
flow charts to represents decision points with multiple exists paths of which
the only one is taken. This implies an ordering of events, which makes no
sense in a DFD.

Do not become bogged down with details. Defer error conditions and error
handling until the end of the analysis.

Data flow diagram levels

Data flow diagrams are also categorized by level. Starting with the most
basic, level 0, DFDs get increasingly complex as the level increases. As
you build your own data flow diagram, you will need to decide which
level your diagram will be.

Level 0 DFDs, also known as context diagrams, are the most basic data
27
flow diagrams. They provide a broad view that is easily digestible but
offers little detail. Level 0 data flow diagrams show a single process node
and its connections to external entities.

Level 1 DFDs are still a general overview, but they go into more detail
than a context diagram. In a level 1 data flow diagram, the single process
node from the context diagram is broken down into sub processes. As
these processes are added, the diagram will need additional data flows and
data stores to link them together.
Level 2 DFDs simply break processes down into more detailed sub
processes. In theory, DFDs could go beyond level 3, but they rarely do.
Level 3 data flow diagrams are detailed enough that it doesn‘t usually
make sense to break them down further.

Figure: 8 0 Level Dataflow Diagram

28
Figure: 9 1 Level Dataflow Diagram

29
Figure: 10 2 Level Dataflow Diagram

30
31
4.5 Database Design (ER-Diagram)

An Entity–relationship model (ER model) describes the structure of a database

with the help of a diagram, which is known as Entity Relationship Diagram
(ER Diagram). An ER model is a design or blueprint of a database that can
later be implemented as a database. The main components of E-R model are:
entity set and relationship set.

An ER diagram shows the relationship among entity sets. An entity set is a

group of similar entities and these entities can have attributes. In terms of
DBMS, an entity is a table or attribute of a table in database, so by showing
relationship among tables and their attributes, ER diagram shows the complete
logical structure of a database. ERD Diagram allows you to communicate with
the logical structure of the database to users

Here, are prime reasons for using the ER Diagram

• Helps you to define terms related to entity relationship modeling

• Provide a preview of how all your tables should connect, what fields are
going to be on each table
• Helps to describe entities, attributes, relationships
• ER diagrams are translatable into relational tables which allows you to build
databases quickly
• ER diagrams can be used by database designers as a blueprint for
implementing data in specific software applications
• The database designer gains a better understanding of the information to be
contained in the database with the help of ERP diagram

Following are the main components and its symbols in ER Diagrams:

• Rectangles: This Entity Relationship Diagram symbol represents entity types

• Ellipses : Symbol represent attributes
• Diamonds: This symbol represents relationship types
• Lines: It links attributes to entity types and entity types with other relationship types
• Primary key: attributes are underlined
• Double Ellipses: Represent multi-valued attributes

32
Figure-11 ER Diagram

33
 5. SYSTEM MODELING

System modeling is the process of developing abstract models of a system,

with each model presenting a different view or perspective of that system. It is
about representing a system using some kind of graphical notation, which is
now almost always based on notations in the Unified Modeling Language
(UML).

Models help the analyst to understand the functionality of the system; they are
used to communicate with customers. Models can explain the system from
different perspectives: An external perspective, where you model the context
or environment of the system.

An interaction perspective, where you model the interactions between a system

and its environment, or between the components of a system.

A structural perspective, where you model the organization of a system or the

structure of the data that is processed by the system.

A behavioral perspective, where you model the dynamic behavior of the

system and how it responds to events

5.1 Detailed Class Diagram

Detailed Class Diagram gives an overview of a software system by displaying

classes, attributes, operations, and their relationships. This Diagram includes
the class name, attributes, and operation in separate designated compartments.

Class Diagram defines the types of objects in the system and the different
types of relationships that exist among them. It gives a high-level view of an
application. This modeling method can run with almost all Object-Oriented
Methods. A class can refer to another class. A class can have its objects or may
inherit from other classes.

Class diagram is a static diagram. It represents the static view of an

application. Class diagram is not only used for visualizing, describing, and
documenting different aspects of a system but also for constructing executable
code of the software application.
Class diagram describes the attributes and operations of a class and also the
34
 constraints imposed on the system. The class diagrams are widely used in the
modeling of object oriented systems because they are the only UML
diagrams, which can be mapped directly with object-oriented languages.
Class diagram shows a collection of classes, interfaces, associations,
collaborations, and constraints. It is also known as a structural diagram.
The purpose of the class diagram can be summarized as −
• Analysis and design of the static view of an application.

• Describe responsibilities of a system.

• Base for component and deployment diagrams.
• Forward and reverse engineering.

Class Diagram Notation

A class notation consists of three parts:

1. Class Name

• The name of the class appears in the first partition.

2. Class Attributes

• Attributes are shown in the second partition.

• The attribute type is shown after the colon.
• Attributes map onto member variables (data members) in code.
3. Class Operations (Methods)

• Operations are shown in the third partition. They are services the class provides.
• The return type of a method is shown after the colon at the end of the method
signature.
• The return type of method parameters is shown after the colon following
the parameter name.
Operations map onto class methods in code

35
36
Figure-12 Detailed Class Diagram

37
5.2 Interaction Diagram
Interaction Diagram are used in UML to establish communication
between objects. It does not manipulate the data associated with the
particular communication path. Interaction diagrams mostly focus on
message passing and how these messages make up one functionality
of a system. Interaction diagrams are designed to display how the
objects will realize the particular requirements of a system. The
critical component in an interaction diagram is lifeline and messages.

Various UML elements typically own interaction diagrams. The

details of interaction can be shown using several notations such as
sequence diagram, timing diagram, communication/collaboration
diagram. Interaction diagrams capture the dynamic behavior of any
system.
5.2.1 Sequence Diagram
UML Sequence Diagrams are interaction diagrams that detail how
operations are carried out. They capture the interaction between objects in
the context of a collaboration. Sequence Diagrams are time focus and they
show the order of the interaction visually by using the vertical axis of the
diagram to represent time what messages are sent and when. A sequence
diagram is a type of interaction diagram because it describes how— and in
what order—a group of objects works together. These diagrams are used by
software developers and business professionals to understand requirements
for a new system or to document an existing process. Sequence diagrams
are sometimes known as event diagrams or event scenarios. Benefits of
sequence diagrams

Sequence diagrams can be useful references for businesses and other

organizations. Try drawing a sequence diagram to:

• Represent the details of a UML use case.

• Model the logic of a sophisticated procedure, function, or operation.
• See how objects and components interact with each other to complete a process.
• Plan and understand the detailed functionality of an existing or

future scenario Notations of a Sequence Diagram

38
Lifeline-An individual participant in the sequence diagram is represented by a
lifeline. It is positioned at the top of the diagram.

Actor-A role played by an entity that interacts with the subject is called as an
actor. It is out of the scope of the system. It represents the role, which involves
human users and external hardware or subjects. An actor may or may not
represent a physical entity, but it purely depicts the role of an entity. Several
distinct roles can be played by an actor or vice versa.

39
Messages-The messages depict the interaction between the objects and are
represented by arrows. They are in the sequential order on the lifeline. The
core of the sequence diagram is formed by messages and lifelines.

Following are types of messages enlisted below:

Call Message: It defines a particular communication between the lifelines of

an interaction, which represents that the target lifeline has invoked an
operation.

Return Message: It defines a particular communication between the lifelines of

interaction that represent the flow of information from the receiver of the
corresponding caller message

Self Message: It describes a communication, particularly between the lifelines

of an interaction that represents a message of the same lifeline, has been
invoked.

Recursive Message: A self message sent for recursive purpose is called a

recursive message. In other words, it can be said that the recursive message is
a special case of the self message as it represents the recursive calls.

Create Message: It describes a communication, particularly between the

lifelines of an interaction describing that the target (lifeline) has been
instantiated.

Destroy Message: It describes a communication, particularly between the

lifelines of an interaction that depicts a request to destroy the lifecycle of
the target.

40
 Figure-13 Sequence Diagram

5.2.2 Collaboration Diagram

Use a Collaboration diagram (collaboration diagram: An interaction
diagram that shows, for one system event described by one use case, how
a group of objects collaborate with one another.) to show relationships
among object roles such as the set of messages exchanged among the
objects to achieve an operation or result.
UML Collaboration diagrams (interaction diagrams) illustrate the
relationship and interaction between software objects. They require use
cases, system operation contracts, and domain model to already exist. The
collaboration diagram illustrates messages being sent between classes and
objects (instances). A diagram is created for each system operation that
relates to the current development cycle (iteration).
A collaboration diagram, also called a communication diagram or
interaction diagram,. A sophisticated modelling tool can easily convert a
collaboration diagram into a sequence diagram and the vice. A
collaboration diagram resembles a flowchart that

41
portrays the roles, functionality and behaviour of individual objects as
well as the overall operation of the system in real time.
When creating collaboration diagrams, patterns are used to justify
relationships. Patterns are best principles for assigning responsibilities to
objects and are described further in the section on patterns. There are two
main types of patterns used for assigning responsibilities which are
evaluative patterns and driving patterns.
Each system operation initiates a collaboration diagram. Therefore, there
is a collaboration diagram for every system operation.

Why Collaboration Diagram ?

Unlike a sequence diagram, a collaboration diagram shows the

relationships among the objects. Sequence diagrams and collaboration
diagrams express similar information, but show it in different ways.

Because of the format of the collaboration diagram, they tend to better

suited for analysis activities (see Activity: Use-Case Analysis).
Specifically, they tend to be better suited to depicting simpler interactions
of smaller numbers of objects. However, if the number of objects and
messages grows, the diagram becomes increasingly hard to read. In
addition, it is difficult to show additional descriptive information such as
timing, decision points, or other unstructured information that can be
easily added to the notes in a sequence diagram.

42
 Figure: 14 Collaboration Diagram

5.3 Activity Diagram

Activity diagram is another important behavioral diagram in UML diagram to
describe dynamic aspects of the system. Activity diagram is essentially an
advanced version of flow chart that modeling the flow from one activity to
another activity.

Activity Diagrams describe how activities are coordinated to provide a service

which can be at different levels of abstraction. Typically, an event needs to be
achieved by some operations, particularly where the operation is intended to
achieve a number of different things that require coordination, or how the
events in a single use case relate to one another, in particular, use cases where

43
activities may overlap and require coordination. It is also suitable for
modeling how a collection of use cases coordinate to represent business
workflow.

1. Identify candidate use cases, through the examination of business workflows

2. Identify pre- and post-conditions (the context) for use cases
3. Model workflows between/within use cases
4. Model complex workflows in operations on objects
5. Model in detail complex activities in a high-level activity Diagram

44
Figure: 15 Activity Diagram for Users

45
Figure: 16 Activity Diagram for Admin

46
47
5.4 Component Diagram
Component diagrams are different in terms of nature and behavior.
Component diagrams are used to model the physical aspects of a system. Now
the question is, what are these physical aspects? Physical aspects are the
elements such as executables, libraries, files, documents, etc. which reside in a
node.

Component diagrams are used to visualize the organization and relationships

among components in a system. These diagrams are also used to make
executable systems.

Purpose of Component Diagrams

Component diagram is a special kind of diagram in UML. The purpose is also

different from all other diagrams discussed so far. It does not describe the
functionality of the system but it describes the components used to make those
functionalities.

Thus from that point of view, component diagrams are used to visualize the
physical components in a system. These components are libraries, packages,
files, etc.

Component diagrams can also be described as a static implementation view of

a system. Static implementation represents the organization of the components
at a particular moment.

A single component diagram cannot represent the entire system but a

collection of diagrams is used to represent the whole.

The purpose of the component diagram can be summarized as –

• Visualize the components of a system.

• Construct executables by using forward and reverse engineering.
• Describe the organization and relationships of the components.

Component diagrams can be used to –

• Model the components of a system.
• Model the database schema.
48
• Model the executables of an application.
• Model the system’s source code

Figure: 17 Component Diagram

49
Deployment Diagram

In the UML, you use class diagrams and component diagrams to reason about
the structure of your software. You use sequence diagrams, collaboration
diagrams, statechart diagrams, and activity diagrams to specify the behavior of
your software. At the edge of your system‘s software and hardware, you use
deployment diagrams to reason about the topology of processors and devices
on which your software executes.
UML deployment diagram is an implementation diagram that shows the
structure of a runtime system. From it, you can learn about the physical
relationships among software and hardware components and the distribution
of components to processing nodes. Use a deployment diagram to show the
structure of the run-time system and communicate how the hardware and
software elements that make up an application will be configured and
deployed.
A UML deployment diagram is a diagram that shows the configuration of run
time processing nodes and the components that live on them. Deployment
diagrams is a kind of structure diagram used in modeling the physical aspects
of an object-oriented system. They are often be used to model the static
deployment view of a system (topology of the hardware).

The purpose of deployment diagrams can be described as –

• Visualize the hardware topology of a system.
• Describe the hardware components used to deploy software components.
• Describe the runtime processing
nodes. Deployment diagrams can
be used –
• To model the hardware topology of a system.
• To model the embedded system.
• To model the hardware details for a client/server system.
• To model the hardware details of a distributed application engineering.

50
Figure: 18 Deployment Diagram

51
 KisaanKart

5.7 Test Plans and Implementation Images

The Test Plan covers the details of the testing process of the project
i.e., ―Ecoomerce Website: KisaanKartManagement System‖. It deals with all
the testing needs for our project that are required at present. The features of
project that will be tested are as follows:

● Add details and items

● Details storage in Database

● Details modified easily

● Train and Test Dataset

● Display the Item details directly

Test Case Pass/Fail criteria for our project clearly states that:

• If the function takes input and provides the exact required output, ―Test case Pass‖.

• If required output is not obtained, ―Test

case Fail‖. Test Cases

Test Id: T01

Test scenario: Checking Empty cart and Check out

52
 KisaanKart

Figure: 19

53
 KisaanKart

54
 KisaanKart

55
 KisaanKart

56
 KisaanKart

6. CONCLUSIONS & FUTURE WORK

The project entitled Ecommerce Website: KisaanKart was completed successfully.

The system has been developed with much care and free of errors and at the same time it is
efficient and less time consuming. The purpose of this project was to develop a web
application and an android application for purchasing items from a shop.

This project helped us in gaining valuable information and practical knowledge on several
topics like designing web pages using mern, usage of responsive templates, designing of
android applications, and management of database . The entire system is secured.

Also the project helped us understanding about the development phases of a project and
software development life cycle. We learned how to test different features of a project. This
project has given us great satisfaction in having designed an application which can be
implemented to any nearby shops or branded shops selling various kinds of products by
simple modifications.

This project is only a humble venture to satisfy the needs in a shop. Several user friendly
coding have also adopted. This shall prove to be a powerful in satisfying all the
requirements of the organization. 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. This website provides a computerized version of shop manipulate system which
will benefit the users as well as the visitor of the shop. It makes entire process online where
users can explore product, and buy various product. It also has a facility for common user by
login into the system where user can login and can see status of ordered item as well request
for items or give some suggestions. It provide the facility of admin‘s login where admins
can add various item, review users activity and also give occasional discount and also add
info about different events for the customer.

6.1 Limitations of Project

Ease of use is the prime reason that drives the success of e-commerce. Though the internet
provides a quick and easy way to purchase a product, some people prefer to use this
technology only in a limited way. Some people also fear that they might get addicted to
online shopping. The major disadvantages of online shopping are as follows.
1. Product Capacity: There can be instances where the Product might not be in sufficient
quantity

2. Product Satisfaction: There can be times when the customer may not be satisfied with the
obtained product like supplements and the crops they receive.

57
 KisaanKart

3. Huge Cost: Last but not the least; a lot of money needs to be invested to be built up the
technical infrastructure as well as to build nurseries at different locations. Moreover, they
need to be upgraded to keep up with the changing technology and fashion.
4. Missing the shopping experience- The traditional shopping exercise provides a lot of fun
in the form of showroom atmosphere, e smart sales attendants, scent and sounds that cannot
be experienced through a website. Indians generally enjoy shopping. Consumers look
forward to it as an opportunity to go out and shop.

6.2 Future Enhancement

Our designed online shopping system provides a 24×7 service, that is customers can surf the
website, place orders anytime they wish to. Also, the delivery system works 24×7 hours a
week. Some of the features that can be modified and added to this system in the future
involve its implementation by local shopkeepers, where shops will be providing an online
interface to customers for shopping and placing orders.

1. Capacity will be increased in accordance with the growing traffic on the site.

2. This application can be used by any user to purchase the online plants and get appropriate
information by viewing short summery about the plants items through videos.

3. If any changes to make customer can purchase the plants through different payment
schemes like debit card, credit card, pat, phone pay, cash on delivery etc.

58
 KisaanKart

7. Bibliography & References

7.1 Reference Books

https://www.youtube.com/watch?v=7CqJlxBYj-M

https://en.wikipedia.org/wiki/2020%E2%80%932021_Indian_farmers%
27_protest#:~:text=Other%20related%20issues%20include%20farmer,i
s%2028%20people%20a%20day.

59