i

DECLARATION

We, KALALA KABANTU Aristote and BAVANGE TABARO Jean-Claude, we

sincerely declare that this work entitled ‘’ online shopping system ‘’ submitted in
a partial fulfilment required for the achievement of the bachelor’s degree in
computer science at Kigali Independent University (ULK) GISENYI COMPUS
during the academic year 2018-2019, is a record of our original real work.

Date ....../......../.................... Date ........./........... /........

Signature............................ Signature.............................

KALALA KABANTU ARISTOTE BAVANGE TABARO JEAN-CLAUDE

Roll Number: 201620035 Roll Number: 201620056

 ii

APPROVAL

This is a work submitted by KALALA KABANTU Aristote and BAVANGE TABARO

Jean-Claude in partial fulfilment of the requirement for the award of a bachelor’s
degree in computer science at Kigali Independent University (ULK) Gisenyi
campus during the academic year 2018-2019

Date........../........./.............

Signature

Supervisor

NZAYISENGA HABARUGIRA Marcellin

 iii

AKONOWLEDGEMENT

First of all, we sincerely thank the almighty God who protected us and guided
us until we are done with this work, we have taken efforts in this project.
However, it would not have been possible without the kind support and help of
many individuals and organizations. we would like to extend our sincere thanks
to all of them;

We are highly indebted to our supervisor NZAYISENGA HABARUGIRA

Marcellin for their guidance and constant supervision as well as for providing
necessary information regarding the project & also for their support in
completing the project;

We would like to express our gratitude towards our parents for their kind co-
operation and encouragement which help us in completion of this project, also
to express our special gratitude and thanks to industry persons for giving me
such attention and time;

Our thanks and appreciations also go to our colleague in developing the project
and people who have willingly helped us out with their abilities.
 iv

ABSTRACT

The business-to-consumer aspect of product commerce (e-commerce) is the most

visible business use of the World Wide Web. The primary goal of an e-commerce
site is to sell goods online;

This project deals with developing an e-commerce website for Online Product
Sale. It provides the user with a catalog of different product available for
purchase in the store. In order to facilitate online purchase a shopping cart is
provided to the user. The system is implemented using a 3-tier approach, with a
backend database, a middle tier of Microsoft Internet Information Services (IIS)
and PHP, and a web browser as the front end client. In order to develop an e-
commerce website, a number of Technologies must be studied and understood;

These include multi-tiered architecture, server and client side scripting

techniques, implementation technologies such as PHP(OOP), JQUERY,
BOOTSTRAP, HTML5, relational databases (such as MySQLi, Access). This is a
project with the objective to develop a basic website where a consumer is
provided with a shopping cart application and also to know about the
technologies used to develop such an application. This document will discuss
each of the underlying technologies to create and implement an e-commerce
website.
 v

Contents
CHAPTER I. GENERAL INTRODUCTION .................................................................................... 1
1.1. Background of Study ..................................................................................................... 1
1.1.1. Introduction .............................................................................................................. 1
1.1.2. Problem Statement ................................................................................................. 2
1.1.3. Hypothesis ................................................................................................................. 2
1.2. Objective of the Project ................................................................................................ 4
1.2.1. General Objective .................................................................................................... 4
1.2.2. Specific Objective ................................................................................................... 4
1.3. CHOICE AND INTEREST OF THE STUDY .............................................................. 4
1.3.1. Choice of the study ................................................................................................ 4
1.3.2. Interest of the study .............................................................................................. 5
1.4. Scope of the project ....................................................................................................... 5
1.5. Research Methodology .................................................................................................. 6
1.5.1. Data collection technique.................................................................................... 6
1.5.2. Software development methodology ............................................................... 6
Gant chart .......................................................................................................................................... 7
1.4. Organization of the study ............................................................................................ 8
CHAPTER II LITERATURE REVIEW............................................................................................. 9
2.1 INTRODUCTION ................................................................................................................... 9
2.2 BASIC CONCEPTS ........................................................................................................... 9
2.3 DATABASE CONCEPTS................................................................................................ 10
2.4 DATA MODELING........................................................................................................... 10
2.5 DATABASE IN NETWORK ENVIRONMENT .......................................................... 12
2.6 TOOLS, TECHNIQUES AND PROGRAMMING LANGUAGE ............................. 13
2.7 THE MODILE MONEY PAYMENT SYSTEM .......................................................... 15
2.8 SOME WEB APPLICATION ATACKS ....................................................................... 15
2.8 SOFTWARE DEVELOPMENT PROCESS MODELS ............................................. 16
2.9 SUMMARY ......................................................................................................................... 23
CHAPTER III. SYSTEM ANALYSIS AND DESIGN .................................................................. 24
3.1. INTRODUCTION ............................................................................................................. 24
3.2. DESCRIPTION OF THE EXISTING SYSTEM ........................................................ 24
 vi

3.2.1. Introduction of Existing System .................................................................... 24

3.2.2. Problem of the current system ........................................................................ 25
3.3. ANALYSIS OF THE PROPOSED SYSTEM ............................................................. 26
3.3.1. Introduction ............................................................................................................ 26
3.3.2. Methodological approach ................................................................................... 28
3.3.3. Data collection techniques ............................................................................... 28
3.3.4. Software development process model .......................................................... 28
3.3.5. Requirements of proposed system ................................................................. 29
3.3.6. Description............................................................................................................... 32
3.3.7. Feasibility study: ................................................................................................... 32
3.4. DESIGN OF NEW SYSTEM .......................................................................................... 33
In order to design the new system, we will deal with the function diagram, context-
diagram, data flow diagram level 1 and entity relationship diagram. Here the
structures of the described diagrams. ...................................................................................... 33
3.4.1. Function Diagram ................................................................................................. 33
A function diagram in software engineering is a block diagram that describes the
functions and interrelations of a system. ............................................................................ 33
3.4.2. Dataflow diagram................................................................................................... 33
A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modeling its process aspects. A DFD shows what
kind of information will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. ....................................... 33
3.4.3. Entity relationship diagram (ERD) ................................................................. 35
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. ER diagrams often use symbols
to represent three different types of information. Boxes are commonly used to
represent entities. Diamonds are normally used to represent relationships and
ovals are used to represent attributes .................................................................................. 35
3.4.4. Data dictionary ...................................................................................................... 38
A data dictionary is a set of information describing the contents, format, and
structure of a database and the relationship between its elements, used to control
access to and manipulation of the database. ..................................................................... 38
CHAPTER IV. SYSTEM IMPLEMENTATION ............................................................................ 41
3.5. INTERFACES OF THE SYSTEM ............................................................................... 41
3.6. The administration interfaces ................................................................................. 50
CHAPTER V Conclusion and Recommendations ................................................................. 58
 vii

Conclusion ........................................................................................................................................... 58
RECOMMENDATIONS ...................................................................................................................... 59
 viii

LIST OF FIGURES

Figure 1: client server architecture ............................................................................................... 12

Figure 2waterfall model..................................................................................................................... 17
Figure 3prototyping ............................................................................................................................ 19
Figure 4 Iterative model .................................................................................................................... 21
Figure 5 timeboxing model ............................................................................................................... 22
Figure 6 agile model ........................................................................................................................... 23
Figure 7 proposed system figure .................................................................................................... 27
Figure 8 shows a data flow diagram about the system ........................................................... 34
Figure 9 shows a data flow diagram about the system.1 ....................................................... 34
Figure 10 shows a data flow diagram about the system2 ...................................................... 35
Figure 11 entity-relationship (ER) diagram .................................... Error! Bookmark not defined.
Figure 12 database relationship ..................................................................................................... 37
Figure 13 home page.......................................................................................................................... 41
Figure 14 search product by its category .................................................................................... 42
Figure 15 search product by typing its name ............................................................................ 43
Figure 16 most viewed today ........................................................................................................... 44
Figure 17 add to cart ......................................................................................................................... 45
Figure 18 view cart ............................................................................................................................. 46
Figure 19 cart....................................................................................................................................... 47
Figure 20 user and admin login ..................................................................................................... 48
Figure 21 user registration .............................................................................................................. 49
Figure 22 Customer profile .............................................................................................................. 50
Figure 23 admin home page ............................................................................................................ 51
Figure 24 management of products .............................................................................................. 52
Figure 25 management of users ..................................................................................................... 53
Figure 26 management of category ............................................................................................... 54
Figure 27 sales pages ........................................................................................................................ 55
Figure 28 transaction details .......................................................................................................... 56
Figure 29 admin profil ....................................................................................................................... 57
 ix

LIST OF TABLES

Table 1 Data dictionary (cart) .......................................................................................................... 38

Table 2 Data dictionary (category) ................................................................................................. 38
Table 3 Data dictionary (details)..................................................................................................... 39
Table 4 Data dictionary (products) ................................................................................................ 39
Table 5 Data dictionary (sales) ........................................................................................................ 40
Table 6 Data dictionary (users) ....................................................................................................... 40
 x

LIST OF ABREVIATIONS

API: Application programming interface

CSS: Cascading style sheet

DB: Database

DBMS: Database management system

DFD: Dataflow diagram

E-Commerce: Electronic commerce

ERD: Entity-Relationship Diagram

HTML: Hypertext Mark-up Language

HTTP: Hypertext Transfer Protocol

MVC: Model View Controller

MVT: Model View Template

MYSQL: My Structural Query Language

RDBMS: Relational Database Management System

SSADM: Structured Systems Analysis and Design Method

SQL: Structured Query Language

ULK: Kigali Independent University

WWW: World Wide Web

 1

CHAPTER I. GENERAL INTRODUCTION

1.1. Background of Study

1.1.1.Introduction
Online shopping is the process whereby consumers directly buy goods, services
etc. from a seller interactively in real-time without an intermediary service over
the internet.

Online shopping is the process of buying goods and services from merchants
who sell on the Internet. Since the emergence of the World Wide Web, merchants
have sought to sell their products to people who surf the Internet. Shoppers can
visit web stores from the comfort of their homes and shop as they sit in front of
the computer. Consumers buy a variety of items from online stores. In fact,
people can purchase just about anything from companies that provide their
products online. Books, clothing, household appliances, toys, hardware,
software, and health insurance are just some of the hundreds of products
consumers can buy from an online store.

Many people choose to conduct shopping online because of the convenience.

For example, when a person shops at a brick-and-mortar store, she has to drive
to the store, find a parking place, and walk throughout the store until she locates
the products she needs. After finding the items she wants to purchase, she may
often need to stand in long lines at the cash register.

Say 'goodbye' to the days when you stood in line waiting, and waiting, and
waiting some more for a store clerk to finally check out your items. Online
shopping transactions occur instantly-saving you time to get your other errands
done! Additionally, unlike a store, online shopping has friendly customer service
representatives available 24 hours a day, 7 days a week to assist you with
locating, purchasing and shipping your merchandise.
 2

1.1.2.Problem Statement
E-commerce provides an easy way to sell products to a large customer base.
There are large numbers of commercial Online Shopping websites offering large
number of products tailored to meet the shopping interests of large number of
customers. These online marketplaces have thousands of products listed under
various categories.

The following problem is found:

 When users go to the market site, they expect to find what they are
looking for quickly and easily.
 Users are not sure about the brands or the actual products they want to
purchase.
 Many customers nowadays search for their products on Google rather
than visiting specific e-commerce sites; They believe that Google will take
them to the e-commerce sites that have their product.
 The basic problems with the existing systems are the non-interactive
environment they provide to the users;
 The use of traditional user interfaces which make continuous post backs
to the server; each post back makes a call to the server, gets the response
and then refreshes the entire web form to display the result. This scenario
adds an extra trade off causing a delay in displaying the results;
 A search engine that would display the results without allowing the users
to further filter the results based on various parameters;
 Use of traditional and non-user friendly interfaces that are hard to use.

1.1.3.Hypothesis
The hypothesis is a particular proposition does not require a system of
experimentation whose purpose is the truth. In this acceptance, Hypothesis is
an idea director or an attempt to explain the facts formulated at the beginning
of the research. It can be invalidated or confirmed by the results of the research.
(Wikipedia 2007)
 3

When looking at this definition, we can tell you that this is the whole answer of
our anticipations to the questions of departure. The following hypothesis is
formulated as a provisional answer to the questions posed in the problematic:

Any member can register and view available products.

Only registered member can purchase multiple products regardless of
quantity.
There are four roles available:
 Visitor
 User
 Operator
 Admin.
Visitor can view, search available products.
User can view and purchase products.
Operator can excess add option and can view everything of admin panel.
 Operator can add product, edit product, update and remove
product.
 Can access users some information.
 Operator can ship order to user based on order placed by sending
confirmation mail.
An Admin has some extra privilege including all privilege of visitor and
user.
 Admin can add products, edit product information and
add/remove product.
 Admin can add user, edit user information and can remove user.

The product will be developed completely independent and dynamic website.

Customer must have an account to purchase the product. This application
stores all the information in the database which can be retrieved whenever
needed and all the validations are performed during the entry of the data by the
 4

user thus ensuring that the user cannot enter any wrong data which could
cause problem later.

1.2. Objective of the Project

1.2.1.General Objective
The main purpose of this study is to automate the manual procedures of
searching articles by providing a comprehensive computerized system, which
can capture, collate and analyze the data and evaluate the impact of the
program, the system would be easy to use and hence make the shopping
experience pleasant for the users.

1.2.2.Specific Objective
In order to achieve the main objective, we have the following specific objectives:

i) Admin user privileges in updating and canceling payment, goods

records.
ii) In comparison to the present system the proposed system will be less
time consuming and is more efficient.
iii) Analysis will be very easy in proposed system as it is automated.
iv) The proposed system is very secure as no chances of loss of data as it
is dependent on the administrator only to add and delete goods.
v) In this new system, customers can search for products, view a complete
description of the products and order the products.

1.3. CHOICE AND INTEREST OF THE STUDY

1.3.1.Choice of the study
The choice of this project result from the interest we have in the development of
the online ecommerce system. Especially when we consider the advantage of the
business in daily life, we find that it’s better to create a distributed system that
will be used by customers so that to get the quick service.
 5

1.3.2.Interest of the study

This study has the personal interest, academic, scientific and social interests.

a. Personal interest
The study design and implementation of this system will help us to improve the
web development skills and use them for real word problem solving, provide
solution to the practical problems using knowledge gained from the particular
class of web design and system management databases in our level of study and
finally understanding better how computerized system work.

b. Scientific interest
This work will serve as reference for other researchers who will be motivated by
the desire to deepen this area and allow others to open the area of research.
Therefore, in order to meet the scientific requirements, the researcher was able
to make comparison between theoretical concepts of research topic and practical
work by preparing a research work on online commerce in Democratic Republic
of Congo.

c. Social interest
This work will help people to have opportunity to search and order goods they
want at any time because the system will be available anytime; This system will
help seller company to easily manage customers’ demand as the record will be
automatically generated.

1.4. Scope of the project

Scope in time: Our work finds its limit on the automation of an online shopping
during a period of 2019 when there was a problem of a system that was paper
based.

Scope in space: boutique Yarazake located in Goma town quarter ‘les volcans’

Scope in domain: This project is limited in the following boundary:

 Online shopping service

 Provide sales information for customers
 6

1.5. Research Methodology

The development of such a kind of system needs data collection techniques and
methodology

1.5.1.Data collection technique

a. Documentation technique
For the development of this system on the side of documentation method for data
collection, the text document and books will be used to carry out information
needed to achieve the goal.

b. Observation technique
Before the development of this system, the observation method will be used to
carry out information and data.

So, we will go and observe how the current system works and what are the
problems to be solved by the new system.

c. Interview technique
This technique involves exchange of ideas between the interviewer and the
interviewee. The interview has been a suitable technique especially for those
respondents who had limited time because of their rushing hours or managerial
responsibilities. In this regard, the researcher selected a set of the most
important questions to be asked and record at the same time the responses
during the interview. It enabled the researcher to obtain first hand and accurate
information since he could obtain non-verbal expressions.

1.5.2.Software development methodology

The development process adopted by the team is a waterfall model. The waterfall
model proceeds from one phase to the next in a sequential manner. First we
complete requirements specification based on our analysis. We then plan on
exactly what has to be achieved at the end of the project. We then proceed to the
design phase where we determine how the goals set for there going to be met and
how the deliverables are going to be achieved. This will be done by making a
blueprint for the design phase to help the group members have a fair idea of
 7

what is expected of the system and what should be included in it and what
should not. (Synopsys Editorial Team, 2017)

Gant chart
 8

1.4. Organization of the study

The chapters are organized as follows;

The first chapter General introduction: covers the background to the study,
problem statement, research objectives and questions, relevance of the study as
well as the scope and limitation of the study,

The second chapter Literature review: In this chapter we will covers theories
and the literature related to the topic by selecting the appropriate measurement
that will help to solve the problem and this will help to anticipate the most
common problems to avoid repetition of same mistakes which other researchers
did before; It covers theories and the literature related to the topic,

The third chapter System analysis and design: this chapter deals with the
logical conception of the system; this covers the conceptually process of the
solutions proposed to solve problems of the existing system. And we also analyze
the existing environment and search for opportunity to improve the new system,

The fourth chapter System implementation: In this chapter we will be

implementing the system and describe the architecture of the online commerce
system in deep,

The last one is Conclusion and recommendation: this chapter will outline the
summary, conclusion and recommendations of the study.
 9

CHAPTER II LITERATURE REVIEW

2.1 INTRODUCTION
This chapter contains explanations of the basic information system concepts
useful for the developer or user before it is developed. it has the aim of giving
brief descriptions about the terms to be used during the development of the work.

2.2 BASIC CONCEPTS

2.2.1 Online

Is the condition of being connected to a network of computers or other devices.

The term is frequently used to describe someone who is currently connected to
the Internet. (MARGUERET ROUSE, 2007)

2.2.2 Commerce

is the conduct of trade among economic agents. Generally, commerce refers to

the exchange of goods, services or something of value, between businesses or
entities. From a broad perspective, nations are concerned with managing
commerce in a way that enhances the well-being of citizens, by providing jobs
and producing beneficial goods and services. (www.investopedia.com,2019)

2.2.3 E-commerce

E-commerce describes any business or commercial transaction that includes the

transfer of financial information over the Internet. E-commerce, unlike
traditional commerce between two agents, allows individual consumers to
exchange value for goods and services with little to no barriers.
(www.investopedia.com,2019)

2.2.4 Shopping

is an activity in which a customer browses the available goods or services

presented by one or more retailers with the potential intent to purchase a
suitable selection of them. (www.merriam-webster.com,2009)
 10

2.3 DATABASE CONCEPTS

2.3.1 Data

Can be defined as facts and statistics collected together for reference or analysis.
(www.dictionary.com,2008)

2.3.2 Database

Is a collection of information that is organized so that it can be easily accessed,

managed and updated. (www. academic.oup.com,2013)

2.3.3 Table

A database table is where all the data in a database is stored, and without tables,
there would not be much use for relational databases. (Wenzel, (225-5704-00L),
ETH Zürich, 2014)

2.3.4 Database management system (DBMS)

Is system software for creating and managing databases. The DBMS provides
users and programmers with a systematic way to create, retrieve, update and
manage data. (Silberschatz, Korth. Sudarshan, 2010)

2.3.5 Records

In database management systems, a record is a complete set of information.

Records are composed of field, each of which contains one item of information.
(Beal, 2018)

2.3.6 Field

Is an area in a fixed or known location in a unit of data such as a record, message

header, or computer instruction that has a purpose and usually a fixed size.
(Rouse, definition, 2005)

2.4 DATA MODELING

Data modeling is the process of creating a data model for the data to be stored
in a Database. (www. academic.oup.com,2013)
 11

2.4.1 Attributes

Each row is a data set that applies to a single item. Each column (attribute)
contains describing characteristics of the rows. A database attribute is a column
name and the content of the fields under it in a table in a database. (Chapple,
2018)

2.4.2 Keys

is a field, or combination of fields, in a database table used to retrieve and sort

rows in the table based on certain requirements. Keys are defined to speed up
access to data and, in many cases, to create links between different tables.

2.4.3 Foreign key

Is a field (or collection of fields) in one table that refers to the primary key in
another table. A foreign key is used to link two tables.(www.w3schools.com,
2009)

2.4.4 Primary key

Is a unique identifier for a database record. (www.w3schools.com, 2009)

2.4.5 Relational database

Is a database that treats all its data as collection of relations (Robbins, 1995)

2.4.6 Entity

Is any object in the system that we want to model and store information about.
Entities are usually recognizable concepts, either concrete or abstract, such as
person, places, things, or events which have relevance to the database.
(www.sqa.org.uk, 2007)
 12

2.5 DATABASE IN NETWORK ENVIRONMENT

2.5.1 Server

Is a computer that provides data to other computers.

(www.searchdatamanagement.techtarget.com,2015)

2.5.2 Client

Is a piece of computer hardware or software that accesses a service made

available by a server. (www.searchdatamanagement.techtarget.com,2015)

2.5.3 client- server architecture

Is a computing model in which the server hosts, delivers and manages most of
the resources and devices to be consumed by the client.

(www.searchdatamanagement.techtarget.com,2015)

Source: www.cio-wiki.org

Figure 1: Client server architecture

 13

2.5.4 Web server

Is a system that delivers content or services to end users over the internet. A web
server consists of a physical server, server operating system (OS) and software
used to facilitate HTTP communication. (www.guru99.com)

2.6 TOOLS, TECHNIQUES AND PROGRAMMING LANGUAGE

2.6.a. 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 language (www.wikipedia.com, 2018)

2.6.b. MySQL

Is a relational database management system. It does store data in separate table

rather than putting all the data in one big storeroom. ( www.mysql.com)

2.6.c. HTML (Hypertext Markup Language)

Is the standard markup language for creating web pages and web applications.
With Cascading Style Sheets (CSS) and JavaScript, it forms a triad of cornerstone
technologies for the World Wide Web (www.wikipedia.com, 2018)

2.6.d. CSS (Cascading Style Sheets)

It describes how HTML elements are to be displayed on screen, paper, or in other

media. (www.wikipedia.com, 2018)

2.6.e. JavaScript (often abbreviated as JS)

Is a high-level, interpreted programming language. It is a language which is also

characterized as dynamic, weakly typed, prototype-based and
multiparadigm.(www.wikipedia.com, 2018)
 14

2.6.f. Django framework

Django is a free and open source web application framework, written in Python.
It follows the MVC pattern closely; however, it does use its own logic in the
implementation. Because the “C” is handled by the framework itself and most of
the excitement in Django happens in models, templates and views, Django is
often referred to as an MTV framework. In the MTV development pattern:

 M stands for “Model,” the data access layer. This layer contains anything
and everything about the data: how to access it, how to validate it, which
behaviors it has, and the relationships between the data. We will be
looking closely at Django’s models in Chapter 4.
 T stands for “Template,” the presentation layer. This layer contains
presentation related decisions: how something should be displayed on a
Web page or other type of document.
 V stands for “View,” the business logic layer. This layer contains the logic
that accesses the model and defers to the appropriate template(s). You can
think of it as the bridge between models and templates. (djangobook.com,
2018)

2.6.g. Framework

A software framework is a universal, reusable software environment that

provides particular functionality as part of a larger software platform to facilitate
development of software applications, products and solutions.” (Shinde, 2017)

2.6.h. Structured Query Language (SQL)

SQL is a standard language for accessing and manipulating databases which

stands for stands for Structured Query Language. (www.mysql.com)

2.6.i. Bootstrap

Bootstrap is front-end web framework which includes HTML and CSS based
design templates for easier development. (www.getbootstrap.com)
 15

2.6.j. MVC

In object-oriented programming development, model-view-controller (MVC) is the

name of a methodology or design pattern for successfully and efficiently relating
the user interface to underlying data models. it has the following components:

 Model, which represents the underlying, logical structure of data in a

software application and the high-level class associated with it. This object
model does not contain any information about the user interface.
 View, which is a collection of classes representing the elements in the user
interface (all of the things the user can see and respond to on the screen,
such as buttons, display boxes, and so forth)
 Controller, which represents the classes connecting the model and the
view, and is used to communicate between classes in the model and view
(Rouse, definition, 2013)

2.7 THE MODILE MONEY PAYMENT SYSTEM

MTN Mobile Money Online is an innovative way to send money from abroad to
someone in Rwanda. The money is sent directly in to the receiver’s Mobile phone,
to the Mobile Money Account, and can then be used in various ways. (mtn.co.rw,
2018)

2.8 SOME WEB APPLICATION ATACKS

We can end up this section without showing some problems that the website can
encounter and some attacks to which the website is exposed.

2.8.1 Credentials Management

A credentials management attack attempts to breach username/password pairs

and take control of user accounts.( www.thalesesecurity.com)
 16

2.7.2 CRLF Injection

CRLF Injection attacks refer to the special character elements "Carriage Return"
and "Line Feed." Exploits occur when an attacker is able to inject a CRLF
sequence into an HTTP stream. (veracode.com, 2018)

2.7.3 Cross-Site Request Forgery

Cross-Site Request Forgery (CSRF) is a malicious attack that tricks the user’s
web browser to perform undesired actions so that they appear as if an authorized
user is performing those actions. (veracode.com, 2018)

2.7.4 Cross-Site Scripting

XSS vulnerabilities target scripts embedded in a page that are executed on the
client-side (in the user’s web browser) rather than on the server-side.
(veracode.com, 2018)

2.7.5 Format String

Format String attacks occur when an application interprets data as a command

and allows an attacker to access the underlying code base. (veracode.com, 2018)

2.7.6 SQL Injection

SQL injection is a type of web application security vulnerability in which an

attacker is able to submit a database SQL command, which is executed by a web
application, exposing the backend database. (veracode.com, 2018)

2.8 SOFTWARE DEVELOPMENT PROCESS MODELS

Software development process models are various processes selected for the
development of the project depending on the projects goals.

In software development process we distinguish the following process models:

1. waterfall
2. prototyping model
3. iterative development model
 17

4. time boxing model

5. agile model

(extremeprogramming.org, 1999)

2.8.1 Waterfall Model

Waterfall Model consists of a number of dependent phases that are executed in

a sequential order. The complete solution is not released until the final phase.

This is the list of waterfall method process:

 Requirements analysis resulting in a software requirements specification

 Software design
 Implementation
 Testing
 Integration, if there are multiple subsystems
 Deployment (or Installation)
 Maintenance

Figure 2 Waterfall model

Source: www.synopsys.com
 18

The basic principles are:

 Project is divided into sequential phases, with some overlap and splash
back acceptable between phases.
 Emphasis is on planning, time schedules, target dates, budgets and
implementation of an entire system at one time.
 Tight control is maintained over the life of the project via extensive written
documentation, formal reviews, and approval/signoff by the user and
information technology management occurring at the end of most phases
before beginning the next phase. Written documentation is an explicit
deliverable of each phase.

Advantages of waterfall model:

 This model is simple and easy to understand and use.

 It is easy to manage due to the rigidity of the model – each phase has
specific deliverables and a review process.
 In this model phases are processed and completed one at a time. Phases
do not overlap.
 Waterfall model works well for smaller projects where requirements are
very well understood.

Disadvantages of waterfall model:

 Once an application is in the testing stage, it is very difficult to go back

and change something that was not well-thought out in the concept stage.
 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements are at a moderate to high
risk of changing
 19

2.8.2 Prototyping

The Prototyping Model is a systems development method (SDM) in which a

prototype (an early approximation of a final system or product) is built, tested,
and then reworked as necessary until an acceptable prototype is finally achieved
from which the complete system or product can now be developed. This model
works best in scenarios where not all of the project requirements are known in
detail ahead of time. It is an iterative, trial-and-error process that takes place
between the developers and the users. (Rouse, definition, 2005)

There are several steps in the Prototyping Model:

 Requirement gathering: identify whatever requirements are known;

 Outline areas where further definition is mandatory ;
 A quick design;
 Construction of prototype;
 Prototype is evaluated by the customer;
 Requirements are refined, Prototype is tuned to satisfy the needs of
customer

Source: www.tryqa.com

Figure 3 Prototyping
 20

Advantages of Prototyping

 Users are actively involved in the development

 It provides a better system to users, as users have natural tendency to
change their mind in specifying requirements and this method of
developing systems supports this user tendency.
 Since in this methodology a working model of the system is provided, the
users get a better understanding of the system being developed.
 Errors can be detected much earlier as the system is mode side by side.
 Quicker user feedback is available leading to better solutions.

Disadvantages

 Leads to implementing and then repairing way of building systems.

 Practically, this methodology may increase the complexity of the system
as scope of the system may expand beyond original plans. (freetutes, 2018)
2.8.3 Iterative development model

Iterative development is a software development approach that breaks the

process of developing a large application into smaller parts. Each part, called
“iteration”, represents the whole development process and contains planning,
design, development, and testing steps. Unlike the

Waterfall model, the iterative process adds features one-by-one, providing a

working product at the end of each iteration, and increases functionality from
cycle to cycle.
 21

Figure 4 Iterative model

Source: en.wikipedia.org

Advantages of the iterative development

 Iterative software development means building the product step by step,

which allows for the identification and correction of defects during the
early stages, to avoid their downward flow into further processes.
 With iterative development at the end of each stage you can get user
feedback, such as how they see the product now and what they are
expecting it to look like n the future. This allows you to make any
necessary improvements and amendments.
 The iterative development approach helps you to save time on
documentation, which often accompanies the waterfall workflow, and to
focus more on designing the project.
 22

Disadvantages of the iterative development

 Although the whole iterative process is quite flexible, iteration phases are
rigid and have to be followed carefully.
 Unpredictable changes may occur during the iterative development
because not all the requirements are specified from the very beginning of
the project. (easternpeak.com, 2018)
2.8.4 Time boxing model

In time boxing model, development is done iteratively as in the iterative

enhancement model.

Figure 5 timeboxing model

Source: rpl-blog.blogspot.com

Advantages

 Speeds up the development process and shortens the delivery time

 Well suited to develop projects with a number of features in short time
period.

Disadvantages

 Project management becomes more complex.

 23

 Not suited to projects in which entire development work cannot be divided

into multiple iterations of almost, equal duration. (Amachu, 2013)

2.8.5 Agile model (extreme programming)

Extreme Programming (XP) is an agile software development framework that

aims to produce higher quality software, and higher quality of life for the
development team. Dynamically changing software requirements

 Risks caused by fixed time projects using new technology

 Small, co-located extended development team
 The technology you are using allows for automated unit and functional
tests. (extremeprogramming.org, 1999)

Figure 6 Agile model

Source: bmyn.wordpress.com

2.9 SUMMARY
This chapter called literature review is the part in which we reviewed some
theories developed by other researchers in the equivalent topics in order to
improve the user system satisfaction and the system performance. We also
mentioned some tools and techniques to be used in our system to achieve our
goal as said above.
 24

CHAPTER III. SYSTEM ANALYSIS AND DESIGN

3.1. INTRODUCTION
Anyone can view Online Shopping portal and available products, but every user
must login by his/her Username and password in order to purchase or order
products. Unregistered members can register by navigating to registration page.
Only Admin will have access to modify roles, by default developer can only be an
‘Admin’. Once user register site, his default role will be ‘User’.

 The system design phase is the phase in which we and the system users
are consulted to gather and interpret facts and diagnosing the existing
problem and using the found information to propose the improvement on
how the system must work, what are the system futures and what are the
operation that have to appear in the system. So, we will analyze the
organization activities monitoring and come out with solutions to be
accomplished by the system.
 In the system design, we will take the ideas found by the system analysis
to form the template of the new system.

3.2. DESCRIPTION OF THE EXISTING SYSTEM

3.2.1.Introduction of Existing System
The existing system was a manual system. It was found to be inefficient in
meeting the growing demands of population because each customers must buy
product by going to the shop physically

Disadvantage of the existing system:

 Time Consuming
 Expensive
 Needed an agent
 We have to out for that.
 Passenger has to go to the shop counter to buy product
 25

 Existing system is totally on book and those a great amount of manual

work has to be done. The amount of manual work increases exponentially
with increase in services.

3.2.2.Problem of the current system

Here is a list of the current system’s drawbacks that emphasis the need of a new
system.

3.2.2.1. Report generated in the existing system

Current system of product placement, buying product services is manual. The

system asks the responsible workers to provide report. As we have observed and
also interview the system managements the report generating mechanism is
manual that is any kind of report is written on paper by system workers and
then it will be transformed for the manager once in week, month and year. Those
forms used to generate reports in the current system are listed as follows.

 Daily report
 Weekly report
 Monthly report.

3.2.2.2. Performance:

Since the existing system is manual, it takes long response time. For example,
when one customer need to buy a product and to pay money he/she must appear
physically in the place and it takes long time

3.2.2.3. Control and Security

In the existing system, it is difficult to control the system because there is no

privilege in data accessing. Here the necessary reports may not generate at exact
time so it may occur security violence. The system shouldn’t provide sufficient
protection for access and manipulation of the records associated with the
system. So, it is not easily protected and used properly the resource.
 26

 Control over the data is too difficult and it takes long time.
 Input data is not adequately edited.
 Redundantly stored data is inconsistent/unreliable in different files.

3.2.2.4. Efficiency

In manual operation, most of the activities are prone to wastage of resources like
papers, man power, time etc. to produce the corresponding outputs. This makes
the current system inefficient while utilizing resources. There should be a
mechanism that reduce wastage of resources and that make the system to be
efficient. As a result, the new system will reduce wastage of resources and make
it efficient.

3.3. ANALYSIS OF THE PROPOSED SYSTEM

3.3.1.Introduction
The new system is targeted to address the problem of the current system and to
support additional manipulations or features. Our proposed system will
overcome the problems being faced by the manual management system. The
newly proposed system is web based system that the users can access the web
page and can get different services from this website of online bus placement
and ticket reservation (OBPTR) system. The system requires very low system
resources and will work in almost all configurations. It has got following features:

 Passenger can product over the Internet, 24 hours a day, 7 days a week,
 Ensure data accuracy.
 Records are efficiently maintained by DBMS which provides security.
 Any person across the country, having Internet can access this service.
 Minimum time need for the various processing.
 Better Service.
 Minimum time required.
 This would help the corporation prepare and organize its schedules more
efficiently on the basis of traffic demand.
 27

 Providing security
 Low cost
 Basic computer knowledge required
 Configurable and extensible application UI design

The proposed system can be used even by the naïve users and it does not require
any educational level, experience, and technical expertise in computer field but
it will be of good use if the user has the good knowledge of how to operate a
computer.

Enter site

Authenticate
User

Display errors message

Check whether saying to retry
Admin or customer

Customer Admin

View Buy
product product Add, delete,
Add, Add,
delete, Verify
delete,
Check customer
View Check
category product category
s

Figure 7 Proposed system figure

 28

3.3.2.Methodological approach
Methodology is a formal development process that define a set of activities,
methods, practices, deliverables that are used by the developer and project
manager to implement information systems.

i. Structured system analysis and design

Structured systems analysis and design methodology (SSADM) is a set of

standards for systems analysis and application design that uses a formal
methodical approach to the analysis and design of information systems. SSADM
follows the waterfall life cycle model starting from the feasibility study to the
physical design stage of development. One of the main features of SSADM is the
intensive user involvement in the requirements analysis stage. (techopedia,
2017)

3.3.3.Data collection techniques

 Documentation technique

By the documentation technique researcher consulted books, reviews,

memories, class notes and web pages related to this project.

 Observation technique

Using this technique, we visited the company to see and conclude what are the
problems and what happens in the existing system in order to come up with
sufficient data.

3.3.4.Software development process model

Software development process models are various processes selected for the
development of the project depending on the projects goals. Among those
software development process models, we have chosen to use the waterfall
model.
 29

i. The waterfall models

Waterfall Model consists of a number of dependent phases that are executed in

a sequential order. The complete solution is not released until the final phase.

So that is the model that we will use in the design of the new system.

3.3.5.Requirements of proposed system

3.3.5.1. Functional Requirements

Functional requirements describe the interaction between the system and its
environment independent of its implementation.

Administrator:

He is provided with the information of users and products and he can update
the system software to meet the requirements.

User:

 The user can view the details of products by entering URL of the website.
 He should be able to search for a particular product.
 He can just view the details but cannot manipulate them.

Others functional requirement

 The system enables Administrator to create account for clerk.

 The system allows cancelling of the ordered product.
 The system enables user to see detail of each product.
 The details of the product and available are to be maintained and can be
updated regularly (of course only by the admin)
 Also first the user needed to login first in order to perform the buying
actions,
 30

3.3.5.2. Non Functional Requirements

 Usability:

The system should provide an easy-to-use graphical interface so user can easily
learn how they use the system. So, little knowledge on how Web pages can be
accessed is required for user to use. The system should be user friendly so that
users can use it easily without confusion. The web interface should be intuitive
and easily navigable Users should be able to understand the menu and options
provided by the system.

 Reliability:

It can send message, receive message and attach file data or information which
is retrieved from the system is accurate (required) in deserved time.

 Availability:

System will be available around the clock except for the time required for the
backup of data.

 Performance:

The system will be used by multiple users and may grow as time passes.
Necessary measures need to be taken to make the system as fast as possible.

 Performance requirement:

Response time of the System should be minimum. The system should show no
visible deterioration in response time as the number of users or reservation data
increases. The system does not take up too much space in memory to store
system’s data.

 Interface:

Our system describes the logical characteristics of each interface between the
system and the users. This may include any graphical user interface(GUI)
standards or product family style guides, screen layout constraints, standard
 31

buttons and functions that will appear on every screen, error message display
standards, and so on. So our system does these all functions in easy and efficient
way. In other words, the system is user interactive.

 Security and Access permissions:

Only system administer has the right to change system parameters, such as time
change, adding new product and others. The system should be secure and Users
need to be authenticated before having access to any personal data.

 Error handling:

The system will check user inputs to the system to handle error. It handles and
show error by displaying the error message when the user enters invalid input.

 Maintainability:

Should be easily maintainable, easy to upgrade and make adjustments as it is

known, every system needs to be maintained and modified, so we will try to make
the code easily readable and write the comment along with necessary to the
codes.

 Security:

This is vital in the design and expectation of any system. It should contain
mechanism to protect the integrity and avoid changes or access by unauthorized
users. Consideration of the security of the system has a great advantage for this
system, because the database should be secured from the unauthorized users.
Only authorized user can get access to the database. To prevent from the
unauthorized user, the user should have their username and password that help
them to login to the system. Additionally, the users should have to take care of
their own username and password. They should have to keep in a secret manner

 Backup and Recovery:

Backup and recovery requirement: The process of backing up refers to the

copying and archiving of computer data by using removable storage media such
 32

as Disk, CD-R and CD-RW so it may be used to restore the original data after a
data loss event is performed by our system.

 Resources:

The main non-functional resource is: - Server in back end and operating system
in the application of the system. In the other case one of the most and available
resource is internet access.

3.3.6.Description
The system is a web-based application that allows visitors to reserve product,
buy and pay product online or offline. It is developed using PHP Hypertext
Preprocessor (PHP) language that was used for the front- end of the software
while the back end was designed using MySQL

3.3.7.Feasibility study:
A feasibility study is a short, focused study, which aims to answer a number of
questions:

 Does the system contribute to the overall objectives of the organizations?

 Can the system be implemented using current technology and within given
cost and schedule constrains?
 Can the system be integrated with systems which are already in place?
3.3.7.1. Technical Feasibility:
 Is the project feasibility within the limits of current technology?
 Does the technology exist at all?
 Is it available within given resource constraints (i.e., budget, schedule)?

3.3.7.2. Financial Feasibility:

 Is the project possible, given resource constraints?
 Are the benefits that will accrue from the new system worth the costs?
 What are the savings that will result from the system, including tangible
and intangible ones?
 What are the development and operational costs?
 33

3.3.7.3. Operational Feasibility:

Define the urgency of the problem and the acceptability of any solution; if the
system is developed, will it be used? Includes people-oriented and social issues:
internal issues, such as manpower problems, labour objections, manager
resistance, 13 organizational conflicts and policies; also external issues,
including social acceptability, legal aspects and government regulations.

3.4. DESIGN OF NEW SYSTEM

In order to design the new system, we will deal with the function diagram,
context-diagram, data flow diagram level 1 and entity relationship diagram.
Here the structures of the described diagrams.
3.4.1.Function Diagram
A function diagram in software engineering is a block diagram that describes
the functions and interrelations of a system.
3.4.2.Dataflow diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system, modeling its process aspects. A DFD shows
what kind of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored.
The development of DFD’S is done in several levels. Each process in lower level
diagrams can be broken down into a more detailed DFD in the next level. The
Top-level diagram is often called context diagram. It consists a single process bit,
which plays vital role in studying the current system. The process in the context
level diagram is exploded into other process at the first level DFD.

Dataflow diagrams can be used to provide the end user with a physical idea of
where the data they input ultimately has an effect upon the structure of the
whole system from order to dispatch to restock how any system is developed can
be determined through a dataflow diagram. The appropriate register saved in
database and maintained by appropriate authorities.
 34

DFD LEVEL 0

DFD LEVEL 1

Figure 8 shows a data flow diagram about the system

DFD LEVEL 2

Figure 9 shows a data flow diagram about the system.1

 35

DFD LEVEL 2

Figure 10 shows a data flow diagram about the system2

3.4.3.Entity relationship diagram (ERD)

An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. ER diagrams often use
symbols to represent three different types of information. Boxes are commonly
used to represent entities. Diamonds are normally used to represent
relationships and ovals are used to represent attributes
An entity-relationship model (ERM) in software engineering is an abstract and
conceptual representation of data. Entity-relationship modeling is a relational
schema database modeling method, used to produce a type of conceptual
schema or semantic data model of a system, often a relational database, and its
requirements in a top-down fashion.

Symbols used in this E-R Diagram:

 36

Entity: is a “thing” in the real world with an independent existence. An entity

may be an object with a physical existence such as person, car or employee.
Entity symbol is as follows:

Attribute: is a particular property that describes the entity. Attribute symbol is

Relationship: Relationship will be several implicit relationships among various

entity types whenever an attribute of one entity refers to another entity type some
relationship exits. Relationship symbol is:

Key attributes: An entity type usually has an attribute whose values are distinct
for each individual entity in the collection. Such an attribute is called key
attribute. Key attribute symbol is as follows:

: Primary Key

: Link
 37

Lastname
First name
loginID
password

email
orNo
info Product ID

customer
request
1,n n,n
order

address picture

quantity
nn

Place
Product
oder
proName category

n,n

proID product

price picture

Figure 11 Entity-Relationship (ER) Diagram

 38

3.4.4.Data dictionary
A data dictionary is a set of information describing the contents, format, and
structure of a database and the relationship between its elements, used to
control access to and manipulation of the database.
Data dictionary (Cart)

Table Name Data Type size constraint description

Id Int 50 Primary key Identification of cart
User_id Int 20 Foreign key Identification of users who
make a product to cart
Product_id Int 20 Not null Identification of product
which was add to cart by
users
quantity Varchar 20 Not null Quantity that was add to cart
Table 1 Data dictionary (cart)

Data dictionary (Category)

Table Name Data Type Size Constraint description

Id Int 50 Primary key Identification of category
Name Varchar 30 Not null Name of category
Cat_slug Varchar 50 Not null Descriprion or explanation of
category
Table 2 Data dictionary (category)

Data dictionary (Details)

Table Name Data Type size constraint description

Id Int 50 Primary key Identification of product
Sales_id Int 20 Foreign key Identification of number of
product sales
Product_id Int 20 Not null Identification of product
 39

quantity Varchar 50 Not null Quantity between cart and

bought product
Table 3 Data dictionary (details)

Data dictionary (products)

Table Name Data Type size Constraint description

Id Int 100 Primary key Identification of product

Category_id Int 100 Foreign key Identification of category in

which product are
categorized in
Name varchar 50 Not null Name of product

Description Varchar 100 Not null First description of product

Slug Varchar 50 Not null Second description of product

Price Varchar 50 Not null The price of the product

Photo Varchar 50 Not null Picture that identify a

product
Date_view Varchar 50 Not null Identifying the last time
product have been seen
counter Varchar 50 Not null Identifying number of time
product have been seen
Table 4 Data dictionary (products)

Data dictionary (Sales)

Table Name Data Type size constraint description

Id Int 100 Primary key Identification of sales

User_id Int 50 Foreign key Identification of the users who

buy the product
Pay_id Int 50 Not null Identification of the pay way
 40

Sales_date varchar 50 Not null Date of product sales

Table 5 Data dictionary (sales)

Data dictionary (Users)

Table Name Data Type size constraint description

Id Int 50 Primary key Identification of users

Email Varchar 50 Foreign key Email of users

Password Varchar 50 Not null Password of users

Type Varchar 50 Not null Differentiate admin to

normal users
Firstname Varchar 50 Not null Firstname of user

Lastname Varchar 50 Not null Lastname of user

Address Varchar 50 Not null Address of user

Contact_info Varchar 50 Not null Phone number of user

Photo Varchar 50 Not null Picture identification of

user
Status Varchar 50 Not null

Activate_code Varchar 50 Not null

Reset_code Varchar 50 Not null

Created_on varchar 50 Not null

Table 6 Data dictionary (users)

 41

CHAPTER IV. SYSTEM IMPLEMENTATION

This chapter is focused on the implementation of the new system; it describes
the working application from print screens and show the major interactive or
important part of the system.

3.5. INTERFACES OF THE SYSTEM

3.5.1.Home page

Source: Own drawing from application

Figure 12 home page

The above page is the home page that provides the menu, different information
about the shop company and allow unknown user to view category of product
before signup.
 42

3.5.2.Search product by its category

Figure 13 search product by its category

Source: Own drawing from application

This page is where customers find the products by choosing the category that
relate the needed product.
 43

3.5.3.Search product by typing its name

Figure 14 search product by typing its name

Source: Own drawing from system

This page is where customers find the products by typing the name of any
product that they want, if the name product typed is in the store, this one will
be shown to the customer and if not the system will tell to the customers that
the typed name isn’t found.
 44

3.5.4.Most viewed today

Figure 15 most viewed today

Source: Own drawing from system

At this part, customers can view the most view product of a day.
 45

3.5.5.Add to cart

Figure 16 add to cart

Source: Own drawing from application

This page is where customers after viewing a product to add it to its cart, means
that it adds it to its preference,

Customer can also increase or decrease the quantity of a needed product

 46

3.5.6.View cart

Figure 17 view cart

Source: Own drawing from application

This part is where customers go seeing product that they saved to their cart
 47

Figure 18 cart

Source: Own drawing from application

When customers enter to their cart, they have place to buy product and increase
or decrease quantity.
 48

3.5.7.User and Admin login

Figure 19 user and admin login

Source: Own drawing from application

The login page provides the interface where users can login in order to start their
buy product process and access their accounts, and the admin to manage the
system.
 49

3.5.8.Customer registrations

Figure 20 user registration

Source: Own drawing from application

The signup page provides the interface where users can make their registration
in order to but product.
 50

3.5.9.Customers profile

Figure 21 Customer profile

Source: Own drawing from application

When a customer already has an account and logging in, he can find all his
information in the profile page. All his product bought are shown on his profile
to make him aware of all transaction he has made.

3.6. The administration interfaces

Is the interface where all administrational activities are done such as deleting,
update creating information and so on.

The admin has to logging and must have the specifics permissions to perform
the managerial tasks.
 51

3.6.1.Admin home page

Figure 22 admin home page

Source: Own drawing from application

On this page, all information is summarized in titles in order to give a quick

management tool to the administrator.

The links that are provided here are:

 The booked link brings us to the page that contains all product that have
been bought by the customers.
 The booked link brings us to the page that contains all product that have
been already record in the system.
 The users’ link brings us to the page where all information about all users
are stored and managed.
 The group link which the link is bringing to all category that are in the
system.
 52

3.6.2.Management of product

Figure 23 management of products

Source: Own drawing from application

At this page, admin have to manage product in adding a new one, edit the one
which exist or delete a product
 53

3.6.3.Management of users

Figure 24 management of users

Source: Own drawing from application

At this page, admin have to manage users in adding a new one, edit the one
which exist or delete a user
 54

3.6.4.Management of category

Figure 25 management of category

Source: Own drawing from application

At this page, admin have to manage category in adding a new one, edit the one
which exist or delete any category
 55

3.6.5.Sales pages

Figure 26 sales pages

Source: Own drawing from application

At this page, admin have to see the sales history

 56

3.6.6.Transaction details

Figure 27 transaction details

Source: Own drawing from application

At this page, admin have to see the transaction details of all sales
 57

3.6.7.Admin profile

Figure 28 admin profil

Source: Own drawing from application

Admin can find all his information in the profile page, and can change his email,
his password, his name and his picture.
 58

CHAPTER V Conclusion and Recommendations

Conclusion

The Internet has become a major resource in modern business, thus electronic
shopping has gained significance not only from the entrepreneur’s but also from
the customer’s point of view. For the entrepreneur, electronic shopping generates
new business opportunities and for the customer, it makes comparative
shopping possible.

As per a survey, most consumers of online stores are impulsive and usually make
a decision to stay on a site within the first few seconds. “Website design is like a
shop interior. If the shop looks poor or like hundreds of other shops the customer
is most likely to skip to the other site.

Hence we have designed the project to provide the user with easy navigation,
retrieval of data and necessary feedback as much as possible. In this project, the
user is provided with an e-commerce web site that can be used to buy all types
baby products online.

In this project the ‘add to cart’ functionality made by raw PHP without using any
plugin and bKash payment system is not included properly in this project
because to complete bKash payment system we require a particular payment
gateway.
 59

RECOMMENDATIONS

The goal of this research, from the beginning, has been to contribute some
additional knowledge about the use of comments and recommendation systems
in online shopping system to our general body of knowledge about both
intelligent systems and e-commerce (online shopping).

As researchers, we cannot put the last dot to this work without giving some
recommendations for farther improvement of this project. So we recommend the
following to improve this work by making it larger that an online shopping system
by adding other services such as passenger payment process, to allow the users
to create accounts and save products in to wish list.
 60

REFERENCES

BIBLIOGRAPHIE

 Chen h and li z.the factors influencing chinese online shopper’s

satisfaction in web2.0 era, 2008 international symposium on electronic
commerce security, 86-90;
 Chen h. (2009) the empirical factors analysis on the contents of comments
on the shopping sites;
 Kim w g, lee c & hiemstra s j. (2004) effects of an online virtual community
on customer loyalty and trabel product purchase. tourism management,
25 (3),343-355;
 Adamic l and ader e (2003). friends and neighbors on the web. social
networks, 25(3), 211-230.
 Young a k, jaideep s. (2007) impact of social influence in e-commerce
decision making. icec, 293-302;
 Bickart b and schindler r m. (2001) internet forums as influential sources
of consumer information. journal of interactive marketing, 15(30),31-40;
 Markopoulos, p. m. and kephart, j. o. 2002. how valuable are shopbots?.
in proceedings of the first international joint conference on autonomous
agents and multiagent systems: part 3 (bologna, italy, july 15 - 19, 2002).
 Häubl, g, trifts, v. 2000. consumer decision making in online shopping
environments: the effects of interactive decision aids. marketing
science,19[1] 4-21;
 Felfernig, a.; gula, b. 2006. an empirical study on consumer behavior in
the interaction with knowledgebased recommender applications. in
proceedings of the 8th ieee international conference on e-commerce
technology and the 3rd ieee international conference on enterprise
computing, e-commerce, and eservices (cec/eee ’06)
 61

 Papatla, p.: do online shopping styles affect preferred site attributes? an

empirical investigation and retailing implications. journal of retailing and
consumer services 18, 362–369 (2011). crossref google scholar
 Forrester consulting, ecommerce web site performance today: an updated
look at consumer reaction to a poor online shopping experience (august
17, 2009). google scholar
 Soopramanien, d.g.r., robertson, a.: adoption and usage of online
shopping: an empirical analysis of the characteristics of “buyers”
“browsers” and “non-internet shoppers. journal of retailing and consumer
services 14, 73–82 (2007). Crossref google scholar
 Moe, w., fader, p.s.: dynamic conversion behaviour at e-commerce sites.
management science 50(3), 326–335 (2004). crossref google scholar
 Close, e.g., kukar-kinney, m.: beyond buying: motivations behind
consumers’ online shopping cart use. journal of business research 63,
986–992 (2010). crossref google scholar
 62

WEBOGRAPHIE
www.investopedia.com
www.merriam-webster.com
www.dictionary.com
www. academic.oup.com
www.w3schools.com
www.searchdatamanagement.techtarget.com
www.cio-wiki.org
www.guru99.com
www.wikipedia.com
www.mysql.com
www.getbootstrap.com
www.thalesesecurity.com
www.veracode.com