UTTARA UNIVERSITY

iShop- A Complete E-commerce Solution

BY
KAIUM HASAN AL- 2191081148 47(DAY)
ASIB

RASHIDA AKTER 2192081005 48(DAY)

TULI

NAYEM HASAN 2192081010 48(DAY)

MD. MONIRUL 2192081024 48(DAY)

ISLAM

DEPARTMENT OF COMPUTER SCIENCE AND

ENGINEERING
SCHOOL OF SCIENCE AND ENGINEERING
UTTARA UNIVERSITY

SPRING 2023
 ABSTRACT

We are doing an E-Commerce Website. A person sitting on his chair

in front of a computer can access all the facilities of the Internet to
buy or sell the products. Unlike traditional commerce that is carried
out physically with effort of a person to go & get products, e-
commerce has made it easier for human to reduce physical work
and to save time. E-Commerce which was started in early 1990’s
has taken a great leap in the world of computers, but the fact that
has hindered the growth of e-commerce is security. Security is the
challenge facing e-commerce today & there is still a lot of
advancement made in the field of security Hence sellers and buyers
are turning to e-commerce platforms. From our website Users can
easily and quickly find their needs, they can pay the bills in very few
ways, and finally it will give idea about the customer’s demand like
as age, personality, likes, scammers or not and so on. The main goal
of this project is to design and develop web application software for
e- commerce platform, study and analyze various types of customer
demands and design user-friendly interfaces. To this entire feature
we are using incremental methodology. This methodology is a way
to manage a project by breaking it up into several phases. It
involves constant collaboration with stakeholders and continuous
improvement at every stage. Once the work begins, teams cycle
through a process of planning, executing, and evaluating. It can be
used as an umbrella term to the process. Incremental is one of the
most popular approaches to project management due to its
flexibility, adaptability to change, and high level of customer input.
For a developing country advancement in the field of e-commerce is
essential. The research strategy shows the importance of the e-
commerce in developing countries for business application. The
importance of e-commerce websites is increasing day by day and it
will lead to 22.3% of total retail sales worldwide in 2023.

Keywords: E-Commerce, Security, Global Market Analysis, Payment

I
 APPROVAL

I certify that I have supervised this project and read this manuscript.
In my opinion, it conforms to acceptable standards of scholarly
presentation and is fully adequate, in scope and quality, as a report
for the degree of BSc. in Computer Science and Engineering.

Dr. A.H.M. Saifullah Sadi

Supervisor

I certify that I have read this study. In my opinion, it conforms to

acceptable standards of scholarly presentation and is fully
adequate, in scope and quality, as a thesis for the degree of BSc. in
Computer Science and Engineering.

Coordinator/Internal
Examiner

This project report was submitted to the Department of Computer

Science and Engineering and is accepted as a fulfilment of the
requirement for the degree of BSc. in Computer Science and
Engineering.

Dr. A.H.M. Saifullah Sadi

Chairman, Dept. of CSE

II
 DECLARATION

We hereby declare that this report is the result of our own

investigations, except where otherwise stated. we also declare that
it has not been previously or concurrently submitted as a whole for
any other degrees at Uttara University or any other institutions. We
also declare that the formatting of the manuscript is same as the
provided template. We also do not have any objections for the
further use of the manuscript as Uttara University has all the rights
to update, publish, or conduct further research of the submitted
work.

Student Names Student IDs Signature Date

KAIUM HASAN AL ______________

2191081148 ______________
ASIB _

RASHIDA AKTER ______________

2192081005 ______________
TULI _

______________
NAYEM HASAN 2192081010 ______________
_

MD. MONIRUL ______________

2192081024 ______________
ISLAM _

III
 UTTARA UNIVERSITY

INTERNATIONAL ISLAMIC UNIVERSITY MALAYSIA

DECLARATION OF COPYRIGHT AND AFFIRMATION OF
FAIR USE OF UNPUBLISHED RESEARCH

iShop - A Complete E-commerce Solution

We declare that the copyright holders of this dissertation are jointly

owned by the students and Uttara University (UU).

Copyright © 2022 Rashida Akter Tuli

and Uttara University (UU). All rights reserved.

No part of this unpublished research may be reproduced, stored in a

retrieval system, or transmitted, in any form or by any means, electronic,
mechanical, photocopying, recording, or otherwise without prior written
permission of the copyright holder except as provided below.

1. Any material contained in or derived from this unpublished

research may be used by others in their writing with due
acknowledgement.

1. UU or its library will have the right to make and transmit copies
(print or electronic) for institutional and academic purposes.

2. The UU library will have the right to make, store in a retrieved

system and supply copies of this unpublished research if
requested by other universities and research libraries.

By signing this form, we acknowledged that we have read and understand

the UU Intellectual Property Right and Commercialization policy.

Affirmed by KAIUM HASAN AL ASIB

……..………………………………………
………………………..
Signature (on behalf of the team)
Date

IV
 DEDICATION

We dedicate this report to

our honorable parents, and our younger brother(s)
for their meticulous support, continuous inspiration, and
unconditional love
till the very end of this journey.

V
 ACKNOWLEDGEMENTS

Firstly, it is our utmost pleasure to dedicate this work to my dear

parents and my family, who granted me the gift of their unwavering
belief in my/our ability to accomplish this goal: thank you for your
support and patience.

I wish to express my appreciation and thanks to those who provided

their time, effort and support for this project. To the members of my
dissertation committee, thank you for sticking with me.

Finally, a special thanks to Assoc. Prof. Dr. A.H.M. Saifullah Sadi

for his continuous support, encouragement, and leadership, and for
that, I will be forever grateful.

VI
 TABLE OF CONTENT

Abstract i
Approval page ii
Declaration iii
Copyright iv
Dedication v
Acknowledgements vi
Table of content vii
List of figures ix

CHAPTER ONE: INTRODUCTION 1

1.1 Overview 1
1.2 Problem Statements and Its Significance 3
1.3 Project Objectives 4
1.4 Project Methodology 5
1.5 Gantt Chart and Research Milestone 11

CHAPTER TWO: BACKGROUND STUDY 12

2.1 Overview 12
2.2 Background Study 12
2.2.1 Related Existing Websites 13
2.3 Summery 15

CHAPTER THREE: SYSTEM ANALYSIS / MODELING & DESIGN

16
3.1 Overview 16
3.2 Analysis, Modeling, and Design 16
3.3 Summary 20
CHAPTER FOUR: SYSTEM SETUP, IMPLEMENTATION, &
TESTING 21
4.1 Overview 21

VII
4.2 System Setup / Experimental Setup 21
4.3 Implementation 25
4.4 Testing 32
4.5 Summary 35

CHAPTER FIVE: RESULT ANALYSIS & BENCHMARKING 36

5.1 Overview 36
5.2 Result Presentation 36
5.3 Summary 46

CHAPTER SIX: CONCLUSION & RECOMMENDATIONS 47

6.1 Project Outcomes 48
6.2 Limitations of the Project 48
6.3 Recommendations 49

REFERENCES 50
APPENDIX A: EXAMPLE CODES 51

VIII
 LIST OF FIGURES

No.

Page

1.1 Flow diagram of Incremental Model 5

1.2 Flow diagram of the project 9

3.1 Activity Diagram 18

3.2 E-R Diagram 19

4.1 Screen shot of the admin homepage (code) 26

4.2 Screen shot of the add product page (code) 27

4.3 Screen shot of the user registration page (code) 28

4.4 Screen shot of the user login page (code) 29

4.5 Screen shot of the contact page (code) 30

4.6 Screen shot of the search page code 30

4.7 Screen shot of the cart page code 31

5.1 Screen shot of the home page 37

5.2 Screen shot of the sign up page 38

5.3 Screen shot of the login page 39

5.4 Screen shot of the product view page 40

5.5 Screen shot of the cart page 41

5.6 Screen shot of FAQ page 42

5.7 Screen shot of the admin home page 43

5.8 Screen shot of the add product page 44

5.9 Screen shot of the checkout page 45

IX
 CHAPTER ONE
INTRODUCTION

1.1 OVERVIEW

Bangladesh is a developing country and Information Communication

and technology are playing their important roles in development of

the country. By e-commerce we mean buying and selling of

products or services over electronic systems such as the Internet

and other computer networks. In truth in Bangladesh we have very

less ways to pay our bills online. But that does not mean we cannot.

There are new players on Bangladeshi ground like Upay, Nagad and

local banks are also available. With launch of these services many

new startups can easily sell their products and services online.

These services have lots of potential and we hope it will succeed

and bring a change in the Bangladeshi e-commerce field. There are

big and old player like Bkash in BD which is already popular for its

money transfer and online shops. E-commerce is fast gaining

ground as an accepted and used business paradigm. More and more

business houses are implementing web sites providing functionality

for performing commercial transactions over the web. It is

reasonable to say that the process of shopping on the web is

becoming commonplace. The objective of this project is to develop a

general-purpose e-commerce store where any product (such as

books, CDs, computers, mobile phones, electronic items, and home

appliances) can be bought from the comfort of home through the

1
Internet. An online store is a virtual store on the Internet where

customers can browse the catalog and select products of interest.

The selected items may be collected in a shopping cart. At checkout

time, the items in the shopping cart will be presented as an order.

At that time, more information will be needed to complete the

transaction. Usually, the customer will be asked to fill or select a

billing address, a shipping address, a shipping option, and payment

information such as credit card number. An e- mail notification is

sent to the customer as soon as the order is placed.

1.2 PROBLEM STATEMENTS AND ITS SIGNIFICANCE

E-commerce provides an easy way to sell products to a large

customer base. However, there is a lot of competition among

multiple E-commerce sites. We highlight some problems on their

websites that we will try to fixed.

i. When users land on an e-commerce site, hard to find what they

are looking for quickly and easily.

ii. Very less ways to pay bills online.

iii. The cost of maintenance is too high.

iv. Existing system’s not able to provide a proper review of the

product they are selling.

2
1.3 PROJECT OBJECTIVES

E-commerce, also known as electronic commerce or internet

commerce, refers to the buying and selling of goods or services

using the internet, and the transfer of money and data to execute

these transactions. The main goal of this project is to design and

develop a web application software for e-commerce platform. The

proposal involves the following objectives:

i. To study and analyze various types of problems, customer

demand and find the solutions.

ii. To design user-friendly interfaces.

iii. To implement and integrate the GUI and database through

coding, testing, debugging.

1.4 PROJECT METHODOLOGY

1.4.1. MODULE

We will use Incremental model because we are going to build an e-

commerce website and a system that customer and organizers can

use effectively. In Incremental model - first, a simple working

system implementing only a few basic features is built and then that

is delivered to the customer. Then thereafter many successive

iterations/ versions are implemented and delivered to the customer

until the desired system is released.

3
 Figure 1.1 Flow diagram of Incremental Model

Different phases of our Project -

1. Requirement collection and Analysis

2. Design

3. Coding /Implementation

4. Integration & Testing

5. Installation/Deployment

6. Maintain

Requirement collection and Analysis/ Planning:

• The audience-

• B2C - Consumer visitors

• SRS - System Requirements Specifications

1. Login and Registration System/ Log Out

2. Dashboard(admin)

a. Add category

b. Add Product

c. Manage Order

4
 d. Manage Payment

e. Check Feedback

3. Payment

a. Online Pay

b. Cash on Delivery

4. Order Status

a. Processing

b. Shipped

c. Delivered

5. Customer

a. Search Product

b. View Product

c. Buy Product

d. Add to Cart

Design

1. Design the Navigation view

2. Starting with the Home Page and 'First level child pages'

3. Hyperlinks plan and buttons

4. Backend required

5
Coding /Implementation

1. Prepare website -

Write codes in HTML/CSS/JS/JQuery/Python/Django/SQLite

Testing

1. Test website

2. Check for broken links

3. Speed: Slow pages

4. Database test records

5. Updating of database

6. Money transaction (if applicable)

Installation/Deployment-

1. Select hosting company

2. Pay hosting charges and get password

3. Upload website to the internet server

Maintain & Update

1. Regularly change and update the content

2. Perform SEO

3. Update keywords /Meta tag as the per the changes in

business needs

6
1.4.2 FLOW CHART

1.2 Flow diagram of the project

7
1.4.3 USE CASE DIAGRAM

1.3 Use Case Diagram

8
1.5 PROJECT TIME TABLE & MILESTONES

Module/ Jul Aug Sept Oct Nov Dec Jan Feb

Time

Basic
Management

Planning

Designing

Coding

Product

Display

Performance

Optimization

Merge all unit

test

Test all
together

9
 CHAPTER TWO
BACKGROUND STUDY

2.1 OVERVIEW

In this chapter, we will compare various types of e-commerce

platform and similar websites. We know that now a days online e-

commerce platform has been a very important thing for peoples.

The number of e-commerce platform increasing day by day. We

studied some of the online e-commerce platform and similar

websites. After the study we listed out some limitations that can be

decreased to improve the platform and make it user friendly. In that

context, we tried to improve the facilities of the existing online e-

commerce platform.

2.2 BACKGROUND STUDY

The research and study done behind this project are focused on web

development. We studied different web design resources to

structure our website in order to make it easy to use god looking

and provide a pleasant experience.

A search bar has proved to be essential for our sieve though all the

different e Commerce feature in the website. We need to arrange

our content in a styled manner and make it simple and appealing for

users to explore though the website, well-structured content

certainly adds to the beauty of a website. Also we need to create a

database to store information related to users, a thorough research

10
needs to be done in order to create an optimum database for fast

and efficient performance on the back end of the website.

2.2.1 RELATED EXISTING WEBSITES

In this section we define some related existing website and discuss

about their features and limitations.

BOIGHOR

https://boighor.com/

Features:

 User friendly navigation.

 Search option

 Product reviews

 Shopping carts

 Show related products

Limitation:

 No FAQ for products.

 No filter option.

 Payment option is not secure.

11
ROKOMARI

https://www.rokomari.com

Features:

 Good user interface and user-friendly.

 Search option

 Product reviews

 Shopping carts

 Show related products

 User can track their product.

Limitations:

 No FAQ for the store.

 User can’t sort out desire product.

12
2.3 SUMMERY

In our background study we have discussed about the background

work of our project. Here we have discussed about some related

existing websites and their features and limitations. Based on this

discussion we will try to develop our online e0 platform.

13
 CHAPTER THREE
SYSTEM ANALYSIS / MODELING & DESIGN

3.1 OVERVIEW

Write Systems analysis is the process by which an individual (s)

studies a system such that an information system can be analyzed,

modeled, and a logical alternative can be chosen. Systems analysis

projects are initiated for three reasons: problems, opportunities, and

directives.

3.2 ANALYSIS, MODELING, AND DESIGN

There are many cases where the original software requirements are

logically well defined, but the scope of the development effort

hinders a straightforward process. software development in a

growing process model. The product is designed, used, assembled

and tested as a series of growing structures. It is a popular software

emerging model used by many trading software companies and

system vendor. Incremental software development model may be

applicable to projects where:

• Software Requirements are well defined, but realization may be

Delayed

• The basic software functionality is required early

14
Use Case Diagram

In the Unified Modeling Language (UML), a use case diagram can

summarize the details of your system’s users (also known as actors)

and their interactions with the system. To build one, you’ll use a set

of specialized symbols and connectors. An effective use case

diagram can help your team discuss and represent:

 Scenarios in which your system or application interacts with

people, organizations, or external systems.

15
  Goals that your system or application helps those entities

(known as actors) achieve.

 The scope of your system.

Activity Diagram

3.1 Activity Diagram

16
Activity diagrams present a number of benefits to users. Consider

creating an activity diagram to:

 Demonstrate the logic of an algorithm.

 Describe the steps performed in a UML use case.

 Illustrate a business process or workflow between users and

the system.

 Simplify and improve any process by clarifying complicated

use cases.

 Model software architecture elements, such as method, func-

tion, and operation.

E-R Diagram

3.2 E-R Diagram

17
An Entity Relationship (ER) Diagram is a type of flowchart that illus-

trates how “entities” such as people, objects or concepts relate to

each other within a system. ER Diagrams are most often used to de-

sign or debug relational databases in the fields of software engi-

neering, business information systems, education and research. Also

known as ERDs or ER Models, they use a defined set of symbols

such as rectangles, diamonds, ovals and connecting lines to depict

the interconnectedness of entities, relationships and their attributes.

They mirror grammatical structure, with entities as nouns and rela-

tionships as verbs.

3.3 SUMMARY

We can see that our project is a web-development project. In our

project we need frequent changes at any time and we need to

decrease the development time. As Incremental model fulfill all the

requirements to develop our project, we are using this development

model in our project.

18
 CHAPTER FOUR
SYSTEM SETUP, IMPLEMENTATION, & TESTING

4.1 OVERVIEW

This is the chapter of the software life cycle where the actual

software is implemented. The result of this phase consists of source

code, together with documentation to make the code reliable the

code reliable. Implementation is the action that must follow any

preliminary in order for something to actually happen. It

encompasses all the processes involved in getting new software and

hardware operating properly in its environment, including

installation, configuration and running, testing and making

necessary changes.

4.2 SYSTEM SETUP

In this section the whole system design and data design is discussed

with the example of user interface system.

Basic Modules:

4.2.1 Admin Login:

 Manage Product details

 Manage users in the system

 Add Products

 Delete Products

 Edit Products

21
4.2.2 User Login:

a. Browse product

b. Search product

c. Take a product

d. Add to cart

e. Order products

4.2.3 DATA DESIGN:

Overview:

In our project system is divided in two portions. One is admin and

the other one is user. We designed various types of data table of

admin category and user category. We have design 5 tables of

admin, user, product, history which are major for our internet

shopping.

Admin Table:

In this table we have 6 columns of admin information. Each column

has its own entities like data type, size, and constraints as given

below:

Table 4.1 Admin database table

Column name Data Type Size Constraints

admin_id Integer Not Null and unique
admin_username Varchar 150 Not Null

admin_password Varchar 150 Not Null

admin_fname Varchar 150 Not Null
admin_lname Varchar 150 Not Null
admin_email Varchar 150 Not Null

20
2
User Table:

In this table we have 6 columns of user information listed as user_id,

user_username, user_password, user_fname, user_lname,

user_email. Each column has its own entities like data type, size,

and constraints as given below:

Table 4.2 User database table

Column name Data Type Size Constraints

user_id Integer Not Null and
unique
user_username Varchar 150 Not Null

user_password Varchar 150 Not Null

user_fname Varchar 150 Not Null
user_lname Varchar 150 Not Null
user_email Varchar 150 Not Null

Product Table:

In this table we have 3 columns of product information listed as

product_id, product_name andproduct_image . Each column has its

own entities like datatype,size and constraints as given below:

Table 4.3 product database table

Column name Data Type Size Constraints

unique_id Integer Not Null
and unique
name Varchar 200 Not Null

image Imagefield Not Null

price Integer Not Null
condition Varchar 50 Not Null
information Varchar 200 Not Null
description Varchar 500 Not Null
stock Varchar 50 Not Null
status Varchar 50 Not Null
created_date Varchar 100 Not Null
categories Varchar 100 Not Null
brand Varchar 100 Not Null
color Varchar 50 Not Null
21
62
Order Table:

In this table we have 3 columns of product information listed as

history_id, user_name, and product added. Each column has its own

entities like data type, size, and constraints as given below:

Table4.4 History database table

Column name Data Type Size Constraints

user Foreign key

firstname Varchar 150 Not Null

lastname Varchar 150 Not Null

country Varchar 150 Not Null

address Varchar 150 Not Null
city Varchar 100 Not Null
state Varchar 100 Not Null
postcode Integer Not Null
phone Varchar 100 Not Null
email EmailField 100 Not Null
additional_info Varchar 200 Not Null
amount Integer Not Null
date DateTimeField Not Null
payment_id Integer Null
paid Boolean Null

4.3 IMPLEMENTATION

In implementation we start with the actual execution of the software

application with the design we have made. Implementation is done

before we start with the coding of the software product

Implementation includes writing codes with the design in and.

Implementation is the process of having systems person can

checkout and put new equipment in to use, train users, installs the

new application depending on the size of the organization that will

be involved.
22
62
 4.3.1 Coding Details:

In this section we have showed the coding details of our iShop

and discussed some of the code

Admin Home Page

At first, we have created the admin home page as it is the most

important page of the project.

Figure 4.1: Screen shot of the admin home page code

23
62
Add Product (Admin):

In the add question page we have keep the option to add,

edit, delete of the questions for the admin.

Figure 4.2: Screen shot of the add product page code

24
User Registration Page:

This page is created for the users who are new to the website

and they have to register manually to use the website.

Figure 4.3: Screen shot of the user registration page code

25
User Login Page:

In this page user will see some information field and they have to fill

those field with proper information for an authentic login to the

website.

Figure 4.4: Screen shot of the user log-in page

26
Contact Page:

This page is created for the users who are willing to contact

with company.

Figure 4.5: Screen shot of the contact page code

Search:

This code is created for the users to find a product.

Figure 4.6: Screen shot of the search page code

27
Cart Page:

This page is created for the cart page so that users to can

easily order any product.

Figure 4.7: Screen shot of the cart page code

28
4.4 TESTING

Software testing is a process which is used to ensure that software

product is defect free and to measure the quality of software

developed. It is also a process of uncovering errors in a program

and makes it a feasible task. It is useful process of executing

program with the intent of finding bugs. In order to prove that a

piece of software works, the software must be tested to determine if

the requirements of the application are met. There are several

different types used throughout the development process. Some of

them are mentioned below:

4.4.1 Component Testing:

Where every component related to the software project is tested.

4.4.2 System Testing:

The testing implemented on overall software project after

component integration is system testing.

4.4.3 Acceptance Testing:

It is performed after software installation in user environment with

data supplied by customers.

4.4.4 Unit Testing:

The first test in the development process is the unit test. Unit testing

is a level of software testing where individual units or components of

software are tested. The purpose is to validate that each unit of the

29
software performs as designed. A unit is the smallest test able part

of

any software. It usually has one or a few inputs and a single output.

The source code is normally divided into modules, which in turn are

divided into smaller unit called units. These units have specific

behavior. The test done on these units of code is called unit test.

Unit test depends upon the language on which the project is

developed. Unit tests ensure that each unique path of the project

performs accurately to the documented specifications and contains

clearly defined input and expected results. Unit tests are typically

written and run by software developers to ensure that code meets

its design and behaves as intended.

Some of the objectives of unit testing:

1 To test every function and procedure

2 To fix bugs early in the development cycle.

3 To help the coder use.

4 To verify the correctness of code.

5 To help find problems and resolve them before

further testing.

4.4.5 Integrated Testing:

Integration testing is a level of software testing where software

modules are integrated logically and tested to verify if they are

working properly and where individual units are combined and

tested as a group. Integration testing carries a lot of significance as

it helps tester in determining the effectiveness as well as the

30
functionality of the software. Integration testing is critical to ensure

the functional correctness of the integrated system. Integration

testing is often the most time consuming and expensive part of

testing. Testing performed to expose defects in the interfaces and in

the interactions between integrated components or systems.

4.4.6 Beta Testing:

Beta testing is the second phase of software testing, which adds

value to the product as the end user validates the product for

functionally, usability, reliability and compatibility. The main goal of

user acceptance testing is to check whether the developed software

product fulfill the user requirements. Beta testing is performed in

order to access the product by exposing into real end users. After

that, the feedback is taken from the user sand the defects are fixed.

Inputs provided by the end users helps in enhancing the quality of

the product further and leads to success. It helps the software

product to provide better user experience and one of the major

advantages is, by beta testing we get the feedback directly.

31
4.5 SUMMARY

In this chapter we discussed about the whole system design,

implementation and testing process of our project. Here we also

discussed about how we design our database and how we built-up

our website with some database table and sample codes of some

pages.

32
 CHAPTER FIVE
RESULT ANALYSIS & BENCHMARKING

5.1 OVERVIEW

In this chapter, we discuss about the outcomes of our projects and

also we will analyze the result after implementing and testing our

project. With the help of our complete project users will easily get all

the benefits of updated features.

5.2 RESULT PRESENTATION

In this section we will show our project result after implementation

and testing. Here we will discuss about our final outcome of our

proposed iShop website.

33
i. Home Page: After opening our website this home page will

be appear first. To see new products or buy products user needs to

create an account first or log-in to their previous account.

Figure 5.1: Screen shot of the home page

34
ii. Sign up Page: This page is for creating new account in

this website. New users need to create an account first.

Figure 5.2: Screen shot of the sign-up page

35
iii. Login Page: This page is for registered users to log in to their

account.

Figure 5.3: Screen shot of the login page

36
iv. Product View: When any user selects a product this page will
appear.

Figure 5.4: Screen shot of the Product view page

37
v. Cart Page: After selecting a product this page will be showing.

Figure 5.5: Screen shot of the cart page

38
viii. FAQ Page: This is the frequently asked question page.

Figure 5.6: Screen shot of the FAQ page

39
ix. Admin Home Page: When an admin login to the website this

homepage will appear before admin.

Figure 5.7: Screen shot of the admin home page

40
 Xi. Add Product: From this page admin can added Product to the
website.

Figure 5.8: Screen shot of the add products page

41
Xii Check out Billing details Page: From this page admin can see a
user’s history.

Figure 5.9: Screen shot of the billing details page

42
5.3 SUMMARY

In this chapter we have discussed about the result of our project.

Here we also discussed about the admin page and user page of our

website.

43
 CHAPTER SIX
CONCLUSION & RECOMMENDATIONS

Conclusion section will present the overall concluding remarks of the

project. This section will briefly explain all the main focuses of the

project. This section will also present about the challenges and

solutions and necessary steps which would be taken to complete the

project successfully.

At the end it is concluded that we have made effort on

following points-

• A description of the background and context of the project and

its relation to work already done in the area

• Made statement of the aims and objectives of the project.

• The description of Purpose, Scope, and applicability

• We define the problem on which we are working in the project.

• We describe the requirement Specifications of the system and

the actions that can be done on these things.

• We understand the problem domain and produce a model of the

System, which describes operations that can be performed on

the system.

• We included features and operations in detail, including screen

layouts.

• We designed user interface and security issues related to

system.

• Finally, the system is implemented and tested according to test

cases.
44
6.1 PROJECT OUTCOMES

This section will point out the possible specific outcomes of the

project. Basically, the specific outcome or new findings should

match with the pointed objectives which are presented in Chapter

one. Outcomes may be presented in three groups; New

findings/knowledge, Specific/Potential applications, and Research

publications. Basically, new findings/knowledge is the most

important which must be presented, and the rest two groups may

be excluded if not necessary for the project.

New findings

a) Users will know whether the product is imported or not by

scanning QR Code.

b) A user-friendly system that everyone can understand.

c) User can easily find products according to their desire

prize range.

6.2 LIMITATIONS OF THE PROJECT

a) User can’t purchase products without log-in to the website.

b) This application is not suitable for those organizations where

there is large quantities of product and different level of

warehouses.

c) Single admin panel is only made.

d) It is not suitable for large organization.

45
6.3 RECOMMENDATIONS

Some recommended future works are written below...

 We can add fake reviews detection feature to prevent fake

reviews.

 We can add a tracking feature through which users can track the
location of parcels.

 We can make it multi-vendor project.

 We can give more advance software for iShop including

more facilities

 User can signup/login using their social media such as facebook,

google etc.

 We can add a chat feature where buyer and seller can

exchange messages with each other.

The above-mentioned points are the enhancements which can be

done to increase the applicability and usage of this project.

46
 REFERENCES

Chaffey, D., 2011. E-business & e-commerce management. Harlow,

England: Pearson/Financial Times Prentice Hall.

Graf, A. and Schneider, H., 2016. The E-Commerce Book. Frankfurt

am Main: Dfv Mediengruppe Fachbuch.

Sakthivel, M., 2005. CRM Implementation Strategies for Mobile Phone

Service Providers. SSRN Electronic Journal,.

SDLC - Overview. Tutorials Point. (n.d.).

https://www.tutorialspoint.com/sdlc/sdlc_overview.htm

47
 APPENDIX
EXAMPLE
CODES

CODES FOR LOGIN PAGE

def HandleLogin(request):
if request.method == 'POST':
username = request.POST.get('username')
password = request.POST.get('password')

user = authenticate(username = username,password =

password)
if user is not None:
login(request,user)
return redirect('home')
else:
return redirect('login')

return render(request,'Registration/auth.html')

CODES FOR REGISTRATION PAGE

def HandleRegister(request):

if request.method == 'POST':

username = request.POST.get('username')

first_name = request.POST.get('first_name')

last_name = request.POST.get('last_name')

email = request.POST.get('email')

48
 pass1 = request.POST.get('pass1')

pass2 = request.POST.get('pass2')

customer = User.objects.create_user(username,email,pass1)

customer.first_name = first_name

customer.last_name = last_name

customer.save()

return redirect('register')

return render(request,'Registration/auth.html')

49
BS
c
in
CS
E

i
S
h
o
p

U
U
,
S
p
ri
n
g
2