Chapter 1: INTRODUCTION: Background

ORGANIC FARMING AND PRODUCT MARKET
Chapter 1: INTRODUCTION
1.1 Background:
Our website deals with Organic Farming i.e. growing food organically without the usage of any harmful
pesticides, weedicides and other chemically produced insecticides, moreover it is concerned with the
health and better nurturing capabilities of food and its intake among the present generation.
India is bestowed with lot of potential to produce all varieties of organic products due to its various
agro climatic regions. An inherited tradition of organic farming in several states of the country is an
added advantage. This holds the promise for organic producers to tap the market which is steadily
growing (15 to 25 %) in the domestic market related to the export market.
1.2 Objectives:
This project is intended to help the people or farmers keen to do Organic farming at their respective
home or garden moreover this app/website will provide them organic seeds and vegetables at wholesale
price.
1.3 Purpose, Scope and Applicability:

The description of Purpose, Scope, and Applicability are given below:
1.3.1 Purpose:
Thinking about Organic Farming is itself a big deal as:
• Lack of Knowledge
• Manageability
• Costly
So, our aim is to remove such myths from peoples mind and provide them the kickstart by our
website, they can learn how to implement organic farming at their respective home itself and
moreover they can buy organic seeds through our website which also includes some of the
organically produced medicines at a wholesale price. The database will be developed with open
source software. The primary purposes for the project are:
1
• To develop a Organic Farm Management and Development System

• To design a Organic Farm Management and Development System
• To design a customer’s Organic Farm Management and Development System interface which
interacts with database system.
• Interface for connecting through PC. 
• Seeking fruitful advice from the experienced Experts.
1.3.2 Scope:
• There are four basic users – General users, Registered Members, Experts, Administrator. 
• The users through the processes of account creation and registration can get the privileges by
becoming our Registered Member.
• The users who are not registered can also seek advice from our Experts. 
• The system will allow customers to The Rational Unified Process brings together elements
from all of the generic process models, supports iteration and illustrates good practice in
specification and design. 
• The system will allow customers to browse, search, select, and even adding of key advices and
items in their cart.
• Our website will not target any particular mob instead it will be fruitfull to every generation as
its target is to bring out the new era of healthy food consumption and to lower down the
problems arising because of adulterated food and habits.
• Other than information and knowledge provided about the Organic Farming and its solutions,
user can also use the Chat facility, Guidance provided by the experts, Map facility to track
offline stores.
• Moreover the user can buy organic foods, medicines, seeds, crops, etx by using add to cart and
Buy Now option, moreover a review and ratting section is also being provided to the user.
➢ Disadvantages of Present Working System:
• Not User Friendly: The existing websites and application available over the internet is not at all user
friendly and are complex in its execution.
• Difficulty in data fetching and gathering: People might generally think that it’s a cumbersome and
tedious task to implement.
2
• Extraneous Cost factors: Present website charges additional costs and are full of inappropriate ads as
well.
1.3.3 Applicability:
At present there is a vivid scope to excel in organic farming field, moreover due to lack of
knowledge among the peoples, they need a helpful guidance under which they can perform organic
farming activities and can reduce the consumption of adulterated and chemical contained junk foods
and start their lives with natural and healthy foods and nurture their health in more effective way.
So, As there is a need of organic farming because of Food Adulteration and consumption of Junk
food results in :-
• Health Problems
• No energy, more Fats
• Lack of essential nutrients, vitamins
• Degradation in Living standards
Other than this information and knowledge about organic farming, user can buy online organic
foods, seeds, medicines, and many other products and that to at a wholesale prices.
1.4 Achievements:
Basically, our website tends to reduce the consumption of junk or chemically produced food and try to
establish a new habit of organically produced food which results into a better health and a brighter
future among the present era. Moreover our goal is to eliminate the root causes of many of the presently
spreaded diseases by the introduction of our organic products and medicines.
3
1.5 Organization of Report:
Fig: Flow of Chapters
We have analyzed that: -
• Requirement Gathering and Analysis – All the requirements of the client are interviewed and
well analyzed through the survey and estimating the functionality of the existing system. 
• Design – The design model of online item sales with mobile SMS has been defined in detail in
this document in an implementation specific fashion so that the construction phase (of waterfall
model applied) can accomplish its task effectively. The Architectural Design gives the overall
view of the system; User interface Design describes how the end user will be able to see the
system.
• Development – After designing the system, the development phase starts.
• Testing – Software testing, depending on the testing method employed, can be implemented at
any time in the development process. A primary purpose of testing is to detect software failures
so that defects may be discovered and corrected. In Digital Parking System, black box and
white-box testing is used. 

4
• Release and Maintenance - After the system is tested it is ready for release. All the measure
will be taken to maintain the software in the market.
In this report the reader will be provided firstly the need and objective of our website, following the
technological survey which includes the behind ideology & the need of the usage of the particular
technology for implementation of particular thing. After that the reader will have complete overview
of the requirement and analysis which portraits the problem definition which includes the proper
requirement specification followed by a governed planning and scheduling with software and hardware
requirements on our project and lastly the preliminary product description explaining about the
infrastructure or usage of our website among the people and also provides the advantages of our website
followed by conceptual models.
5
Chapter 2: SURVEY OF TECHNOLOGY
Technology used:
FRONT END HTML, JSP, Javascipt, CSS, ANDROID

SERVICES JAVA
BACK END MySQL,
MODEL RATIONAL ROSE 7.0
Tools used:
FRONT END Netbeans IDE 8.0.2,

SERVICES Netbeans IDE 8.0.2, Apache Tomcat 8
BACK END SQLyog, Query Browser
MODEL Rational Rose 7.0
2.1 Product Perspective:
Fig : Behind concept of our Project
6
2.2 Software Interface:
• Client on Internet: Web Browser, Windows, Linux. 

• Client on Intranet: Web Browser. 
• Web Server: Apache Tomcat. 
• Data Base Server: SQL YOG
• Development End: Net Beans, J2EE, Java, Java Bean, Servlets, HTML, XML), SQL Yog,
OS(Windows, Linux), RSA, Apache Tomcat (Web Server) 
#Reason behind selecting above technologies:
1. Java:
Java is an object-oriented programming language developed by Sun Microsystems a company best
known for its high end. UNIX platforms workstations. Java language was designed to be small,
simple, and portable operating systems, both at the source and at the binary level, which means that
Java programs (applet and application) can run on any machine that has the Java virtual machine
(JVM).
1.1 JSP:
JavaServer Pages (JSP) is a technology for developing web pages that support dynamic content which
helps developers insert java code in HTML pages by making use of special JSP tags, most of which
start with <% and end with %>.A JavaServer Pages component is a type of Java servlet that is designed
to fulfill the role of a user interface for a Java web application. Web developers write JSPs as text files
that combine
HTML or XHTML code, XML elements, and embedded JSP actions and commands.
In the presentation layer most code is HTML/JS. On the other hand, business logic is in most part
Java code, so in that case it's better to use Servlets or POJOs (plain, old Java objects). EDIT: there's
no performance difference since JSP code, as such, is never run, it's converted to a servlet.
1.2 JavaScript:
JavaScript is (often) for the dynamic or reactive aspects of your webpage or web app: animations,
form validation, ajax, and so forth. You can use JavaScript to make your pages more interactive. You
can check stuff before sending it server and save time for the user.
7
The main use of JavaScript is that it allows you to make things happen in the user's browser without
sending messages back and forth to the server. There are a variety of reasons why you might want to
do this.
For example, sending a message to the server and getting a reply is a relatively long process: it is
almost always a noticable time lag, and can take many seconds. Doing something directly in the
browser can be much faster. So if, for example, you want to give the user an "invalid data" message
of some sort, it can be much faster if it comes from JavaScript.
2. HTML:
Browsers do not display the HTML tags, but use them to interpret the content of the page. HTML can
embed programs written in a scripting language such as JavaScript which affect the behavior and
content of web pages. Inclusion of CSS defines the look and layout of content.
3. CSS:
Use CSS to define styles for your documents, including the design, layout and variations in display
for different devices and screen sizes. You can place your CSSin the <head> of a document with an
embedded style sheet, or attach a separate file that defines your styles with an external style sheet
5. MySQL:
MySQL is a relational database system. MySQL is faster, more reliable, and cheaper or simply better
than any other database system (including commercial systems such as Oracle and DB2).
8
Chapter 3: Requirements and Analysis
3.1 Problem Definition:

As there is a need of organic farming because of Food Adulteration and consumption of Junk food
results in:
• Health Problems
• No energy, more Fats
• Lack of essential nutrients, vitamins
• Degradation in Living standards
Moreover, the common myths related to Organic Farming are: -
• Lack of Knowledge
• Costly
So, the problem we are targeting through this project is the food consumption of the mass and
bringing out different ways to surpass the knowledge of implementation of organic farming and also
reducing the harmful, chemically produced foods, seeds, medicines with our chemical free
3.2 Requirements Specification:

• The user will enter the product to be purchased in the Search Box or can see the items listed
in the Categorically created list.
• User need to register himself as a premium user for availing all functionalities.
• User can add or remove items (one at a time) from his Cart and can check-out for payment
via Cash on Delivery or Debit card.
• Other than this, user can write a blog, have some expert guidance, chat with us via browsing
respective sections over the website.
• Also, the user will get an easy-to-use interface, a clearly understandable list of suitable
products along with the constituents.
Supplementary Requirement:
• Safety Requirements: Highly recommend internet security to been Installed in users PC to

prevent the harm that may occur by unwanted malicious software, phishing URLs and all the
9
types of virus attacks during using this application. 

• Security Requirements: All users should be properly authenticated before allowed entry into
the system authentication will be based on an e-mail address, and a password. All activities on
the system must be logged.
• Non-Functional Requirements: Secure access of confidential data (user’s details). SSL can be
used 24x7 availability.Better component design to get better performance at peak time. Flexible
service based architecture will be highly desirable for future extension. 
• Other Requirements: The user must be agreed with all the terms and conditions that are provided
by the System Administrator, local authority and should obey to the all International standards
and Protocols.
Existing System -
• Manual Registration 
• Discussion Forum 
Proposed System -
• Registration for users. 

• Sale of items with Net Banking or with Cash on Delivery.
3.3 Planning and Scheduling:

• A list of items will be retrieved to the user’s screen by matching the search keywords from
the items present in our database.
• Other than this, user can get the information and knowledge about organic farming from the
home page by watching videos, reading blogs, chat with experts, etc.
• For Map tracking facility, we will include the JavaScript API for google maps.
• Other than these, we plan to optimize the user experience on our website by applying user
friendly user interface and provide the knowledge of implementation of organic farming and
by using the above stated techniques to interpret the user demands and provide the needed
product or information from the website.
10
Constraints:
• GUI is only in English. 

• Login and Password is used for the identification of users. 
• Only registered members (Corporate user/Retail clients) will be authorized to use the services. 
• Limited to HTTP and HTTPS. 
• The information of all the users must be stored in a database that is accessible by the
Administrator. 
• Organic Farming and Maintenance system is connected to the computer and is running all 24
hours of a day.
Below are the gantt chart and the P.E.R.T. diagrams related to our planning schedule and
procedure on day-to-day basis and the task is being divided into the group members as well for
simplicity.
Fig: Gantt Chart for our Project Planning and Scheduling
11
Fig: Gantt Chart(continue) for our project planning and Scheduling
Fig: P.E.R.T chart for our Project Planning and Scheduling
12
3.4 Software and Hardware Requirements:

For the implementation of our website, the user is needed the following:
Hardware Requirement
CLIENT SIDE
RAM 256 MB (minimum)
HARD DISK SPACE 100 MB (FREE SPACE REQUIRED)
PROCESSOR All Intel or AMD- 1 GHz (minimum)
SERVER SIDE
RAM HARD DISK SPACE PROCESSOR
NET BEANS IDE / 2 GB (minimum) 3.5 GB ( FREE ) All Intel /AMD-2GHz

ANDROID STUDIO
SQL YOG 512 MB (minimum) 500 MB (FREE) All Intel /AMD-2GHz
Software Requirement –
• Client on Internet: Web Browser, Windows, Linux. 

• Client on Intranet: Web Browser. 
• Web Server: Apache Tomcat. 
• Data Base Server: SQL YOG
• Development End: Net Beans ,J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX),
SQLYog, OS(Windows, Linux),RSA, Apache Tomcat (Web Server), Android Studio.
13
3.5 Preliminary Product Description:

Q) What basically user is required to do in our website?
• The user will enter the product to be purchased in the Search Box or can see the items listed
in the Categorically created list.
• User need to register himself as a premium user for availing all functionalities.
• User can add or remove items (one at a time) from his Cart and can check-out for payment via
Cash on Delivery or Debit card.
• Other than this, user can write a blog, have some expert guidance, chat with us via browsing
respective sections over the website.
• Also, the user will get an easy-to-use interface, a clearly understandable list of suitable
products along with the constituents.
So, the basic objective behind this project is intended to help the people or farmers keen to do
Organic farming at their respective home or garden moreover this app/website will provide them
organic seeds, vegetables and medicines at wholesale price.
Proposed System –
• Registration for users. 

• Sale of items with Net Banking or with Cash on Delivery.
• Offline stores view on Map
• Product Tracking Facility on Map.
• Expert Guidance and help Portal.
Functions and Operations Performed:
• A list of items will be retrieved to the user’s screen by matching the search
keyword from the items present in our database.
• Other than this, user can get the information and knowledge about organic
farming from the home page by watching videos, reading blogs, chat with
experts, etc.
14
Conceptual Models and Diagrams :

FLOW CHART DIAGRAM :
15
USE CASE MODEL
Use case model definition:-
• Use cases are designed for object oriented software development; these are focused on the
user’s need from the system. 
• This approach is more powerful as compared to traditional approach. 
• It uses a combination of text and pictures in order to improve the understanding of
requirements. 
• The use case describes ‘what of a system and not how of a system’. 
• They only give the functional view of the system. 
Use case model survey:-
• General Users-These are unregistered users and can search for the items and seek some piece
of advice by the Experts. 
• Registered Member - Users that exhibits registration, can search the items from Item-list and
16
can place an order. 

• Expert –These are the virtuosos that are available 24/7 in order to resolve the queries of the
users.
• Administrator- He has the authority to add/delete users and the items. He also views the
complaints of registered users and takes necessary actions.
Use case reports:
Administrator:-
17
USE CASE DESCRIPTION

Sign in The admin has to Sign-In, in order to start begin his work.
View Profile Admin has his/her own profile containing personal and professional details.
Update Profile The admin has the option to update his/her own profile.
View Complaint The admin views the complaint sent by other users.
Take action The admin can take necessary actions.
Add Item The admin has option to add Item.
Delete Item The admin has option to delete Item.
Add user The admin is given the option to add the users.
Delete user The admin is given the option to delete the users.
Interacts with Expert The admin interacts with Expert in order to resolve queries of Users.
Receive SMS The admin can receive private messages from retail clients and corporate user.
Search The admin can search for a particular item in website by entering the keyword.
Authenticate The admin will authenticate the user.
Take Backup The admin can take back-up of the system.
View thread The admin can view already created thread in a discussion forum.
Create thread The admin can create a new thread in a discussion forum.
Post thread The admin can post a new created or already present thread.
View help The admin view the help.
18
Registered member use-case report:
19
USEFARMING
ORGANIC CASE AND PRODUCT MARKET DESCRIPTION
Sign in The user has to Sign-in in order to start begin his work.
View Profile Every registered user has his/her own profile containing personal details.
Update Profile The user has the option to update his/her own profile.
File Complaint The user can file any kind of complaint.
Withdraw Complaint The user has option to withdraw his/her complaint
Create thread The user can create a new thread in a discussion forum.
View thread The user can view already created thread in a discussion forum.
Create new post The user can create a new post in a newly created or already present thread.
Send Query The user can send valid queries to Experts.
Receive mail The user can receive mail
Search The user can search for a particular item in website by entering the keyword.
View help The user will view the help.
Expert use case report :-
USE-CASE DESCRIPTION
R Reply Query The Expert will reply to the queries fired by the Users.
Login The expert logs in to perform his tasks.
20
ARCHITECTURE DESIGN
Application Layer Business Layer Database Layer
Login UI Login UI Login
Registration UI Registration UI
Admin
/Registered
Search UI Search UI member
Complaint UI Complaint UI
Complain
t
Discussion Discussion
Forum
Forum Forum
Order of items UI Order of items UI

Order
Expert UI Expert UI
Expert
Feedback UI Feedback UI
Feedback
k
Fig: Architectural Design Of our Website
21
ACTIVITY DIAGRAM
• Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency.
• In the Unified Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system.
• An activity diagram shows the overall flow of control.
User Registration Activity :
• Initially user fills the details present in registration form. As user click on submit button
verification of username takes place. 
• If user name is already present then that user is again taken back for changing username. 
22
• If user is not present then it checks for password and remaining mandatory fields. If any of the
mandatory field is empty or filled incorrectly, user is told to enter the correct values. 
• Once all these verifications are succeeded, then the registration is done.
Registered member Login Activity:
• User is made to enter the username and password. 

• If it is valid username and password then the user is logged in and it is automatically redirected
to home page. 
• If username or password is invalid then that user is again taken back so that he can re-enter the
details correctly. 
23
Placing an Order Activity:
• Firstly the member enters the search query.

• After validation of query, results are displayed to the user from which the user can select a particular 
item and place an order.
• Depending on whether the item is available or not in the user is notified via an e-mail.
• If the user places an order, then it is redirected to the Transaction page. 
• After the successful transaction, Bank receipt is provided as an acknowledgement
24
Lodging complaints by Registered member:
• The user enters the complaint text and sends it to admin. 

• The system generated Complaint ID is returned to user. 
25
Reply to complaint by Admin:
• The admin views the complaint and checks for validation. 

• If the complaint is valid, appropriate actions are taken. 
• If the complaint is invalid or unapprehendable, then it is rejected. 
26
Discussion forum activity :
• All the posts are displayed to the system for the user from which user can select a thread
from the recent post and can reply for the same or the user can also create the new post.The
user can directly create a new thread and thereafter he can create a new a new post. 
• The particular topic can be searched by the user and thus he can select a thread from the result
and a new post can be created. 
27
Generating a Receipt after placing an order :-
28
Seeking advice from Expert:-
• The member sends the query about Organic Farming to the Admin.
• Admin validates the query and sends it to the Expert.
• Expert resolves it and send back the reply to the authenticated user.
• It is the process of producing a detail data model of a database.This logical data model contains all
the needed logical and physical parameters.
29
SEQUENCE DIAGRAM:-
User Login -
30
Placing an Order –
31
User Lodging a Complaint –
32
Admin reply to complaint –
33
User seeking advice from Expert:-
34
DATABASE DESIGN
Fig: Database Design Of our Website
35
ER DIAGRAM
36
DATA FLOW DIAGRAM
Fig: Level 0 Data Flow Diagram
Fig: Level 2 Data Flow Diagram
37
Fig : Level 2 for 4.0 Data Flow Diagram
Fig : level 3 for 4.0 Data Flow Daigram
38
Fig: Level 2 for 5.0 Data Flow Diagram
39
Chapter 4: SYSTEM DESIGN
• Software design is actually a multistep process that focuses on four distinct attributes of a
program: data structure, software architecture, Interface representations, and procedural
detail. The design process translates requirements into a representation of the software that
can be assessed for quality before coding begins. Like requirements, the design is
documented and becomes and becomes a part of the software configuration.
• Software design is the process by which an agent creates a specification of a software
artifact, intended to accomplish goals, using a set of primitive components and subject to
constraints. Software design may refer to either "all the activities involved in
conceptualizing, framing, implementing, commissioning, and ultimately modifying
complex systems" or "the activity following requirements specification and before
programming, as in a stylized software engineering process."
4.1 Design Concepts:

The design concepts provide the software designer with a foundation from which more
sophisticated methods can be applied. A set of fundamental design concepts has evolved.
They are:
• Abstraction - Abstraction is the process or result of generalization by reducing the

information content of a concept or an observable phenomenon, typically in order to
retain only information which is relevant for a particular purpose.
• Refinement - It is the process of elaboration. A hierarchy is developed by decomposing a

macroscopic statement of function in a step-wise fashion until programming language
statements are reached. In each step, one or several instructions of a given program are
decomposed into more detailed instructions. Abstraction and Refinement are
complementary concepts.
• Modularity - Software architecture is divided into components called modules.
• Software Architecture - It refers to the overall structure of the software and the ways in
which that structure provides conceptual integrity for a system. Good software
40
architecture will yield a good return on investment with respect to the desired outcome of
the project, e.g. in terms of performance, quality, schedule and cost.
• Control Hierarchy - A program structure that represents the organization of a program

component and implies a hierarchy of control.
• Structural Partitioning - The program structure can be divided both horizontally and
vertically. Horizontal partitions define separate branches of modular hierarchy for each
major program function. Vertical partitioning suggests that control and work should be
distributed top down in the program structure.
• Data Structure - It is a representation of the logical relationship among individual

elements of data.
• Software Procedure - It focuses on the processing of each modules individually
• Information Hiding - Modules should be specified and designed so that information

contained within a module is inaccessible to other modules that have no need for such
• information.
4.2 Design Technique:

• UML: The Unified Modeling Language (UML) is a general-purpose modeling language
in the field of software engineering, which is designed to provide a standard way to
visualize the design of a system.
It is important to distinguish between the UML model and the set of diagrams of a
system. A diagram is a partial graphic representation of a system's model. The set of
diagrams need not completely cover the model and deleting a diagram does not change
the model. The model may also contain documentation that drives the model elements
and diagrams (such as written use cases). UML diagrams represent two different views of
a system model:
• Static (or structural) view: emphasizes the static structure of the system using
objects, attributes, operations and relationships. The structural view includes class
diagrams and composite structure diagrams.
41
• Dynamic (or behavioral) view: emphasizes the dynamic behavior of the system by
showing collaborations among objects and changes to the internal states of
objects. This view includes sequence diagrams, activity diagrams and state
machine diagrams.
4.3 Basic Modules:

Module I) User Login module
Functionality : The above login module is basically made to request user to enter his credentials
so that he can redirect himself to the Home page and continue shopping then after.
42
Functionality : Above is the view of home page through which user can swirl to different pages
in order to get the information about organic products and can shop for the same.
Module II) Buy Module :
Functionality : The above page is intended to help user to shop his desired product and add the
same into the cart to proceed further, which will redirect user to the final checkout page.
43
Functionality : The above page will redirect the user to bank page.
(1) (2)
44
(3) (4)
(5)
45
(6)
Functionality : the above pages shows the flow of money from customers bank account to our
website’s bank account.
Other modules includes information modules, which includes the information about our seeds,
fruits, vegetables in the form of clickable pictures. There are some more modules namely,
feedback and complaint modules.
4.4 Data Design :
Data which is being processed in our website, is stored in our database and a proper retrieval of
the data is done through database connectivity, Other than this we have applied security assets
too while the user is registering onto our website or entering his important credentials which
incudes a CAPTCHA code verification for identifying a robot ,proper validation and verification
of data is also done from our database, secured banking process through instamojo.com api link.
4.4.1 Schema Design :
• Registration Table data :
46
• Expert Table data :
• Feedback Table data :
• Item table data :
4.4.2 Data Integrity and Constraints:
• A proper client side validation is done.

• A proper userid and password verification is also done.
• Userid acts as foreign key in order placing process in our database.
4.5 Procedural Design:
4.5.1 Logic Diagrams:
Logic diagrams are used to represents the flow of information or data over the system which
include Flow charts, process diagram etc.
47
Flow Chart :
48
4.5.2 Data Structures: Basically, primitive data structures are used such as int, float,
double , etx and some non-primitive data structures such as arrays are also being used.
4.5.3 Algorithms Design: Since, this project is a shopping site which also provide a
platform where user can learn how to produce organic seeds, we have used a normal
algorithm explained below:
I) Login algorithm
Step 1) User signs up into our website.
Step 2) Check, if user is a registered one
Step 3) If yes, then log in.
Step 4) Else, sign up form.
INPUT DATA PROCESS OUTPUT DATA
User enter his Servlet is called in form A successfully

credentials while sign tag. registered msg is
up. Data is stored in our displayed.
database.
II) Buy Algorithm :
Step 1) User logs in
Step 2) User enters his quantity
Step 3) User clicks on proceed further button
Step 4) User confirms his order
Step 5) User gets redirected to the banking page by clicking on check out.
49
INPUT DATA PROCESS OUTPUT DATA
User enter his quantity of Servlet is called which An order successful or

products. itself calls a bank api payment successful is
page. msg displayed.
4.6 User Interface Design:

1) User login page :
50
2) User sign up form :
51
3) General Store page :
52
4) Checkout and buying pages:
53
5) Information page:
4.7 Security Issues :

In terms of security parameters, we have used :
1) This website is prepared in Java which is known for its security management. Java created
websites has no access to the other parts of system and memory etc. It has access to only
those memory areas which is allocated to the system. Thus it is one way to ensure security.
It has no threat to the network and its resources.
2) Proper client side Validations and server side Verifications.
3) CAPCHA code in Registration form for robot detection.
4) Safe and secured banking from instamojo.com api
5) Secure Programming : There is a strict transparency provided between layers which
enhances the security. Tasks of a single layer do not interfere the tasks of other layer. One
layer will only provide the service to other layer and nothing else.
54
4.7 Test Cases Design:

In-general Test Cases:
1. Verify that user is able to navigate through all the products across different categories
2. Verify that all the links and banners are redirecting to correct product/category pages and
none of the links arr broken
3. Verify that the company logo is clearly visible
4. Verify that all the text - product, category name, price and product description are clearly
visible
5. Verify that all the images - product and banner are clearly visible
Product buy Test Cases:
1. Verify that on the product page, user can select the desired attribute of the product.
2. Verify that user can add to cart one or more products
3. Verify that user can buy products added to cart after signing in to the application (or as per
the functionality of the website)
4. Verify that user can successfully buy more than one products that were added to his/her
cart
5. Verify that the limit to the number of products a user can by is working correctly by
displaying error message and preventing user from buying more than the limit
6. Verify that the delivery can be declined of for the places where shipping is not available
7. Verify that the different pre-paid methods of payments are working fine
User(Buyer) Registration - Test cases
1. Verify that all the specified fields are present on the registration page.
2. Verify that the required/mandatory fields are marked with * against the field.
3. Verify that for better user interface dropdowns, radio buttons and checkboxes etc fields are
displayed wherever possible instead of just textboxes.
4. Verify the page has both submit and cancel/reset buttons at the end.
55
5. Verify that clicking submit button after entering all the required fields, submits the data to
the server.
6. Verify that clicking cancel/reset button after entering all the required fields, cancels the
submit request and resets all the fields.
7. Verify that whenever possible validation should take place at client side.
8. Verify that not filling the mandatory fields and clicking submit button will lead to
validation error.
9. Verify that not filling the optional fields and clicking submit button will still send data to
server without any validation error and Verify that after making a request to the server and
then sending the same request again with the same unique key will lead to server side
validation error.
User information about seeds Test Cases:
1. Verify that user is able to read all the information.

2. Verify that the website contents is eye catchy and lucrative at the same tie.
3. Verify that the content is really useful and informative.
56
Chapter 5: Implementation and Testing
5.1 Implementation Approaches:
Fig : behind ideology of the project
• The implementation approach used in this project is based on the above diagram, we have
simply divided into 3-tier layers, front end is differentiated from the back end via the
business layer.
• Servlets are called from the front end views for storing data persistently into our database
tables which uses the concepts of RDBMS.
• The Architecture could be established by following a 3-tier Layered approach.
• Our website would be developed on Layering architecture mainly 3 layers: -
• A database layer / data layer which consists the code of database connectivity and
operations, database would be accessed only through data layer and no other layer would
write a single line of code for database connectivity.
• A business layer: - which consists of interconnection between the presentation and the
database layer.
57
• A presentation layer: - which consists the code for GUI designing and modeling and they
would connect with the business layer for further processing. Processing would be done at
business layer side.
• Object oriented Architecture: - we would develop our software by following the rules of
object oriented methodology
• The Benefits we achieve by using the Layered Architecture are numerous some of them
are as follows: -
• Maintainable: - It is easy to maintain a software developed in layers as in our case any
bug related to database would claim that the error is in data layer and not in business
layer and presentation layer.
• Robustness: - The layered approach makes the application easy to debug and hence more
resilient. Problems are handled at their source rather than travelling the whole way.
• Secure programing: - There is a strict transparency provided between layers which
enhances the security. Tasks of a single layer do not interfere the tasks of other layer. One
layer will only provide the service to other layer and nothing else.
Coding Details and Code Efficiency:
1) User Registration Form code with o/p :

//function to be called
function display()
{
var uid, password, cpassword, name, address, contact, city, state, emailed;
var error="";
password=document.getElementById("password").value;
cpassword=document.getElementById("cpassword").value;
uid=document.getElementById("uid").value;
name=document.getElementById("name").value;
pin=document.getElementById("pin").value;
contact=document.getElementById("contact").value;
address=document.getElementById("address").value;
emailid=document.getElementById("emailid").value;
58
city=document.getElementById("city").value;
state=document.getElementById("state").value;
ree = document.getElementById("number").value;
uee =document.getElementById("userI").value;
if(check=document.getElementById("check").checked!=true)
{
alert("Please tick the checbox if you agree with the terms and conitions");
}
//validation needs to be done
re =/[!@#$%^&*()_+={}|\<>?;:",/']/;
if(re.test(p))
{
alert("Pin code cannot contain alphabets");
document.getElementById("pin").focus().select();
error="huh";
return error;
}
}
var phoneno = /^\d{6}$/;
if(p.match(phoneno))
{
return true;
}
else
{
alert("Invalid Pin no");
return false;
}
}
59
function passvalidation(password)
{
if(password=="")
{
alert("Password cannot be blank");
document.getElementById("password").focus().select();
error="huh";
return error;
}
else
{
if((password.length>16)||(password.length<8))
{
alert("Password must contain atleast 8 characters and atmost 16”);
error="huh";
return error;
}
re = /[0-9]/;
if(!re.test(password))
{
alert("Error: password must contain at least one number (0-9)!");
error="huh";
return error;
}
re = /[a-z]/;
{
alert("Error: password must contain at least one lowercase letter (a-z)!");
60
error="huh";
return error; }
re = /[A-Z]/;
{
alert("Error: password must contain at least one uppercase letter (A-Z)!");
error="huh";
return error;
}
re =/[!@#$%^&*()_+={}|\<>?;:",/']/;
{
alert("Error: password must contain at least one special character)!");
error="huh";
return error;
}
}
}
61
OUTPUT :
Code Efficiency : All the validation are implemented in the less line of codes which ensures lesser
complexity and higher efficiency.
62
2) CAPCHA code used in the Registration form :

//take a random string
String a="ab1dhsd2isaudhaHI";
//take its length into a variable
int n=a.length();
//make obj of Random class
Random rg = new Random();
char r[]=new char[6];
int i;
OUTPUT :
Code Efficiency: The above code is written in least no. of lines and producing a randomly
generated CAPCHA code, hence its most efficient in its working .
63
3) Login on Home page :

function display()
{
var uid,password;
uid=document.getElementById("uid").value;
if(uid=="")
{
alert("User-id cannot be blank");
document.getElementById("uid").focus();
return false;
}
password=document.getElementById("password").value;
if(password=="")
{
alert("Password cannot be blank");
document.getElementById("password").focus();
return false;
}
if(password==uid)
{
alert("User-id and password field cannot be same");
return false;
}
if((password>16)||(password<8))
{
alert("Password must contain atleast 8 and atmost 16 characters");
return false;
}
return true; }
64
OUTPUT :
Code Efficiency : The above code is quite efficient in itself as its written in least line of code and
execution time is also faster, basically this login.html is included in the main home page like this:
65
4) Learn more pages :
66
5) Buying Pages :
function test()
{
//a function to be called for total amount to be paid by the customer
var one=document.getElementById("one").value;
var two=document.getElementById("two").value;
var three=document.getElementById("three").value;
var four=document.getElementById("four").value;
var five=document.getElementById("five").value;
var six=document.getElementById("six").value;
var seven=document.getElementById("seven").value;
var eight=document.getElementById("eight").value;
sum=+(one*110) + +(two*45) + +(three*60) + +(90*four) + +(40*five) +
+(2500*six) + +(3500*seven) + +(5000*eight);
//calculates total amount
document.getElementById("hiddenvalue").value = sum;
var r=confirm("Total cost "+sum);
if(r==true)
{
alert("Thank you for your order.. ");
return true;
}
else
{
return false;
}
}
67
OUTPUT :
<form method="post" action="proceedfurther.jsp">

<center>
<br>
<br>
<br>
<input type="hidden" id="hiddenvalue" name="xyz" value=sum>
<input type="submit" name="tt" value="Proceed Further" onclick="return t()">
<%
String summ=request.getParameter("sum");
if(summ!=null)
{
out.println(summ);
}
%>
OUTPUT :
68
Code Efficiency : The above code is running well in least possible Line of code and execution
time is also less, hence this code is efficient enough.
5.2 Testing Approach:
5.2.1 Testing Objectives

Testing is a process of executing a program with the intent of finding an error. A good test case is
one which has a high probability of finding a yet undiscovered error. A successful test is one that
uncovers a yet undiscovered error. Our objective is to design a test that systematically uncovers
different classes of errors and to do so with minimum amount of time and effort.
Software Testing has different goals and objectives. The major objectives of Software testing are as
follows:
Finding defects which may get created by the programmer while developing the software.
Gaining confidence in and providing information about the level of quality.
• To prevent defects.
• To make sure that the end result meets the business and user requirements.
• To ensure that it satisfies the BRS that is Business Requirement Specification and SRS that is
System Requirement Specifications.
• To gain the confidence of the customers by providing them a quality product.
• Software testing helps in finalizing the software application or product against business
and user requirements. It is very important to have good test coverage in order to test the
software application completely and make it sure that it’s performing well and as per the
specifications.
• While determining the test coverage the test cases should be designed well with maximum
possibilities of finding the errors or bugs. The test cases should be very effective. This objective
can be measured by the number of defects reported per test cases. Higher the number of the
defects reported the more effective are the test cases.
• Different testing techniques are appropriate at different point of time.
• Testing and debugging are different activities, but debugging must be accommodating in the
testing strategy.
69
• A strategy for the software testing must be accommodate low level tests that necessary to verify
that a small source code segment is performing correctly according to the customers
requirement and that of developers expectations.
5.3 Testing Methods & Strategies Used
5.3.1 Unit Testing

Unit testing is a software development process in which the smallest testable parts of an application,
called units, are individually and independently scrutinized for proper operation. Unit testing is often
automated but it can also be done manually. This testing mode is a component of Extreme
Programming (XP), a pragmatic method of software development that takes a meticulous approach to
building a product by means of continual testing and revision.
In our project unit testing on the registration page is done by checking all the validations:
• If user have not tick the I agree policy:
• If user enters wrong PIN code :
70
• If user enters wrong contact no. :
• If user enters wrong userid or pwd during Log-in :
5.3.2 Integration Testing

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in
software testing in which individual software modules are combined and tested as a group. It
occurs after unit testing and before validation testing. Integration testing takes as its input
modules that have been unit tested, groups them in larger aggregates, applies tests defined in
an integration test plan to those aggregates, and delivers as its output the integrated system
ready for system testing.
71
5.4 Test Cases :

I) Connection.java
/*
* To change this license header, choose License Headers in Project Properties.
* To change this template file, choose Tools | Templates
* and open the template in the editor.
*/
package database;
public class Connections
{
public Connection conn;
public Statement stmt;
public Connections() {
try
{
Class.forName("org.sqlite.JDBC");
conn=DriverManager.getConnection("jdbc:sqlite:Test.sqlite");
stmt= conn.createStatement();
}
catch(ClassNotFoundException e){ }
catch(SQLException e){}
}
}
72
II) LoginServ.java:
try
name=request.getParameter("nm");
emailid=request.getParameter("mail");
contact=request.getParameter("contact");
address=request.getParameter("address");
city=request.getParameter("city");
password=request.getParameter("pass");
state=request.getParameter("state");
pincode=request.getParameter("pin");
country=request.getParameter("country");
ifield=request.getParameter("sg");
veggies=request.getParameter("t1");
userid=request.getParameter("uid");
if(name!=null && emailid!=null && contact!=null && address!=null && city!=null &
password!=null && state!=null && pincode!=null && country!=null && ifield!=null
veggies!=null)
sql="insert into registration values(?,?,?,?,?,?,?,?,?,?,?,?)";
stat=con.prepareStatement(sql);
73
stat.setString(1, name);
stat.setString(2,emailid );
stat.setString(3,contact);
stat.setString(4,address);
stat.setString(5,city );
stat.setString(6,state);
stat.setString(7,pincode );
stat.setString(8,country);
stat.setString(9,ifield);
stat.setString(10,veggies );
stat.setString(11,userid);
stat.setString(12,password );
if(stat.executeUpdate()>0)
out.println("<br>");
out.println("<font color=red><center>You Have Successfully Registered Your
Details</center></font>");
74
out.print("<a href='index.jsp'><font color=orange<center>Click here , Home
Page</center></font></a>");
out.println("</center>");
else
out.print(x);
con.close();
catch(Exception e)
e.printStackTrace();
catch(Exception e)
e.printStackTrace();
75
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws

ServletException,
IOException
processRequest(request, response);
protected void doPost(HttpServletRequest request, HttpServletResponse response) throws

ServletException,
IOException
processRequest(request, response);
5.5 Modifications and Improvements:

While performing UNIT Testing, there we faced many bugs, which includes:
1. Usage of obsolete methods, which we have replaced with the current java methods
2. Null Pointer Exceptions which we have dealt with proper session handling and variable
declaration in the right form and right direction of use.
3. Improper linking b/w pages , which we have dealt with calling servlets correctly through
the form tags in the jsp’s
4. Some general human errors also being detected has been corrected by proper indentation
among codes and using generalized methods in place of specialized ones.
76
All the above bugs/exceptions are taken cared of in the correct direction and lastly improved our
website as a whole in terms of execution time, deployment time, lesser LOC, etx.
77
Chapter 6: Results and Discussion
In this report, we have thoroughly gone through the concepts of software engineering. We have
researched for all models in software development. We have implemented the project with incremental
model. This is because the project is based on requirements. Therefore we have complemented the
requirement analysis and designing phase. All the aspects are covered in this report.
The designing phase consists of all the software design paradigms. We have followed the object
oriented approach and it seems to be well suited accordingly to the project’s requirement. The diagrams
are specifically designed and analysed so that we can cover the basic set of the requirements and hence
we can move them on to the development phase.
So the work on design has been accomplished. The other aspects like the security and the data flow
are also maintained .The database is consistent according to the requirements and will be improved
periodically.
6.1 Test Reports:

As, we have already discussed about the different Test Cases in our website, now lets further
scrutinize the reports of the test cases:
In-general Test Cases :
1. Verify that user is able to navigate through all the products across different categories
2. Verify that all the links and banners are redirecting to correct product/category pages and
none of the links are broken.
3. Verify that the company logo is clearly visible
4. Verify that all the text - product, category name, price and product description are clearly
visible
5. Verify that all the images - product and banner are clearly visible
The above test cases are resolved quite efficiently by reviewing each and every module accurately.
Product buy Test Cases :
1. Verify that on the product page, user can select the desired attribute of the product.
78
2. Verify that user can add to cart one or more products

3. Verify that user can buy products added to cart after signing in to the application (or as per
the functionality of the website)
4. Verify that user can successfully buy more than one products that were added to his/her
cart
5. Verify that the limit to the number of products a user can by is working correctly by
displaying error message and preventing user from buying more than the limit
6. Verify that the delivery can be declined of for the places where shipping is not available
7. Verify that the different pre-paid methods of payments are working fine
The above test cases are also resolved quite efficiently by checking each and every module till its
depth and verifying each point through the test cases being made.
The same is examined through the screenshots of our website, which are given below:
In above Screenshot, the customer enters 2 as number of Composter to be purchased, and click to
the ADD TO CART button which will result in below screenshot:
79
User/Buyer Registration Test Cases:
1. Verify that all the specified fields are present on the registration page.
2. Verify that the required/mandatory fields are marked with * against the field.
3. Verify that for better user interface dropdowns, radio buttons and checkboxes etc fields are
displayed wherever possible instead of just textboxes.
4. Verify the page has both submit and cancel/reset buttons at the end.
5. Verify that clicking submit button after entering all the required fields, submits the data to
the server.
6. Verify that clicking cancel/reset button after entering all the required fields, cancels the
submit request and resets all the fields.
7. Verify that whenever possible validation should take place at client side.
8. Verify that not filling the mandatory fields and clicking submit button will lead to
validation error.
9. Verify that not filling the optional fields and clicking submit button will still send data to
server without any validation error.
10. Verify that after making a request to the server and then sending the same request again
with the same unique key will lead to server side validation error.
The above test cases are also resolved quite efficiently by checking each and every field in the
registration form and verifying each point through the test cases being made.
The same is examined through the screenshots of our website, which are given as:
80
User information about seeds Test Cases :
1. Verify that user is able to read all the information.

2. Verify that the website contents is eye catchy and lucrative at the same tie.
3. Verify that the content is really useful and informative.
The above test cases are also resolved quite efficiently by checking each and every pages
accurately and verifying each point through the test cases being made.
The same is examined through the screenshots of our website, which are given as:
81
6.2 User Documentation:

This project is intended to help the people or farmers keen to do Organic farming at their respective
home or garden moreover this website will provide them organic seeds and vegetables at wholesale
price.
Our website deals with Organic Farming i.e. growing food organically without the usage of any
harmful pesticides, weedicides and other chemically produced insecticides, moreover it is
concerned with the health and better nurturing capabilities of food and its intake among the present
generation.
82
In this website a user can have some knowledge about how to grow organic seeds and at the same
time can have the knowledge of which fruit/vegetable is important as per his needs or bodily
demands.
We also supply organically produced foods and fruits to the schools, daycares , restaurants and
tiffin centers.
83
The user can sign up and log in, in order to avail all the functionality and can there after buy
products from our website.
Proper safe and secure data flow and banking pages are developed hence there is no doubts in
having any security breach or data theft from our website.
84
Chapter 7: CONCLUSION
7.1 Conclusion:
• In this report we have thoroughly gone through the concepts of software engineering. We have
researched for all models in software development. We have implemented the project with
incremental model. This is because the project is based on requirements. Therefore we have
complemented the requirement analysis and designing phase. All the aspects are covered in
this report.
• The designing phase consists of all the software design paradigms. We have followed the object
oriented approach and it seems to be well suited accordingly to the project’s requirement. The
diagrams are specifically designed and analysed so that we can cover the basic set of the
requirements and hence we can move them on to the development phase.
• So the work on design has been accomplished. The other aspects like the security and the data
flow are also maintained. The database will be consistent according to the requirements and
will be improved periodically.
• The basic aim of this project is to implement “Organic Farming and Product Market” which
overcomes the shortcomings of traditional way of purchasing the chemically oriented
vegetables which threatens the life of consumers. Even farmers can also convert their
normal farms to organic one.
• The development of the objectives is not just a final piece of code that gives satisfaction
but rather the process of creating the software that give a sense of fulfillment.
• Project implementation always leaves a possibility of many other ways of future
extensions, which can be worked upon on later stages of time by the same or other team to
enhance the subjective knowledge of the domain
• In conclusion, having access to this type of farming has truly revolutionized and influenced
our society as a whole. This use of technology has opened new doors and opportunities that
enable for a more healthy lifestyle today. Variety, Quick service and Reduced prices were
three significant ways in which development of an organic Farming is influencing people
from all over the world.
85
7.2 Limitations of the System:
7.2.1 Technical Limitation :
• A minimum of 512 MB ram is required, to run this website onto your

browser.
• Filter in the shopping experience is placed in the future scope of the
project.
7.2.2 Non-Technical Limitation :
• Rectification of any damage in the delivered item caused by the recipient will not be our
responsibility. 
• Items in any condition once sold will not be replaced or returned. 
• Once delivery receipt is signed by the customer then no complaints will be entertained
regarding false address delivery. 
• Cash On Deivery option is not added. 

7.2.3 Future Scope of the Project:

• Though in the present scenario people prefer to buy vegetables possessing threatening
chemicals from vendors so ORGANIC FARMING is the solution to prevent customers
from such harmful chemicals.
• In future, this technology would be much in demand in years to come. Due to it's simple
and quicker facility for developing an Organic Farm at the home itself and that too with
meager maintenance.
• There are several major variables that make online item sales with mobile SMS attractive
to the worldwide market. These variables include: 
 Value of Products (Items)/Services offered.
 Authentication of the Seller. 
 Ease and Security of payment for placing an order. 
 Ease and Security of shipping of items. 
 Ease of searching of various items suggested by the expert.
86
ther than this, we will include :

1. Filter among the products based on some attributes such as: price, availability, etx
2. Related products list
3. Bargain option
87
REFERENCES :
Reference Books:
JAVA, the complete reference 7th Edition
Java Programming Language By Ken Arnold, James Gosling, David Holmes
Other Documentation & Resources :
https://www.tutorialspoint.com/java/
https://www.codecademy.com/learn/learn-sql
https://www.tutorialspoint.com/sql/
https://stackoverflow.com/
http://www.w3schools.in/java-tutorial/intro/
88
GLOSSARY :
3-tier application
a program that is organized into three major parts: the workstation or presentation interface; the
business logic; and the database and related programming. Each of these is distributed to one or
more separate places on a network..
agile software development

calls for keeping code simple, testing often, and delivering small, functional bits of the
application as soon as they're ready. The focus is to build a succession of parts, rather than
delivering one large application at the end of the project.
antipattern
a frequently used, but largely ineffective solution to a problem. The term was originally used to
refer to a design pattern gone wrong.
API (application programming interface)

a specific method prescribed by a computer operating system or by an application program by
which a programmer writing an application program can make requests of the operating system
or another application.
application integration
the process of bringing data or a function from one application program together with that of
another application program. Where these programs already exist, the process is sometimes
realized by using middleware.
application program
a program designed to perform a specific function directly for the user or, in some cases, for
another application program.
aspect-oriented programming (AOP)

an approach to programming that allows global properties of a program to determine how it is
compiled into an executable program.
best practice
a technique or methodology that, through experience and research, has proven to reliably lead
to a desired result.
89
bug
a coding error in a computer program.
build
a version of a program, usually pre-release, and identified by a build number, rather than by a
release number. As a verb, to build can mean either to write code or to put individual coded
components of a program together.
build tool
a programming utility that is used when building a new version of a program.
debugging
the process of locating and fixing or bypassing bugs (errors) in computer program code or the
engineering of a hardware device.
design pattern
a written document that describes a general solution to a design problem that recurs repeatedly
in many projects.
entity-relationship diagram
a data modeling technique that creates a graphical representation of the entities, and the
relationships between entities, within an information system.
functional programming
a style of programming that emphasizes the evaluation of expressions rather than the execution
of commands.
Gantt chart
a horizontal bar chart frequently used in project management that provides a graphical
illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project.
risk management
the process of planning, organizing, leading, and controlling the activities of an organization in
order to minimize the effects of risk on an organization's capital and earnings.
runtime
when a program is running.
90
SDK (software development kit)

a set of programs used by a computer programmer to write application programs.
service pack
an orderable or downloadable update to a customer's software that fixes existing problems and,
in some cases, delivers product enhancements.
structured programming
a subset of procedural programming that enforces a logical structure on the program being
written to make it more efficient and easier to understand and modify.
synchronize-and-stabilize
a systems development life cycle model in which teams work in parallel on individual
application modules, frequently synchronizing their code with that of other teams, and
debugging (stabilizing) code regularly throughout the development process.
systems development method (SDM)

a work discipline that is chosen by the developers of a computer system or product as a way to
ensure successful results.
systems development life cycle model (SDLC)

one of a number of structured approaches to information system development, created to guide
all the processes involved, from an initial feasibility study through maintenance of the
completed application. Models include the waterfall model; rapid application development
(RAD); joint application development (JAD); the fountain model; the spiral model; build and
fix; and synchronize-and-stabilize.
user interface
everything designed into an information device with which a human being may interact --
including display screen, keyboard, mouse, light pen, the appearance of a desktop, illuminated
characters, help messages, and how an application program or a Web site invites interaction
and responds to it.
utility
a small program that provides an addition to the capabilities provided by the operating system.
91
Web services
services made available from a business's Web server for Web users or other Web-connected programs.
92
APPENDICES :
APPENDIX 1:
Source Code of Project (Welcome New_User Session) :
function test()
//function to be called from form tag
var one=document.getElementById("one").value;
var two=document.getElementById("two").value;
var three=document.getElementById("three").value;
var four=document.getElementById("four").value;
var five=document.getElementById("five").value;
var six=document.getElementById("six").value;
var seven=document.getElementById("seven").value;
var eight=document.getElementById("eight").value;
sum=+(one*110) + +(two*45) + +(three*60) + +(90*four) + +(40*five) + +(2500*six));
// String s3=String(sum);
//window.location.replace("proceedfurther.jsp?sum="+sum);
document.getElementById("hiddenvalue").value = sum;
var r=confirm("Total cost "+sum);
if(r==true)
93
alert("Thank you for your order..Please proceed further in order to avail your order");
return true;
else
return false;
<%
//fetching the value of session from servlet
String s1=session.getAttribute("lol").toString();
out.println("Welcome "+s1 +",");
%>
OUTPUT :
94

Chapter 1: INTRODUCTION: Background

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Chapter 1: INTRODUCTION: Background

Caricato da

Copyright:

Formati disponibili

ORGANIC FARMING AND PRODUCT MARKET

1.3 Purpose, Scope and Applicability:

• To develop a Organic Farm Management and Development System

➢ Disadvantages of Present Working System:

1.5 Organization of Report:

Fig: Flow of Chapters

We have analyzed that: -

• Development – After designing the system, the development phase starts.

Chapter 2: SURVEY OF TECHNOLOGY

FRONT END HTML, JSP, Javascipt, CSS, ANDROID

FRONT END Netbeans IDE 8.0.2,

2.1 Product Perspective:

Fig : Behind concept of our Project

2.2 Software Interface:

• Client on Internet: Web Browser, Windows, Linux. 

#Reason behind selecting above technologies:

Chapter 3: Requirements and Analysis

3.1 Problem Definition:

3.2 Requirements Specification:

• Safety Requirements: Highly recommend internet security to been Installed in users PC to

types of virus attacks during using this application. 

• Registration for users. 

3.3 Planning and Scheduling:

• GUI is only in English. 

Fig: Gantt Chart for our Project Planning and Scheduling

Fig: Gantt Chart(continue) for our project planning and Scheduling

Fig: P.E.R.T chart for our Project Planning and Scheduling

3.4 Software and Hardware Requirements:

RAM 256 MB (minimum)

HARD DISK SPACE 100 MB (FREE SPACE REQUIRED)

PROCESSOR All Intel or AMD- 1 GHz (minimum)

RAM HARD DISK SPACE PROCESSOR

NET BEANS IDE / 2 GB (minimum) 3.5 GB ( FREE ) All Intel /AMD-2GHz

SQL YOG 512 MB (minimum) 500 MB (FREE) All Intel /AMD-2GHz

• Client on Internet: Web Browser, Windows, Linux. 

3.5 Preliminary Product Description:

• Registration for users. 

Functions and Operations Performed:

Conceptual Models and Diagrams :

USE CASE MODEL

Use case model definition:-

Use case model survey:-

can place an order. 

Use case reports:

USE CASE DESCRIPTION

Registered member use-case report:

Expert use case report :-

Login The expert logs in to perform his tasks.

Application Layer Business Layer Database Layer

Login UI Login UI Login

Order of items UI Order of items UI

User Registration Activity :

Registered member Login Activity:

• User is made to enter the username and password. 

Placing an Order Activity:

• Firstly the member enters the search query.

Lodging complaints by Registered member:

• The user enters the complaint text and sends it to admin. 

Reply to complaint by Admin:

• The admin views the complaint and checks for validation. 

Discussion forum activity :

Generating a Receipt after placing an order :-

Seeking advice from Expert:-