System Features:

In general the user should be familiar and must have the knowledge of windows operating
system. Basic computer knowledge of using keyboard, mouse and common windows
environment is required. The primary user is admin who maintains the software or product he
should know about the data present and the data he want to view, so that he can effectively use
the function of the proposed system. The software is GUI based to reduce the user non-affability
towards the software. It is also provided with the proper information message when clicked on
the button.

Specific Requirements:

External Interface Requirements:

 User Interface: Accomplishes via mouse and keyboard input to the GUI based forms.
 Software Interface: The product requires to runtime Php environment in server machine.

Functional Requirements:

Functional requirements are statements of the services that the system must provide or are
descriptions of how some computations must be carried out.The plan for implementing
functional requirements is detailed in the system design.

 Admin is provided with Username and Password to avoid unauthorized access.

 Basic and advance admin facilities like add/update/delete Product details are provided.
 Sends the quotations to the customer generated by the Admin.
 Manages details about the different types of plants.
 Manages customer details.
 Manages requests about experts.
 Back up /recovery of data such as product details.
 Role based System functions access
Non-Functional Requirements

A non-functional requirement is a requirement that specifies criteria that can be used to judge the
operation of a system, rather than specific behaviors. This should be contrasted with functional
requirements that define specific behavior or functions. The plan for implementing non-
functional requirements is detailed in the system architecture.

 The application is available from several locations and it is accessible 24*7 with the help of
internet
 The code is easily understood and read because of the structure and coding style of the
application.
 Various components are provided in order to improve the performance at peak time

DATA FLOW DIAGRAM:

Zero Level DFD:

admin

Leaf disease Customer

detection

Experts

Data Base
FIRST LEVEL DFD:

ADMIN:

Admin Leaf
disease Data Base
detection

CUSTOMER:

Leaf
Customer disease
Data Base
detection

EXPERTS:

Leaf
Experts disease
detection
Database
SECOND LEVEL DFD:

ADMIN:

Admin Login Homepage

Manage Products,
Update Manage Experts,
Data Base View response,
View request

CUSTOMER:

Username&

Homepage
PwdValid
Customer Login
Invalid

Update Manage Profile, send

reques, view
Data Base
feedback from
experts, view ratings
EXPERT:

Username&

Experts PwdValid Homepage

Login

Invalid

View request, give

Update feedback
Data Base
ER Diagram

Ad Admin
d

Vie Experts
Plants
w

Queries Hav Vie

hav e w
e

Vie
Reply
w

Disease Ask

Vie
w Ratings

Vie Users Vie

w w