lOMoARcPSD|15944306

Mini Project Report On Online Shopping S

Web Design/Cybersecurity (Vardhaman Mahaveer Open University)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Dhananjaya dhanu (dhanu.innovation@gmail.com)
 lOMoARcPSD|15944306

Online Shopping System

Mini Project

Report On

ONLINE SHOPPING
SYSTEM

Submitted By:
SHIBIN CHITTIL
(80)
NIDHEESH CHITTIL (52)
RISHIKESE M R (73)

In partial fulfillment for the award of the degree of

B. TECH DEGREE

In

COMPUTER SCIENCE & ENGINEERING

SCHOOL OF ENGINEERING
COCHIN UNIVERSITY OF SCIENCE & TECHNOLOGY
KOCHI-682022
MARCH 2014
Department of Computer Science, CUSAT Page 1
 lOMoARcPSD|15944306

Division of Computer Science

School of Engineering
Cochin University of Science &
Technology
Kochi-

682022

CERTIFICA

TE

Certified that this is a bonafide record of the project work titled

ONLINE SHOPPING SYSTEM

Done

by SHIBIN

CHITTIL

(80)
NIDHEESH CHITTIL (52)
RISHIKESE M R (73)

of VI semester Computer Science & Engineering in the year 2014

in partial fulfillment of the requirements for the award of Degree of
Bachelor of Technology in Computer Science & Engineering of
 lOMoARcPSD|15944306

Cochin University
of Science & Technology.

PREETHA S PRAMOD PAVITHRAN

 lOMoARcPSD|15944306

Project Guide Head of the Division

 lOMoARcPSD|15944306

ABSTRACT

This project is a web based shopping system for an

existing shop. The project objective is to deliver the online
shopping application into android platform.

This project is an attempt to provide the advantages of online

shopping to customers of a real shop. It helps buying the
products in the shop anywhere through internet by using an
android device. Thus the customer will get the service of
online shopping and home delivery from his favorite shop.
This system can be implemented to any shop in the locality
or to multinational branded shops having retail outlet chains.

If shops are providing an online portal where their customers

can enjoy easy shopping from anywhere, the shops won’t be
losing any more customers to the trending online shops such
as flipcart or ebay. Since the application is available in the
Smartphone it is easily accessible and always available.

. i
 lOMoARcPSD|15944306

LIST OF FIGURES
1.1 ADMIN MODULE 5

1.2 MANAGE MODERATORS 6

1.3 MANAGE PRODUCTS 8

1.4 MANAGE USERS 9

1.5 MANAGE ORDERS 10

1.5 MODERATOR MODULE 11

1.7 USER MODULE 12

E-R DIAGRAMS & DFD

3.5 LOGIN 30

3.6 USER DETAILS 30

3.7 PRODUCT DETAILS 31

3.8 PRODUCT ORDERS 31

3.9 COMPLETE DIAGRAM 32

ii
 lOMoARcPSD|15944306

3.10LOGIN DFD 35

3.11REGISTRATION DFD 36

3.12ADMIN DFD 37

3.13MODERATOR DFD 38

iii
 lOMoARcPSD|15944306

LIST OF TABLES

3.1LOGIN TABLE 28

3.2 USER DETAILS 28

3.3 PRODUCT DETAILS 29

3.4 PRODUCT ORDERS 29

iv
 lOMoARcPSD|15944306

ACKNOWLEDGEMENT

I take this occasion to thank God, almighty for

blessing us with his grace and taking our endeavor to a

successful culmination. I extend my sincere and heartfelt

thanks to our esteemed guide, Mrs. PREETHA S, for providing

me with the right guidance and advice at the crucial

junctures and for showing me the right way. I extend my

sincere thanks to our respected Head of the division Mr.

PRAMOD PAVITHRAN, for allowing us to use the facilities

available. I would like to thank the other faculty members

also, at this occasion. Last but not the least, I would like to

thank my friends and family for the support and

encouragement they have given me during the course of our

work.

SHIBIN
CHITTIL
NIDHEESH
CHITTIL
RISHIKESE M
lOMoARcPSD|15944306

v
 lOMoARcPSD|15944306

TABLE OF CONTENTS

ABSTRACT i
LIST OF FIGURE ii
LIST OF TABLES iv
ACKNOWLEDGEMENT v

1. INTRODUCTION PAGE
1.1PROJECT OBJECTIVES 1
1.2PROJECT OVER VIEW 2
1.3PROJECT SCOPE 2
1.4STUDY OF SYSTEMS 3
1.4.1 MODULES 3
1.4.1.1 ADMIN 3
1.4.1.2 MODERATOR
11
1.4.1.3 USER 12

2. SYSTEM ANALYSIS 15
2.1EXISTING SYSTEM 15
2.2PROPOSED SYSTEM 16
2.3SYSTEM REQUIREMENT SPECIFICATION 16
 lOMoARcPSD|15944306

2.3.1 GENERAL
DESCRIPTION 16

2.3.2 SYSTEM OBJECTIVES 17

2.3.3 SYSTEM REQUIREMENTS 17
2.3.3.1 NON FUNCTIONAL REQUIREMENT 18
2.3.3.2 FUNCTIONAL REQUIREMENT 19

3. SYSTEM DESIGN 23

3.1INPUT AND OUTPUT DESIGN 24

3.1.1 INPUT DESIGN 24

3.1.2 OUTPUT DESIGN 24

3.2DATABASE 25

3.3SYSTEM TOOLS 25

3.3.1 FRONT END 26

3.3.2 BACK END 27

3.4TABLES 28

3.5E-R DIAGRAMS 30

3.6DATA FLOW DIAGRAMS (DFD) 32

 lOMoARcPSD|15944306

3.7SCREEN SHOTS 39

3.8SAMPLE CODE 47

4. CONCLUSION 67

REFERENCES 69
 lOMoARcPSD|15944306

CHAPTER 1

INTRODUCTION
This project is a web based shopping system for an existing
shop.
The project objective is to deliver the online shopping
application into android platform.

Online shopping is the process whereby consumers directly

buy goods or services from a seller in real-time, without an
intermediary service, over the Internet. It is a form of
electronic commerce. This project is an attempt to provide
the advantages of online shopping to customers of a real
shop. It helps buying the products in the shop anywhere
through internet by using an android device. Thus the
customer will get the service of online shopping and home
delivery from his favorite shop

1.1 PROJECT OBJECTIVE:

The objective of the project is to make an application

in android platform to purchase items in an existing shop.
In order to build such an application complete web support
need to be provided. A complete and efficient web
application which can provide the online shopping
experience is the basic objective of the project. The web
application can be implemented in the form of an android
application with web view.
 lOMoARcPSD|15944306

1.2 PROJECT OVER VIEW:

The central concept of the application is to allow the

customer to shop virtually using the Internet and allow
customers to buy the items and articles of their desire from
the store. The information pertaining to the products are
stores on an RDBMS at the server side (store).

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.3 PROJECT SCOPE:

 lOMoARcPSD|15944306

This system can be implemented to any shop in the

locality or to multinational branded shops having retail outlet
chains. The system recommends a facility to accept the
orders 24*7 and a home delivery system which can make
customers happy.
If shops are providing an online portal where their
customers can enjoy easy shopping from anywhere, the
shops won’t be losing any more customers to the trending
online shops such as flipcart or ebay. Since the application is
available in the Smartphone it is easily accessible and always
available.

1.4 STUDY OF THE SYSTEM

1.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

1.4.1.1 ADMINISTRATOR:
 lOMoARcPSD|15944306

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
2. Manage Products
3. Manage Users
4. Manage Orders

Hardware and Software Requirements

REQUIREMENT ANALYSIS
HARDWARE REQUIREMENTS
 Hardware :Processor Intel dual core and above
 Clock speed :3.0 GHz
 RAM size :512 MB
 Hard Disk capacity :400 GB
 Monitor type :15 inch color monitor

SOFTWARE REQUIREMENTS
 Operating System :Windows XP, Windows 7, Windows
8,Windows 10
 Application :HTML, CSS, JS, Python, Flask
 Browser :Google chrome, Firefox
 Database :Google Firebase/Firestore.
 Documentation :MS-Office
 lOMoARcPSD|15944306

Software Requirement Specification

1. Flask: Flask is a high-level Python web framework that enables rapid
development of secure and maintainable websites. It provides a
powerful set of tools for building web applications, including a robust
ORM (Object-Relational Mapping) system, automatic admin
interface, and built-in security features.

2. Python: Python is a high-level programming language used for a

wide range of purposes, including web development. It is known for
its ease of use, simplicity, and versatility
3. HTML: Hypertext Markup Language (HTML) is the standard markup
language used to create web pages. It provides a structure for
content on the internet, allowing developers to define and organize
the various elements on a webpage.
4. CSS: Cascading Style Sheets (CSS) is a language used for describing
the presentation of a document written in HTML. It provides a way to
add style and design to a webpage, including colors, fonts, and
layouts.
 lOMoARcPSD|15944306

5. Java Script: JavaScript (JS) is a programming language used primarily

for developing interactive and dynamic front-end web applications.
It allows for the creation of responsive and userfriendly websites.
6. Firebase : Firebase is a Non-SQL database system that provides a
flexible and scalable solution for storing and retrieving data. It is
designed for handling large volumes of data and provides high
availability and automatic scaling.

In summary, the project requires the use of standard web development

technologies such as HTML, CSS, and JavaScript, as well as the Python
programming language and the Flask web framework. Additionally, the
use of DBSql is required to provide a scalable and efficient data storage
solution. All of these technologies are essential for building a modern
and functional web application that meets the needs of users.

SYSTEM ANALYSIS
System analysis is the most essential part of the development of the project.
The analyst has to understand the functions and concepts in detail before
designing the appropriate computer based system. He has to carry out
customary appropriate that includes the following steps:
• Requirement specification
• Preliminary investigation
• Feasibility study
• Detailed investigation
• Design and coding
• Testing
 lOMoARcPSD|15944306

• Implementation

System engineering and analysis encompasses requirement gathering at the

system level with a small level of top level design and analysis. This
process of analyzing and gathering requirements is known as software
requirement specification (SRS). The requirement gathering process
intensified a focus especially on software. The preliminary investigation,
Feasibility study and the detailed investigation allows the system to
comprehend the full scope of this project. Soon after testing,
implementation of the developed system is followed by training

FEASIBILITY STUDY
A feasibility study is a high-level capsule version of the entire System
analysis and Design Process. The study begins by classifying the problem
definition. Feasibility is to determine if it’s worth doing. Once an
acceptance problem definition has been generated, the analyst develops a
logical model of the system. A search for alternatives is analyzed carefully.
There are 3 parts in feasibility study.

Operational Feasibility

Operational feasibility is the measure of how well a proposed system

solves the problems, and takes advantage of the opportunities identified
during scope definition and how it satisfies the requirements identified in
the requirements analysis phase of system development.The operational
feasibility assessment focuses on the degree to which the proposed
development projects fits in with the existing business environment and
objectives with regard to development schedule, delivery date, corporate
culture and existing business processes.To ensure success, desired
 lOMoARcPSD|15944306

operational outcomes must be imparted during design and development.

These include such design-dependent parameters as reliability,
maintainability, supportability, usability, producibility, disposability,
sustainability, affordability and others. These parameters are required to
be considered at the early stages of design if desired operational
behaviours are to be realised. A system design and development requires
appropriate and timely application of engineering and management efforts
to meet the previously mentioned parameters. A system may serve its
intended purpose most effectively when its technical and operating
characteristics are engineered into the design. Therefore, operational
feasibility is a critical aspect of systems engineering that needs to be an
integral part of the early design phases.

Technical Feasibility

This involves questions such as whether the technology needed for the
system exists, how difficult it will be to build, and whether the firm has
enough experience using that technology. The assessment is based on
outline design of system requirements in terms of input, processes,
output, fields, programs and procedures.This can be qualified in terms
of volume of data,trends,frequency of updating inorder to give an
introduction to the technical system. The application is the fact that it
has been developed on windows XP platform and a high configuration of
1GB RAM on Intel Pentium Dual core processor.This is technically
feasible .The technical feasibility assessment is focused on gaining an
understanding of the present technical resources of the organization
and their applicability to the expected needs of the proposed system. It
is an evaluation of the hardware and software and how it meets the
need of the proposed system.
 lOMoARcPSD|15944306

Economical Feasibility

Establishing the cost-effectiveness of the proposed system i.e. if the

benefits do not outweigh the costs then it is not worth going ahead. In
the fast paced world today there is a great need of online social
networking facilities. Thus the benefits of this project in the current
scenario make it economically feasible. The purpose of the economic
feasibility assessment is to determine the positive economic benefits to
the organization that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This
assessment typically involves a cost/benefits analysis.

DESIGN

Introduction:

Design is the first step in the

development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient
detail to permit its physical realization.

Once the software requirements have

been analyzed and specified the software design involves three
technical activities - design, coding, implementation and testing
that are required to build and verify the software.

The design activities are of main

importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation
 lOMoARcPSD|15944306

and its ease of maintenance are made. These decisions have the
final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s
requirements into finished software or a system.

Design is the place where quality

is fostered in development. Software design is a process through
which requirements are translated into a representation of
software. Software design is conducted in two steps. Preliminary
design is concerned with the transformation of requirements into
data.

UML Diagrams:

Actor:
A coherent set of roles that users of use cases play when interacting
with the use `cases.

Use case:
A description of sequence of actions, including
variants, that a system performs that yields an observable result
of value of an actor.
 lOMoARcPSD|15944306

UML stands for Unified Modeling Language. UML is a language for

specifying, visualizing and documenting the system. This is the
step while developing any product after analysis. The goal from
this is to produce a model of the entities involved in the project
which later need to be built. The representation of the entities
that are to be used in the product being developed need to be
designed.

There are various kinds of methods in software design:

They are as follows:
Use case Diagram
Sequence Diagram
Collaboration Diagram
Activity Diagram
State chat Diagram

Use case Diagrams:

Use case diagrams model behavior within a system and helps the
developers understand of what the user require. The stick man
represents what’s called an actor.

Use case diagram can be useful for getting an overall

view of the system and clarifying that can do and more
importantly what they can’t do.
 lOMoARcPSD|15944306

Use case diagram consists of use cases and actors and shows the
interaction between the use case and actors.

 The purpose is to show the interactions between the

use case and actor.
 To represent the system requirements from user’s
perspective.
 An actor could be the end-user of the system or an
external system.

Use case Diagram

A Use case is a description of set of sequence of actions.
Graphically it is rendered as an ellipse with solid line including
only its name. Use case diagram is a behavioral diagram that
shows a set of use cases and actors and their relationship. It is
an association between the use cases and actors. An actor
represents a real-world object. Primary Actor – Sender,
Secondary Actor Receiver.
ADMIN

View
Users

View
Admin Reports

Add Staff,
View Staffs
 lOMoARcPSD|15944306

User

View
Profile

View
User
 lOMoARcPSD|15944306

Sequence Diagram

Sequence diagram and collaboration diagram are called

INTERACTION DIAGRAMS. An interaction diagram shows an
interaction, consisting of set of objects and their relationship
including the messages that may be dispatched among them.

A sequence diagram is an introduction that empathizes the time

ordering of messages. Graphically a sequence diagram is a table
that shows objects arranged along the X-axis and messages
ordered in increasing time along the Y-axis.

Data Flow Diagram

 lOMoARcPSD|15944306

DFD LEVEL 0

ADD View Staffs,

ADMIN
Online View Reports
Shopping

DFD LEVEL 1

Select Product,
User
Online AddToCart, View
Shopping Reports

DATA FLOW DIAGRAMS:

The DFD takes an input-process-output view of a system

i.e. data objects flow into the software, are transformed by
processing elements, and resultant data objects flow out of the
software.

Data objects represented by labeled arrows and

transformation are represented by circles also called as bubbles.
DFD is presented in a hierarchical fashion i.e. the first data flow
model represents the system as a whole. Subsequent DFD refine
the context diagram (level 0 DFD), providing increasing details
with each subsequent level.
 lOMoARcPSD|15944306

The DFD enables the software engineer to develop

models of the information domain & functional domain at the
same time. As the DFD is refined into greater levels of details,
the analyst performs an implicit functional decomposition of the
system. At the same time, the DFD refinement results in a
corresponding refinement of the data as it moves through the
processes that embody the applications.

A context-level DFD for the system the primary external

entities produce information for use by the system and consume
information generated by the system. The labeled arrow
represents data objects or object hierarchy.

RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions

 Reads left to right and top to bottom.

 Identify all inputs and outputs.

 Identify and label each process internal to the system with

Rounded circles.

 A process is required for all the data transformation and

Transfers. Therefore, never connect a data store to a data Source
 lOMoARcPSD|15944306

or the destinations or another data store with just a Data flow

arrow.

 Do not indicate hardware and ignore control information.

 Make sure the names of the processes accurately convey

everything the process is done.

 There must not be unnamed process.

 Indicate external sources and destinations of the data, with

Squares.

 Number each occurrence of repeated external entities.

 Identify all data flows for each process step, except simple
Record retrievals.

 Label data flow on each arrow.

 Use details flow on each arrow.

 Use the details flow arrow to indicate data movements.

E-R Diagrams:
 lOMoARcPSD|15944306

The Entity-Relationship (ER) model was originally proposed by

Peter in 1976 [Chen76] as a way to unify the network and
relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and
relationships. A basic component of the model is the Entity-
Relationship diagram which is used to visually represent data
objects. Since Chen wrote his paper the model has been
extended and today it is commonly used for database design For
the database designer, the utility of the ER model is:

 It maps well to the relational model. The constructs used in

the ER model can easily be transformed into relational
tables.
 It is simple and easy to understand with a minimum of
training. Therefore, the model can be used by the database
designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the
database developer to implement a data model in specific
database management software.
Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-

to-many, and many-to-many. A one-to-one (1:1) relationship is
when at most one instance of a entity A is associated with one
instance of entity B. For example, "employees in the company
are each assigned their own office. For each employee there
exists a unique office and for each office there exists a unique
employee.
 lOMoARcPSD|15944306

A one-to-many (1:N) relationships is when for one instance of

entity A, there are zero, one, or many instances of entity B, but
for one instance of entity B, there is only one instance of entity A.
An example of a 1:N relationships is
a department has many employees

Each employee is assigned to one department

A many-to-many (M:N) relationship, sometimes called non-

specific, is when for one instance of entity A, there are zero, one,
or many instances of entity B and for one instance of entity B
there are zero, one, or many instances of entity A. The
connectivity of a relationship describes the mapping of
associated
ER Notation

There is no standard for representing data objects in ER

diagrams. Each modeling methodology uses its own notation.
The original notation used by Chen is widely used in academics
texts and journals but rarely seen in either CASE tools or
publications by non-academics. Today, there are a number of
notations used; among the more common are Bachman, crow's
foot, and IDEFIX.

All notational styles represent entities as rectangular boxes

and relationships as lines connecting boxes. Each style uses a
special set of symbols to represent the cardinality of a
 lOMoARcPSD|15944306

connection. The notation used in this document is from Martin.

The symbols used for the basic ER constructs are:

 Entities are represented by labelled rectangles. The label is the

name of the entity. Entity names should be singular nouns.
 Relationships are represented by a solid line connecting two
entities. The name of the relationship is written above the line.
Relationship names should be verbs
 Attributes, when included, are listed inside the entity
rectangle. Attributes which are identifiers are underlined.
Attribute names should be singular nouns.
 Cardinality of many is represented by a line ending in a crow's
foot. If the crow's foot is omitted, the cardinality is one.
 Existence is represented by placing a circle or a perpendicular
bar on the line. Mandatory existence is shown by the bar (looks
like a 1) next to the entity for an instance is required. Optional
existence is shown by placing a circle next to the entity that is
optional
 lOMoARcPSD|15944306

Fig 1.1: Admin module

MANAGE MODERATOR
 lOMoARcPSD|15944306

Fig 1.2: Manage Moderator

➢ Add Moderator

Only admin is having the privilege to add a moderator. A

moderator can be considered as a staff who manages the
orders or owner of a group of products.

➢ Block moderator
 lOMoARcPSD|15944306

Admin can restrict a moderator from managing the orders

by blocking them. Admin can unblock a blocked user if
needed.

➢ Remove Moderator

Admin has privilege to delete a moderator who was added.

➢ Search moderator:

All existing moderators can be viewed by the administrator

as a list. If there is number of moderators and admin need to
find one of them, the admin can search for a moderator by
name.

MANAGE PRODUCTS
 lOMoARcPSD|15944306

Fig 1.3: 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 Products

Administrator can delete the products based on the stock of

that particular product.

➢ Search products
 lOMoARcPSD|15944306

Admin will have a list view of all the existing products. He

can also search for a particular product by name.

MANAGE USER

Fig 1.4: Manage User

 lOMoARcPSD|15944306

➢ 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.

MANAGE ORDERS

Fig 1.5: Manage Orders

 lOMoARcPSD|15944306

➢ View Order
Administrator can view the Orders which is generated by the
users. He can verify the details of the purchase.

➢ Delete order
Admin can delete order from the orders list when the product is
taken for delivery.

1.4.1.2 MODERATORS

Fig 1.6: Moderator

Module

A moderator is considered as a staff who can manage orders

for the time being. As a future update moderator may give
facility to add and manage his own products . Moderators can
reduce the work load of admin. Now moderator has all the
privilege an admin having except managing other
 lOMoARcPSD|15944306

moderators. He can add products and users. He can

also check the orders and edit his profile.

➢ Manage products
➢ Manage users
➢ Manage orders

1.4.1.3 USERS

Fig 1.7: User Module

➢ Registration
 lOMoARcPSD|15944306

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 clicking on the cart button. All

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

➢ 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.

➢ History
In the history the user will have a view of pending orders.

➢ Edit Profile

The user can view and edit the profile.

 lOMoARcPSD|15944306

CHAPTER 2

SYSTEM ANALYSIS

System analysis is the process of gathering and interpreting

facts, diagnosing problems and using the information to
recommend improvements on the system. System analysis is
a problem solving activity that requires intensive
communication between the system users and system
developers.

System analysis or study is an important phase of any

system development process. The system is viewed as a
whole, the inputs are identified and the system is subjected
to close study to identify the problem areas. The solutions
are given as a proposal. The proposal is reviewed on user
request and suitable changes are made. This loop ends as
soon as the user is satisfied with the proposal.

2.1 EXISTING SYSTEM

The current system for shopping is to visit the shop manually

and from the available product choose the item customer
want and buying the item by payment of the price of the
item .

1. It is less user-friendly.
 lOMoARcPSD|15944306

2. User must go to shop and select products.

3. It is difficult to identify the required product.
4. Description of the product limited.
5. It is a time consuming process
6. Not in reach of distant users.

2.2 PROPOSED SYSTEM

In the proposed system customer need not go to the

shop for buying the products. He can order the product he
wish to buy through the application in his Smartphone. The
shop owner will be admin of the system. Shop owner can
appoint moderators who will help owner in managing the
customers and product orders. The system also recommends
a home delivery system for the purchased products.

2.3 SYSTEM REQUIREMENT SPECIFICATION

2.3.1 GENERAL DESCRIPTION

Product Description:

The system consists of two parts .A web application which can

provide the online shopping service and an android
application for the customer to
 lOMoARcPSD|15944306

access the web service from his Smartphone. Web

application should be able to help the customer for selecting
his item and to help the owner in managing the orders from
the customers.

Problem Statement:

As online shopping became a trend nowadays the regular

shops are losing their customers to online brands. Customers
have effortless shopping experience and saving time through
shopping online. For competing with those online brands , If
shops are providing an online portal where their customers
can shop through internet and get the products at their doors
it will increase the number of customers.

2.3.2 SYSTEM OBJECTIVES

➢ To provide an android application for online shopping

of products in an existing shop.
➢ To provide a online shopping web site for the same shop.

2.3.3 SYSTEM REQUIREMENTS

 lOMoARcPSD|15944306

2.3.3.1 NON FUNCTIONAL REQUIREMENTS

i. EFFICIENCY REQUIREMENT

When an online shopping cart android application

implemented customer can purchase product in an efficient
manner.

ii. RELIABILITY REQUIREMENT

The system should provide a reliable environment to both

customers and owner. All orders should be reaching at the
admin without any errors.

iii. USABILITY REQUIREMENT

The android application is designed for user friendly

environment and ease of use.

iv. IMPLEMENTATION REQUIREMENT

Implementation of the system using css and html in front end

with jsp as back end and it will be used for database
connectivity. And the database part is developed by mysql.
Responsive web designing is used for making the website
compatible for any type of screen.

v. DELIVERY REQUIREMENT

The whole system is expected to be delivered in four months of time with

 lOMoARcPSD|15944306

a weekly evaluation by the project guide.

2.3.3.2 FUNCTIONAL REQUIREMENTS

USER

➢ USER

LOGIN

Description of

feature

This feature used by the user to login into system. A user

must login with his user name and password to the system
after registration. If they are invalid, the user not allowed to
enter the system.

Functional requirement

- Username and password will be provided after user

registration is confirmed.
- Password should be hidden from others while typing it in the
field

➢ REGISTER NEW

USER Description of
 lOMoARcPSD|15944306

feature
 lOMoARcPSD|15944306

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.

Functional requirement

- System must be able to verify and validate information.

- The system must encrypt the password of the
customer to provide security.
➢ PURCHASING AN

ITEM Description of

feature

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
clicking on the cart button. All products added by cart can be
viewed in the cart. User can remove an item from the cart by
clicking remove. 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.

Functional requirement

- System must ensure that, only a registered customer

can purchase items.
 lOMoARcPSD|15944306

ADMIN

➢ MANAGE

USER

Description of

feature

The administrator can add user, delete user, view user and block
user.

➢ MANAGE

MODERATOR

Description of feature

The administrator can add moderator, delete moderator,

block moderator and search for a moderator.

➢ MANAGE

PRODUCTS

Description of feature

The administrator can add product, delete product and view

product.

➢ MANAGE

ORDERS

Description of
 lOMoARcPSD|15944306

feature

The administrator can view orders and

delete orders. Functional requirements

-The system must identify the login of the admin.

 lOMoARcPSD|15944306

-Admin account should be secured so that only owner of

the shop can access that account

MODERATOR

Description of features

A moderator is considered as a staff who can manage orders

for the time being. As a future update moderator may give
facility to add and manage his own products. Moderators can
reduce the work load of admin. Now moderator has all the
privilege of an admin having except managing other
moderators. He can manage users and manage products. He
can also check the orders and edit his profile.

Functional requirement

-The system must identify the login of a moderator.

 lOMoARcPSD|15944306

CHAPTER 3

SYSTEM DESIGN

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
 lOMoARcPSD|15944306

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.

3.1.2 OUTPUT DESIGN:

 lOMoARcPSD|15944306

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.

3.2 DATABASE

DATABASE DESIGN:

Databases are the storehouses of data used in the software

systems. The data is stored in tables inside the database.
Several tables are created for the manipulation of the data
for the system. Two essential settings for a database are

- the field that is unique for all the record

occurrences.

-the field used to set relation between tables.

Normalization is a technique to avoid redundancy in the tables.

3.3 SYSTEM TOOLS

The various system tools that have been used in developing

both the front end and the back end of the project are being
discussed in this chapter.
 lOMoARcPSD|15944306

3.4 TABLES

3.5 E-R DIAGRAMS

➢ LOGIN

Fig 3.5: Login

➢ USER DETAILS

Fig 3.6: User Details

 lOMoARcPSD|15944306

➢ PRODUCT DETAILS

Fig 3.7: Product

Details

➢ PRODUCT ORDERS

Fig 3.8: Product

Orders
 lOMoARcPSD|15944306

➢ COMPLETE DIAGRAM

Fig 3.9: Complete Diagram

3.6 DATA FLOW DIAGRAM

A Data Flow Diagram (DFD) is a structured analysis

and design tool that can be used for flowcharting. A DFD is
a network that describes the flow of data and the
processes that change or transform the data throughout a
system. This network is constructed by using a set of
symbols that do not imply any physical implementation. It
has the purpose of clarifying system
 lOMoARcPSD|15944306

requirements and identifying major transformations. So it is

the starting point of the design phase that functionally
decomposes the requirements specifications down to the
lowest level of detail. DFD can be considered to an
abstraction of the logic of an information-oriented or a
process- oriented system flow-chart. For these reasons
DFD’s are often referred to as logical data flow diagrams.

EXTERNAL ENTITY

An external entity is a source or destination of a data flow.

Only those entities which originate or receive data are
represented on a data flow diagram. The symbol used is a
rectangular box.

PROCESS

A process shows a transformation or manipulation of data

flow within the system. The symbol used is an oval shape.

DATAFLOW
 lOMoARcPSD|15944306

The data flow shows the flow of information from a source to

its destination. Data flow is represented by a line, with
arrowheads showing the direction of flow. Information always
flows to or from a process and may be written, verbal or
electronic. Each data flow may be referenced by the
processes or data stores at its head and tail, or by a
description of its contents.

DATA STORE

A data store is a holding place for information within the

system: It is represented by an open ended narrow rectangle.
Data stores may be long-term files such as sales ledgers, or
may be short-term accumulations: for example batches of
documents that are waiting to be processed. Each data store
should be given a reference followed by an arbitrary number.

➢ LOGIN DFD
 lOMoARcPSD|15944306

Fig 3.10: Login DFD

➢ REGISTRATION DFD
 lOMoARcPSD|15944306

Fig 3.11: Registration DFD

➢ ADMIN DFD
 lOMoARcPSD|15944306

Fig 3.12: Admin DFD

 lOMoARcPSD|15944306

➢ MODERATOR DFD

Fig 3.13: Moderator DFD

 lOMoARcPSD|15944306

3.7 SCREEN SHOTS

Home Page

AboutPage
 lOMoARcPSD|15944306

ServicesPage

GalleryPage
 lOMoARcPSD|15944306

REGISTRATION
 lOMoARcPSD|15944306

AdminLogin

Staff Login

UserLogin
 lOMoARcPSD|15944306

AdminMainPage

NewStaff
 lOMoARcPSD|15944306

NewProduct

AdminViewStaffs
 lOMoARcPSD|15944306

ViewCustomersPage

ViewCartPage
 lOMoARcPSD|15944306

UserViewProducts

UserViewCartPage
 lOMoARcPSD|15944306

UserViewReports
 lOMoARcPSD|15944306

CHAPTER 4

CONCLUSION

The project entitled Online 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.
 lOMoARcPSD|15944306

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 extend. A number of features can be added to this
system in future like providing
 lOMoARcPSD|15944306

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.
 lOMoARcPSD|15944306

REFERENCES

[1]JavaScript Enlightenment,Cody Lindley-First

Edition, based on JavaScript 1.5, ECMA-262, Edition

[2] Mc GrawHill’s , Java : The complete reference

7thEdition, Herbert Schildit

[3]Complete CSS Guide ,Maxine Sherrin and John

Allsopp-O'Reilly Media; September 2012

[4]http://www.w3schools.com/html/
defualt.asp,
http://www.w3schools.com/css/defau
lt.asp,
http://www.w3schools.com/js/default
.asp