E-MANDI

SYNOPSIS

OF

E-MANDI

INTRODUCTION

1
 E-MANDI

The purpose of designing E-MANDI in java is to provide

better solution to the farmers. Here administrator of the
project can create farmer, dealer in to the SQL database
where he can login into this web application. In this
application first of all admin create farmers and dealers
through that he get password and enter in our e-mandi
application.

Under admin Moudle:

Add product price list
View product enquiry
Sells products
Search dealers stock
Send notification

Under farmers Module

Add Crops information
View product Price
Enquiry Details on product
Revert product

Under Dealers Module

Search product details
View product price list
Put enquiry
View product response
View notificaiton

2
 E-MANDI

Objective & Scope of the project

The main objective of this project is to make farmers . The system should
have a provision for the administrator to accept/reject the request by the
dealer and farmers. This process will make e-mandi process very easy,
fast and by one farmes can add product . Person who is working we only
give command to design his work this will reduce the human effort and
make the system fast.
BRIEF ANALYSIS: After strategizing, I gathered specific information,
analyzed the specific requirements of the e-mandi and then produce a set
of clear cut functional requirements that the system must address. This
stage focuses largely on filling in the details for the system element.
Information gathered are analyzed and systematically dealt in detail by
using DFD.
Main Objectives are :-
The e-mandi is meant to keep the security of the admin and
between the farmers and dealers.
A farmers can add product details.
A dealers can view the notification towards admin.
Admin can sell products between admin and user.
The main concern of this project is to improve the efficiency
and effectiveness of the whole system.

Other Objectives
User friendly interface.
A central database holds the key to system.
All forms are html templates driven
Integration among all functional areas.
The availability of the information is easy.
Routine tasks are easily performed.
It automates the redundant tasks.
3
 E-MANDI

It will save time and money.

In summary we can say that main objective of the
project is to make the work easy and smooth.
It will provide the better customer service and
enhance the profit of the organization.

METHODOLOGY

4
 E-MANDI

Proposed Methodology to be followed for the project work:

Figure No: waterfall model

Reasons for choosing waterfall model

5
 E-MANDI

1) Waterfall model is simple to implement and also the amount of resources required

for it are minimal.

2) In this model, output is generated after each stage (as seen before), therefore it has

high visibility. The client and project manager gets a feel that there is considerable

progress. Here it is important to note that in any project psychological factors also

play an important role.

3) Project management, both at internal level and client's level, is easy again because

of visible outputs after each phase. Deadlines can be set for the completion of each

phase and evaluation can be done from time to time, to check if project is going as per

milestones.

4) This methodology is preferred in projects where quality is more important as

compared to schedule or cost

Process Description including DFDs (Level 0/ Level 1)/Use Case

Diagrams and ER diagram(if any)

6
 E-MANDI

ANALYSIS

DATA FLOW DIAGRAM

The Data flow diagram can be explained as the separate levels indicating the
individual complexity in the each level of the system and gives a detailed explanation
in the further levels that are following them.

LEVEL 0

Initially in the first level of the Data flow the level 0 explains the basic outline
of the system. The end-user sends the packets to the system to determine the source
and destination address. The diagram marked as the 0 represents the complete Packet
watching system which simply represents the basic operation that is being performed
by it in the initial level.

LEVEL 1

The level 1 of the Data flow diagram given explains in detail about the Packet
watching system which was marked as 0 in the previous level. In this level the end-
user who passes the request for the system enters into the first process, the capturing
process and then to the processing module. After processing the packets it was send
for storing.

LEVEL 2

The level 2 provides the clear explanation about the whole system. In this
level first we have to select the packet and perform test over that selected packets.
Then identify the end address of the packet and send that packet for processing. After
processing the packet it was send to the identity content. Then send the processed
packet for storing and display the source and destination addresses.

7
 E-MANDI

DATA FLOW DIAGRAMS

Context Level DFD

Farmers
USER

Enters or update users data

E-Mandi

Generates the entire

Administrate the processes reports
entire process

Administrator REPORT

8
 E-MANDI

First Level DFD

1.0
Administrator Admin Admin login
Module
Info about Admin

Give permission

2.0
Farmers details
Farmers Farmers login
Module

Generate reports

3.0
Reports
Crops Info
Module

Notification list

Selling

9
 E-MANDI

Second level DFD

2nd Level DFD for Admin Module

1.0
Administrator Admin Admin login
Module

1.1
Data Entry Product
of Product

1.2
Update
Product

1.3
Notifica Notification
tion

1.4
Dealers Dealers

10
 E-MANDI

Second Level DFD for Farmers module

Farmers 2.0
Farmers
Module

Info for Farmersdetails

2.1
Product Product

Info for users for discusion

2.2
Dealers communication
communic
ation

Info about dealers

2.3
dealers

dealers

2.4
My A/c
Details
Info about my a/c & password

User account

2.5
Change
Password

11
 E-MANDI

ER- Diagram For Farmers

dob

pwd
Add
price
sname id
fname descriptio
n
id details fid date

User A/c

communication
Product

Has

id Uname
cre
vie ate

Password Change
Passeord Farmers
eid

L
User_login og
date
in name

enquiry

12
 E-MANDI

ER- Diagram For Admin

dob

pwd
Add
descripti
sname id on
name address

id descrip did phone

tion
Farmers
A/c

Dealers
enquiry

Has

id Uname
cre
res ate

ult

Password Change
Passeord Admin
eid

L
admin_login og
date
in name

notification

13
 E-MANDI

Hardware & Software to be used Server, Clients, Back end,

Tools, Software platform, programming language, etc.

HARDWARE SPECIFICATION

VIRTUAL MEMEORY
PROCESSOR : 32 BIT, Pentium IV

RAM : 1 GB
HARD DISK : 40 GB
MONITOR : SVGA Monitor (800 * 600RESOLUTIONS)
CLOCK SPEED : 266 MHz

SOFTWARE SPECIFICATION

OPERATING SYSTEM : Windows 2000/XP.

FRONT END : Java
BACK END : My Sql

14
 E-MANDI

CONCLUSION

There is always a room for improvement in any software, however

efficient the system may be. The important thing is that the system should
be flexible enough for future modifications. The system has been factored
into different modules to make system adapt to the further changes. Every
effort has been made to cover all user requirements and make it user
friendly.

Goal achieved: The System is able provide the interface to the

owner so that he can replicate his desired data. .

User friendliness: Though the most part of the system is supposed

to act in the background, efforts have been made to make the foreground
interaction with user(owner) as smooth as possible. Also the integration
of the existing system with the project has been kept in mind throughout
the development phase.

15
 E-MANDI

BIBLIOGRAPHY

Software Engineering, A Practitioners Approach,

Pressman McGraw Hill.

An Introduction To Database Systems by Bipin

C Desai

Object-Oriented Modelling and Design by James

Rambagh

Java Complete Reference by Patrick

Naughton, Herbert Schildt
Jdbc Database Access With Java By Graham
Amelton

16