ONLINE SHOPPING AND MANGEMENT SYSTEM

A
Project Report
IN
PARTIAL FULFILLMENT
FOR THE AWARD OF
Diploma in Department of Computer science & Engineering
(With specialization in Computer Science & Engineering)

Submitted By: - Submitted To:-

Pritam Raj Miss. Preeti Sharma
(Assistant Professor)

UDAIPUR

Department Of Computer Science and Engineering

Aravali Institute of Technical Studies, Udaipur
(Raj.) Board of Technical Education, Jodhpur (june-2019)
0
 ACKNOWLEDGEMENT
I have done my best for this project. However, it was impossible without direction and kind
support of some people. We would like to extend our sincere thanks to all of them.

I am highly indebted to ATN Technology Pvt. Ltd. For providing as a productive environment
and all the facilities to learn. ATN Technology for their support and for giving us this
opportunity to take this project. His constant guidance, suggestions and kind support has made
this project to its desired end. I would like to thanks our colleagues for their support and
encouragement during the project work.

I perceive this project as a big milestone in our career development. I will strive to use gained
skills and knowledge in the best possible way. And I will continue to work on their
improvement, to order to attend desired career objectives.

Sincerely
Pritam Raj
Department of computer science
Aravali Institute of Technical studies, Udaipur

1
 INDEX

1. Introduction………………………………………………………………………………………….….... 3
1.1 Purpose of the Project ………………………………………………………………………….……………….. 3
1.2 Objectives …………………………………………………………………………………………….……………….. 3
1.3 Scope …………………………………………………………………………………………………………………….. 4
1.4 Benefits from Administrative View…………………………………………………………………………. 5
2. Requirement analysis………………………………………………………………………………….. 6
2.1 Requirements Analysis …………………………………………………………………………………………… 6
2.1.1 Data Requirements …………………………………………………………………………………………… 7
2.1.2 Process Requirement………………………………………………………………………………………… 7
2.2 Use case Diagram ………………………………………………………………………………………….….... 8
2.2.1 Use Case Diagram for Administrative Management …………………………………………. 9
2.2.2Use Case Diagram for Policyholder ………………………………………………………………….. 12
3. Designee Specification …………………………………………………………………………….… 15
4. Implementation and User Feedback……………………………………………………….…. 20

5. Conclusion……………………………………………………………………………………….………… 25

2
 Introduction

1.1 Purpose of the project

Shopping has long been considered as refreshment by many. Shopping in online

became a recreational activity of life. The reason of developing web based online
shopping system is everyone walking down the street has some difficulties, also
some people are so much busy and not able to go out for shopping, some don’t like
to shop in crowd. There is another reason that it’s not possible to see all the product
of a store, also its hazardous for both the customer and the seller. The world of
software development there lots of improvement in this area and to reduce the
complexity of people of life online shopping system development.

Online shopping system is a virtual store on Internet where customer can browse
the product and select the product of interest. The selected product may be
collected in shopping cart. At checkout time the items in the shopping care will be
presented as an order. At that time shipping information and payment method have
to select to the customer. Finally by confirming the order has to complete the
shopping and the product will deliver to customer via currier, post office or by

direct agent of company.

3
1.2 Objectives

The objective of the Shopping systems is to increase the point of customer choice,
reduce time used in shopping and efficiency in buying product.
 To develop an easy way to use web based interface where users can search
for product view the details of the product and order it without going to
market.
 The searching product can be done by product category, manufacturer as
well as latest product, view it purchase it become a convenient way for
customer.
 Customer can add product to cart to purchase, delete the product from cart
before selecting the final submission.
 A user can view the complete specification of the product with various
images and also view the customer review the product.
 It minimizes the shopping time of customer, increase the point of choice.
 It also facilitate the service provider to know the current status of market
and take decision which product are selling more now a days and have to
keep in store.

1.3 Scope

Following are the scope of the developed systems:

For Customer

Online registration: Customer has to register to buy product online.

View Product: Customer can view product according to category,

manufacturer and latest product. Select the items to cart, also can delete from
cart before final submission, he can also view product details, shipping info and
price that means all in invoice.

4
 Shipping Information: Customer has to give the product delivery location.

Payment Method: Customer can select the payment method what is easy for
him for payment the cost.

For admin:

Category: admin can add category, view, publish, unpublished, edit and delete
category.

Manufacturer: admin can add manufacturer, view, publish, unpublished, edit

manufacturer and delete manufacturer.

Product: admin can add product, view, publish, unpublished, edit manufacturer
and delete product.

Product delivery status: Admin can update sold product status.

1.4 Benefits from admin view

Following are the benefit from the administrative view

 Helps to efficient management of the company

 Easy to manage the whole system 3
 Time consuming and give better services.
 Admin can publish or unpolished the category as a result it will not show
from customer end for those product category not available, and published
the product those available.
 Same application can be used for different online shopping purpose.

5
Requirement Analysis

2.1 Requirement Analysis

As the goal of the application is ease of use and to provide an interactive interface,
extensive research has been done to gain an insight into the needs and behaviors of
various users. The working of the application is made convenient and easy to use for the
end user. In online web based shopping systems there are two party who interact with
the system, one of them are customer who wants to buy product and other the system
admin manage the system. A good web based online shopping system should present
the following factors to the customers for better usability.

Customer requirements:

 Knowing when an item have to save not save in the shopping cart.
 Returning the different parts of the site after adding an item to the shopping
cart.
 Easy scanning and selecting items in the list.
 Effective categorical organization of the products.
 Simple navigation from home page to information and order links for specific
products.
 Obvious shopping links or buttons.
 Consistent layout of product information.
 A well-organized web interfaces to work as admin so that he can handle all the
part of the system properly.

6
2.1.1 Data Requirement

 A customer can view the product properly but to buy he has to add the
product in shopping cart, for this he has to register or have to login if he is an
existing user.
 To launch the system, admin have to select the category of product,
company or manufacturer of product will remain in the system for customer
view and he can select those from his panel
 From user part or customer part when a customer order from his part can
manage the order of the product.
 Admin can add manufacturer of product, view manufacturer, delete
manufacturer, update manufacturer and its status those are not available in
shop as unpublished.
 Admin can add product, view product, delete product, update product and
its status those are not available in shop as unpublished.
 Admin can add category of product, delete, view, update product and its
status those are not available in shop or stop to sell or not to show to
customer.
 Another important factor in the design of the software that the feedback.
The interactive cycle between a use and website in not complete until the
responds to a command by the user.

2.1.2 Process Requirement

To perform any systems have some specific authentication functionality. The following
process requirements are identified for the better performance of the system:

7
  A valid admin user is needed to access the information of the system for the
admin.

 A valid customer ID is need to the customer to buy the product.

 Admin login to the system can view, edit, delete and update category,
manufacturer and product related information. Also he can update the order
information

 Customer can add product to cart only when he is a register user to the system,
as well as have to login to the system otherwise not able to add product to cart.

2.2 Use Case Diagram

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It
consists of a group of elements (for example, classes and interfaces) that can be used
together in a way that will have an effect larger than the sum of the separate elements
combined

The use case should contain all system activities that have significance to the users. A use
case can be thought of as a collection of possible scenarios related to a particular goal,
indeed, the use case and goal are sometimes considered to be synonymous.

In this use case diagram of Online Shopping admin can add, delete, edit and view Category,
Manufacturer and Product as well as admin can manage all of them. Also Admin can
manage order those are requested by the customer, and can change the status.

8
 2.2.1 Use Case Diagram for Administrative Management

Figure: Use case Diagram for Administrative Management

Description:

Use case No: 001

Use case Name: Add Category

Actor: Admin

Pre-requisite: login

Primary path: Click on Add Category

Use Case No: 002

Use Case Name: View Category

Actor: Admin

Pre-requisite: login

9
Primary Path: Click on View Category

Use Case No: 003

Use Case Name: Edit Category

Actor: Admin

Pre-requisite: login

Primary Path: Click on Edit Category

Use Case No: 004

Use Case Name: Delete Category

Actor: Admin

Pre-requisite login

Primary Path: Click on Delete Category

Use Case No: 005

Use Case Name: Add Manufacturer

Actor: Admin

Pre-requisite: login

Primary Path: Click on Add Manufacturer

Use Case No: 006

Use Case Name: View Manufacturer

Actor: Admin

Pre-requisite: login

Primary Path: Click on View Manufacturer

Use Case No: 007

Use Case Name: Edit Manufacturer

10
Actor: Admin

Pre-requisite: login

Primary Path: Click on Edit Manufacturer

Use Case No: 008

Use Case Name: Delete Manufacturer

Actor: Admin

Pre-requisite: login

Primary Path: Click on Delete Manufacturer

Use Case No: 009

Use Case Name: Add product

Actor: Admin

Pre-requisite: login

Primary Path: Click on Add product

Use Case No: 0010

Use Case Name: View product

Actor: Admin

Pre-requisite: login

Primary Path: Click on View product

Use Case No: 0011

Use Case Name: Edit product

Actor: Admin

Pre-requisite: login

Primary Path: Click on Edit product

11
Use Case No: 0012

Use Case Name: Delete product

Actor: Admin

Pre-requisite: login

Primary Path: Click on Delete product

Use Case No: 0013

Use Case Name: Manage Order

Actor: Admin

Pre-requisite: login

Primary Path: Click on Manage Order

2.2.2 Use Case Diagram for Customer

Figure 2.2: Use Case Diagram for Customer

12
Description:
This is the Use Case diagram for customer. This diagram shows the activity done from
customer end to buy the product. There are several option of searching a product by the
category, manufacturer, top selling and latest product. Those are given below one by one.

Use Case No: 001

Use Case Name: Register

Actor: Customer

Pre-requisite: None

Primary Path: Go to Home page of the shopping system, click on create account, fill the form
and finally click on create An Account

Use Case No: 002

Use Case Name: Search Product

Actor: Customer

Pre-requisite: None

Primary Path: Click on Category or Manufacturer name

Use Case No: 003

Use Case Name: View Product

Actor: Customer

Pre-requisite: None

Primary Path: Click on product

Use Case No: 004

Use Case Name: View Image

Actor: Customer

Pre-requisite: None

Primary Path: Put cursor on product image

13
Use Case No: 005

Use Case Name: Login

Actor: Customer

Pre-requisite: None

Primary Path: Click on login button

Use Case No: 006

Use Case Name: Add to cart

Actor: Customer

Pre-requisite: login

Primary Path: Click on add to cart button

Use Case No: 007

Use Case Name: Edit Cart

Actor: Customer

Pre-requisite: Have to add product to cart

Primary Path: Click on update

Use Case No: 008

Use Case Name: Add Shipping info

Actor: Customer

Pre-requisite: Checkout button

Primary Path: Give Shipping information and click on submit button

14
 Design Specification

3.1 Customer Interface

3.1.1 Home page

A home page is a webpage that serves as the starting point of website. It is the default webpage
that loads when visit a web. The home page is located in the root directory of a website. Most
web server allows the home page to have one of several different filenames. Examples include
index.html, index.htm, index.shtml, index, PHP, default.html, and home.html. The default
filename of a website's home page can be customized on both Apache and IIS servers. Since the
home page file is loaded automatically from the root directory, the home page URL does not
need to include the filename. There is no standard home page layout, but most home pages
include a navigation bar that provides links to different sections within the website. Other
common elements found on a home page include a search bar, information about the website,
and recent news or updates. Some websites include information that changes every day. For
example, the Tech Terms home page includes a daily quiz and tech term of the day. Home page
of shopping system includes so many part of the system those are below.

 Home Page view is shown in figure below:

Fig: Home Page

15
 Search Product

16
 Add To Cart

Fig: Add to cart

 Card View

Fig: Card View

17
 Add To favorite

Fig: Add to favorite

 Cart

Fig: cart View

18
 Category of products

Fig: Product’s Category

 Confirmation Message of adding in cart

Fig: Confirmation Message

19
 Implementation and User Feedback
4. 1 Implementation

While there are number of software tools to develop and implement the web based online
shopping system, I have chosen those are open source, so that it will reduce the developing
cost of the project. For designing the project HTML, CSS, Bootstraps, Apache server as web
server, PHP for making the system dynamic. MySQL as database server. All of the tools are open
source.

4.1.1 HTML

In this project HTML used for design the structure. HTML is a markup language for describing
web documents and stands for Hyper Text Markup Language, a markup language is a set of
markup tags.HTML documents are described by HTML tags. Each HTML tag describes different
document content. HTML used because:

• Easy to learn. • Easy to use. • Supported by all browser. • Cost effective.

4.1.2 PHP

In this project making the web page content dynamic and for interconnecting with database
coding done by PHP. PHP stats for Hypertext Preprocessor. The reason of using PHP are:

 PHP can generate dynamic page content.

 PHP can create, open, read, write, delete, and close files on the server.
 PHP can collect form data.
 PHP can send and receive cookies.
 PHP can add, delete, and modify data in database.
 PHP can be used to control user-access.
 PHP can encrypt data.

With PHP we cannot limited to output HTML. We can output images, PDF files, and even
flash movies. We can also output any text, such as XHTML and XML.

20
4.1.3 MySQL
MySQL is a database system used for the web application and it runs that runs on a server.
The reason of using MySQL are:

 MySQL is ideal for both small and large applications.

 MySQL is very fast, reliable, and easy to use.
 MySQL uses standard SQL.
 MySQL compiles on a number of platforms.
 MySQL is free to download and use.

The data in a MySQL database are stored in tables. A table is a collection of related data,
and it consists of columns and rows.

4.1.4 XAMPP server

XAMPP is a free and open source cross-platform web server solution stack package
developed by Apache Friends, consisting mainly of the Apache HTTP Server, Maria DB
database, and interpreters for scripts written in the PHP and Perl programming languages.
XAMPP stands for Cross-Platform (X), Apache (A), Maria DB (M), PHP (P) and Perl (P). It is a
simple, lightweight Apache distribution that makes it extremely easy for developers to
create a local web server for testing purposes. Everything needed to set up a web server –
server application (Apache), database (Maria DB), and scripting language (PHP) – is included
in an extractable file. XAMPP is also cross-platform, which means it works equally well on
Linux, Mac and Windows. Since most actual web server deployments use the same
components as XAMPP, it makes transitioning from a local test server to a live server
extremely easy as well.

4.2 Testing

Exhaustive testing for the project is not possible. Some testing strategies and stage
designed manually. For this project Black box and White box testing are chosen. This two
type testing applied different part of the project.

21
4.1.1 Black Box Testing

Black Box Testing, also known as Behavioral Testing, is a software testing method in which
the internal structure/ design/ implementation of the item being tested is not known to the
tester.

These tests can be functional or non-functional, though usually functional. This

method is named so because the

Software program, in the eyes of the tester, is like a black box; inside which one cannot see.
This method attempts to find errors in the following categories:

• Incorrect or missing functions

• Interface errors

• Errors in data structures or external database access

• Behavior or performance errors

• Initialization and termination errors

4.2.2 White Box Testing

White Box Testing also known as Clear Box Testing, Open Box Testing, Glass Box Testing,
Transparent Box Testing, Code-Based Testing or Structural Testing is a software testing
method in which the internal structure/ design/ implementation of the item being tested is
known to the tester. The tester chooses inputs to exercise paths through the code and
determines the appropriate outputs. Programming know-how and the implementation
knowledge is essential. White box testing is testing beyond the user interface. The white
box testing perform normally in this project different part.

22
 4.3 User Feedback
Topic: Web Based Application for Online Shopping System

This survey is done for a study on ‘Web Based Application for Online Shopping System’ for a
project in M. Sc. in C.S.E. Your answers will be strictly confidential and used only for the
purpose of the project. Thank you for your help.

Participants’ Information

Status: In-service of Web Based Online Shopping System

Name (optional):____________________________

Years of experience__________________________

Please answer the following questions:

1. What is the purpose of the project?

 To tell the product.
 To promote the services.
 To collect email address
 To build a brand/community
2. Use words to describe the outlook of the site
3. Use words to describe the outlook of the site
4. Do you prefer the image of the product?
 Yes
 No

5. DO you prefer the website photos?

6. Is the site useful to you?

User feedback is one of the important part of a product, this survey is done by one of the authority of
the company employee, evaluate the feedback and take initiative to make the system more convenient
to the user as well as it will be a part of great satisfactory of developing the system.

23
 CONCLUSION

5.1 Conclusion

The Internet has become a major resource in modern business, thus online shopping has gained
significance not only from the entrepreneur’s but also from the customers point of view. For
the entrepreneur, online shopping generates a new business opportunities and for the
customer, it makes the comparative shopping possible. A god shopping cart design must be
accompanied with user-friendly shopping cart application logic. It should be convenient for the
customer to view the content s of their cart and to be able to remove or add items to their cart.
The shopping cart application described in this project provides a numbers of features that are
designed to make the customer more comfortable. This project helps in understanding the
creation of an interactive web page and technologies user to implement it. During the course of
the project, we have across the wide variety of problems and difficulties. We have learned the
appropriate intricate working behind the dynamic website, how tricky data manipulation can be
occurred sometimes but we have done everything

Successfully, the system has been designed in response to the system analysis. All possible error
in the program have been eliminated. Necessary validation techniques have been used and
normal, abnormal and extremely data was used to test the system. However, doing this project
has been a good boost to our confidence as the future IT member of our global village.

5.2 Limitation

The software we have developed have some limitation. We are trying to fulfill all requirements.
But some tasks are not done here. Real time services like voice, chatting and video conferencing
are not done here. The system is developed for only cash on delivery as payment method.
PayPal not added just added to show it. Upcoming product will display only website but not
added messaging service that when any product will come will send message to customer
mobile that new product available.

24
5.3 Future Scope

If its limitation can be solved then it would be more effective. In future we will try to develop
our project so that we able to give these facilities and credit card validation is not done. The
administrator of the website can be given more functionality, looking specific customer
generate invoice from admin panel of customer till present for taking decision. Adding SMS
gateway to confirm that customer order successfully submitted, and also the current stats of
order that means any state change of order customer will get a notification.

25