BIRENDRA MULTIPLE CAMPUS

Institute of Science and Technology

A PROJECT REPORT

“Nepali Store- E-Commerce Website”

A PROJECT REPORT

Submitted to

Department of Computer Science and Information Technology

BIRENDRA MUTIPLE CAMPUS

2020

In partial fulfillment of the requirements for the Bachelor's Degree in Computer

Science and Information Technology

Submitted by

Asbin Giri (TU Exam Roll No. 11596/073)

Bigyan Neupane (TU Exam Roll No. 11602/073)

i
Namuna Shrestha (TU Exam Roll No. 11619/073)

Rupesh Subedi (TU Exam Roll No. 11634/073)

feb , 2021

ii
 BIRENDRA MULTIPLE CAMPUS
TRIBHUVAN UNIVERSITY
INSTITUTE OF SCIENCE AND TECHNOLOGY

Major Project on

“Nepali Store- E-Commerce Website”

A Major project report submitted in partial fulfillment of the requirements for the
degree of Bachelor of Science in Computer Science and Information Technology
awarded by Tribhuvan University.

Submitted to
Birendra Multiple Campus
Department of Computer Science and Information Technology
Bharatpur-10, Chitwan

Feb, 2021

1
 Birendra Multiple Campus

Tribhuvan University

Supervisor Recommendation

I hereby recommend that this project prepared under my supervision by Namuna Shrestha,
Rupesh Subedi, Asbin Giri and Bigyan Neupane entitled “Nepali Store” in partial fulfillment of
the requirements for the degree of Bachelors of Science in Computer Science and Information
Technology be processed for the evaluation.

………………………..

Er. Binod sharma

Supervisor

Certificate of Approval

The undersigned certify that they have read and recommended to the Department of Computer
Science and Information Technology, IOST, Birendra Multiple Campus, a project work

2
entitled “Nepali Store- E-commerce Website’’ submitted by Namuna Shrestha, Rupesh
Subedi, Asbin Giri and Bigyan Neupane in partial fulfillment for the award of Bachelor’s
Degree in Computer Science and Information Technology. The Project was carried out under
special supervision and within the time frame prescribed by the syllabus.

We found the students to be hardworking, skilled and ready to undertake any related work to
their field of study and hence we recommend the award of partial fulfillment of Bachelor’s
degree of Science in Computer Science and Information Technology.

…
……………………… ………………………….
Er. Binod sharma Mr.
Project Supervisor Campus Principle
Birendra Multiple Campus Birendra Multiple Campus

…………………………. …………………………
Mr. Er.
(External Examiner) (Internal Examiner)

Students

The project work entitled “Nepali Store E-Commerce Website” is submitted to the office of the
Dean, Faculty of Science and Information Technology, Tribhuvan University, is based on the

3
work carried out during the course of study under the supervision and guidance of Mr. Binod
Sharma. This project All the statement and conclusion written in this are the outcome of the
project work.

……………….. ………....………..

Namuna Shrestha Rupesh Subedi

(symbol no:11619/073) (symbol no:11634/073)

……………….. ………....……

Asbin Giri Bigyan Neupane

(symbol no:11596/073) (symbol no:11602/073)

4
 ACKNOWLEDGEMENTS

This project is developed in order to fulfill the partial requirement of Tribhuvan University for
the completion of Bsc. CSIT 7th semester. This is a project with the objective to develop a basic
website where customer can buy or order required product through online. Although this is the
individual project assigned to us during our study. Huge thanks to all the college staffs, teachers
and fellow classmates, for helping out in every aspect of this project. Special thanks to our
Supervisor Mr. Binod Sharma. He has been supportive and his feedback has greatly improved
our work. Thanks to Mr. Gobinda Sapkota for bombarding us with each and every opportunity
that he provided us. He helped a lot in completion of this project, for any financial support, and
Resource needs, and surely, he handled it well. Moreover, finally thanks to every person who has
directly or indirectly contributed in the project. Special thanks go to the online sites, and forums
which were very helpful throughout the project, Thanks to all the writers and scientific journalist
who has their immense contribution to our project, through their papers and Journals.

Nepali Store

Birendra Multiple Campus

Tribhuvan University

………………………… ………....…………….

Namuna Shrestha Rupesh Subedi

(symbol no:11619/073) (symbol no:11634/073)

…………………………… ………....……………………

Asbin Giri Bigyan Neupane

(symbol no:11596/073) (symbol no:11602/073)

5
 ABSTRACT

This project is a web based shopping system for an existing shop. The project objective is to
deliver the online shopping application into web platform. This project is an attempt to provide
the advantages of online shopping to customers of a real shop. It helps buying the products in the
shop anywhere through internet by using all kinds of device like computers and smartphones.
Thus the customer will get the service of online shopping and home delivery from this website.
This system can be implemented to any shop in the locality or to multinational branded shops
having retail outlet chains .If shops are providing an online portal where their customers can
enjoy easy shopping from anywhere, the shops won’t be losing any more customers to the
trending online shops such as amazon , ebay and daraz . Since this web application is available in
all kinds of computer and smartphones easily accessible and always available.

TABLE OF CONTENTS
6
Supervisor Recommendation...........................................................................................................ii

Certificate of Approval...................................................................................................................iii

Students..........................................................................................................................................iv

ACKNOWLEDGEMENTS.............................................................................................................v

ABSTRACT...................................................................................................................................vi

LIST OF FIGURES.........................................................................................................................x

LIST OF TABLE.............................................................................................................................x

CHAPTER-1 INTRODUCTION.....................................................................................................1

1.1: INTRODUCTION....................................................................................................1

1.2: HISTORY OF E-COMMERCE...............................................................................1

1.3: DESCRIPTION OF PROJECT................................................................................2

1.3.1: MODULES:...................................................................................................................2

1.4: PROBLEM STATEMENT.......................................................................................9

1.5: OBJECTIVES...........................................................................................................9

1.6: SCOPES..................................................................................................................10

1.6: LIMITATION.........................................................................................................10

CHAPTER:2 LITERATURE REVIEW.......................................................................................10

CHAPTER: 3.................................................................................................................................11

REQUIREMENT ANALYSIS AND FEASIBILITY ANALYSIS..............................................11

3.1:REQUIREMENT ANALYSIS:...............................................................................12

3.1.1: FUNCTIONAL REQUIREMENT:.............................................................................12

3.1.2: NON FUNCTIONAL REQUIREMENT:...................................................................14

3.2: FEASIBILITY ANALYSIS...................................................................................15

3.2.1: TECHNICAL :............................................................................................................15

3.2.2: ECONOMIC FEASIBILITY:......................................................................................16

7
 2.2.3:OPERATIONAL FEASIBILITY:................................................................................16

3.2.4 SCHEDULE FEASIBILITY:.......................................................................................16

CHAPTER-4..................................................................................................................................17

METHODOLOGY........................................................................................................................17

4.1: SYSTEM ARCHITECTURE.................................................................................17

4.2: SYSTEM DESIGN.................................................................................................18

4.2.1: FLOWCHART:...........................................................................................................19

4.2.2: ENTITY RELATIONSHIP DIAGRAM (ERD).........................................................20

4.2.3: DATA FLOW DIAGRAM (DFD):.............................................................................22

4.2.4: DATABASE DESIGN...............................................................................................26

4.2.5: USE CASE DIAGRAM:.............................................................................................28

CHAPTER: 5.................................................................................................................................29

SYSTEM IMPLEMENTATION AND TESTING......................................................................29

5.1: SOFTWARE DEVELOPMENT LIFECYCLE MODEL......................................29

5.2: CODING TOOLS:..................................................................................................29

5.2.1: FRONT-END:.............................................................................................................29

5.2.2:BACK-END:................................................................................................................30

5.3: TESTING................................................................................................................31

5.3.1 UNIT TESTING...........................................................................................................32

5.3.2 INTREGATION TESTING..........................................................................................32

5.3.3 SYSTEM TESTING.....................................................................................................33

CHAPTER 6..................................................................................................................................34

MAINTENANCE..........................................................................................................................34

CHAPTER- 7.................................................................................................................................35

FUTURE SCOPE AND CONCLUSION......................................................................................35

8
 7.1: FUTURE:................................................................................................................35

7.2: CONCLUSION:.....................................................................................................36

Bibliography..................................................................................................................37

Web Reference...............................................................................................................37

APPENDIX....................................................................................................................................38

HOME PAGE................................................................................................................38

ADD TO CART PAGE.................................................................................................39

LOGIN PAGE...............................................................................................................40

REGISTERATION PAGE............................................................................................41

ABOUT US PAGE........................................................................................................42

CONTACT US PAGE...................................................................................................43

CHECKOUT PAGE......................................................................................................44

ADMIN PANEL............................................................................................................45

9
 LIST OF FIGURES

Figure 1 Admin Module Block Diagram.......................................................................................................3

Figure 2 Manage Moderator Block Diagram................................................................................................4
Figure 3 Manage Products Block Diagram...................................................................................................5
Figure 4 Manage User Block diagram..........................................................................................................6
Figure 5 Manage User Block Diagram..........................................................................................................7
Figure 6 Moderator Module Block Diagram................................................................................................7
Figure 7 User Module Block Diagram..........................................................................................................8
Figure 8 System Architechture Diagram....................................................................................................18
Figure 9 Flowchart of Online Shopping System.........................................................................................20
Figure 10 Entity Relationship Diagram Of Online Shopping (ERD).............................................................21
Figure 11 Level Diagram of Online Shopping System.................................................................................22
Figure 12 Level 0 DFD for Online shopping System...................................................................................23
Figure 13 Level 1 DFD for User..................................................................................................................24
Figure 14 Level 2 DFD for User..................................................................................................................25
Figure 15 Admin side DFD.........................................................................................................................26
Figure 16 Use case Diagram.......................................................................................................................28
Figure 17 Home Page.................................................................................................................................38
Figure 18 Add to Cart View........................................................................................................................39
Figure 19 Login Page..................................................................................................................................40
Figure 20 Registeration Page.....................................................................................................................41
Figure 21 About us page............................................................................................................................42
Figure 22 Contact Us Page.........................................................................................................................43
Figure 23 Checkout Page...........................................................................................................................44
Figure 24 Admin Panel...............................................................................................................................45

LIST OF TABLE
Table 1 Time chart or Gantt Chart.............................................................................................................28
Table 2 System Testing..............................................................................................................................44

10
 CHAPTER-1 INTRODUCTION

1.1: INTRODUCTION
As a general definition, e-commerce is the branch of business that includes all activities, which
directly or indirectly are involved in exchanging goods or services. The trade can be held
between businesses or individuals, eventually achieving the goal of transferring goods from
producers to consumers. When information and communication technologies are applied to
support these activities, we are referring to electronic commerce, also commonly known as e-
commerce.

Currently there are four major types of e-commerce, classified based on the roles involved in the
trade: business-to-business (B2B), business-to-consumer (B2C),consumer-to-business (C2B) and
consumer-to-consumer (C2C). Other lesser types may involve roles such as government,
employee or manager in order to define more specialized e-commerce business models. Though
any of those types can be considered to be subtypes of the four major models.

By keeping in mind, the importance of e-commerce website is increasing day by day, we decided
to develop the e-commerce website named”Nepali Store”. In this web based e-commerce
application , we provide the service to the consumer to search for required products, and buy it
as their needs. Consumer have facility to give the review to our online shopping website
including their shopping experience.

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 mobile notification is sent to the customer as soon as the order is placed.

1.2: HISTORY OF E-COMMERCE

Originally, electronic commerce meant the facilitation of commercial transactions electronically,

using technology such as Electronic Data Interchange (EDI) and Electronic Funds Transfer
(EFT). These were both introduced in the late 1970s, allowing businesses to send commercial
documents like purchase orders or invoices electronically.

11
Online shopping, a form of electronic commerce, In 1979 Michael Aldrich, an English inventor,
connected a modified 26" color domestic television to a real-time transaction processing
computer via a domestic telephone line and invented online shopping. The first recorded B2B
was Thomson Holidays 1981 the first recorded B2C was Gateshead SIS/Tesco in 1984. The
world's first recorded online home shopper was Mrs. Jane Snowball, 72, of Gateshead, England
in May 1984. During the 1980s Aldrich sold many systems mainly in the UK including Ford,
Peugeot, General Motors and Nissan. The Nissan system of 1984/5 was revolutionary. It enabled
a car buyer on a dealer's lot to both buy and finance the car, including credit check, online.
Aldrich invented both the online shopping system and the business rationale for using it. His
1980s systems were as fast as 2010 internet shopping systems. They used dial-up and leased
telephone lines as broadband was not available. From the 1990s onwards, electronic commerce
would additionally include enterprise resource planning systems (ERP), data mining and data
warehousing.

An early example of many-to-many electronic commerce in physical goods was the Boston
Computer Exchange, a marketplace for used computers launched in 1982. An early online
information marketplace, including online consulting, was the American Information Exchange,
another pre-Internet online system introduced in 1991.

The Internet became popular worldwide around 1994 when the first internet online shopping
started; it took about five years to introduce security protocols and DSL allowing continual
connection to the Internet. By the end of 2000, many European and American business
companies offered their services through the World Wide Web. Since then people began to
associate a word "ecommerce" with the ability of purchasing various goods through the Internet
using secure protocols and electronic payment services.

1.3: DESCRIPTION OF PROJECT

In this e-commerce website any member can register and view available products. Only
registered member can purchase multiple products regardless of quantity. ContactUs page is
available to contact Admin for queries. There are three roles available: Visitor, User and Admin.

•Visitor can view available products.

•User can view and purchase products.

•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. Admin can ship order to user based on order placed by sending
confirmation mail.

1.3.1: MODULES:
The system after careful analysis has been identified to be presented with the following modules
and roles. The modules involved are:

12
  Administrator
 Moderators
 Users

1.3.1.1 ADMINISTRATOR:

The administrator is the super user of this application. Only admin have access into this admin
page. Admin may be the owner of the shop. The administrator has all the information about all
the users and about all products. This module is divided into different sub-modules.

1. Manage Moderators

2. Manage Products

3 .Manage Users

4. Manage Orders

Figure 1 Admin Module Block Diagram

13
MANAGE MODERATOR

Figure 2 Manage Moderator Block Diagram

 Add Moderator

Only admin is having the privilege to add a moderator. A moderator can be considered as a
staff who manages the orders or owner of a group of products.

 Block moderator
Admin can restrict a moderator from managing the orders by blocking them. Admin can
unblock a blocked user if needed.

 Remove Moderator
Admin has privilege to delete a moderator who was added.

 Search moderator:

14
 All existing moderators can be viewed by the administrator as a list. If there is number of
moderators and admin need to find one of them, the admin can search for a moderator by
name.

MANAGE PRODUCTS

Figure 3 Manage Products Block Diagram

 Add Products
The shopping cart project contains different kind of products. The products can be
classified into different categories by name. Admin can add new products into the
existing system with all its details including an image.

 Delete Products
Administrator can delete the products based on the stock of that particular product.

 Search Products
Admin will have a list view of all the existing products. He can also search for a
particular product by name.

15
MANAGE USER

Figure 4 Manage User Block diagram

 View Users
The admin will have a list view of all the users registered in the system. Admin can view
all the details of each user in the list except password.

 Add Users
Admin has privileges to add a user directly by providing the details.

 Delete & Block Users

Administrator has a right to delete or block a user. The default status of a new user
registered is set as blocked. The admin must accept the new user by unblocking him.

16
MANAGE ORDERS

Figure 5 Manage User Block Diagram

 View Order
Administrator can view the Orders which is generated by the users. He can verify the
details of the purchase.

 Delete Order
Admin can delete order from the orders list when the product is taken for delivery

1.3.1.2 MODERATORS

Figure 6 Moderator Module Block Diagram

A moderator is considered as a staff who can manage orders for the time being. As a future
update moderator may give facility to add and manage his own products . Moderators can reduce

17
the work load of admin .Now moderator has all the privilege an admin having except managing
other moderators. He can add products and users. He can also check the orders and edit his
profile.

 Manage Products
 Manage Users
 Manage Orders

1.3.1.3 USERS

Figure 7 User Module Block Diagram

 Registration
A new user will have to register in the system by providing essential details in order to
view the products in the system. The admin must accept a new user by unblocking him

 Login
A user must login with his user name and password to the system after registration.

 View Products

18
 User can view the list of products based on their names after successful login. A detailed
description of a particular product with product name, products details, product image
and price can be viewed by users

 Search Products
Users can search for a particular product in the list by name.

 Add to cart
The user can add the desired product into his cart by clicking add to cart option on the
product .He can view his cart by clicking on the cart button. All products added by cart
can be viewed in the cart. User can remove an item from the cart by clicking remove.

 Submit Cart
After confirming the items in the cart the user can submit the cart by providing a delivery
address. On successful submitting the cart will become empty

 History
In the history the user will have a view of pending orders.

 Edit Profile
The user can view and edit the profile.

1.4: PROBLEM STATEMENT

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.

 Traditional way of shopping was time consuming and costly.

 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
 No proper review and rating features on other existing system.
 Lack of enough Security and Privacy of user data in existing system .

19
1.5: OBJECTIVES

The main objectives of e-commerce website are as follows:

 To develop an easy to use web based interface where users can search for products,
view a complete description of the products and order the products
 To provide search engine that provides an easy and convenient way to search for
products specific to their needs. The search engine would list a set of products based on
the search term and the user can further filter the list based on various parameters.
 To enable user can view the complete specification of the product along with various
images and also view the customer reviews of the product. They can also write their
own reviews.
 To Provide Interactive interface through which a user can interact with different areas of
application easily.
 To provide strong security and provide the user data a strong privacy

1.6: SCOPES

 This system can be implemented to any shop in the locality or to multinational branded
shops having retail outlet chains.
 The system recommends a facility to accept the orders 24*7 and a home delivery system
which can make customers happy.
 Strong security applied in our System can gain more trust in our e-commerce website.
 There is strong security in our system.
 Cost of product are made cheaper as possible than other e-commerce website
 Viewers have previleged to create their own account

1.6: LIMITATION

As we know that, no systems are perfect. There are also some flaws on our system which are as
follows:

20
  International Payment systems are currently unavailable due to policy of Nepal
Government.
 Only limited types of materials are available till now.
 Tracking system is currently unavailable.

CHAPTER:2 LITERATURE REVIEW

As we know that, People have to go to the shop directly to buy the required items or products. It
was time consuming as well as more costly. In traditional way of shopping we have to visit
different shop to buy different types of products. There was also problem of not finding required
items in local market. By addressing, these entire problems in traditional way of shopping,
people were searching some alternatives, development of the online or electronic type of
shopping was started. Different types of e-commerce website or online shopping website are
developed till now, to make people easy to shop online through e-commerce website and order
required products. This system also provides home delivery service to provide the required item
to the residence of costumer.

Now, people began to demand different types of e-commerce website which can fulfill their
enhanced and easy type of online shopping experience. By analyzing the increasing craze of
people towards e-commerce, we decided to develop a e-commerce website based on Nepal with
enhanced way and with more quality of service. Till now, there are different types of e-
commerce website based on Nepal. But, there are also lack of different service and enough
quality required by costumers. Our e-commerce website is developed in such way to fulfill the
required service of online shopping by addressing all the problems faced by costumers. Our
system is designed in such way to provide quality products and quality service to costumer. Our
main objective is to satisfy the costumer on their shopping experience through our website.

Internet has major influence on the globe since it can serve billions of users all over the world.
Thousands of local and global networks including private, public, academic, business, and
government networks, all contribute to the creation of the Internet. E-commerce is
overwhelmingly affecting both national and global economy. Recent research studies indicate
that e-commerce has a positive influence on the development of countries’ overall economies,
and this contribution to economies will continue to grow (Shahriari et al., 2015). There is no
doubt that the overall sales and productivity of an organization will increase due to the trend of
this technological enhancement.

The idea of culture is very complex. E-commerce websites are always changing. The global
Internet usage is also growing considerably. Most of the e-commerce websites are in English, but
the majority of the online users are non-English speaking. Most information on the website is
presented by elements such as color, images, logos, shapes, frame, links, banner, buttons,
animation, splash windows, and white spaces (Asimionoaei, 2009; Punhani and Batra, 2014). It
is important that e-commerce website designers consider the local culture when designing the

21
website to reflect the local users’ emotions, thoughts, desires, and most importantly, the culture.
The study indicates that different countries’ e-commerce website users have diverse preferences
and motives to use global e-commerce websites (Punhani and Batra, 2014).

Although there are many other e-commerce website, there are some lack of security, reliability
and quality. We hope our system will meet the requirements of people like security, reliability
and quality in online shopping experience.

CHAPTER: 3

REQUIREMENT ANALYSIS AND FEASIBILITY ANALYSIS

3.1:REQUIREMENT ANALYSIS:

Requirement analysis is the process of precisely identification, defining and documenting the
various requirements that are related to a particular system objectives. Requirements gathering
helps in clearly understanding the needs of the users, defining the scope of project and accessing
the time scales and resources required to complete it. There are two types of requirement which
are as follows:-

 Functional requirement
 Non-Functional requirement

3.1.1: FUNCTIONAL REQUIREMENT:

In order to prove the value of the platform and identify any possible lack of functionality, the
application should have all the common features of a regular web-shop. Accordingly, it has been
considered that the initial appropriate set of functionalities for this project include those related
to browsing and purchasing products, as well as management of a customer account. The
detailed behavior expected for the web-shop is described below.

USER

 USER LOGIN

Description of feature

This feature used by the user to login into system. A user must login with his user name and
password to the system after registration. If they are invalid, the user not allowed to enter the
system.

Functional requirement

22
-Username and password will be provided after user registration is confirmed.
-Password should be hidden from others while typing it in the field

 REGISTER NEW USER

Description of feature

A new user will have to register in the system by providing essential details in order to view the
products in the system. The admin must accept a new user by unblocking him.

Functional requirement

-System must be able to verify and validate information.

-The system must encrypt the password of the customer to provide security.

 PURCHASING AN ITEM

Description of feature

The user can add the desired product into his cart by clicking add to cart option on the
product. He can view his cart by clicking on the cart button. All products added by cart
can be viewed in the cart. User can remove an item from the cart by clicking remove.
After confirming the items in the cart the user can submit the cart by providing a delivery
address. On successful submitting the cart will become empty.

Functional requirement
-System must ensure that, only a registered customer can purchase items.

ADMIN

 MANAGE USER

Description of feature

The administrator can add user, delete user, view user and block user.

 MANAGE MODERATOR

Description of feature

The administrator can add moderator, delete moderator, block moderator and search for a
moderator.

23
  MANAGE PRODUCTS

Description of feature
The administrator can add product, delete product and view product.
 MANAGE ORDERS

Description of feature

The administrator can view orders and delete orders.

Functional requirements

-The system must identify the login of the admin.

-Admin account should be secured so that only owner of the shop can access that account.

MODERATOR
Description of features

A moderator is considered as a staff who can manage orders for the time being. As a future
update moderator may give facility to add and manage his own products. Moderators can reduce
the work load of admin. Now moderator has all the privilege of an admin having except
managing other moderators. He can manage users and manage products. He can also check the
orders and edit his profile.

Functional requirement

-The system must identify the login of a moderator.

3.2.1Interface Requirements

24
This section describes how the
software interfaces with other
software products or
users for input or output.
User Interface
Application will be accessed
through a Browser Interface.
The interface would be
viewed best using 1024 x 768
and 800 x 600 pixels resolution
setting. The software
would be fully compatible with
Microsoft Internet Explorer for
version 6 and above.

25
No user would be able to access
any part of the application
without logging on to
the system.
4.Non Functional
Requirements
4.1. User Interfaces
Application will be accessed
through a Browser Interface.
The interface would be viewed
best using 1024 x 768 and 800 x
600 pixels resolution setting.
The software would be fully

26
compatible with Microsoft
Internet Explorer for version 6
and above. No user would be
able to access any part of the
application without logging on
to the syste
3.2.1Interface Requirements
This section describes how the
software interfaces with other
software products or
users for input or output.
User Interface
Application will be accessed
through a Browser Interface.
The interface would be
27
viewed best using 1024 x 768
and 800 x 600 pixels resolution
setting. The software
would be fully compatible with
Microsoft Internet Explorer for
version 6 and above.
No user would be able to access
any part of the application
without logging on to
the system.
4.Non Functional
Requirements
4.1. User Interfaces

28
Application will be accessed
through a Browser Interface.
The interface would be viewed
best using 1024 x 768 and 800 x
600 pixels resolution setting.
The software would be fully
compatible with Microsoft
Internet Explorer for version 6
and above. No user would be
able to access any part of the
application without logging on
to the syste
3.1.2: NON FUNCTIONAL REQUIREMENT:

 Efficency Requirement:
When an online shopping cart web application implemented customer can
purchase product in an efficient manner.

 Reliability Requirement:

29
 The system should provide a reliable environment to both customers and
owner. All orders should be reaching at the admin without any errors.

 Usability Requirement:

The web application is designed for user friendly environment and ease of use.
 Implementation Requirement:

Implementation of the system using css and html in front end with python in
django framework as back end and it will be used for database connectivity.
And the database part is developed by mysql. Responsive web designing is
used for making the website compatible for any type of screen.

 Delivery Requirement

The whole system is expected to be delivered in four months of time with a

weekly evaluation by the project guide.

3.2: FEASIBILITY ANALYSIS

After doing the project Web-shop, study and analyzing all the existing or required functionalities
of the system, the next task is to do the feasibility study for the project. All project are feasible-
given unlimited resources and infinite time.

Feasibility study includes consideration of all the possible ways to provide a Solutions to the
given problem. The proposed solution should satisfy all the user requirement and should be
flexible enough so that future changes can be easily done based on the future upcoming
requirement.

3.2.1: TECHNICAL :

This includes the study of function, performance and constraints that may
affect the ability to achieve an acceptable system. For this feasibility study, we
studied complete functionality to be provided in the system, as described in the
System Requirement Specification (SRC) and checked if everything was possible
using different of frontend and back end platform.

3.2.2: ECONOMIC FEASIBILITY:

In our web-shop, all user have facility to use this web-shop according to their budget. Searching
items and accessing to website is almost free but Charges are only applied when consumer buy
some items. Some additional charges for taxes, delivery charges are applied to the price of items

30
when consumer buy some items. Our web-shop provide the items to consumer that best matches
the technical as well as economic requirements of the consumers.

2.2.3:OPERATIONAL FEASIBILITY:

Nepali Store is targeted to all kinds of users including seller and buyers. This system aims to
drive the consumer from traditional way of shopping to digital and online type of shopping
where all kinds of material needed by all types of consumers can be sold and buy. Different types
of small business shop can collaborate with us to sell their product in our platform.

3.2.4 SCHEDULE FEASIBILITY:

The complete schedule of the system can be seen in the gantt chart. Project can be developed in
given schedule, given the right resources. The project took about twelve week to complete.

TASK Time 2020

Duratio September October November December
n
1. Problem 13 days
Identification
2. System 7 days
Requirement
Specification
3. Feasibility Study 10 days

4. System Design 30days

5. Coding 30 days

6. Implementing, 14 days
Testing
and Debugging
7. Maintenance and 16 days
Support
TOTAL

Table 1 Time chart or Gantt Chart

31
3.3 PLATEFORM SPECIFICATION

3.3.1: HARDWARE SPECIFICATION

Processor P IV

RAM 250 MB

Minimum Space Required 100 MB

Display 16 bit color

3.3.2: SOFTWARE SPECIFICATION

Operating Environment Win 2000/XP

Visual studio Code

SQLite

32
 CHAPTER-4

METHODOLOGY

4.1: SYSTEM ARCHITECTURE

System architecture difines the overall design of a system including the relationship of the sytem
components with the environment. A system architecture is the conceptual model that defines the
structure, behavior, and more views of a system. System architecture also refers to the placement
of these software components on physical machines. Two closely related components can be co-
located or placed on different machines. The location of components will also impact
performance and reliability. Our System is based on three tier architecture.

Figure 8 System Architechture Diagram

33
4.2: SYSTEM DESIGN

System design is the solution for the creation of a new system. This phase focuses on the detailed
implementation of the feasible system. It emphasis on translating design . Specifications to
performance specification . System design has two phases of development

 Logical design

 Physical design

During logical design phase the analyst describes inputs (sources), outputs(destinations),
databases (data sores) and procedures (data flows) all in a format that meets the user
requirements. The analyst also specifies the needs of the user at a level that virtually determines
the information flow in and out of the system and the data resources. Here the logical design is
done through data flow diagrams and database design. The physical design is followed by
physical design or coding. Physical design produces the working system by defining the design
specifications, which specify exactly what the candidate system must do .The programmers write
the necessary programs that accept input from the user, perform necessary processing on
accepted data and produce the required report on
a hard copy or display it on the screen

4.2.1: FLOWCHART:

A flow chart is a graphical or symbolic representation of a process. Each step in

the process is represented by a different symbol and contains a short description
of the process step. The flow chart symbols are linked together with arrows
showing the process flow direction.
Different flow chart symbols have different meanings. The most common flow
chart symbols are:
Terminator: An oval flow chart shape indicating the start or end of the process.

Process: A rectangular flow chart shape indicating a normal process flow step.
Decision: A diamond flow chart shape indication a branch in the process flow.
Connector: A small, labeled, circular flow chart shape used to indicate a jump in
the process flow.
Data: A parallelogram that indicates data input or output (I/O) for a process.
Document: Used to indicate a document or report (see image in sample flow chart below.)

34
 Figure 9 Flowchart of Online Shopping System

4.2.2: ENTITY RELATIONSHIP DIAGRAM (ERD)

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is an object, a component of data. An entity set is a collection of similar
entities. These entities can have attributes that define its properties. By defining the entities, their
attributes, and showing the relationships between them, an ER diagram illustrates the logical
structure of databases.

35
Figure 10 Entity Relationship Diagram Of Online Shopping (ERD)

36
4.2.3: DATA FLOW DIAGRAM (DFD):

A data flow diagram (DFD) maps out the flow of information for any process or system. It uses
defined symbols like rectangles, circles and arrows, plus short text labels, to show data inputs,
outputs, storage points and the routes between each destination. Data flowcharts can range from
simple, even hand- drawn process overviews, to in-depth, multi-level DFDs that dig
progressively deeper into how the data is handled. They can be used to analyze an existing
system or model a new one. Like all the best diagrams and charts, a DFD can often visually
“say” things that would be hard to explain in words, and they work for both technical and
nontechnical audiences, from developer to CEO. That’s why DFDs remain so popular after all
these years. While they work well for data flow software and systems, they are less applicable
nowadays to visualizing interactive, real-time or database-oriented software or systems.

4.2.3.1: Context Level Diagram

Request 0.0 Request

User Online Shopping Admin

System
Response Response

Figure 11 Level Diagram of Online Shopping System

37
4.2.3.2: Level 0 DFD for Online Shopping System

0.1
Request for login Check for login
Admin Admin
Response accept / reject
Login Process Response

Request for login Check for login

User
Response accept / reject Response

User

Search for product items 0.2

Check for product
Product Product mst
Manage Product Response
Response accept / reject

Response accept / reject

Request for product order 0.3

Check for order detail Order_Mst
Response accept / reject Order
Response
Request for view order

Response accept / reject

Request for payment 0.4

Check for payment
Payment Payment_Mst
Responsefor
Request accept
view /payment
reject
Response

Response accept / reject

Figure 12 Level 0 DFD for Online shopping System

38
4.2.3.3: Level 1 DFD for User

Figure 13 Level 1 DFD for User

39
4.2.3.4: Level 2 DFD for User

Figure 14 Level 2 DFD for User

40
4.2.3.5: Admin side DFD

Figure 15 Admin side DFD

41
4.2.4: DATABASE DESIGN

At present, Current mainstream databases include Oracle, MYSQL, Access, etc. The reason to
choose SQLite due to comparison with other databases, which is more lightweight than MYSQL,
and more advanced in performance of query speed and support schema than SQL SERVER.
With rapid increase of data, users and number of visitor, the system of Online Shopping is
confronting higher demand in technology and platform. In order to have better management of
data, this system uses SQLite database system, which is mainly used to storing all kinds of
related information of the commodities; the system mainly establishes the table of commodities,
orders, users, and messages

Database table structure design

The system mainly includes the table of goods, Orders, User. As shown in the following tables:

TABLE1: User Table

Field Name Data Type Character Length Primary key
User_id Varchar 20 YES
User_name Varchar 100 NO
User_email Varchar 100 NO
User_pass Varchar 50 NO
User_address Varchar 50 NO

TABLE 2: Order Table

Field Name Data Types Character length Primary Key
Customer_id Varchar 50 YES
Data_order Varchar 50 NO
Complete Varchar 50 NO
Transaction_order Varchar 50 NO
User_id Varchar 50 Foreign Key

TABLE 3. Product Table

Field Name Data Types Character Length Primary Key
Good_id Varchar 50 YES
Good_name Varchar 50 NO
Good_price Varchar 20 NO
Description Varchar 50 NO
Order_id Varchar 50 Foreign Key

42
4.2.5: USE CASE DIAGRAM:

Figure 16 Use case Diagram

43
 CHAPTER: 5

SYSTEM IMPLEMENTATION AND TESTING

5.1: SOFTWARE DEVELOPMENT LIFECYCLE MODEL

Software Development life cycle (SDLC) is a spiritual model used in project management that
defines the stages include in an information system development project, from an initial
feasibility study to the maintenance of the completed application.

The model of this project used is Waterfall model:

 Requirement Analysis
 System Design
 Implementation
 Testing
 Devlopment
 Maintenance

44
 Figure 17 Waterfall Model

5.2: CODING TOOLS:

5.2.1: FRONT-END:
The front end of a website is the part that users interact with. Everything that you see when
you’re navigating around the Internet, from fonts and colors to dropdown menus and sliders, is a
combo of HTML, CSS, and JavaScript being controlled by your computer’s browser.
A front-end is responsible for the interior design of a house that’s been built by a back-end dev.
In this online shoping system, we use html, tailwind css and little effort of JavaScript for making
front-end like login page, signinpage , home page , checkout page, contact page and so on.

HTML :

Html stands for Hyper Text Markup Language. It is the standard markup language for creating
Web pages. It describes the structure of a Web page. It consists of a series of elements. Html
elements tell the browser how to display the content. Html elements label pieces of content such
as "this is a heading", "this is a paragraph", "this is a link", etc. An HTML element is defined by
a start tag, some content, and an end tag.  

CSS:

CSS stands for Cascading Style Sheets. It describes  how HTML elements are to be displayed on

screen, paper, or in other media. It saves a lot of work. It can control the layout of multiple web
pages all at once. External stylesheets are stored in css file .CSS is the language we use to style
an HTML document. It describes how HTML elements should be displayed. CSS is used to
define styles for your web pages, including the design, layout and variations in display for
different devices and screen sizes.

JAVASCRIPT:

JavaScript is the world's most popular programming language. it is the programming language
of the Web. JavaScript is easy to learn.

45
5.2.2:BACK-END:

The back end of a website consists of a server, an application, and a database. A back-end
developer builds and maintains the technology that powers those components which, together,
enable the user-facing side of the website to even exist in the first place. In online shopping
system, for the case of backend purpose, we take the help of django framework of python and
also use SQLite for database purpose.

Python ( Django)

Python is an interpreted, high-level and general-purpose programming language. Python

provides effective framework called django. Django is a Python-based free and open-source web
framework that follows the model-view-template (MVT) architectural pattern. It is maintained
by the Django Software Foundation (DSF), an American independent organization established.
Python is used throughout, even for settings files and data models. Django also provides an
optional administrative create, read, update and delete interface that is generated dynamically
through introspection and configured via admin models.

SQLite:

SQLite is a programming language designed for querying data from a database. SQLite is an
open source relational database management system (RDBMS). We will use SQLite for the
database management for our system. SQLite is a fast, easy-to-use RDBMS being used for many
small and big businesses. SQLite is becoming so popular because of many good reasons:

 SQLite uses a standard form of the well-known SQL data language.

 SQLite is released under an open-source license. So you have nothing to pay to use it.
 SQLite is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.

5.3: TESTING

Testing is the testing process of a complete and fully integrated software product. During testing,
the system is used experimentally to ensure that the software does not fail. System testing is
performed on the entire system in the context of either functional requirement specifications
(FRS) or system requirement specification (SRS), or both. 

The aim of the system testing process was to determine the defects in our project. The program
was subjected to a set of test inputs and various observations were made and based on these
observations it will be decided whether the program behaves as expected or not. The overall

46
purpose of testing is to ensure the Smart Library meets all of its requirements. Our Project went
through three levels of testing
1.Unit testing
2. Integration testing
3. System Testing

5.3.1 UNIT TESTING

Unit testing emphasizes the verification effort on the smallest unit of software design i.e.; a
software component or module. Unit testing is a dynamic method for verification, where
program is actually compiled and executed. Unit testing is performed in parallel with the coding
phase. Unit testing tests units or modules not the whole software. I have tested each view/module
of the application individually. As the modules were built up testing was carried out
simultaneously, tracking out each and every kind of input and checking the corresponding output
until module is working correctly.

5.3.2 INTREGATION TESTING

Integration testing a system consisting of different modules is tested for problems arising from
component interaction. Integration testing should be developed from the system specification.
Firstly, a minimum configuration must be integrated and tested. In my project I have done
integration testing in a bottom up fashion i.e. in this project I have started construction and
testing with atomic modules. After unit testing the modules are integrated one by one and then
tested the system for problems arising from component interaction.

5.3.3 SYSTEM TESTING

System testing is a type of testing which is used to check whether the actual Software Product
matches expected requirements or not and to ensure that the software product is defect free. It
involves the execution of software / system components using manual or automated tools to
evaluate one or more properties of interest. The purpose pf software testing is to identify errors,
gaps or missing requirements in contrast to actual requirements.

47
S. Action Input Expected Actual Test Test Test
N Output Output Brows Resu Comme
er lt nt

1. Launch http://127.0.0.1:8000/ Nepali Nepali Mozill Pass Succesf

Applicatio Store Store a ul
n Homepage Homepage Firefo
x
2. Registerati http://127.0.0.1:8000/re Registerati Registerati Mozill Pass Successf
on input gister/ on Page on Page a ul
field filled Firefo
x
3. Registerati http://127.0.0.1:8000/re Registerati Error Mozill Faile Successf
on Input gister/ on Page a d ul
Field Firefo
empty x
3. Login http://127.0.0.1:8000/lo Login Login Mozill Pass Successf
input field gin/ page Page a ul
filled firefox
4. Login http://127.0.0.1:8000/lo Login Error Mozill Faile Successf
Input gin/ page a d ul
Filed Firefo
empty x

Table 2 System Testing

48
 CHAPTER 6

MAINTENANCE

The maintenance phase involves making changes to hardware, software, and documentation to
support its operational effectiveness. It includes making changes to improve a system’s
performance, correct problems, enhance security, or address user requirements. To ensure
modifications do not disrupt operations or degrade a system’s performance or security,
organizations should establish appropriate change management standards and procedures

Routine changes are not as complex as major modifications and can usually be implemented in
the normal course of business. Routine change controls should include procedures for requesting,
evaluating, approving, testing, installing, and documenting website modifications. Maintaining
accurate, up-to-date hardware and software inventories is a critical part of all change
management processes. Management should carefully document all modifications to ensure
accurate system inventories. Management should coordinate all technology related changes
through an oversight committee and assign an appropriate party responsibility for administering
software patch management programs. Quality assurance, security, audit, regulatory compliance,
network, and end-user personnel should be appropriately included in change management
processes. Risk and security review should be done whenever a system modification is
implemented to ensure controls remain in place.

For maintenance of the website:

1 The database has to be updated regularly according to new available information

2 Redundant and false information must be removed from the database
3 Newer version of django and SQLite can be used for up gradation of website and to improve
the overall performance of the system

49
 CHAPTER- 7

FUTURE SCOPE AND CONCLUSION

7.1: FUTURE:
The need of e-commerce of website is increasing day by day. So, we have seen very good scope
of our system in future also. We are planning to develop our e-commerce website with new
technologies that will be developed in future to provide more enhanced and quality shopping
experience to the costumers. We have tried our best to developed responsive type of e-commerce
website that can be accessed from computers as well as mobile platform with good interface.
However, There are some lacks still remaining on our sytem. To address those lacks, We are
planning to do following works as per the need of costumers:

 Mobile Application:
Nowadays , Most of the people spend their time mostly on mobile phone. So , people will
be happy to receive all type of service on their mobile phone. By analyzing this fact , we
are planning to developed mobile application of our e-commerce website .

 Addition of more types of items:

In our present sytem, we have included only some limited types of items. But in future,
we are planning to provide almost all type of items as per the demand of costumers

 Security:
We have developed our system by applying strong security measures that we can have till
now. However, there must me some security flaws, that we may not have found till now.
So, in future , we will add more security measures in our system and make more secure to
ensure the costumers safe shopping experience.

50
7.2: 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 books
online. To implement this as a web application we used django as the Technology. django has
several advantages such as enhanced performance, scalability, built-in security and simplicity.

Design and Implementation of E-Commerce Site for Online Shopping 20 To build any web
application using django we need a programming language such as python . python was the
language used to build this application. provides in-memory caching that eliminates the need to
contact the database server frequently and it can easily deploy. SQL was used as back-end
database since it is one of the most popular databases, and it provides fast data access, easy
installation and simplicity.A good shopping cart design must be accompanied with user-friendly
shopping cart application logic. It should be convenient for the customer to view the contents of
their cart and to be able to remove or add items to their cart. The shopping cart application
described in this project provides a number of features that are designed to make the customer
more comfortable. This project helps in understanding the creation of an interactive web page
and the technologies used to implement it. The design of the project which includes Data Model
and Process Model illustrates how the database is built with different tables, how the data is
accessed and processed from the tables. The building of the project has given me a precise
knowledge about how django is used to develop a website, how it connects to the database to
access the data and how the data and web pages are modified to provide the user with a shopping
cart application.

51
 REFERENCES
Bibliography
I. Alan Dennis, System Analysis and Design, 4th edition 2008, Wiley Publication
II. Roger S.Pressman, Software Engineering: A Beginner’s Guide, 7th Edition 2009,
McGraw-Hill Publication
III. P. W. Farris, N. T. Bendle, P. E. Pfeifer and D. J. Reibstein, "Marketing Metrics: The
Definitive Guide to Measuring Marketing Performance, 2010 Edition , Pearson
Education.

Web Reference
I. http://www.w3schools.com/html/defualt.asp
II. http://www.w3schools.com/css/default.asp
III. http://www.w3schools.com/js/default.asp
IV. [Online]. Available: http://www.hcltech.com/blogs/engineering-and-rd-services/multi-
vendor-marketplace-%E2%80%93-new-trend-ecommerce
V. "Shopping Cart Software Review.," 23 jan 2014. [Online]. Available: Internet:
http://shopping-cart-review.toptenreviews.com/
VI. Interspire, " “Interspire Shopping Cart Developer Documentation”
VII. "Online-Shopping in Deutschland weit verbreitet, Presseinformation. Berlin,
2009.http://www.bitkom.org/files/documents/BITKOM_Presseinfo_E-
Commerce_21_05_2009.pdf," 2009
VIII. [31] Laycock, G. T. (1993). The Theory and Practice of Specification Based Software
Testing (PostScript). Dept of Computer Science, Sheffield University, UK. Retrieved
2008-02-13.

52
 APPENDIX

HOME PAGE

Figure 18 Home Page

53
ADD TO CART PAGE

Figure 19 Add to Cart View

54
LOGIN PAGE

Figure 20 Login Page

55
REGISTERATION PAGE

Figure 21 Registeration Page

56
ABOUT US PAGE

Figure 22 About us page

57
CONTACT US PAGE

Figure 23 Contact Us Page

58
CHECKOUT PAGE

Figure 24 Checkout Page

59
ADMIN PANEL

Figure 25 Admin Panel

60