4 Chapters

ONLINE SHOPPING 2018-19
CHAPTER-1
INTRODUCTION
1.1 OBJECTIVE
The Shopping cart is mainly useful for who haven’t time to go to shopping, those are just entered
into this website and bought whatever they want.Even it is night or morning they entered into
this site, and chosen different items like, books, toys etc.
1.2 SCOPE
Once customer entered with his own username and password, at that time automatically one
shopping cart will be created, once user select an item it will add to cart. In case user thinks the
selected item is not useful for me, then deleted that item from shopping cart.Customer selected
some items, but in his credit or debit cart hasn't that much balance, then he was logout from the
website, the selected items are stored at cart with specific users with his allotted carts, after some
days he bought those items then automatically deleted from the cart.
1.2.1DEFINATION
The system after careful analysis has been identified to be presented with the following modules
and roles. The modules involved are: Administrator Moderators Users 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.
Dept. of ISE, YDIT Page 1

1.2.1.1 CATAGORY
This module is divided into different sub-modules. 1. Manage Moderators 2. Manage Products 3.
Manage Users 4. Manage Order 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.
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.

CHAPTER-2
SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
In this chapter, we will discuss and analyze about the developing process of hotel Management
System including software requirement specification (HMS) and comparison between existing
and proposed system . The functional and nonfunctional requirements are included in HMS part
to provide complete description and overview of system requirement before the developing
process is carried out. Besides that, existing vs proposed provides a view of how the proposed
system will be more efficient than the existing one.
2.2 PROPOSED SYSTEM
HOTEL Management System is a computerized system which helps user(receptionist) to manage

the hotels daily activity in electronic format. It reduces the risk of paper work such as file lost,
file damaged and time consuming.It can help user to manage the transaction or record more
effectively and time-saving.
⦁Difficult to search record
When there is no computerized system there is always a difficulty in searching records if the
records are large in number .
⦁Space consuming
After the number of records become large the space for physical storage of file and records also
increases if no computerized system is implemented.
⦁Cost consuming
As there is no computerized system the to add each record paper will be needed which will
increase the cost for the management of library.

CHAPTER-3
SYSTEM REQUIREMENT
3.1 DETAILS OF SOFTWARE
3.1.1 HTML
HTML is used to create and save web document. E.g. Notepad/Notepad++
3.1.2 CSS
(Cascading Style Sheets) Create attractive Layout.
3.1.3 JavaScript
It is a programming language, commonly use with web browsers.
3.1.4 PHP
Hypertext Preprocessor (PHP) is a technology that allows software

developers to create dynamically generated web pages, in HTML, XML, or other document
types, as per client request. PHP is open source software.PHP is a server-side scripting language
designed primarily for web development but also used as a general-purpose programming
language. Originally created by Rasmus Lerdorf in 1994, the PHP reference implementation is
now produced by The PHP Development Team. PHP originally stood for Personal Home Page,
but it now stands for the recursive acronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML or HTML5 markup, or it can be used in combination
with various web template systems, web content management systems and web frameworks.
PHP code is usually processed by a PHP interpreter implemented as a module in the web server
or as a Common Gateway Interface (CGI) executable. The web server software combines the
results of the interpreted and executed PHP code, which may be any type of data, including
images, with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released under the
PHP License. PHP has been widely ported and can be deployed on most web servers on almost
every operating system and platform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014, leaving
the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a
formal PHP specification.

During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7.
The numbering of this version involved some debate. While the PHP 6 Unicode experiment had
never been released, several articles and book titles referenced the PHP 6 name, which might
have caused confusion if a new release were to reuse the name. After a vote, the name PHP 7
was chosen.The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next
generation (phpng). It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov, and
aimed to optimize PHP performance by refactoring the Zend Engine to use more compact data
structures with improved cache locality while retaining near-complete language compatibility.
As of 14 July 2014, WordPress-based benchmarks, which served as the main benchmark suite
for the phpng project, showed an almost 100% increase in performance. Changes from phpng are
also expected to make it easier to improve performance in the future, as more compact data
structures and other changes are seen as be better suited for a successful migration to a just-in-
time (JIT) compiler. [44] Because of the significant changes, the reworked Zend Engine is called
Zend Engine 3, succeeding Zend Engine 2 used in PHP 5. Because of major internal changes in
phpng, it must receive a new major version number of PHP, rather than a minor PHP 5 release,
according to PHP's release process. Major versions of PHP are allowed to break backward-
compatibility of code and therefore PHP 7 presented an opportunity for other improvements
beyond phpng that require backward-compatibility breaks, including wider use of exceptions,
reworking variable syntax to be more consistent and complete, and the deprecation or removal of
various legacy features.PHP 7 also introduced new language features, including return type
declarations for functions which complement the existing parameter type declarations, and
support for the scalar types (integer, float, string, and boolean) in parameter and return type
declarations.
3.1.5 MYSQL
MySql is a database, widely used for accessing querying, updating, and managing data in
databases. MySQL is an open-source relational database management system (RDBMS). Its
name is a combination of "My", the name of co-founder Michael Widenius daughter, and "SQL",
the abbreviation for Structured Query Language. The MySQL development project has made its
source code available under the terms of the GNU General Public License, as well as under a
variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm,
the Swedish company MySQL AB, now owned by Oracle Corporation For proprietary use,
several paid editions are available, and offer additional functionality.

MySQL is a central component of the XAMPP open-source web application software stack (and
other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python".
Applications that use the MySQL database
include: TYPO3, MODx, Joomla, WordPress, phpBB, MyBB, and Drupal. MySQL is also used
in many high-profile, large-scale websites, including Google (though not for searches),
Facebook, Twitter, Flickr, and YouTube.
MySQL is written in C and C++. Its SQL parser is written in yacc, but it uses a home-brewed
lexical analyzer. MySQL works on many system platforms, including AIX, BSDi, FreeBSD, HP-
UX, eComStation, i5/OS, IRIX, Linux, macOS, Microsoft Windows, NetBSD, Novell NetWare,
OpenBSD, OpenSolaris, OS/2 Warp, QNX, Oracle Solaris, Symbian, SunOS, SCO OpenServer,
SCO UnixWare, Sanos and Tru64. A port of MySQL to OpenVMS also exists.
3.2 SYSTEM REQUIREMENTS
3.2.1 HARDWARE CONFIGURATION
⦁ Operating system: Window 10
⦁ Hard disks: 40GB
⦁ RAM: 256 MB
3.2.2 SOFTWARE CONFIGURATION
⦁ HTML, CSS, PHP
⦁ My-SQL server & Apache (Xampp)

CHAPTER-4
SYSTEM DESIGN
4.1 USE CASE DIAGRAM
A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their goals
(represented as use cases), and any dependencies between those use cases. The main purpose of a
use case diagram is to show what system functions are performed for which actor. Roles of the
actors in the system can be depicted. Use Case diagrams are formally included in two modeling
languages defined by the OMG: the Unified Modeling Language (UML) and the Systems
Modeling Language (SysML). Interaction among actors is not shown on the use case diagram. If
this interaction is essential to a coherent description of the desired behavior, perhaps the system
or use case boundaries should be re-examined. Alternatively, interaction among actors can be
part of the assumptions used in the use case.
⦁Use cases
Use case describes a sequence of actions that provide something of measurable value to an actor
and is drawn as a horizontal ellipse.
⦁Actors
An actor is a person, organization, or external system that plays a role in one or more interactions
with the system.
⦁System boundary boxes (optional)
⦁A rectangle is drawn around the use cases, called the system boundary box, to indicate the
scope of system. Anything within the box represents functionality that is in scope and anything
outside the box is not.

FIG 1. USERCASE DIAGRAM FOR ONLINE SHOPPING
4.2 ER DIAGRAM
What is an Entity Relationship Diagram (ERD)?
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate the
logical structure of databases.At first glance an entity relationship diagram looks very much like
a flowchart. It is the specialized symbols, and the meanings of those symbols, that make it
unique.
ER Diagram Uses
When documenting a system or process, looking at the system in multiple ways increases the
understanding of that system. ERD diagrams are commonly used in conjunction with a data flow

diagram to display the contents of a data store. They help us to visualize how data is connected
in a general way, and are particularly useful for constructing a relational database.
FIG 2. ER DIAGRAM FOR HOSTEL MANAGEMENT SYSTEM

4.3 RELATIONAL DATABASE DESIGN

4.3.1 CATEGORY
Cat_id Cat_dis Cat_ name Creation_date Updation_date
4.3.2 ORDERS
order_id cust_name track_details Remarks sContact
4.3.3 PRODUCT VIEWS
Product _id Quality Price Summary review date
4.3.4 PRODUCTS
Pro_id pro_name category sub_category Price Discount availability
4.3.5 TRIGGER TABLE
Booking id cust_ name Product_id order_status
4.3.6 USER TABLE
id username name password email active code

4.4 DATABASE NORMALIZATION

4.4.1 FIRST NORMAL FORM
The relation is in 1NF if it has no repeating groups.All tables has no repeating groups as they are
in 1NF.
4.3.1 CATEGORY
4.3.2 ORDERS
4.3.3 PRODUCT VIEWS
4.3.4 PRODUCTS
4.3.5 TRIGGER TABLE
4.3.6 USER TABLE

4.4.2 SECOND NORMAL FORM:

A relation is in second normal form if it is already in first normal form and it has no partial
dependency.
1.CATEGORY:
The absence of partial dependency in relation takes it into 2NF without any modification.
2.ORDERS:
3.PRODUCT REVIEW:
4.TRIGGER:
No partial dependenCies.
5.USER TABLE:
Tables:
4.3.1 CATEGORY
4.3.2 ORDERS
4.3.3 PRODUCT VIEWS

4.3.4 PRODUCTS
4.3.5 TRIGGER TABLE
4.3.6 USER TABLE
4.4.3 THIRD NORMAL FORM:

A relation is said to be in third normal form if it is already in first and second normal form and
has no transitive dependency.
1.CATEGORY:
In adopter depends upon category id name with another table so it is in third normal form.
2.ORDERS:
In animal depends upon order id with another table so it is in third normal form.
3.PRODUCT REVIEW:
In every attribute depends on primary key i.e.product id. so it is in third normal form.
5.TRIGGER TABLE:
In trigger every attribute depends on primary key i.e.id so it is in third normal form.
6.USER:
In user every attribute depends on primary key i.e. id so it is in third normal form.
Tables:
4.3.1 CATEGORY

4.3.2 ORDERS
4.3.3 PRODUCT VIEWS
4.3.4 PRODUCTS
4.3.5 TRIGGER TABLE
4.3.6 USER TABLE

CHAPTER-5
SYSTEM IMPLEMENTATION
5.1 MODULE DESCRIPTION

5.1.1 ADMIN MODULE
When email and password provided by the administrator are correct, the php file named
“login_admins.php” will send the request to the database server which will check the
information, if everything is correct, it will redirect the administrator to the “login_success.php”
file. On this page the administrator will be able to insert, add, edit, delete, and update products
information. He will be able to view, edit, and update customers’ information. He will be able to
view orders and view customers’ payments. The administrator will be able to process the orders
made by customers. By confirming the orders, a customer will be able to get the products
ordered.
Any user can search products and add also add products to the cart but need to register before
checking out. For that we have the registration page form. Through the form, the user will fill the
fields with his/her personal information. After that he will click on the button “Register”. There
is a PHP file called “customer_registration.php” that will process all the data before sending it to
the database (table “Customers”).

5.1.2 VIEW MODULE

In this module, the whole database can be viewed. The details are fetched directly from backend
(Mysql) and displayed on the front end (website).
5.1.3 INSERTION MODULE

Here admin as a user will be inserting the details with respect to customers, products and
bookings process. This uses the frontend and is dynamically inserted in the backend

CHAPTER-6
SYSTEM TESTING
TEST CASES
6.1 LOGIN
No Test cases Case Type Expected ResultActual Result Pass/Fail
1 1 Login Website 1Correct Username and Successful login Successful Pass

Password
2.Login with wrong Login Stayed in Pass
Username and Password unsuccessful index.php
2 Validation Test Required field validation Field should not beUser have to enter Pass
case empty the value
TABLE 6.2
UPLOAD DATA IN DATABASE
No Test cases Case Type Expected Result Actual Result Pass/Fail

1 1 Upload Data 1.Insert Query Executed Successful Upload Successful Pass
1 2.Insert wrong Query Unsuccessful Upload Successful Pass
TABLE 6.3
VIEW DATA OF DATABASE
No Test cases Case Type Expected Result Actual Result Pass/Fail

1 1View Data SelectQuery Executed Successful Successful Pass
Select wrong Query Unsuccessful Display Successful Pass
Executed

TABLE 6.4
UPDATE DATA OF DATABASE
No Test cases Case Type Expected Result Actual Pass/Fail

Result
Update 1.UpdateQuery Successfully Updated Successful Pass
1 Data Executed
2.UpdatewrongQuery Unsuccessfully Successful Pass
Executed Updated
TABLE 6.5
DELETE DATA OF DATABASE
No Test cases Case Type Expected Result Actual Pass/Fail

Result
1 Delete 1.Delete Query Executed Successfully Deleted Successful Pass
1 Data
2.Delete wrong QueryUnsuccessfully Successful Pass
Executed Deleted

CHAPTER-7
RESULTS
ADMIN LOGIN
SNAPSHOT 01

ADMIN USERS LOG
SNAPSHOT 02

ADMIN MANAGE USERS
SNAPSHOT 03

CREATE CATEGORY
SNAPSHOT 04

SUB CATEGORY
SNAPSHOT 05

ADMIN MANAGE PRODUCTS
SNAPSHOT 6

4 Chapters

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

4 Chapters

Transféré par

Droits d'auteur :

Formats disponibles

ONLINE SHOPPING 2018-19

Dept. of ISE, YDIT Page 1

Dept. of ISE, YDIT Page 2

2.2 PROPOSED SYSTEM

HOTEL Management System is a computerized system which helps user(receptionist) to manage

⦁Difficult to search record

Dept. of ISE, YDIT Page 3

HTML is used to create and save web document. E.g. Notepad/Notepad++

(Cascading Style Sheets) Create attractive Layout.

It is a programming language, commonly use with web browsers.

Hypertext Preprocessor (PHP) is a technology that allows software

Dept. of ISE, YDIT Page 4

Dept. of ISE, YDIT Page 5

3.2 SYSTEM REQUIREMENTS

3.2.1 HARDWARE CONFIGURATION

⦁ Operating system: Window 10

⦁ Hard disks: 40GB

3.2.2 SOFTWARE CONFIGURATION

⦁ HTML, CSS, PHP

⦁ My-SQL server & Apache (Xampp)

Dept. of ISE, YDIT Page 6

A use case diagram in the Unified Modeling Language (UML) is a type of

⦁System boundary boxes (optional)

Dept. of ISE, YDIT Page 7

FIG 1. USERCASE DIAGRAM FOR ONLINE SHOPPING

What is an Entity Relationship Diagram (ERD)?

Dept. of ISE, YDIT Page 8

FIG 2. ER DIAGRAM FOR HOSTEL MANAGEMENT SYSTEM

Dept. of ISE, YDIT Page 9

4.3 RELATIONAL DATABASE DESIGN

Cat_id Cat_dis Cat_ name Creation_date Updation_date

order_id cust_name track_details Remarks sContact

4.3.3 PRODUCT VIEWS

Product _id Quality Price Summary review date

Pro_id pro_name category sub_category Price Discount availability

4.3.5 TRIGGER TABLE

Booking id cust_ name Product_id order_status

4.3.6 USER TABLE

id username name password email active code

Dept. of ISE, YDIT Page 10

4.4 DATABASE NORMALIZATION

Cat_id Cat_dis Cat_ name Creation_date Updation_date

order_id cust_name track_details Remarks sContact

4.3.3 PRODUCT VIEWS

Product _id Quality Price Summary review date

Pro_id pro_name category sub_category Price Discount availability

4.3.5 TRIGGER TABLE

Booking id cust_ name Product_id order_status

4.3.6 USER TABLE

id username name password email active code

Dept. of ISE, YDIT Page 11

4.4.2 SECOND NORMAL FORM:

Cat_id Cat_dis Cat_ name Creation_date Updation_date

order_id cust_name track_details Remarks sContact

4.3.3 PRODUCT VIEWS

Product _id Quality Price Summary review date

Dept. of ISE, YDIT Page 12

Pro_id pro_name category sub_category Price Discount availability

4.3.5 TRIGGER TABLE

Booking id cust_ name Product_id order_status

4.3.6 USER TABLE

id username name password email active code