CHAPTER 1

PROJECT DESCRIPTION
1.1 Introduction

This project is a web based herbal shopping system for an existing shop. The project objective is
to deliver the online shopping application into java platform. This project is an attempt to provide
the advantages of online shopping to customers of a real shop. It helps buying the herbal products
in the shop anywhere through internet by using an in this java application. Thus the customer will
get the service of online shopping and home delivery from his favorite herbal shop. This system
can be implemented to any herbal shop in the locality or to multinational branded herbal shops
having retail outlet chains. If shops are providing an online portal where their customers can enjoy
easy shopping from anywhere, since the java application is available in the Smartphone it is easily
accessible and always available. Shopping has long been considered a recreational activity by
many. Shopping online is no exception. The goal of this application is to develop a web based
interface for online retailers. The system would be easy to use and hence make the herbal
shopping experience pleasant for the users. This is a small scale project for online women
shopping system. The basic idea is that customers can buy products using online. The
administrator can enter the name/and password and can create an account and then generate the
receipt of the products purchased. The online herbal shopping system enables vendor to set up
online shops, customers to browse through the shops, and a system administrator to approve and
reject requests for new herbal shops and maintain lists of shop categories.it is useful where the
buyer can directly buy the products from home via internet on mobile or system. The Server
process the customers and the items are shipped to the address submitted by them. The application
was designed into two modules first is for the customers who wish to buy the articles. Second is
for the storekeepers who maintains and updates the information pertaining to the articles and those
of the customers. The end user of this product is a departmental store where the application is
hosted on the web and the administrator maintains the database. The application which is
deployed at the customer database, the details of the items are brought forward from the database
for the customer view based on the selection through the menu and the database of all the products
are updated at the end of each transaction. Data entry into the application can be done through
various screens designed for various levels of users. Once the authorized personnel feed the
relevant data into the system, several reports could be generated as per the security.

1
1.2 Existing System

The large volume of data has to be handled with regard to various transactions. Number of
documents is to be referred to access any information about any herbal products. A lot of
validation work is to be done. These processes are time-consuming and tedious. Any changes
made at any point have to be incorporated with the whole system and are really cumbersome.
Preparing any herbal product catalog comparison report is the most daunting task. In existing
system, all activities are carried out manually. Day-to-day Work is managed manually.to view a
particular product information or product price, technology, features and product specification
information we need to go through all the data entered and view the details which consume time.

DRAW BACKS:

 Retrieval of information from different sources is difficult.

 Less Security.
 Slow processing.
 Time consuming.
 Restrict their herbal shop in a particular area only limit the selection.
 Need to browse for number of products brands and their features.
 Need to browse the variety of herbal products and description.
 Individual customer oriented.

In order to overcome these hurdles the following software is proposed.

1.3 PROPOSED SYSTEM:

In the modern scenario, this project is accelerated by virtue of its excellence. Anything and
everything needs time management, accuracy with proper care. The effective utilization of the
available resources, timing and needs are said to be satisfied. The flexibility of the software is
used to facilitate the customer. In order to accelerate the service, the advancement is existed. By
using this software a customer can order the goods through the system and who may not be
interested in going for shopping at stores. This software is to provide requirements of the user to
purchase on

2
an easy way. There are many facilities, which include in our proposed system as various mobile
comparison, view their selected mobile compare with other selected mobile features, easily view
the price and specification of the mobile. In service of this project they can easily place online
order, easy purchasing and quick delivery. The proposed system can overcome almost all the
drawbacks of existing system. Only authenticated users can access the software. It has many
advantages. Some important advantages are given below.

BENEFITS:

 Reduces the laborious search process and purchasing time.

 Searches facilities and price from more companies and brands.
 Customers can easily purchase their mobile within their budget.
 Facility to compare price, technology and specifications in different models And brands.
 Facilities available to place order.
 User can easily compare software in various brands.

3
1.31 HARDWARE REQUIREMENTS

 Processor : Dual core processor 2.6.0 GHz

 RAM : 4GB
 Hard disk : 160 GB
 Compact Disk : 650 MB
 Keyboard : Standard keyboard
 Monitor : 19 inch color monitor

1.3.2 SOFTWARE REQUIREMENT

Software requirements are a field within software engineering that deals with establishing the
needs of stakeholders that are to be solved by software. Elicitation is the gathering and discovery
of requirements from stakeholders and other sources. A variety of techniques can be used such as
joint application design (JAD) sessions, interviews, document analysis, focus groups, etc.
Elicitation is the first step of requirements development.

 Operating System :Windows XP, Windows 7, Windows 8,Windows 10

 Internet connection : Existing telephone lines, Data card.
 Browser :Google chrome latest version
 Database : MySQL.
 Performance : The turn-around time of the project will bemedium.
 Documentation :MS-Office

4
PHP

PHP is a server-side scripting language designed primarily for web development but also used as
a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the
PHP reference implementation is now produced by The PHP Development Team. PHP originally
stood for personal home page but it now stands for the recursive acronym PHP: Hypertext
Preprocessor.

PHP code may be embedded into HTML or HTML5 code, or it can be used in combination with
various web template systems, web content management systems and web frameworks. PHP
code is usually processed by a PHP interpreter implemented as a module in the web server or as
a Common Gateway Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including images, with the
generated web page. PHP code may also be executed with a command-line interface (CLI) and
can be used to implement standalone graphical applications.

The standard PHP interpreter, powered by the Zend Engine, is free software released under
the PHP License. PHP has been widely ported and can be deployed on most web servers on
almost every operating system and platform, free of charge.

The PHP language evolved without a written formal specification or standard until 2014, leaving
the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a
formal PHP specification.PHP development began in 1995 when Rasmus Lerdorf wrote
several Common Gateway Interface (CGI) programs in C, which he used to maintain
his personal homepage. He extended them to work with web forms and to communicate
with databases, and called this implementation "Personal Home Page/Forms Interpreter" or
PHP/FI.

PHP/FI could help to build simple, dynamic web applications. To accelerate bug reporting and to
improve the code, Lerdorf initially announced the release of PHP/FI as "Personal Home Page
Tools(PHPTools)version1.0"onthe Usenet discussiongroup comp.infosystems.www.authoring.cg
i on June 8, 1995. This release already had the basic functionality that PHP has as of 2013. This
included Perl-like variables, form handling, and the ability to embed HTML.
The syntax resembled that of Perl but was simpler, more limited and less consistent.
5
Lerdorf did not intend the early PHP to become a new programming language, but it grew
organically, with Lerdorf noting in retrospect. A development team began to form and, after
months of work and beta testing, officially released PHP/FI 2 in November 1997.

The fact that PHP lacked an original overall design but instead developed organically has led to
inconsistent naming of functions and inconsistent ordering of their parameters. In some cases,
the function names were chosen to match the lower-level libraries which PHP was
"wrapping",while in some very early versions of PHP the length of the function names was used
internally as a hash function, so names were chosen to improve the distribution of hash values.

 PHP 3 and 4

Zeev Suraski and Andi Gutmans rewrote the parser in 1997 and formed the base of PHP 3,
changing the language's name to the recursive acronym PHP:Hypertext Preprocessor.
Afterwards, public testing of PHP 3 began, and the official launch came in June 1998. Suraski
and Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in 1999. They
also founded Zend Technologies in Ramat Gan, Israel. On May 22, 2000, PHP 4, powered by the
Zend Engine 1.0, was released. As of August 2008 this branch reached version 4.4.9. PHP 4 is
no longer under development nor will any security updates be released.

 PHP 5

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II. PHP 5 included new
features such as improved support for object-oriented programming, the PHP Data Objects
(PDO) extension (which defines a lightweight and consistent interface for accessing databases),
and numerous performance enhancements. In 2008 PHP 5 became the only stable version under
development. Late static binding had been missing from PHP and was added in version 5.3.

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,
2008, because of the GoPHP5 initiative, provided by a consortium of PHP developers promoting
the transition from PHP 4 to PHP 5. Over time, PHP interpreters became available on most
existing 32-bit and 64-bit operating systems, either by building them from the PHP source code,
or by using pre-built binaries. For the PHP versions 5.3 and 5.4, the only available Microsoft
Windows binary distributions were 32-bit x86 builds, requiring Windows 32-bit compatibility
mode while using Internet Information Services (IIS) on a 64-bit Windows platform. PHP
version 5.5 made the 64-bit x86-64 builds available for Microsoft Windows.
6
 PHP 6 and Unicode

PHP has received criticism due to lacking native Unicode support at the core language level,
instead only supporting byte strings. In 2005, a project headed by Andrei Zmievski was initiated
to bring native Unicode support throughout PHP, by embedding the International Components
for Unicode (ICU) library, and representing text strings as UTF-16 internally. Since this would
cause major changes both to the internals of the language and to user code, it was planned to
release this as version 6.0 of the language, along with other major features then in development.

However, a shortage of developers who understood the necessary changes, and performance
problems arising from conversion to and from UTF-16, which is rarely used in a web context,
led to delays in the project. As a result, a PHP 5.3 release was created in 2009, with many non-
Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its
current form was officially abandoned, and a PHP 5.4 release was prepared containing most
remaining non-Unicode features from PHP 6, such as traits and closure re-binding. Initial hopes
were that a new plan would be formed for Unicode integration, but as of 2014 none have been
adopted.

 PHP 7

During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7.
The numbering of this version involved some debate. While the PHP 6 Unicode experiment had
never been released, several articles and book titles referenced the PHP 6 name, which might
have caused confusion if a new release were to reuse the name. After a vote, the name PHP 7
was chosen.The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next
generation (phpng). It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov, and
aimed to optimize PHP performance by refactoring the Zend Engine to use more compact data
structures with improved cache locality while retaining near-complete language compatibility.
As of 14 July 2014, WordPress-based benchmarks, which served as the main benchmark suite
for the phpng project, showed an almost 100% increase in performance. Changes from phpng are
also expected to make it easier to improve performance in the future, as more compact data
structures and other changes are seen as better suited for a successful migration to a just-in-
time (JIT) compiler. Because of the significant changes, the reworked Zend Engine is
called Zend Engine 3, succeeding Zend Engine 2 used in PHP 5. Because of major internal
changes in phpng, it must receive a new major version number of PHP, rather than a minor PHP
7
5 release, according to PHP's release process. Major versions of PHP are allowed to break
backward-compatibility of code and therefore PHP 7 presented an opportunity for other
improvements beyond phpng that require backward-compatibility breaks, including wider use
of exceptions, reworking variable syntax to be more consistent and complete, and the
deprecation or removal of various legacy features. PHP 7 also introduced new language features,
including return type declarations for functions,which complement the existing parameter type
declarations, and support for the scalar types (integer, float, string, and boolean) in parameter
and return type declarations.

 Data Types

PHP stores integers in a platform-dependent range, either a 64-bit or 32-

bit signed integer equivalent to the C-language long type. Unsigned integers are converted to
signed values in certain situations; this behavior is different from that of other programming
languages. Integer variables can be assigned using decimal (positive and
negative), octal, hexadecimal, and binary notations.Floating point numbers are also stored in a
platform-specific range. They can be specified using floating point notation, or two forms
of scientific notation. PHP has a native Boolean type that is similar to the native Boolean types
in Java and C++. Using the Boolean type conversion rules, non-zero values are interpreted as
true and zero as false, as in Perl and C++.The null data type represents a variable that has no
value; NULL is the only allowed value for this data type.

Variables of the "resource" type represent references to resources from external sources. These
are typically created by functions from a particular extension, and can only be processed by
functions from the same extension; examples include file, image, and database resources.

Arrays can contain elements of any type that PHP can handle, including resources, objects, and
other arrays. Order is preserved in lists of values and in hashes with both keys and values, and
the two can be intermingled. PHP also supports strings, which can be used with single quotes,
double quotes, nowdoc or heredoc syntax. The Standard PHP Library (SPL) attempts to solve
standard problems and implements efficient data access interfaces and classes.

 Functions

PHP defines a large array of functions in the core language and many are also available in
various extensions,these functions are well documented in the online PHP
8
documentation. However, the built-in library has a wide variety of naming conventions and
associated inconsistencies, as described under history above.

In lieu of function pointers, functions in PHP can be referenced by a string containing their
name. In this manner, normal PHP functions can be used, for example, as callbacks or
within function tables. User-defined functions may be created at any time without
being prototyped. Functions may be defined inside code blocks, permitting a run-time
decision as to whether or not a function should be defined. There is
a function_exists function that determines whether a function with a given name has
already been defined. Function calls must use parentheses, with the exception of zero-argument
class constructor functions called with the PHP operator new, in which case parentheses are
optional.

Until PHP 5.3, support for anonymous functions and closures did not exist in PHP.
While create_function() exists since PHP 4.0.1, it is merely a thin wrapper

around eval() that allows normal PHP functions to be created during program
execution. PHP 5.3 added syntax to define an anonymous function or "closure"which can capture
variables from the surrounding scope. In the example above, getAdder() function creates a

closure using passed argument $x (the keyword use imports a variable from the lexical

context), which takes an additional argument $y , and returns the created closure to the caller.
Such a function is a first-class object, meaning that it can be stored in a variable, passed as a
parameter to other functions, etc.

Unusually for a dynamically typed language, PHP supports type declarations on function
parameters, which are enforced at runtime. This has been supported for classes and interfaces
since PHP 5.0, for arrays since PHP 5.1, for "callables" since PHP 5.4, and scalar (integer, float,
string and boolean) types since PHP 7.0. PHP 7.0 also has type declarations for function return
types, expressed by placing the type name after the list of parameters, preceded by a colon.For
example, the getAdder function from the earlier example could be annotated with types like
so in PHP 7.

9
5.1.2 Html

Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms a triad
of cornerstone technologies for the World Wide Web. Web browsers receive HTML documents
from a web server or from local storage and render them into multimedia web pages. HTML
describes the structure of a web page semantically and originally included cues for the
appearance of the document.HTML elements are the building blocks of HTML pages. With
HTML constructs, images and other objects, such as interactive forms, may be embedded into
the rendered page. It provides a means to create structured documents by denoting
structural semantics for text such as headings, paragraphs, lists, links, quotes and other items.
HTML elements are delineated by tags, written using angle brackets. Tags such
as <img /> and <input /> introduce content into the page directly. Others such

as <p>...</p> surround and provide information about document text and may include other
tags as sub-elements. 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. The World Wide Web Consortium (W3C), maintainer of both the
HTML and the CSS standards, has encouraged the use of CSS over explicit presentational
HTML.

MY SQL

MySQL is the world's most used open source relational database management system (RDBMS) as of
2008 that run as a server providing multi-user access to a number of databases.

The MySQL development project has made its source code available under the terms of the
GNU General Public License, as well as under a variety of proprietary agreements. MySQL was
owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned
by Oracle Corporation.
MySQL is a popular choice of database for use in web applications, and is a central component
of the widely used LAMP open source web application software stack—LAMP is an acronym
for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that require

10
a full-featured database management system often use MySQL.

For commercial use, several paid editions are available, and offer additional functionality.
Applications which use MySQL databases include: TYPO3, Joomla, Word Press, phpBB,
MyBB, Drupal and other software built on the LAMP software stack. MySQL is also used in
many high- profile, large-scale World Wide Web products, including Wikipedia, Google(though
not for searches), ImagebookTwitter, Flickr, Nokia.com, and YouTube.

INTERIMAGES

MySQL is primarily an RDBMS and ships with no GUI tools to administer MySQL databases or manage
data contained within the databases. Users may use the included command line tools, or use MySQL
"front-ends", desktop software and web applications that create and manage MySQL databases, build
database structures, back up data, inspect status, and work with data records. The official set of MySQL
front-end tools, MySQL Workbench is actively developed by Oracle, and is freely available for use.

11
 CHAPTER 2
LOGICAL DEVELOPMENT

2.1. DFDs
A two-dimensional diagram explains how data is processed and transferred in a system. The
graphical depiction identifies each source of data and how it interacts with other data sources to
reach a common output. Individuals seeking to draft a data flow diagram must identify external
inputs and outputs, determine how the inputs and outputs relate to each other, and explain with
graphics how these connections relate and what they result in. This type of diagram helps
business development and design teams visualize how data is processed and identify or improve
certain aspects.

Data flow Symbols:

Symbol Description

An entity. A source of data or a destination

for data.

A process or task that is performed by

the system.

A data store, a place where data is held

between processes.

A data flow.

12
LEVEL 0

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system or
process being analyzed or modeled. It’s designed to be an at-a-glance view, showing the system
as a single high-level process, with its relationship to external entities. It should be easily
understood by a wide audience, including stakeholders, business analysts, data analysts and
developers. A context diagram gives an overview and it is the highest level in a data flow
diagram, containing only one process representing the entire system. It should be split into major
processes which give greater detail and each major process may further split to give more detail.

Level 0 DFD must balance with the context diagram it describes. Input going into a process is
different from outputs leaving the process. Data stores are first shown at this level.

Admin

Registration
User

HERBAL
SHOPPING

Stock details
Product details

Buy product

Fig 2.1.1 level 0-DFD

13
LEVEL 1

DFD Level 1 provides a more detailed breakout of pieces of the Context Level Diagram. You
will highlight the main functions carried out by the system, as you break down the high-level
process of the Context Diagram into its sub – processes. Level 1 - interaction between 2 different
business applications. This is primarily used to explain the process to business and tech leads,
QA leads. As described previously, context diagrams (level 0 DFDs) are diagrams where the
whole system is represented as a single process. A level 1 DFD notates each of the main sub-
processes that together form the complete system. We can think of a level 1 DFD as an
“exploded view” of the context diagram.

1.0
User Buy Product
Registra tion

Database
Admin

Login

Add produc
t details

View stocks

List of brands Place order

Fig 2.1.2 level 1 DFD

14
2.2 ARCHITECTURAL DESIGN

A system architecture or systems architecture is the conceptual model that defines the structure,
behavior, and more views of a system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the structures and
behaviors of the system. System architecture can comprise system components, the externally
visible properties of those components, the relationships (e.g. the behavior) between them. It can
provide a plan from which products can be procured, and systems developed, that will work
together to implement the overall system. There have been efforts to formalize languages to
describe system architecture; collectively these are called architecture description languages
(ADLs).

Various organizations define systems architecture in different ways, including:

 An allocated arrangement of physical elements which provides the design solution for a
consumer product or life-cycle process intended to satisfy the requirements of the functional
architecture and the requirements baseline.
 Architecture comprises the most important, pervasive, top-level, strategic inventions,
decisions, and their associated rationales about the overall structure (i.e., essential elements and
their relationships) and associated characteristics and behavior.
 If documented, it may include information such as a detailed inventory of current
hardware, software and networking capabilities; a description of long-range plans and priorities
for future purchases, and a plan for upgrading and/or replacing dated equipment and software.

An architecture diagram is a graphical representation of a set of concepts that are part of

architecture, including their principles, elements and components. Architecture diagram can help
system designers and developers visualize the high-level, overall structure of their system or
application, in order to ensure the system meets their users' needs. Using architecture diagram,
you can also describe patterns that are used throughout the design. It's somewhat like a blueprint
that you use as a guide, so that you and your colleagues can discuss, improve and follow.

15
 CHAPTER 3
DATABASE DESIGN

DATA DICYIONARY TABLE DESGN

3.3 RELATIONSHIP DIAGRAM

Entity Relationship Diagram, also known as ERD, ER Diagram or ER model, is a type of

structural diagram for use in database design. An ERD contains different symbols and
connectors that visualize two important information: The major entities within the system
scope, and the inter-relationships among these entities. And that's why it's called "Entity"
"Relationship" diagram (ERD)!When we talk about entities in ERD, very often we are referring
to business objects such as people/role (e.g. Student), tangible business objects (e.g. Product),
intangible business objects (e.g. Log), etc. "Relationship" is about how these entities relate to
each other within the system.

Fig 3.3.1ER diagram

16
 CHAPTER 4
PROGRAM DESIGN
4.1 MODULES

The system after careful analysis has been identified to be presented with the following modules
and roles.
The modules involved are:
 Administrator
 Moderators
 Users
4.1.1 ADMINISTRATOR:
The administrator is the super user of this application. Only admin have access into this admin
page. Admin may be the owner of the shop. The administrator has all the information about all
the users and about all products.
This module is divided into different sub-modules. 1. Manage Moderators
 Manage Products
 Manage Users
 Manage Orders
MANAGE
MANAGE USER MANAGE ORDER
PRODUCT

ADMIN

MANAGE
NODERATOR

Fig 4.1.1: Admin module

17
 4.1.2. Manage Products

VIEW PRODUCT ADMIN ADD PRODUCT

DELETE PRODUCT

Fig 4.1.2: Manage Products

Add Products

The shopping cart project contains different kind of products. The products can be classified into
different categories by name. Admin can add new products into the existing system with all its
details including an image.

Delete Product

Administrator can delete the products based on the stock of that particular product

Search Products

Admin will have a list view of all the existing products. He can also search for a particular
product by name.

18
4.1.3 MANAGE USER

BLOCK/UNBLOCK
USER

DELETE USER MANAGE USER ADD USER

VIEW USER

Fig 4.1.3: Manage User

View Users

The admin will have a list view of all the users registered in the system. Admin can view all the
details of each user in the list except password.

Add Users

Admin has privileges to add a user directly by providing the details.

Delete &Block Users

Administrator has a right to delete or block a user. The default status of a new user registered is
set as blocked. The admin must accept the new user by unblocking him.

19
 4.1.4 MANAGE ORDERS

MANAGE
DELETE ORDER VIEW ORDER
ORDER

Fig 4.1.4: Manage Orders

4.2.1 USERS

VIEW
PRODUCT

PURCHASE
USER
PRODUCT
SEARCH
PRODUCT

EDIT PROFILE

Fig: 4.2.1User Module

20
Registration

A new user will have to register in the system by providing essential details in order to view the
products in the system. The admin must accept a new user by unblocking him.

Login

A user must login with his user name and password to the system after registration.

View Products

User can view the list of products based on their names after successful login. A detailed
description of a particular product with product name, products details, product image, price can
be viewed by users.

Search Product

Users can search for a particular product in the list by name.

Add to cart:

The user can add the desired product into his cart by clicking add to cart option on the product.
He can view his cart by

View Cart

All products added by cart can be viewed in the cart. User can remove an item from the cart by
clicking remove.

Submit Cart:

After confirming the items in the cart the user can submit the cart by providing a delivery
address. On successful submitting the cart will become empty.

Edit Profile

The user can view and edit the profile.

21
 CHAPTER 5
TESTING
System design is the solution for the creation of a new system. This phase focuses on the
detailed implementation of the feasible system. It emphasis on translating design. Specifications
to performance specification. System design has two phases of development Logical design
Physical design During logical design phase the analyst describes inputs (sources), output
s(destinations), databases (data sores) and procedures (data flows) all in a format that meets the
user requirements. The analyst also specifies the needs of the user at a level that virtually
determines the information flow in and out of the system and the data resources. Here the logical
design is done through data flow diagrams and database design. The physical design is followed
by physical design or coding. Physical design produces the working system by defining the
design specifications, which specify exactly what the candidate system must do. The
programmers write the necessary programs that accept input from the user, perform necessary
processing on accepted data and produce the required report on a hard copy or display it on the
screen.

3.1 INPUT AND OUTPUT DESIGN

3.1.1 INPUT DESIGN:

Input design is the link that ties the information system into the world of its users. The input
design involves determining the inputs, validating the data, minimizing the data entry and
provides a multi-user facility. Inaccurate inputs are the most common cause of errors in data
processing. Errors entered by the data entry operators can be controlled by input design. The
user-originated inputs are converted to a computer based format in the input design. Input data
are collected and organized into groups of similar data. Once identified, the appropriate input
media are selected for processing. All the input data are validated and if any data violates any
conditions, the user is warned by a message. If the data satisfies all the conditions, it is
transferred to the appropriate tables in the database. In this project the student details are to be
entered at the time of registration. A page is designed for this purpose which is user friendly and
easy to use. The design is done such that users get appropriate messages when exceptions occur.

22
3.1.2 OUTPUT DESIGN:

Computer output is the most important and direct source of information to the user. Output
design is a very important phase since the output needs to be in an efficient manner. Efficient
and intelligible output design improves the system relationship with the user and helps in
decision making. Allowing the user to view the sample screen is important because the user is
the ultimate judge of the quality of output. The output module of this system is the selected
notifications.

 SYSTEM TESTING

After a system has been verified, it needs to be thoroughly tested to ensure that every component
of the system is performing in accordance with the specific requirements and that it is operating
as it should including when the wrong functions are requested or the wrong data is introduced.
Testing measures consist of developing a set of test criteria either for the entire system or for
specific hardware, software and communications components. For an important and sensitive
system such as an electronic voting system, a structured system testing program may be
established to ensure that all aspects of the system are thoroughly tested.

Testing measures that could be followed include:

 Applying functional tests to determine whether the test criteria have been met
 Applying qualitative assessments to determine whether the test criteria have been met.
 Conducting tests in “laboratory” conditions and conducting tests in a variety of “real life”
conditions.
 Conducting tests over an extended period of time to ensure systems can perform
consistently.
 Conducting “load tests”, simulating as close as possible likely conditions while using or
exceeding the amounts of data that can be expected to be handled in an actual situation.

23
Test measures for hardware may include:

 Applying “non-operating” tests to ensure that equipment can stand up to expected levels
of physical handling.
 Testing “hard wired” code in hardware (firmware) to ensure its logical correctness and
that appropriate standards are followed.
 Tests for software components also include:
 Testing all programs to ensure its logical correctness and that appropriate design,
development and implementation standards have been followed.
 Conducting “load tests”, simulating as close as possible a variety of “real life” conditions
using or exceeding the amounts of data that could be expected in an actual situation.
 Verifying that integrity of data is maintained throughout its required manipulation.

 UNIT TESTING

The first test in the development process is the unit test. The source code is normally divided into
modules, which in turn are divided into smaller units called units. These units have specific
behavior. The test done on these units of code is called unit test. Unit test depends upon the
language on which the project is developed.

Unit tests ensure that each unique path of the project performs accurately to the documented
specifications and contains clearly defined inputs and expected results. Functional and reliability
testing in an Engineering environment. Producing tests for the behavior of components (nodes
and vertices) of a product to ensure their correct behavior prior to system integration.

 SYSTEM TESTING

Several modules constitute a project. If the project is long-term project, several developers write
the modules. Once all the modules are integrated, several errors may arise. The testing done at
this stage is called system test. System testing ensures that the entire integrated software system
meets requirements. It tests a configuration to ensure known and predictable results. System
testing is based on process descriptions and flows, emphasizing pre-driven process links and
integration
24
points. Testing a specific hardware/software installation. This is typically performed on a COTS
(commercial off the shelf) system or any other system comprised of disparate parts where
custom configurations and/or unique installations are the norm.

 INTEGRATION TESTING

Testing is which modules are combined and tested as a group. Modules are typically code
modules, individual applications, source and destination applications on a network, etc.
Integration Testing follows unit testing and precedes system testing. Testing after the product is
code complete. Betas are often widely distributed or even distributed to the public at large in
hopes that they will buy the final product when it is release.

25
 CHAPTER 6
CONCLUSION
The project entitled Online herbal shopping system was completed successfully. The
system has been developed with much care and free of errors and at the same time it is efficient
and less time consuming. The purpose of this project was to develop a web application and an
android application for purchasing items from a shop. This project helped us in gaining valuable
information and practical knowledge on several topics like designing web pages using html &
css, usage of responsive templates, designing of android applications, and management of
database using MySQL. The entire system is secured. Also the project helped us understanding
about the development phases of a project and software development life cycle. We learned how
to test different features of a project. This project has given us great satisfaction in having
designed an application which can be implemented to any nearby shops or branded shops selling
various kinds of products by simple modifications. There is a scope for further development in
our project to a great extent. A number of features can be added to this system in future like
providing moderator more control over products so that each moderator can maintain their own
products. Another feature we wished to implement was providing classes for customers so that
different offers can be given to each class. System may keep track of history of purchases of
each customer and provide suggestions based on their history. These features could have
implemented unless the time did not limited us.

26
 CHAPTER 7
BIBLIOGRAPHY

The following books were referred during the analysis and execution phase of the project

PHP and MySQL Web Development Book by Luke Welling

Head First PHP & MySQL

Book by Lynn Beighley and Michael Morrison

PHP & MySQL for Dummies Book by Janet Valade

WEBSITES:

 www.google.com
 www.w3schools.com
 www.tutorialspoint.php
 http://stackoverflow.com

27
CHAPTER 8
APPENDIX

28