Anda di halaman 1dari 71

A MINI PROJECT REPORT ON

“E-MANDI”
Submitted

In the partial fulfilment of the requirements for


The award of the degree of
BACHELOR OF TECHNOLOGY

In

COMPUTER SCIENCE & ENGINEERING


By

D.JYOTHIKA (151FA04014)
N.NAVYA (151FA04180)
P.ANANYU (151FA04308)
Under the esteemed guidance of
Mr. Ch. Venkata RamiReddy, Assistant Professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING


VIGNAN'S FOUNDATION FOR SCIENCE, TECHNOLOGY AND
RESEARCH
(Accredited by NAAC “A” grade)
Vadlamudi, Guntur.

~i~
A MINI PROJECT REPORT ON

“E-MANDI”
Submitted

In the partial fulfilment of the requirements for


The award of the degree of
BACHELOR OF TECHNOLOGY

In

COMPUTER SCIENCE & ENGINEERING


By

D.JYOTHIKA (151FA04014)
N.NAVYA (151FA04180)
P.ANANYU (151FA04308)

Under the esteemed guidance of


Mr. Ch. Venkata RamiReddy, Assistant.Professor

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING


VIGNAN'S FOUNDATION FOR SCIENCE, TECHNOLOGY AND
RESEARCH
(Accredited by NAAC “A” grade)
Vadlamudi, Guntur.

~ ii ~
VIGNAN’S FOUNDATION FOR SCIENCE TECHNOLOGY
AND RESEARCH
(Accredited by NAAC “A” grade)

CERTIFICATE

This is to certify that the Mini project Report entitled “E-MANDI” that is being
submitted by D.Jyothika (151FA04014), P.Ananyu (151FA04308) and N.Navya
(151FA04180) in partial fulfilment for the award of B.Tech degree in Computer
Science and Engineering to the Vignan’s Foundation for Science, Technology and
Research, Deemed to be University, is a record of bonafide work carried out by them
under my supervision.

Mr. Ch.Venkata Ramireddy External Examiner Dr. D. Venkatesulu


Assistant.Professor HOD, CSE

~ iii ~
DECLARATION

I hereby declare that the project entitled “E-MANDI submitted for the
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING, VFSTR
Deemed to be University . This dissertation is our original work and the project has
not formed the basis for the award of any degree, associate-ship and fellowship or any
other similar titles and no part of it has been published or sent for publication at the
time of submission.

By
D.JYOTHIKA (151FA04014)
N.NAVYA (151FA04180)
P.ANANYU (151FA04308)

Date: 06-04-2018

~ iv ~
ACKNOWLEDGEMENT

We are very grateful to our beloved Chairman Dr. Lavu. Rathaiah, and Vice
Chairman Mr. Lavu. Krishna Devarayalu , for their love and care.

It is our pleasure to extend our sincere thanks to Vice-Chancellor Dr. M.Y.S.


Prasad and Dean Engineering & Management, Dr. V.MADHUSUDAN RAO, for
providing an opportunity to do my academics in VFSTR.

It is a great pleasure for me to express my sincere thanks to Dr. D.Venkatesulu


HOD, CSE of VFSTR, for providing me an opportunity to do my Mini Project.

We feel it our responsibility to thank Mr. Ch. Venkata RamiReddy under whose
valuable guidance that the project came out successfully after each stage.

We extend our whole hearted gratitude to all our faculty members of Department of
Computer Science and Engineering who helped us in our academics throughout
course.
Finally we wish to express thanks to our family members for the love and
affection overseas and forbearance and cheerful depositions, which are vital for
sustaining effort, required for completing this work.

With Sincere regards,


D.JYOTHIKA (151FA04014)
N.NAVYA (151FA04180)
P.ANANYU (151FA04308)

~v~
TABLE OF CONTENTS

ACKNOWLEDGEMENT ..................................................................................................... v
LIST OF FIGURES ............................................................................................................ viii
LIST OF TABLES ................................................................................................................ ix
ABBREIVATIONS ............................................................................................................... x
1. INTRODUCTION ............................................................................................................. 2
1.1 Introduction .................................................................................................................. 2
1.2Literature Survey .......................................................................................................... 2
1.3 Project Background ...................................................................................................... 2
1.4 Objective ...................................................................................................................... 3
1.5 Project Description....................................................................................................... 3
2. SOFTWARE REQUIREMENTS SPECIFICATION ........................................................ 6
2.1 Requirement Analysis .................................................................................................. 6
2.2 Problem Statement ....................................................................................................... 6
2.3 Functional Requirements ............................................................................................. 7
2.4 Non-Functional Requirements ..................................................................................... 7
2.5 External Interface Requirements .................................................................................. 9
2.6 Feasibility study ........................................................................................................... 9
2.8 Software Requirements .............................................................................................. 12
2.9 Hardware Requirements............................................................................................. 12
3. ANALYSIS & DESIGN .................................................................................................. 14
3.1 Introduction ................................................................................................................ 14
3.2 System Overview ....................................................................................................... 15
3.3 System Architecture ................................................................................................... 16
3.4 Data Design................................................................................................................ 18
4. MODELING .................................................................................................................... 25
4.1 Design ........................................................................................................................ 25
5. IMPLEMENTATION ...................................................................................................... 36
5.1 Sample Code .............................................................................................................. 36
5.2 Screen Captures ......................................................................................................... 42
6. TESTING ......................................................................................................................... 50
6.1 Software Testing ........................................................................................................ 50
6.2 Black box Testing ...................................................................................................... 50
6.3 White box Testing ...................................................................................................... 50

~ vi ~
6.4 Performance Testing .................................................................................................. 50
6.5 Load Testing .............................................................................................................. 50
6.6 Manual Testing .......................................................................................................... 51
7. RESULTS AND CHALLENGES ................................................................................... 57
7.1 Results ........................................................................................................................ 57
7.2 Challenges .................................................................................................................. 57
8. CONCLUSION ................................................................................................................ 59
8.1 Conclusions ................................................................................................................ 59
8.2 Scope for future work ................................................................................................ 59
8.3 Limitations ................................................................................................................. 59
BIBLIOGRAPHY ................................................................................................................ 60

~ vii ~
LIST OF FIGURES
Figure 3-1 Web Application Architecture 17
Figure 4-1 Use case Diagram for the system 26
Figure 4-2 Sequence Diagram for the system 28
Figure 4-3 Activity Diagram for the system 30
Figure 4-4 Class Diagram for the system 32
Figure 4-5 Deployment Diagram of the System 33
Figure 4-6 ER Diagram for the system 34
Figure 5-1 Home Page 42
Figure 5-2 Register Page 42
Figure 5-3 Retailer Price 43
Figure 5-4 Feedback Price 43
Figure 5-5 After login in 44
Figure 5-6 Buy Vegetables 44
Figure 5-7 Buy Fruits 45
Figure 5-8 Contact Details 45
Figure 5-9 Admin Panel 46
Figure 5-10 Fruits 46
Figure 5-11 Vegetables 47
Figure 5-12 Feedback Form 48
Figure 5-13 Orders 45
Figure 6-1 Test Case for Registration 51
Figure 6-2 Test Case for Adding vegetables 52
Figure 6-2 Test Case for Adding fruits 53
Figure 6-2 Test Case for Adding government price 54
Figure 6-2 Test Case for Adding wholesaler price 55

~ viii ~
LIST OF TABLES
Table 2:1 Client Requirements ………………………………………11
Table 2:2 Server Requirements ……………………………………….12
Table 3:1 Structure of EMANDI Database ………………………………...18
Table 3:2 List of Database Tables …………………………………………….18
Table 3:3 Structure of feedback table of EMANDI Database...………………..19
Table 3:4 Structure of fruits table of EMANDI Database ... ……………….....20
Table 3:5 Structure of government table of EMANDI Database .…………....20
Table 3:6 Structure of products table of EMANDI Database ………………...21
Table 3:7 Structure of register table of EMANDI Database ………………….21
Table 3:8 Structure of retailer table of EMANDI Database …………………..22
Table 3:9 Structure of wholesaler table of EMANDI Database ……………….22
Table 3:10 Structure of seller table of EMANDI Database ………………….....23

~ ix ~
ABBREIVATIONS
 UML :UNIFIEDMODELLINGLANGUAGE
 LOR :LETTEROFRECOMENDATION
 SOP :STATEMENTOFPURPOSE
 SDK : SOFTWARE DEVELOPMENT KIT
 CSS :CASCADINGSTYLESHEETS
 HTTP :HYPERTEXTTRANSFERPROTOCAL
 CGI :COMMONGGATEWAYINTERFACE
 API : APPLICATION PROGRAMMING INTERFACE
 XAMPP : CROSS PLATFORM, APACHE, MYSQL,PERLPHP
 PHP : HYPERTEXT PREPROCESSOR
 IDE : INTEGRATED DEVELOPMENT ENVIRONMENT
 HTML : HYPER TEXT MARKUP LANGUAGE
 JDK : JAVA DEVELOPMENT KIT
 XML : EXTENSIBLE MARKUP LANGUAGE
 MB :MEGABYTES
 GB :GIGABYTES
 IBM :INTERNATIONALBUSINESSMACHINES

~x~
ABSTRACT:

 The project entitled “E-MANDI” is an online vegetable store that maintains


centralized repository of all the information related to fruits and vegetables.

 This Project provides a platform for wholesellers and retailers an easy


communication

 This project makes the selling’s and purchases of vegetables and fruits easy

~ xi ~
CHAPTER - 1

INTRODUCTION

~1~
1. INTRODUCTION
1.1 Introduction
E-Mandi is an online fruits & vegetable store dedicated towards providing
services to people in making online marketing accessible to them. E-Mandi is an
online store which allows the people to buy the Vegetables and Fruits with ease and
maintains a transparency between the whole seller and retailer. With this application
the customer can buy the vegetables and fruits at best value.

One can easily browse through the various items using the well defined
interfaces provided by the system.

1.2Literature Survey
Literature survey is the most important step in software development
process. Before developing the tool it is necessary to determine the time factor,
economy and company strength. Once these things are satisfied, then next steps are
to determine which operating system and language can be used for developing the
tool. Once the programmers start building the tool the programmers need lot of
external support. This support can be obtained from senior programmers, from book
or from websites. Before building the system the above consideration are taken into
account for developing the proposed system.
 Building a web application which gives information about vegetables and
fruits.
 Designing an application with which user can feel free to know the details.

1.3 Project Background


At E-Mandi we believe in complete customer satisfaction. The online retail
market has grown tremendously over the last decades, with sales and consumer
adoption increasing every year. However, this growth has been highly heterogeneous
across retail segments. The online fruits and vegetables business, in particular, has
witnessed a difficult start in Europe and the U.S., with the online operations of
established retailers and click-only E-mandi stores struggling to survive.
Consequently, the scope of previous academic research related to online shopping and
consumer behaviour has seldom addressed the grocery retail market, with the few
existing studies focusing only on consumers’ adoption and general attitudes and

~2~
motivations towards online vegetables and fruits shopping. As a result, not much is
known about how exactly consumers shop online for fruits and vegetables. In this
contemporary society, bounded by the search of constant technological advances and
innovations, consumers are becoming less and less loyal to any specific brand or retail
format and increasingly focus on the satisfaction of immediate goals and needs.
Consequently, online shopping has become a highly profitable retail format, achieving
high sales values across much of the developed world .Although yet far from reaching
its full potential in several markets, the current percentage of online fruits and
vegetables sales is certainly something to follow closely .As traditional and click-only
retailers begin to learn from past errors and learn to take better advantage of the
technological innovations developed for the digital world, more companies are
venturing into this segment with improved business models and service levels
Concurrently, Western consumers are experiencing increasing time and budget
constraints, both of which are impacting considerably their shopping behavior
Namely, they are becoming more value-conscious due to the current economic crisis,
which together with the time scarcity felt, leads to an increasing demand for lower
search costs, higher shopping convenience, better price deals and more rewarding
purchase experiences.

1.4 Objective
The General objective of this dissertation is to portray a complete and detailed picture of
overall purchase decision making process of consumers shopping online for fruits and
vegetables.

1.5 Project Description


In this section all features in application are explained in brief.

1.5.1Registration
This is the initial phase in the application where the user creates an account in
order to do the transactions and buy the fruits and vegetables

1.5.2Login
The user access his account by using the credentials in order to view the items and
make a purchase

~3~
1.5.3Purchasing of fruits and vegetables
The buyer will add the items to the cart which he/she is willing to buy and then makes
the payment
1.5.4 Complaint form
Here the customer can give a complaint if he/she is not satisfied by the
services

1.5.5. Feedback
Here the customer can give us the feedback about the items and he/she can
give us in what way we can develop our services further if any

~4~
CHAPTER - 2

SOFTWARE REQUIREMENT SPECIFICATION

~5~
2. SOFTWARE REQUIREMENTS SPECIFICATION
2.1 Requirement Analysis
For the purpose of easy access we proposed to develop a computerized system in
which we can communicate and making text easily between the clients. As a part of
this system we are going to develop a Network based software in which protocols can
be accessed and making interaction easily. The required documents for these
processes areasfollows.
1. Problem statement
2. Data flow diagrams
3. Use case diagram
4. Other UML diagrams.
The above mentioned documents gives us diagrammatical view of the system
what we are going to develop.

2.2 Problem Statement


Although several studies have looked at online fruit and vegetable shopping at
various levels, such as adoption profiling of consumer segments or relationship with
situational variables very few have investigated the actual purchase decision making
processes of online fruits and vegetable shoppers. Since vegetable and fruit shopping
involves purchase decisions that are markedly different from those in other product
categories such as apparel or technology for instance, it is crucial for retailers to learn
how their customers shop online for fruits and vegetables if they want to tap into this
market’s potential and thrive in the highly competitive online environment. It
becomes, therefore, necessary for retailers and managers to better understand not only
what motivates their consumers to shop for fruits and vegetables online in the first
place, but also how online consumers go about making buying decisions in a digital
environment. This dissertation intends to contribute to the growing body of
knowledge of the consumer decision making processes in online vegetable and fruits
shopping environments. Namely, it will seek to explore, in as much detail as possible,
how consumers purchase supermarket products in online retail stores and uncover the
main features of the buying decision processes involved in this type of consumer
behavior.

~6~
2.3 Functional Requirements
2.3.1 User Registration:
 This module helps the customers to create an account in order to access the
website.
 User registration includes Name, User Name, Email, Repeat Email, Password,
Repeat password
 By submitting these values they will be stored in the database

2. 3.2. User Login:


 Here user logins into the website using his credentials like username and
password.
 Then he/she views the sites and performs some operations
 We are providing a brief description about those courses by giving an
overview about those exams and the topics that include in that exams.

2.3.3.Buying Fruits and vegetables:


 The user checks the price of the vegetable and fruit that he /she wants to buy
and verifies the current market price, whole seller price etc
 Then they can add items to the cart

2.4.4.Cart operations:

The items in the cart can be added or can be removed. The total amount is
calculated based on each product price and its count

2.4.5. Delivering the fruits and vegetables:

The customer will get his order within 5 hrs if he/she chooses a speed delivery and
in 7 hrs if he/she chooses a normal delivery

2.4 Non-Functional Requirements


2.4.1 Flexibility & Scalability
Google itself has given a set of applications on web based but the whole

~7~
developer community can develop their own applications and they have access to
same resources and public API which are accessible to core applications.

2.4.2 Robust
It is quite robust because it’s based on windows precisely and it gives a lot of
freedom to end user. The end user can choose what application to use either the core
application or downloaded application for any activity.

2.4.3 Fragmentation
Web gave the same environment which is open the entire API’s which is open
to all the devices which reduces fragmentation. If you develop a web application, it
will run on all the devices.

2.4.4 Open Source:


An Open Source Windows Is 'Definitely Possible' Microsoft's software empire
rests on Windows, the computer operating system that runs so many of the world's
desktop PCs, laptops, phones, and servers.

2.4.5 Performance:
Optimizing web application performance is all about numbers and metrics so,
before delving into optimization techniques, it is essential to understand what can be
optimized and how to measure improvements in performance.

2.4.6 Reliability:
Since the application is being developed through html,the most famous
hypertext language which is very easy, so it is reliable in every aspect until and unless
there is an error in the programming side. Thus the application can be a compatible
and reliable one.

2.4.7 Portability:
This System must be intuitive enough such that user with average background
in using mobile phones or any operating system can quickly work on the system. The
system has user friendly interface.

2.4.8 Privacy:

~8~
System shall protect user’s privacy by e-mail,password,contact

2.5 External Interface Requirements


2.5.1 User Interface
The user interface requirements include the necessary Graphical User
Interface that is required for the user to easily communicate with the system. An
efficient and accepted system has a very good Graphical User Interface provided that
it well acceptedandefficient.Theadminthatworkonthesystemshouldnotbedisgusted
with the system appearance for working with the system.

2.5.2 Event log/database


Once the register Event is created, it needs to be stored somewhere.
The system supports development of a SQL database. Once the event is created then
the data is stored in the database.

2.6 Feasibility study


A key part of the preliminary investigation that reviews anticipated costs and
benefits and recommends a course of action based on operational, technical,
economic, and time factors. The purpose of the study is to determine if the systems
request should proceed further.

2.6.1 Organisational Feasibility


The application would contribute to the overall objectives of the organization.
It would provide a solution to many issues in the current system. As the new system
is flexible and scalable it can also be upgraded and extended to meet other
requirements which may be raised in the future. However it is up to the organization
to upgrade or extend it.

2.6.2 Economic Feasibility


The modules are economically feasible as it is used to develop through
browser with any operating system. The users should be able to connect to internet
through system/mobile phone and this would be the only cost incurred on the project.

2.6.3 Technical Feasibility


To develop this application, a high speed internet connection, a database
server, a web server and software are required. The current modules are being used by

~9~
the company during project selling process and customer relation maintenance.

2.6.4 Behavioural Feasibility


The application is behaviourally feasible since it requires no technical
guidance, all the modules are user friendly and execute in a manner they were
designed to.

2.7 Software Requirement Specification


The project is developed in HTML with CSS. At the Server side XAMPP
Server is used. XAMPP stands for Windows/Apache/MySQL/PHP,ATOM.

2.7.1 Purpose

The purpose of this document is to present a detailed description of “E-


MANDI” for purchasing fruits and vegetables. It will explain the purpose and
features of the system that it will provide. The document also describes the
nonfunctional requirements of the system.

2.7.2 Scope of the project


This Project is used by two kinds of modules
1) Administrator
2) User

 Administrator
 Manages the entire application and also manages the customer details
 Adds the vegetables and fruits details to the website
 Publish the details in website and to the people
 Updates the vegetables and fruits details to the website
 Adds and updates the prices of vegetables and fruits to the website
 User
 The user can register into the system and can get all the information
about vegetables, fruits and their prices
 User can give the feedback
 User can give the complaint

~ 10 ~
2.7.3 Technologies Used
 HTML
Hyper Text Markup Language, commonly abbreviated as HTML, is the
standard markup language used to create web pages. Along with CSS,
and JavaScript, HTML is a cornerstone technology used to create web
pages, as well as to create user interfaces for mobile and web applications
 CSS
CascadingStyleSheet (CSS)are used to style the front-end of the E-Mandi,
web application.
 JAVASCRIPT
JavaScript is a scripting language commonly implemented as part of a web
browser in order to create enhanced user interfaces and dynamic websites.
 MySQL
MySQL is one of the most popular relational database management systems
on the web. MySQL is used for the internet applications as it provides good
speed and is very secure. MySQL was developed to manage large volumes of
data at very high speed to overcome the problems of existing solutions.

2.7.4 Overview
The application is based on PHP technology an application which
communicates with the server allowing the collection of data of the customers who
have made an order and who wants to clarify any queries.

2.7.5 Overall Description


The objective of this document therefore is to formally describe the system’s
high level requirements including functional requirements, non-functional
requirements. The detail structure of this document is organized as follows:
Section 1 of this document provides an overview of the web application. This
includes a general description of the product, user characteristics, general constraints,
and any assumptions for this system. This model demonstrates the development team
understands of the application with limited fields as a proof of concept and serves to
maximize the team’s ability to build a system that truly does support the business.
Section 2 presents the detail requirements.

~ 11 ~
Section 3 consists of the modeling, low level and high level designing and
screen captures demonstrating the functional requirements.
Section 4 shows testing the application using different testing techniques like
load testing, performance testing, manual testing etc.

2.7.6 Specific Requirements


This section will describe the functions of actors, their roles in the system and
the constraints faced by the system.

2.8 Software Requirements


The software interface is the operating system, and application programming
interface used for the development of the software.

Operating System: Windows 8.1


Database: MySQL
Technologies:HTML, CSS, PHP.

2.9 Hardware Requirements


CLIENT
OPERATING SYSTEM PROCESSOR RAM
Intel core i3
Windows 8.1 256 MB
And above
Table 2:1 Client Requirements

SERVER
OPERATING SOFTWARE PROCESSOR RAM DISK
SYSTEM SPACE
WINDOWS XAMPP Intel core i3 and 256MB Minimum
SERVER2000 above 3GB

Table 2:2 Server Requirements

~ 12 ~
CHAPTER - 3

ANALYSIS & DESIGN

~ 13 ~
3. ANALYSIS & DESIGN
3.1 Introduction
3.1.1 Purpose
In this section the purpose of the document and the project is described.
3.1.1.1 Document Purpose
An SDD is a representation of a software system that is used as a medium for
communicating software design information.

3.1.1.2 Project Purpose


The prime purpose of this “E-Mandi” is to premier professional organization for
consultants who focus exclusively on helping students realize their full potential, especially
the transition from undergraduate to graduate programs. The application stores customer
details from the server and syncs it to the database. These details can be stored in the
My SQL database.

3.1.2 Scope
In this section the scope of the document and the project is explained in brief.

3.1.2.1 Document Scope


This document contains a thorough description of the high level architecture
that will be used in developing the system. Communicating at a purposefully high
level, it will only form the basis for the Software Detailed Design and
implementation. However, the SDD itself will not be in sufficient detail to implement
the code. It will convey the overall system design of the system, the user interface
design and higher level module.
Design details that will not be included in the SDD are:
 Low level classes that will be used in the implementation. The full description
of the implementation of each module is not needed, but the public modules that
will be interfaced will be described.
 Exact detailed description of interactions within each module.

~ 14 ~
3.1.2.2 Project Scope
The actions performed by user are
 Register into the system
 Get all the information about vegetables, fruits and their prices
 Give the feedback about the items, services and other things which can
be improved &any other items should be added if necessary
 Give the complaint if services, items are not up to the mark.
The actions performed by admin are
 Admin maintains the page in appropriate way
 Manages the customer details
 Adds the vegetables and fruits details to the website
 Publish the details in website and to the people
 Updates the vegetables and fruits details to the website
 Adds and updates the prices of vegetables and fruits to the website

3.2 System Overview


3.2.1 Development Tools
Web framework uses certain development tools which are as follows:

3.2.1.1XAMPP Server
It stands for "Windows, Apache, MySQL, and PHP". XAMPP is a variation
of LAMP for Windows systems and is often installed as a software bundle (Apache,
MySQL, and PHP). It is often used for web development and internal testing, but may
also be used to serve live websites. The most important part of the XAMPP package
is Apache (or "Apache HTTP Server") which is used run the web server within
Windows. By running a local Apache web server on a Windows machine, a web
developer can test webpages in a web browser without publishing them live on the
Internet. XAMPP also includes MySQL and PHP, which are two of the most common
technologies used for creating dynamic websites. MySQL is a high-speed database,
while PHP is a scripting language that can be used to access data from the database.
By installing these two components locally, a developer can build and test a dynamic
website before publishing it to a public web server.

~ 15 ~
3.2.1.2 PHP
It stands for "Hypertext Preprocessor." PHP is an HTML-embedded Web
scripting language. This means PHP code can be inserted into the HTML of a Web
page. When a PHP page is accessed, the PHP code is read or "parsed" by the server
the page resides on. The output from the PHP functions on the page are typically
returned as HTML code, which can be read by the browser. Because the PHP code is
transformed into HTML before the page is loaded, users cannot view the PHP code on
a page. This make PHP pages secure enough to access databases and other secure
information. A lot of the syntax of PHP is borrowed from other languages such as C,
Java and Perl. However, PHP has a number of unique features and specific functions
as well. The goal of the language is to allow Web developers to write dynamically
generated pages quickly and easily.

3.2.1.3HTML
This stands for "Hypertext Markup Language." HTML is the language used to
create web pages. "Hypertext" refers to the hyperlinks that an HTML page may
contain. "Markup language" refers to the way tags are used to define the page layout
and elements within the page.

3.3 System Architecture


3.3.1 Architectural Design

Web applications are popular due to the ubiquity of web browsers, and the
convenience of using a web browser as a client to update and maintain web
applications without distributing and installing software on potentially thousands of
client computers is a key reason for their popularity, as is the inherent support for
cross-platform compatibility."Web applications" are those which have similar
functionality to a desktop software application or to a mobile app. HTML introduced
explicit language support for making applications that are loaded as web pages, but
can store data locally and continue to function while offline.

~ 16 ~
Figure 3-1Web application architecture

The Web Applications has various components. Some of the components are:

 Application
o Additional archive file (web application)
o Additional archive file (Java application)
o Enterprise application component
o Existing Web Service Provider Endpoint
o Java application
o Policy Set
o Web application component

 Database

o Database Studio web console


o Database (DB2®), such as IBM® DB2
o Existing database (DB2)
o Existing database (Informix®)
o Existing database (Oracle)
o Existing IMS™ database

3.3.2 Overall Software Architecture


The architecture shown in above figure is used in the sync operation where the
data from web application goes to web server (PHP) to database server (MySQL).

~ 17 ~
PHP is used here because of the interaction it can offer with the databases and it is
easy to deploy on the xaamp web server. On web application HTTP Client is used to
communicate with webserver (PHP). SQL insert query is written in PHP script to
insert this data into MySQL database server.

3.4 Data Design


3.4.1 Databases
MySQL
Name

Emandi

Table 3:2 MySQL Database

3.4.2 Tables

Name Description
Register MyISAM
Products MyISAM
Seller MyISAM
Fruits MyISAM
Government MyISAM
Retailer MyISAM
Wholesaler MyISAM
Feedback MyISAM

Table 3:3 List of Database Tables

~ 18 ~
3.4.2.1 Database: emandi
Table: feedback
Description:
Columns
Name Type Null Default
Customer name Varchar(50) Yes NULL
Feedback Varchar(50) Yes NULL

Table 3:4 Structure of feedback table of emandi Database


Definition
CREATE TABLE `feedback` (
`customer name` varchar(50) DEFAULT NULL,
`feedback` varchar(50) DEFAULT NULL,
)
3.4.2.2 Database: emandi
Table: fruits
Description:
Columns:
Name Type Null Default
id Int(10) no None
name Varchar(50) no None
code Int(10) no None
image text no None
price Int(20) no None

Table 3:5 Structure of fruits table emandi Database


Definition:

CREATE TABLE `fruits` (


`id` int(10) NULL ,
`name` varchar(50) NULL,
`code` int ( 10 ) NULL,
‘image’ text NULL,
‘price’ int(20) NULL
)

~ 19 ~
3.4.2.3 Database: emandi
Table: government
Description:
Columns:
Name Type Null Default
Item name Varchar(20) no None
Price per kg Int(20) no None

Table 3:6 Structure of government table emandi Database

Definition:

CREATE TABLE `government` (


`itemname` varchar(20) NULL ,
`price per kg` int(20) NULL,
)

3.4.2.4 Database: emandi


Table: products
Description:
Columns:
Name Type Null Default
Id Int(10) no None
Name Varchar(50) no None
Code Int(10) no None
Image text no None
Price Int(20) no None

Table 3:7 Structure of products table emandi Database


Definition:

~ 20 ~
CREATE TABLE `products` (
`id` int(10) NULL ,
`name` varchar(50) NULL,
`code` int ( 10 ) NULL,
‘image’ text NULL,
‘price’ int(20) NULL
)

3.4.2.5 Database: emandi


Table: register
Description:
Columns:
Name Type Null Default
Name Varchar(20) no None
Username Varchar(20) no None
Email id Varchar(20) no None
Pass1 Varchar(20) no None
Pass2 Varchar(20) no None

Table 3.8 Structure of register table emandi Database


Definition:

CREATE TABLE `register` (


`name` Varchar(20)NULL ,
`username` Varchar(20)NULL,
`email id` Varchar(20)) NULL,
‘pass1’ Varchar(20)NULL,
‘pass2’ Varchar(20)NULL
)

3.4.2.6 Database: emandi


Table: retailer
Description:

~ 21 ~
Columns:
Name Type Null Default
Item name Varcha(20) no None
Price per kg Int(20) no None

Table 3:9 Structure of retailer table emandi Database

Definition:

CREATE TABLE `retailer` (


`itemname` varchar(20) NULL ,
`price per kg` int(20) NULL,
)

3.4.2.7 Database: emandi


Table: wholesaler
Description:
Columns:
Name Type Null Default
Item name Varcha(20) no None
Price per 10kgs Int(50) no None

Table 3.10 Structure of wholesaler table emandi Database

Definition:

CREATE TABLE `wholesaler` (


`itemname` varchar(20) NULL ,
`price per 10kgs` int(50) NULL,
)

~ 22 ~
3.4.2.4 Database: emandi
Table: selleru
Description:
Columns:
Name Type Null Default
Customer name Varchar(50) no None
Item name Varchar(50) no None
quantity Int(10) no None
price Int(10) no None
Total Price Int(20) no None

Table 3:11 Structure of selleru table emandi Database


Definition:

CREATE TABLE `selleru` (


`customername` vachar(50) NULL ,
`itemname` varchar(50) NULL,
`quantity` int ( 10 ) NULL,
‘price’ int(10) NULL,
‘total price’ int(20) NULL

~ 23 ~
CHAPTER - 4

MODELING

~ 24 ~
4. MODELING
4.1 Design
Requirements gathering followed by careful analysis leads to a systematic
Object Oriented Design (OOAD). Various activities have been identified and are
represented using Unified Modeling Language (UML) diagrams. UML is used to
specify, visualize, modify, construct and document the artifacts of an object-oriented
software-intensive system under development.

4.1.1. Use Case Diagram


In the Unified Modeling Language (UML), the use case diagram is a type of
behavioral diagram defined by and created from a use-case analysis. It represents a
graphical over view of the functionality of the system in terms of actors, which are
persons, organizations or external system that plays a role in one or more interaction
with the system. These are drawn as stick figures. The goals of these actors are
represented as use cases, which describe a sequence of actions that provide something
of measurable value to an actor and any dependencies between those use cases.
In this application there is only actor – soldier and below is the use case
diagram of this application.

~ 25 ~
Figure 4-1 Use Case Diagram of the system

~ 26 ~
4.1.2 Sequence Diagram

UML sequence diagrams are used to show how objects interact in a given
situation. An important characteristic of a sequence diagram is that time passes from
top to bottom: the interaction starts near the top of the diagram and ends at the bottom
(i.e. Lower equals later).

A popular use for them is to document the dynamics in an object-oriented


system. For each key, collaboration diagrams are created that show how objects
interact in various representative scenarios for that collaboration.

Sequence diagram is the most common kind of interaction diagram, which


focuses on the message interchange between a numbers of lifelines.

The following nodes and edges are typically drawn in a UML sequence
diagram: lifeline, execution specification, message, combined fragment, interaction
use, state invariant, continuation, destruction occurrence.

~ 27 ~
Figure 4-2 Sequence Diagram of the system

~ 28 ~
4.1.3 Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic
aspects of the system. Activity diagram is basically a flow chart to represent the flow
form one activity to another activity. The activity can be described as an operation of
the system. So the control flow is drawn from one operation to another. This flow can
be sequential, branched or concurrent. Activity diagrams deals with all type of flow
control by using different elements like fork, join etc. Activity is a particular
operation of the system

~ 29 ~
Fig4.3Activity Diagram of the admin and seller

~ 30 ~
Fig4.3.2.Activity diagram for user

4.1.4 Class Diagram


In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a system by
showing the system’s classes, their attributes, operations (or methods), and the
relationships among the classes.
The class diagram is the main building block of object oriented modeling. It is
used both for general conceptual modeling of the application, and for detailed
modeling translating the models into programming code. Class diagrams can also be
used for data modeling. The classes in a class diagram represent both the main
objects, interactions in the application and the classes to be programmed.

~ 31 ~
Figure 4-4 Class Diagram of the system

4.1.5 Deployment Diagram


Deployment diagram shows execution architecture of systems that represent
the assignment (deployment) of software artifacts to deployment targets (usually
nodes).
Nodes represent either hardware devices or software execution environments. They
could be connected through communication paths to create network systems of
arbitrary complexity. Artifacts represent concrete elements in the physical world that
are the result of a development process and are deployed on nodes.

~ 32 ~
Figure 4-5 Deployment Diagram of the system

4.1.6 ER Diagram
An ER model is an abstract way to describe a database. Describing a database
usually starts with a relational database, which stores data in tables. Some of the data
in these tables point to data in other tables - for instance, your entry in the database
could point to several entries for each of the phone numbers that are yours. The ER
model would say that you are an entity, and each phone number is an entity, and the
relationship between you and the phone numbers is 'has a phone number'. Diagrams
created to design these entities and relationships are called entity–relationship
diagrams or ER diagrams.

~ 33 ~
Figure 4-6 ER Diagram for the system

~ 34 ~
CHAPTER - 5

IMPLEMENTATION

~ 35 ~
5. IMPLEMENTATION
5.1 Sample Code
5.1.1 Code for registration.php
<?php
$name=$user=$pass1=$pass2=$email="";
$conn=@mysqli_connect("localhost","root","root","emandi");
if($_SERVER["REQUEST_METHOD"]=="POST")
{
$name=$_POST["name"];
$user=$_POST["user"];
$pass1=$_POST["pass1"];
$pass2=$_POST["pass2"];
$email=$_POST["email"];

if($pass1==$pass2)
{
$query="insert into register values('".$name."','".$user."'
,'".$pass1."','".$pass2."','".$email."')";
$result=@mysqli_query($conn,$query);
if($result)
{
echo '<script type="text/javascript"> alert("USER REGISTERED
SUCCESFULLY") </script>';
}
}
else
{
echo '<script type="text/javascript"> alert("passwords did not match")
</script>';
}
}

?>

~ 36 ~
5.1.2 Code for vegetables.php
<?php
session_start();
require_once("dbcontroller.php");
$db_handle = new DBController();
if(!empty($_GET["action"])) {
switch($_GET["action"]) {
case "add":
if(!empty($_POST["quantity"])) {
$productByCode = $db_handle->runQuery("SELECT * FROM
products WHERE code='" . $_GET["code"] . "'");
$itemArray =
array($productByCode[0]["code"]=>array('name'=>$productByCode[0]["name"],
'code'=>$productByCode[0]["code"], 'quantity'=>$_POST["quantity"],
'price'=>$productByCode[0]["price"]));

if(!empty($_SESSION["cart_item"])) {

if(in_array($productByCode[0]["code"],array_keys($_SESSION["cart_item"])
)) {
foreach($_SESSION["cart_item"] as $k => $v)
{
if($productByCode[0]["code"]
== $k) {

if(empty($_SESSION["cart_item"][$k]["quantity"])) {

$_SESSION["cart_item"][$k]["quantity"] = 0;
}

$_SESSION["cart_item"][$k]["quantity"] += $_POST["quantity"];
}
}
}

~ 37 ~
else {
$_SESSION["cart_item"] = array_merge($_SESSION["cart_item"],$itemArray);
}
}
else {
$_SESSION["cart_item"] = $itemArray;
}
}
break;
case "remove":
if(!empty($_SESSION["cart_item"])) {
foreach($_SESSION["cart_item"] as $k => $v) {
if($_GET["code"] == $k)
unset($_SESSION["cart_item"][$k]);
if(empty($_SESSION["cart_item"]))
unset($_SESSION["cart_item"]);
}
}
break;
case "empty":
unset($_SESSION["cart_item"]);
break;
}
}
?>

~ 38 ~
5.1.3Code for main.html
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<style>
body
{
font-family:Verdana;
background-size:cover;
margin:0;
}
h1{
font-size:50px;
}
.a:active{
background-color:green;
}

ul {
list-style-type: none;
margin: 0;
padding: 0;

}
li a {
display: block;
background-color:lightgray;
padding: 8px 16px;
color:black;
text-decoration: none;

~ 39 ~
li a:hover {
background-color:green;
color: white;
}
*{
box-sizing: border-box;

}
table {
font-family: arial, sans-serif;
border-collapse: collapse;
width: 50%;
}td, th {
border: 1px solid lavenderblush;
text-align: left;
padding: 8px;
}

tr {
background-color: ghostwhite;
}

.menu {
float:left;
width:20%;
text-align:center;
opacity:0.8;
}
</style>
</head>
<body background="22.jpg" >
<div style="color:#7FFF00;padding:10px;text-align:center;">
<h1>E-MANDI</h1><br>

~ 40 ~
<marquee width=40% scrolldelay=10> <h2> electronic agriculture
market</h2></marquee>
</div>
<div style="overflow:auto">
<div class="menu">
<ul>
<li class="a"><a href="#">Home</li>
<li><a href="rpm.php">Retailler Price</li>
<li><a href="wpm.php">Wholeseller Price</li>
<li><a href="gpm.php">Government Price</li>
<li><a href="reg.php" >Register</li>
<li><a href="data.php">Feedback Form</li>
</ul>
</div>
<div class="main" >
</div>
<div class="right">
<center>
<h2>LOGIN</h2><br>
<table>
<form action="main.php" method="POST">
<tr><th>UserName</th><td><input type="text" name="uname"></td></tr>
<tr><th>Password</th><td><input type="password" name="pass"></td></tr><br>
<tr><td><input type="submit" value="submit" ></td>
<td><input type="button" value="cancel" ></td>
</form>
</table>
<ul>
<li><a href="reg.php">New User</li>
</ul>
</center>
</div>
</body>
</html>

~ 41 ~
5.2 Screen Captures
5.2.1 Home Page

Figure 5-1Home Page


5.2.2 Register Page

Figure 5-2 Register Page

~ 42 ~
5.2.3RetailerPrice

Figure 5-3 Retailer Price

5.2.4 Feed Back Page

Figure 5-4 Feed back page

~ 43 ~
5.2.5 After Login in

Figure 5-5 After login in


5.2.6 BUY VEGETABLES

Figure 5-6 BUY VEGETABLES

~ 44 ~
5.2.7 Buy Fruits

Figure 5-7 Buy Fruits


.
5.2.8ContactDetails

Figure 5-8 Contact Details

~ 45 ~
5.2.9 ADMIN PANEL

Figure 5-9 Admin Panel

5.2.10 Vegetables

Figure 5-10 VEGETABLES

~ 46 ~
5.2.11 FRUITS

Figure 5-11 FRUITS

5.2.12 FEED BACK FORM

Figure 5-12 FEED BACK FORM

~ 47 ~
5.2.13.SELLER LOGIN

~ 48 ~
CHAPTER - 6

TESTING

~ 49 ~
6. TESTING
6.1 Software Testing
Software testing is the process of validating and verifying that a software
applicationmeets the technical requirements which are involved in its design and
development. It is alsoused to uncover any defects/bugs that exist in the application. It
assures the quality of thesoftware. There are many types of testing software viz.,
manual testing, unit testing, black box testing, performance testing, stress testing,
regression testing, white box testing etc. Among theseperformance testing and load
testing are the most important one for an android application and nextsections deal
with some of these types.

6.2 Black box Testing


Black box testing treats the software as a "black box"—without any
knowledge of internal implementation. Black box testing methods include:
equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing,
model-based testing, traceability matrix, exploratory testing and specification-based
testing.

6.3 White box Testing


White box testing is when the tester has access to the internal data structures
and algorithms including the code that implement these.

6.4 Performance Testing


Performance testing is executed to determine how fast a system or sub-system
performsunder a particular workload. It can also serve to validate and verify other
quality attributes of thesystem such as scalability, reliability and resource usage.

6.5 Load Testing


Load testing is primarily concerned with testing that can continue to operate
underspecific load, whether that is large quantities of data or a large number of users.

~ 50 ~
6.6 Manual Testing
Manual Testing is the process of manually testing software for defects.
Functionality of this application is manually tested to ensure the correctness. Few
examples of test case for Manual Testing are discussed later in this chapter.

Test Case 1
Test Case Name Register page testing
Description The user fill all the details on this page.
Output Successful registration. Redirect to home page

Figure 6-1 Test Case for registration page

~ 51 ~
Test Case 2
Test Case Name Adding vegetables
Description The admin add vegetables that are stored in database

Output Successfuly added.

Figure 6-2 Test Case for Vegetables insertion by Admin

~ 52 ~
Test Case 3
Test Case Name Adding Fruits
Description The admin add Fruits that are stored in database

Output Successfuly added.

Figure 6-3 Test Case for Fruits insertion by Admin

~ 53 ~
Test Case 4
Test Case Name Adding Government Price
Description The admin add Government prices that are stored in database

Output Successfuly added.

Figure 6-4 Test Case for government price adding by Admin

~ 54 ~
Test Case 5
Test Case Name Adding Wholesaler Price
Description The admin add Wholesaler prices that are stored in database

Output Successfuly added.

Figure 6-5 Test Case for Wholesaler price adding by Admin

~ 55 ~
CHAPTER - 7

RESULTS &CHALLENGES

~ 56 ~
7. RESULTS AND CHALLENGES
7.1 Results
The current application is developed using web application and can be used by
the admin where they can show their data on website screen and expose the services
done by the consultancy. By using this database they contact customers those who are
registered and do services to them. They update their services for every semester.
At the time of submission of my application was capable of doing the
following:
 Displaying a welcome screen
 Home screen to choose on online mode.
 List of prices like government, retailer, wholesaler.
 List of vegetables and fruits.
 Fill feedback form

7.2 Challenges
 Understanding the client requirements was one of the crucial tasks of the
whole project.
 Graphic User Interface (GUI) design was a difficult task as there are many
types of devices with varying screen size and resolutions.
 Implementing synchronization with server was a challenging task.
 Learning different technologies and frameworks with little guidance.

~ 57 ~
CHAPTER - 8

CONCLUSIONS & FUTURE WORK

~ 58 ~
8. CONCLUSION
8.1 Conclusions
With regard to the requirements specified, we completed the project. This
system satisfies the users and it is a user–friendly application which is easy to
operate.
The hypothesis was that EMandi would last the longest in all of the devices tested.
My results do support my hypothesis.
8.2 Scope for future work
The system is developed in such a way that it can be further modified &new update
can be added to the system. So that the system can have flexibility.
The following enhancements that the system provides compared to the exist in gone:
 Technologies used for the entire system improves the efficiency.
 It provides a friendly user interface which proves I it better when compared to
existing system.
 System security, data security are provided

8.3 Limitations
The current application stores data in the Mysql database. There is a loss of
data when any crashes occur. So some techniques have to be maintained to extract the
lost data or data in database should be copied in to a disk drive once in a week.

~ 59 ~
BIBLIOGRAPHY

REFERENCES
 http://www.tutorialpoints.com
 http://www.slideshare.net
 http://www.w3schools.com/
 http://www.homeandlearn.co.uk/

~ 60 ~