1

MCSP-060
Synopsis on Online Shopping
by
Shreya Golchha
125129252
Under The Guidance
of

Submitted to the School of Computer and Information Sciences,

IGNOU
in partial fulfillment of the requirements
for the award of the degree
Master of Computer Application (MCA)
2015

INDIRA GANDHI NATIONAL OPEN UNIVERSITY

MAIDAN GARHI
NEW DELHI -110068

Contents
S.No Title
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.

Pg No.

Title of the project

Introduction and Objective of the Project
Project Category
Tools/Platform, Hardware and Software
Requirement Specifications
Problem Definition, Requirement Specifications,
Project Planning and Scheduling
Scope of the solution
Analysis
A complete Database
A complete Structure
Overall network architecture
Implementation of security mechanisms
Future Scope and further enhancement
Bibliography

3
4
5
6
7
13
14
22
24
28
29
30
31

TITLE OF THE PROJECT

Online Shopping

2. INTRODUCTION & OBJECTIVE OF THE

PROJECT

2.1 INTRODUCTION
Online shopping represents the direction of future trade
development. Promotion of e-commerce will bring great
benefits to the society and the economy. For example, online
shopping improves the speed and quality of services of
transaction, promotes the globalization of markets, and cuts
down cost. For these reasons, this project aimed to design
and implement an e-commerce website. The website is
designed for people who prefer online shopping of daily
necessities and requirement. This website covers the entire
process of trading online.

2.2 OBJECTIVES OF THE PROJECT

The main objective of this project are as follows :
i.

Provide trading of products online.

ii.

User can be either a seller or a customer.

iii.

Special banking services are provided.

iv.

Feedback is taken by the user for the improvement in t project.

3. PROJECT CATEGORY
RDBMS stands for Relation Database Management System. It organizes data
into related rows and columns. It has following special features.
i.
ii.
iii.
iv.
v.
vi.
vii.

Provides data to be stored in tables

Persists data in the form of rows and columns
Provides primary key, to uniquely identify the rows
Creates indexes for quicker data retrieval
Provides a virtual table creation in which sensitive data can be
stored and simplified query can be applied (views)
Sharing a common column in two or more tables
Provides multi user accessibility that can be controlled by
individual users

SQL Server is designed to be a client server system. Client server systems are
constructed so that the database can reside on a control computer and be
shared among several users. SQL Server can work with thousands of client
applications simultaneously. SQL Server user Transact SQL as its database
query and programming language. SQL is a set of commands that allows the
user to specify the information to be retrieved or modified with Transact SQL.
We can access data and query, update and manage relational database system.

4. TOOLS/PLATFORM, HARDWARE AND

SOFTWARE REQUIREMENT
SPECIFICATIONS
4.1

TOOLS/PLATFORM-

Operating System

Windows XP/7 or Linux

Web Applications

ASP.net, XML, CSS, JS

4.2

SOFTWARE REQUIREMENTS-

.Net Framework 4.0 or above

Database SQL Server
IDE/Workbench Visual Studio 2010 or above

4.3

HARDWARE REQUIREMENTS-

Processor Pentium IV or Above

Hard Disk 40GB
RAM 512MB or more

5. PROBLEM DEFINITON, REQUIREMENT

SPECIFICATIONS, PROJECT PLANNING AND
SCHEDULING
5.1 PROBLEM DEFINITION
Many people still travels to different places searching for products where they
end up being stranded and dont get the products or services of their choice.
Existing system are complex for users because they need a lot of clicking
different links before one can buy or order their items. It is also time
consuming looking for a certain products or service in different shops and
comparing their quality and price. In order to solve this, simple and secure
online shop management system has to be developed. Using this system, we
can buy goods online just by visiting the website, ordering the items and
making payments online. The system also minimize on expenditure and cost
of transport for customers.

5.2

REQUIREMENT SPECIFICATIONS

The aim of this document is to gather and analyze and give in-depth insight of
the Online Shopping by defining the problem statement in detail.
5.2.1

PURPOSE

The purpose of the document is to provide a detailed overview of our software

product, its parameters and goals. This document describes the project's target
audience and its user interface, hardware and software requirements. It defines
how our client, team and audience see the product and its functionality.

5.2.2 Functionality
Sell Configured to Ordered Products.
i.

The system shall display all the products that can be configured.

ii.

The system shall allow user to select the product to configure.

iii.

The system shall enable user to add one or more component to the
configuration.

iv.

The system shall notify the user about any conflict in the current
configuration.

v.

The system shall allow user to update the configuration to resolve

conflict in the current configuration.

vi.

The system shall allow user to confirm the completion of current

configuration

Provide comprehensive product details.

i.

The system shall display detailed information of the selected products.

ii.

The system shall provide browsing options to see product details.

Detailed product Categorizations

i.

The system shall display detailed product categorization to the user.

Provide Search facility.

i.
ii.
iii.
iv.
v.

The system shall enable user to enter the search text on the screen.
The system shall display all the matching products based on the search
The system shall display only 10 matching result on the current screen.
The system shall enable user to navigate between the search results.
The system shall notify the user when no matching product is found on
the search.

Maintain customer profile.

i.
ii.
iii.

The system shall allow user to create profile and set his credential.
The system shall authenticate user credentials to view the profile.
The system shall allow user to update the profile information.

Provide personalized profile

i.
ii.
iii.
iv.
v.

The system shall display both the active and completed order history in
the customer profile.
The system shall allow user to select the order from the order history.
The system shall display the detailed information about the selected
order.
The system shall display the most frequently searched items by the
user in the profile.
The system shall allow user to register for newsletters and surveys in
the profile.

Provide Customer Support.

i.
ii.
iii.
iv.
v.
vi.
vii.

The system shall provide online help, FAQs customer support, and
sitemap options for customer support.
The system shall allow user to select the support type he wants.
The system shall allow user to enter the customer and product
information for the support.
The system shall display the customer support contact numbers on the
screen.
The system shall allow user to enter the contact number for support
personnel to call.
The system shall display the online help upon request.
The system shall display the FAQs upon request.

Email confirmation.
i.
ii.

The system shall maintain customer email information as a required

part of customer profile.
The system shall send an order confirmation to the user through email.

Detailed invoice for customer.

i.
ii.

The system shall display for current order once it is confirmed.

The system shall optionally allow user to print the invoice.

Provide shopping cart facility.

i.
ii.

The system shall provide shopping cart during online purchase.

The system shall allow user to add/remove products in the shopping
cart.

10

Provide multiple shipping methods.

i.
ii.
iii.
iv.

The system shall display different shipping options provided by

shipping department.
The system shall enable user to select the shipping method during
payment process.
The system shall display the shipping charges.
The system shall display tentative duration for shipping.

Online tracking of shipments

i.
ii.

The system shall allow user to enter the order information for tracking.
The system shall display the current tracking information about the
order.

Provide online Tax Calculations

i.
ii.

The system shall calculate tax for the order.

The system shall display tax information for the order.

Allow multiple payment methods.

i.
ii.

The system shall display available payment methods for payment.

The system shall allow user to select the payment method for order.

Allow online change or cancellation of order.

i.
ii.
iii.
iv.
v.

The system shall display the orders that are eligible to change.
The system shall allow user to select the order to be changed.
The system shall allow user to cancel the order
The system shall allow user to change shipping, payment method.
The system shall notify the user about any changes made to the order.

Allow Online Product reviews and ratings

i.
ii.

The system shall display the reviews and ratings of each product, when
it is selected.
The system shall enable the user to enter their reviews and ratings.

Offer financing options.

i.
ii.
iii.

The system shall display all the available financing options.

The system shall allow user to select the financing option.
The system shall notify the use about the financing request.

10

11

Provide detailed sitemap.

i.

The system shall allow user to view detailed sitemap.

Offer online promotions and rewards.

i.
ii.

The system shall display all the available promotions to the user.
The system shall allow user to select available promotion.

Online Purchase of products.

i.
ii.

The system shall allow user to confirm the purchase.

The system shall enable user to enter the payment information.

Usability
i.
ii.
iii.

The system shall provide a uniform look and feel between all the web
pages.
The system shall provide a digital image for each product in the
product catalog.
The system shall provide use of icons and toolbars.

Accessibility
i.
ii.

The system shall provide handicap access.

The system shall provide multi language support.

Reliability & Availability

Back-end Internal Computers
i.
ii.
iii.

The system shall provide storage of all databases on redundant

computers with automatic switchover.
The system shall provide for replication of databases to off-site storage
locations.
The system shall provide RAID V Disk Stripping on all database
storage disks.

Performance
i.
ii.

iii.

The product shall be based on web and has to be run from a web
server.
The product shall take initial load time depending on internet
connection strength which also depends on the media from which the
product is run.
The performance shall depend upon hardware components of the
client/customer.
11

12

Security
Data Transfer
i.
ii.
iii.
iv.
v.

The system shall use secure sockets in all transactions that include any
confidential customer information.
The system shall automatically log out all customers after a period of
inactivity.
The system shall confirm all transactions with the customers web
browser.
The system shall not leave any cookies on the customers computer
containing the users password.
The system shall not leave any cookies on the customers computer
containing any of the users confidential information.

Interfaces
i.

There are many types of interfaces as such supported by the E-Store

software system namely; User Interface, Software Interface and
Hardware Interface.

ii.

The protocol used shall be HTTP.

iii.

The Port number used will be 80.

iv.

There shall be logical address of the system in IPv4 format.

User Interfaces
The user interface for the software shall be compatible to any browser such as
Internet Explorer, Mozilla or Netscape Navigator by which user can access to
the system.
i.

The user interface shall be implemented using any tool or software

package like Java Applet, MS Front Page, EJB etc.

Hardware Interfaces
Since the application must run over the internet, all the hardware shall require
to connect internet will be hardware interface for the system. As for e.g.
Modem, WAN LAN, Ethernet Cross-Cable.

Software Interfaces
The e-store system shall communicate with the Configurator to identify all the
available components to configure the product.

12

13

i.

The e-store shall communicate with the content manager to get the
product specifications, offerings and promotions.

ii.

The e-store system shall communicate with billPay system to identify

available payment methods , validate the payments and process
payment.

iii.

The e-store system shall communicate to credit management system

for handling financing options.

iv.

The e-store system shall communicate with CRM system to provide

support.

v.

The e-store system shall communicate with Sales system for order
management.

Communications Interfaces
i.

The e-store system shall use the HTTP protocol for communication
over the internet and for the intranet communication will be
through TCP/IP protocol suite.

Legal, Copyright, and Other Notices

i.

E-store should display the disclaimers, copyright, word mark,

trademark and product warranties.

5.3 PROJECT PLANNING AND SCHEDULING

6. SCOPE OF THE SOLUTION

13

14

For this project we want to define what will be done such that the final product
meets expectations. With this in mind, the following are the parts that will be
completed:
1. Secure registration and profile management facilities for customers
2. Browsing through the e-shops to see the items that are there in each
category of products like Apparel, Kitchen Accessories, Food, etc.
3. Adequate searching mechanisms for easy and quick access to
particular products and services.
4. Payment mechanism and gateway for all popular credit cards,
checks and other relevant payment options.
In addition to the above mentioned basic functional requirements for the
project, we plan for the following supplementary requirements as well. We
will create a shopping cart so that the customers can save their items and
checkout later with the entire shopping cart. A sorting mechanism for products
in each category such as: most purchased, price from low to high, and newly
listed. We also plan for a feedback mechanism for the products from the
customers. Feedback can also be given on a particular vendor and the entire
mall.
For maintaining the robustness of the system and also for the safety of
customers and vendors, we will ensure following in the project:
1. Overall system quality should be good and it should be a smooth
experience for both vendors and customers.
2. The system should be easy to maintain. We will be using object
oriented programming techniques.
3. Customers and vendors details will be secure from outside
intruders.
4. Safe payment gateways will be used and all the security checks
will be made to ensure a safe deal.
5. The system will remain up at all times. The hardware and
software should be robust and will be tested extensively.

7. ANALYSIS
7.1 Data Flow Diagram (DFD)
14

15

A Data flow diagram (DFD) is used to express system requirements in a

graphical form. It is also known as a bubble chart. A DFD depicts information
flow and transform that are applied as data moves from input. Use of DFD helps
to clarify the system requirements. DFD are drawn surging analysis and are the
starting point for the design phase. A DFD could be used represent a physical
system, at the beginning of analysis, or a logical system at alter point in the
system development life cycle. Being graphical, it is easy to understand.
A DFD is used to describe what data flows rather how it flows. The concern is
understanding the transforms that are required to convert the input to output. It
is independent of hardware, software, data structure and file organization.
Level 0 DFD-

Level 1 DFD-

15

16

16

17

Level 2 DFD-

Level 2 for 4.0

17

18

Level 2 for 5.0

Level 3 for 4.3

18

19

7.2

Activity Diagrams

7.2.1 System Administrator

7.2.2 Owner

19

20

7.2.3 Registered User

7.2.3 Unregistered User

20

21

7.3 Class Diagram

21

22

7.4

State Diagram

22

23

23

24

7.5

E-R Diagrams

An E-R diagram is a model that identifies the concept or entities that exist in a
system and the relationships between those entities. An ERD is often used as a
way to visualize a relational database. Each entity represents a database table
and the relationship lines represents the key in one table that point to specific
records in related tables.
Advantages of ER diagram
Professional and faster Development.
Productivity Improvement.
Fewer Faults in Development.
Maintenance becomes easy.

24

25

8. A COMPLETE DATABASE

8.1 TABLE STRUCTURE

Table 1

Table 2

UserConstraints

Atrributes

Datatype

Primary key

*Userno

Int

Pwd

Varchar

10

Username

Varchar

20

UserinfoConstraints

Primary Key

Table 3

Table 4

Category
Constraints
Primary Key

Product
Constraints
Primary Key

Size

Attributes
u_type
i_auto id
*i_net id
c_utype
c_address
c_name
i_mobile
c_Email id
c_A/c no
c_bank name

Datatype
Varchar
Int
Int
Varchar
Varchar
Varchar
Int
Varchar
Varchar
Varchar

Size
10

Attributes

Datatype

Size

*catid int

Int

catname
catype

Varchar
Varchar

Attributes
*Pid
Pname

Datatype
Int
Varchar

10
10
20
20
20
20

10
10

Size
20
25

26

Table 5
Sales
Constraints
Primary Key

Table 6
Cart
Constraints
Primary Key
Foreign Key

Category
Brand
Img
Price
Content

Varchar
Varchar
Binary
Varchar
Varchar

10
10

Attributes
*sid
sname
pname
ptype
Price
Contact_no
Addr

Datatype
Int
Varchar
Varchar
Varchar
Varchar
Varchar
Varchar

Size

Attributes
*ctid
*pid
Pname
Price
Total
Qty

Datatype
Int
Int
Varchar
Varchar
Varchar
Varchar

Size

10
50

20
10
10
10
50

20
10
10
10

26

27

9. A COMPLETE STRUCTURE
9.1

MODULE DESCRIPTION

9.1.1

Modules

The modules used in this software are as follows:

Login: This module has a drop down list box from where we have to
select ADMIN or USER. The ADMIN has all the rights in the software
including updating the status of his site. The other fields in login are username
and password. If the username and password are correct then it is directed to
next page.
New user: This module is for the users who do not have their account.
Here user is allowed to create an account to login. The account creation is
done by filling the registration form with user details such as name, phone,
email etc.
Product: This module has information regarding the products such as
its name, model, color, price information, its features etc.The ADMIN has the
authority to Add, Delete, Update etc. The USER can only view the Products,
add to cart only those in the stock etc.
27

28

Accessories: This module consists of various available accessories of

the Mobile with its name and picture, price information etc.
Search: This module helps the customer to ease his search based on
his budget or interest. The search can be done on different categories like
mobile model name, model number, colour, price etc
Cart: User can select any number of Mobile and add to the cart. He
can also remove from the cart if he dislikes it later.
Payment: This module describes the payment done by the customer.
The payment information can include information like the model purchased,
quantity, mode of payment (cash, loan) etc.
Stocks: This gives the details regarding the products available for sale.

9.1.2

Flow Diagrams of main Modules

28

29

Navigation is a fundamental component of any website. Although it is easy

enough to switch the user from one page to another, creating a unified system
of navigation that works across an entire website takes more effort. For the
Online Website, the special columns and functions design of the navigation
bar in sales module is as explained below:
1. Product special columns displays new arrivals, special offers, hot sales,
sales ranking and recommended. Each column is divided according to the
product information in a particular field of database table. For example, the
29

30

products displayed in special offers column are those with discounts of more
than 20%. New arrivals are products released within the previous three days or
one week. Sales ranking is organized according to the number of orders.
2. Shopping cart functions display the select item, view, and empty the cart.
Before the customer submits an order, information about all the selected
products is stored in the dataset of the implementation class file of the
shopping cart. When the order is submitted, the dataset is written into the
database. The user cannot use the submit function before they log in. If the
user adds an item into the shopping cart, the system prompts user login.
3. Membership centre displays registration, login, and reclaim password. For
registration function, the system requires the user to enter information
depending on the field of the database membership information in the data
table. Parity is achieved through various types of validation controls. Log in
and reclaim the password functions are also required data on the membership
information data sheet.
4. News management functions display news in the database on the home
page, while allowing the user to click on a specific news headline for more
information.
5. Login and registration: The system is to be emptied of the members login
infor-mation after they logout.
9.1.3 Background Management System Design
The background system management module is used by the administrators. It
consists of product information, orders, news, main category, secondary
category, comment management, member management and administrator
management.

30

31

9.2 Product Functions

9.2.1 For Users
(i) Basic Account features are required for both Customers and Sellers.
This includes
Registering
Login
Forgot/change passwords
Account Details section containing contact details
Browse and Search:
User should be able to browse through the entire items list by
modifying certain selection criteria's such as: Item category, Price
range selection, Item/Seller Rating based selection
In addition to providing the above mentioned search feature, user
should also be able to search for a particular product. This is applicable
to all stakeholders (Guests, Customers, Sellers and Administrators)
Shopping:
Add / remove items to their shopping cart/list
Customer should have the option to buy desired item(s) sold by one or
more sellers.
Customer will have access to finalize product lists of items she wishes
to buy and make the final payment.
The website should support all popular credit cards and make sure that
the transaction happens securely
History:
Shopping history: List of items previously shopped
Item View history : List of recently viewed items
Search history: Recent search criteria used by a customer.
31

32

9.2.2 For Sellers

Account Setting
The requirements specified in the Accounts section in user
requirements
Shop installation request
Transaction history
Status of all the transactions for a seller.
9.2.3 For Administrators
Account Setting
Authorizing shop installation requests
Updating product information
Monitoring transactions and keeping track of its status
Update Seller/Customer/transaction information (In case of system
errors/complaints)

10 Overall Network Architecture

Architectural design
In this design level, the basic structural framework that identifies the major
components of asystem and the communications between these components.
Below is a general model for the whole system

32

33

11. IMPLEMENTATION OF SECURITY

MECHANISM AT VARIOUS LEVELS
11.1

System Integration and Testing

Having written the codes for each module, the modules were integrated
and then the resultant main module was tested to detect and correct any errors
11.1.1 Unit Testing
The resultant system after the integration of the modules was tested to
ascertain its correctness in terms input, processing and output. This was done
by executing prepared test scenario. The unit testing focused on the internal
processing logic and data structures within
the boundaries of a component. More than often, the developer had to keep edi
ting a module severally until each module was complete and correct.
11.1.2 Validation Testing
The system was tested using prepared test cases to ascertain that the right
system was built. It was also done to test if the system satisfied all the problem
requirements of the project. The system was also given out to enumerators to
work with and identify any faults in its functionalities.
11.1.3 Security testing
Security testing attempted to verify that protection mechanism of the system.
It is protected against unauthorized access. There was deliberate inputting of
username with a passwords and the reaction of the system were checked.

33

34

12. FUTURE SCOPE

The current level of empirical research done on retail in the Indian context is
miniscule. This study is concentrated on perceptions and evaluations of food
& grocery stores and seeks to build on the very little research done in retailing
in general, and data mining in retailing in particular. In the future, researchers
can seek other relevant research problems from the industry and from existing
literature.
In terms of future scope, a variety of data mining techniques can be used by
researchers to simplify customer perceptions and attitudes. Every day, every
hour and every minute, tera-bytes of data gets generated from millions of
shoppers, yet, retail managers/ business executives always grapple with
relevant information that can help retailers/ researchers design strategies to
generate customer loyalty.

34

35

13.

BIBLIOGRAPHY

BOOKS
System Analysis & Design (MCS_014)
Software Engineering(MCS_034)
Database Concepts by B.C Desai
Professional SQL server 2000 programming Rob Viera, Wrox Publication

WEB SITE

www.msdn.microsoft.com
www.support.microsoft.com
www.altavista.com
www.developer.com/net

35

36

X.

CERTIFICATE OF ORIGINALITY

This is to certify that the project report entitled

__________________________________ submitted to Indira Gandhi
National Open University in partial fulfilment of the requirement for the
award of the degree of MASTER OF COMPUTER APPLICATIONS
( MCA) , is an authentic and original work carried out by Mr. /
Ms.___________________________________with enrolment no.
_______________________under my guidance.

The matter embodied in this project is genuine work done by the

student and has not been submitted whether to this University or to any other
University / Institute for the fulfilment of the requirements of any course of
study.
.
Signature of the Student

....
Signature of the Guide

Date: ..

Date:

Name and Address

Name, Designation

of the student

and Address of the

Guide:
36

37

..

..

..

..

..

..

..

..

Enrolment No

37