EZ-Buy (Temp # 6 & 7)

EZ-Buy
Final Year Project
Session 2018-2022
A project submitted in partial fulfillment of the degree of
BS in Software Engineering
Department of Software Engineering

Faculty of Computer Science & Information Technology
The Superior University, Lahore
Spring 2021
EZ-Buy
Type (Nature of project) [ ✓ ] Development [ ] Research [ ] R&D
Area of specialization E-Commerce
FYP ID FYP-009
Project Group Members
Sr.# Reg. # Student Name Email ID *Signature
Bsem-f18- Huraira bin Zahid Bsem-f18-135@superior.edu.pk

(i) 135 huraira
Bsem-f18- Muhammad Imran Bsem-f18-200@superior.edu.pk
(ii) 200 imran
Bsem-f17- M-Zia-ul-Haq Bsem-f17-114@superior.edu.pk

(iii) 114 zia
*The candidates confirm that the work submitted is their own and appropriate credit has been
given where reference has been made to work of others
Plagiarism Free Certificate

This is to certify that, I S/D of Muhammad Siddique, group leader of FYP under registration no
at Software Engineering Department, The Superior College, Lahore. I declare
that my FYP report is checked by my supervisor.
Date: 13/6/2022 Name of Group Leader: Huraira Bin Zahid Signature:
Name of Supervisor: Mr. Muhammad Ahmad Co-Supervisor: Mr. Saleem Zubair

Designation: Lecturer Designation: Professor
Signature: Signature:
HOD: Dr. Tehreem Masood

Signature:
Faculty of CS&IT, The Superior University Lahore, Pakistan ii

EZ-Buy
EZ-Buy
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>
Faculty of CS&IT, The Superior University Lahore, Pakistan iii

EZ-Buy
APPROVAL
PROJECT SUPERVISOR
Comments:
Name:
Date: Signature:
PROJECT MANAGER
Comments:
Date: Signature:
HEAD OF THE DEPARTMENT

Comments:
Date: Signature:
Faculty of CS&IT, The Superior University Lahore, Pakistan iv

EZ-Buy
Dedication
This work is dedicated to my parents and friends
Faculty of CS&IT, The Superior University Lahore, Pakistan v

EZ-Buy
Acknowledgements
I am really thankful to my supervisor Mr. Muhammad Ahmed who has Excellent Supervision!
Faculty of CS&IT, The Superior University Lahore, Pakistan vi

EZ-Buy
Executive Summary
This project is about to provide a platform to wholesaler/manufacturer sellers and buyers. Here
buyer can easily compare market rates and easily access wholesalers or manufacturers. Also,
wholesaler can easily increase their sale rate.
Figure EZ-Buy
Faculty of CS&IT, The Superior University Lahore, Pakistan vii

EZ-Buy
Contents
EZ-Buy ......................................................................................................................................... i
Final Year Project ........................................................................................................................ i
Session 2018-2022 ....................................................................................................................... i
BS in Software Engineering......................................................................................................... i
The candidates confirm that the work submitted is their own and appropriate credit has been
given where reference has been made to work of other.............................................................. ii
Plagiarism Free Certificate ......................................................................................................... ii
EZ-Buy ...................................................................................................................................... iii
Dedication ................................................................................................................................... v
Acknowledgements .................................................................................................................... vi
Executive Summary .................................................................................................................. vii
Chapter 1 .................................................................................................................................. xiii
Introduction .............................................................................................................................. xiii
1.1. Background ........................................................................................................................ 14
1.2. Motivations and Challenges ............................................................................................... 14
1.3. Goals and Objectives ........................................................................................................... 2
1.4. Literature Review/Existing Solutions .................................................................................. 2
1.5. Gap Analysis ........................................................................................................................ 2
1.6. Proposed Solution ................................................................................................................ 3
1.7. Project Plan .......................................................................................................................... 3
1.7.1. Work Breakdown Structure .............................................................................................. 3
1.7.2. Roles & Responsibility Matrix ......................................................................................... 4
1.7.3. Gantt Chart ........................................................................................................................ 5
1.8. Report Outline...................................................................................................................... 5
1.8.1. Summary ........................................................................................................................... 5
1.8.2 Introduction ........................................................................................................................ 5
1.8.3. Goals and Objectives ........................................................................................................ 6
1.8.4. Project Plan ....................................................................................................................... 6
1.9. Empathy Map ....................................................................................................................... 7
Chapter 2 ..................................................................................................................................... 8
Software Requirement Specifications ......................................................................................... 8
2.1. Introduction .......................................................................................................................... 9
2.1.1. Purpose.............................................................................................................................. 9
2.1.2. Document Conventions ..................................................................................................... 9
2.1.3. Intended Audience and Reading Suggestions ................................................................... 9
2.1.4. Product Scope ................................................................................................................. 10
2.2. Overall Description ............................................................................................................ 11
2.2.1. Product Perspective ......................................................................................................... 11
2.2.2. User Classes and Characteristics .................................................................................... 11
2.2.3. Operating Environment ................................................................................................... 11
2.2.4. Design and Implementation Constraints ......................................................................... 12
2.2.5. Assumptions and Dependencies ..................................................................................... 12
2.3. External Interface Requirements........................................................................................ 13
2.3.1. User Interfaces ................................................................................................................ 14
2.3.2. Hardware Interfaces ........................................................................................................ 14
Faculty of CS&IT, The Superior University Lahore, Pakistan viii

EZ-Buy
2.3.3. Software Interfaces ......................................................................................................... 14

2.3.4. Communications Interfaces ............................................................................................ 15
2.4. System Features ................................................................................................................. 15
2.4.1. System Feature 1 ............................................................................................................. 15
2.4.1.1. Description and Priority ............................................................................................... 16
2.4.1.2. Stimulus/Response Sequences ..................................................................................... 16
2.4.1.3. Functional Requirements ............................................................................................. 17
2.4.2. System Feature 2 ............................................................................................................. 17
2.4.2.1. Description and Priority ............................................................................................... 18
2.4.2.2. Stimulus/Response Sequences ..................................................................................... 18
2.4.2.3. Functional Requirements ............................................................................................. 18
2.5. Nonfunctional Requirements ............................................................................................. 19
➢ Usability ...................................................................................................................................... 19
2.5.1. Performance Requirements ............................................................................................. 20
2.5.2. Safety Requirements ....................................................................................................... 20
2.5.3. Security Requirements .................................................................................................... 20
2.5.4. Usability Requirements ................................................................................................... 20
2.5.5. Reliability Requirements ................................................................................................ 21
2.5.6. Maintainability/Supportability Requirements ................................................................. 21
2.5.7. Portability Requirements ................................................................................................ 21
2.5.8. Efficiency Requirements ................................................................................................. 21
2.6. Domain Requirements ....................................................................................................... 22
Chapter 3 ...................................................................................................................................... 23
Use Case Analysis...................................................................................................................... 23
3.1. Use Case Model ................................................................................................................. 24
3.2. Use Cases Description ....................................................................................................... 25
Chapter 4 ...................................................................................................................................... 26
System Design ........................................................................................................................... 26
4.1. Architecture Diagram......................................................................................................... 27
4.2. Domain Model ................................................................................................................... 28
4.3. Class Diagram .................................................................................................................... 29
4.4. Sequence / Collaboration Diagram .................................................................................... 30
4.5. Activity Diagram ............................................................................................................... 31
4.6. State Transition Diagram ................................................................................................... 32
4.7. Component Diagram .......................................................................................................... 33
4.8. Deployment Diagram ......................................................................................................... 34
Chapter 5 ....................................................................................................................................... 35
Implementation ............................................................................................................................. 35
5.1. Important Flow Control/Pseudo codes ........................................................................... 36
5.2. Components, Libraries, Web Services and stubs ........................................................... 37
5.3. Deployment Environment .............................................................................................. 37
5.3.1. Understand the business case .......................................................................................... 37
5.4. Tools and Techniques..................................................................................................... 39
5.4.1. Unbxd ........................................................................................................................................ 39
5.4.2. Google AdWords ....................................................................................................................... 39
Faculty of CS&IT, The Superior University Lahore, Pakistan ix

EZ-Buy
5.4.3. Optimizely ................................................................................................................................. 39

5.4.4. Search Spring............................................................................................................................. 39
5.4.5. Crazy Egg ................................................................................................................................... 40
5.4.6. Conclusion ................................................................................................................................. 40
5.5. Best Practices / Coding Standards ..................................................................................... 40
5.6. Version Control .................................................................................................................. 41
Chapter 6 ....................................................................................................................................... 42
Testing and Evaluation ................................................................................................................. 42
6.1. Use Case Testing ............................................................................................................ 43
General Test Cases for EZ-Buy ................................................................................................ 43
Product Buy Flow – Test cases for EZ-Buy ............................................................................. 44
User (Buyer) Registration – Test cases ..................................................................................... 44
Seller – Product creation Test cases.......................................................................................... 45
6.2. Equivalence partitioning ................................................................................................ 46
Guidelines for Equivalence Partitioning: .................................................................................. 46
6.3. Boundary value analysis................................................................................................. 46
6.4. Data flow testing ............................................................................................................ 47
6.5. Unit testing ..................................................................................................................... 47
6.6. Integration testing ........................................................................................................... 48
6.7. Performance testing ........................................................................................................ 48
6.8. Stress Testing ................................................................................................................. 49
Chapter 7 ....................................................................................................................................... 50
Summary, Conclusion and Future Enhancements ........................................................................ 50
7.1. Project Summary ............................................................................................................ 51
7.2. Achievements and Improvements .................................................................................. 51
1. Platform and theme ............................................................................................................... 51
2. E-commerce plugins ............................................................................................................. 51
3. Search engine optimization ................................................................................................... 52
4. Website content .................................................................................................................... 52
5. Check-out Process ................................................................................................................. 52
6. Marketing strategy ............................................................................................................... 53
1. Upsell and Cross-sell ............................................................................................................ 53
2. Close Out Slow-moving Products ......................................................................................... 54
3. Add Live Chat ....................................................................................................................... 54
4. Add a Phone Number ............................................................................................................ 55
5. Proofread Your Website ....................................................................................................... 55
7.3. Critical Review............................................................................................................... 55
7.4. Lessons Learnt................................................................................................................ 56
7.5. Future Enhancements/Recommendations ...................................................................... 56
Reference and Bibliography ......................................................................................................... 58
Appendix A: Literature Review/Existing Solutions ................................................................. 59
Appendix B: Motivations and Challenges ................................................................................ 59
Architecture Diagram................................................................................................................ 60
Appendix C: Equivalence partitioning...................................................................................... 60
Faculty of CS&IT, The Superior University Lahore, Pakistan x

EZ-Buy
List of figures
Chart 1.7.1 Gantt Chart 1 ................................................................................................................ 5
Map 1.9.1 Empathy Map 1.............................................................................................................. 7
4.1.1 Architecture Diagram 1 ........................................................................................................ 27
4.2.1 Domain Model Diagram 1 .................................................................................................... 28
4.3.1 Class Diagram 1 .................................................................................................................... 29
4.4.1 Sequence / Collaboration Diagram 1 ................................................................................... 30
4.5.1 Activity Diagram 1 ................................................................................................................ 31
4.6.1 State Transition Diagram 1................................................................................................... 32
Appendix B /Architecture Diagram 1. ........................................................................................... 61
Faculty of CS&IT, The Superior University Lahore, Pakistan xi

EZ-Buy
List of Tables
• Table 1.7.1 Work Breakdown Structure 1 ................................................................................4
Faculty of CS&IT, The Superior University Lahore, Pakistan xii

EZ-Buy
Chapter 1
Introduction
Faculty of CS&IT, The Superior University Lahore, Pakistan xiii

EZ-Buy
Chapter 1: Introduction
Mostly buyers don’t know; how to find the best wholesaler/manufacturer in the market? They
only know minimum wholesalers, can’t compare whole market rates, sometimes they have no
knowledge but dealing with resellers and don’t get good rates. Often new out of city buyers come
to find the best and genuine wholesaler to get good rates but they lost most of the time in finding
wholesaler and then got it. In some cases, new or inexperienced buyer have no good reviews
about wholesaler due to limited info. Many other Problems got the buyer in this field.
We are going to develop a web and mobile application for buyers and wholesalers to
make their job effortless like; Easy to find the best, genuine, rated and approved all wholesalers
with complete information, easy comparison, time and budget saving.
This project is effective and effortless dealing point between manufacturer/wholesaler and
buyers.
1.1. Background
1.2. Motivations and Challenges

Convenience shoppers those motivated to shop online because of convenience have the
strongest influence on scarcity, while store-oriented shoppers those who are motivated by the
need for social interaction and immediate possession of goods have the strongest influence on
consensus. Another problem faced in online shopping is issues with delivery and logistics.
Faculty of CS&IT, The Superior University Lahore, Pakistan xiv

EZ-Buy
Products are often lost or damaged while in transit, and order tracking systems are unable to
accurately locate the product. People choose the same-day. one-day or two-day delivery, paying
extra money to get their product delivered.
1.3. Goals and Objectives

The primary goal of is to reach maximum customers at the right time to increase sales and
profitability of the business. Functions of include buying and selling goods, transmitting
funds or data over the internet. Our company will provide a highly convenient service for
its consumers by allowing them to save an item in their personal shopping bag and then
purchase it at a later time
1.4. Literature Review/Existing Solutions

Our shopping indicates electronic commerce to buy products or services directly from the
seller through the Internet. Internet-based or Click and Order business model has replaced
the traditional Brick and Mortar business model.
1.5. Gap Analysis

As a starting point, you need to identify where your business is today. In some instances,
this could be a painful or scary process, but it’s a reality that needs to be faced in order for
real growth to take place. First, look at the numbers. Are your sales numbers below your
goal? Is employee or customer turnover higher than it should be? Is your supplier charging
more than you can afford? Are your marketing costs rising?
1.6. Proposed Solution

➢ We are going to develop a web and mobile application for buyers and wholesalers to
➢ On our platform buyer can easily find all wholesalers and then he will easily compare
market rates that will be easy to find the best rate, quality and manufacturer/wholesaler. New
buyer can get fast and easily awareness about wholesalers/manufacturers and also get good
rates as compare to resellers who tell lie and represent their self as wholesaler.
➢ Manufacturer/wholesaler by joining our platform can increase their sales, customer and
Faculty of CS&IT, The Superior University Lahore, Pakistan 15

EZ-Buy
also expand their business.
1.7. Project Plan

➢ 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.
1.7.1. Work Breakdown Structure

Roles & Responsibility Matrix
➢ The Purpose of the roles & Responsibility Matrix is to identify who will do what.
WBS# WBS #Activity Activity to Complete the Duration Responsible

Deliverable Deliverable (# of Team
Days) Member(s)
& Role(s)
1 Feasibility 1 Documentation 4days Huraira Bin
Study Zahid
2 System 2 Documentation 3days All Members
Analysis

EZ-Buy
3 Requirement 3 Documentation 4days Muhammad

Gathering Zia-ul-haq
4 Equipment 4 Documentation 6ays M-Imran
Validation
5 Project Plan 5 Documentation 3days All Members
6 Modeling 6 Documentation/Design 6days Huraira Bin
Zahid
Muhammad
Zia-ul-haq
7 Coding of 7 Coding 26days All Members
modules
8 Testing 8 Test plans, Test Cases 12days All Members
9 Testing 9 Training 13days M-Imran
Table 1.7.1 Work Breakdown Structure 1
1.7.2. Roles & Responsibility Matrix

Our rules and responsibility to our shopping site to care our customer and it's used to clarify
employee roles and responsibilities for each task, milestone and decision that takes place
throughout a project. The chart is designed to ensure clear communication and smooth
workflows across all parts of a team.

EZ-Buy
1.7.3. Gantt Chart
Chart 1.7.1 Gantt Chart 1
1.8. Report Outline

1.8.1. Summary
1.8.2 Introduction
Mostly buyers don’t know; how to find the best wholesaler/manufacturer in the market? They
only know minimum wholesalers, can’t compare whole market rates, sometimes they have no
knowledge but dealing with resellers and don’t get good rates. Often new out of city buyers come
to find the best and genuine wholesaler to get good rates but they lost most of the time in finding

EZ-Buy
wholesaler and then got it. In some cases, new or inexperienced buyer have no good reviews
about wholesaler due to limited info. Many other Problems got the buyer in this field.
We are going to develop a web and mobile application for buyers and wholesalers to
This project is effective and effortless dealing point between manufacturer/wholesaler and
buyers.
1.8.3. Goals and Objectives

profitability of the business. Functions of include buying and selling goods, transmitting funds or
data over the internet. Our company will provide a highly convenient service for its consumers
by allowing them to save an item in their personal shopping bag and then purchase it at a later
time.
1.8.4. Project Plan

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.
1.8.5. Conclusion
E-Commerce is not an IT issue but a whole business undertaking. Companies that use it as a
reason for completely re-designing their business processes are likely to reap the greatest
benefits. Moreover, E-Commerce is a helpful technology that gives the consumer access to
business and companies all over the world.

EZ-Buy
1.9. Empathy Map
Map 1.9.1 Empathy Map 1

EZ-Buy
Chapter 2
Software Requirement
Specifications

EZ-Buy
Chapter 2: Software Requirement Specifications

2.1. Introduction
2.1.1. Purpose
An ecommerce website caters to the exchange of goods and services for electronic transaction
of money as well as Cash-On-Delivery (COD). People can visit your website, choose the products
they like, enter the required details, make payment (or choose to pay later), and purchase
goods and services in a jiffy
2.1.2. Document Conventions

There are a set of guidelines to be followed while preparing the software requirement
specification document. This includes the purpose, scope, functional and nonfunctional
requirements, software and hardware requirements of the project. In addition to this, it
also contains the information about environmental conditions required, safety and security
requirements, software quality attributes of the project etc. A Software Requirements
Specification (SRS) is a document that describes the nature of a project, software or
application. In simple words, SRS document is a manual of a project provided it is prepared
before you kick-start a project/application. This document is also known by the names SRS
report, software document. A software document is primarily prepared for a project,
software or any kind of application.
2.1.3. Intended Audience and Reading Suggestions

2.1.3.1. Introduction:
This section offers a summary of the Split Pay project, including goals and objectives, project
scope, general system details, and some major constraints associated with the intended
platform.
ZILDOR, INC. Software Design Document88
2.1.3.2. Data Design:

Readers interested in how Split Pay organizes and handles data should consult this section, which
covers data structures and flow patterns utilized by the system.
EZ-Buy
2.1.3.3. Architectural and Component-Level Design:

This section describes the Split Pay system class by class, including interface details, class
hierarchies, performance/design constraints, process details, and algorithmic models.
2.1.3.4. User Interface Design:

This section covers all of the details related to the structure of the graphical user interface (GUI),
including some preliminary mockups of the Split Pay Android application. Readers can view this
section for a tentative glimpse of what the final product will look like.
2.1.3.5. Restrictions, Limitations, and Constraints:

This section discusses the general constraints imposed upon the project
2.1.3.6. Testing Issues:

Readers interested in the software testing process should consult this section, which offers a list
of test cases, expected responses, and other pertinent information.
2.1.3.7. Appendices:
This section includes any additional information which may be helpful to readers
2.1.4. Product Scope

profitability of the business. Functions of include buying and selling goods, transmitting
funds or data over the internet. Our company will provide a highly convenient service for
its consumers by allowing them to save an item in their personal shopping bag and then
purchase it at a later time

EZ-Buy
2.2. Overall Description

2.2.1. Product Perspective
➢ Product overview.
➢ Context & scope.
➢ Stakeholders & stakeholder analysis.
➢ Business processes & usage processes.
➢ Product requirements (including use cases)
2.2.2. User Classes and Characteristics

➢ A slick, speedy website.
➢ An easy checkout processes.
➢ Competitive shipping policies.
➢ Multiple payment options.
➢ Quality images and solid product descriptions.
➢ A mobile-friendly site design.
➢ Good customer support.
➢ Multichannel storefronts.
2.2.3. Operating Environment

➢ Enhanced Shopping Cart.
➢ Flexible Return Policy.
➢ Mobile-Friendly Website.
➢ Highly Customizable Themes.
➢ Content management system.
➢ Email Marketing tools.
➢ Social media integration.

➢ Third-party shipment integration.

EZ-Buy
2.2.4. Design and Implementation Constraints

➢ Identify Your Niche. The first step in building an e-commerce application is todecide
on your niche.
➢ Planning Essential Features.
➢ Balancing Design Elements.
➢ Platform Selection & Development.
➢ Intensive Testing.
➢ App Launch and Support.
➢
2.2.5. Assumptions and Dependencies
Assumptions
➢ They Care About You
➢ They Shop Only on Price
➢ They Know the Product
➢ They Know What They Want
➢ They Have Time for Research
➢ They Are Rational
➢ They Will Find You
➢ They Will Give You Feedback
➢ They Will Spread the Word
Dependencies
➢ Enhanced Shopping Cart.
➢ Flexible Return Policy.

EZ-Buy
➢ Mobile-Friendly Website.
➢ Highly Customizable Themes.
➢ Content management system.
➢ Email Marketing tools.
➢ Social media integration.
➢ Third-party shipment integration.
2.3. External Interface Requirements

Requirement Title:
➢ Shopping Cart Operation
Requirement Description:
➢ The shopping cart function should display all the product descriptions added by
user to theshopping cart.
➢ While displaying the product, it should get the product availability from inventory
system and product price from pricing system to display the availability and pricing
information
➢ It should allow the user to check out the product(s) in shopping cart.
Business Rationale:
➢ Provide the online users with a seamless shopping experience.
Exception Scenarios:
➢ If the selected quantity of products is not available, system
➢ Scenarios should not allow the user to check out that product. It should display
Dependencies:
➢ FR 1: Users should be logged in
➢ FR 2: Users should have selected non-zero products from search operation.

EZ-Buy
2.3.1. User Interfaces

References to GUI standards or product family style guides that are to be followed.
➢ Standards for fonts, icons, button labels, images, color schemes, field tabbing sequences,
commonly used controls, and the like.
➢ Screen layout or resolution constraints.
➢ Standard buttons, functions, or navigation links that will appear on every screen, such as a
helpbutton.
➢ Shortcut keys.
➢ Message display conventions.
➢ Layout standards to facilitate software localization.
➢ Accommodations for visually impaired users.
2.3.2. Hardware Interfaces

The logical characteristics of each interface between the software product and the hardware
components of the system' Similarly, it defines 'User Interfaces' as. 'The logical characteristics of
each interface between the software product and its users'.
Hardware requirements for insurance on internet
will be same for both parties which are as follows:
Processor: Dual Core
RAM:2 GB
Hard Disk:320 GB
NIC: For each party
2.3.3. Software Interfaces

1. Operating System: Windows10 Ultimate which
supports networking.
2. JAVA development toolkit.

EZ-Buy
3. Flutter is an open-source UI software development kit created by Google. It is used to develop

cross platform applications for Android, iOS, Linux, Mac, Windows, Google Fuchsia, Web
platform, and the web from a single codebase.
2.3.4. Communications Interfaces

The two parties should be connected by LAN or WAN for the communication purpose
2.4. System Features

They included such items as: reliability, availability, serviceability, security, scalability,
maintainability. Unlike the functional requirements (which are usually narrative in form), the
system qualities usually consist of tables of specific metrics that the system must meet to be
accepted
1. Combining data streams
2. Splitting data streams
3. Modifying data streams
2.4.1. System Feature 1

➢ Organization: It implies structure and order
➢ Interaction: It refers to the manner in which each component functions with other
components of the system.
➢ Interdependence
➢ Integration: It refers to the holism of systems.
➢ Central Objective:

EZ-Buy
2.4.1.1. Description and Priority

➢ Modern customers have more options on where to purchase a product than ever before.
With that knowledge, it’s changed their outlook on shopping. For example, it’s no longer based
on the product itself but the shopping experience instead.
➢ Updating inventory regularly
➢ Easy-to-use search functionality
➢ Personalized experience
➢ A mobile-friendly website
➢ Rich content and product information
➢ Varied payment and delivery options
2.4.1.2. Stimulus/Response Sequences

This section provides requirement overview of the system.
➢ Registration: If customer wants to buy the product, then he/she must be registered,
unregistered user can’t go to the shopping cart.
➢ Login: Customer logins to the system by entering valid user id and password for the
shopping.
Changes to cart means the customer after login or registration can make order or cancel
order of the product from the shopping cart
➢ Payment: For customer there are many types of secure billing will be prepaid as debtor
credit card, post-paid as after shipping, checker bank draft. The security will provide by
the third party like HBL etc.
➢ Report generation: After all transaction the system can generate a portable document file
and send one copy to the customer email-address and other one from the system
database to calculate the monthly transaction.
➢ Logout: After the payment or surf the product the customer will logged out

EZ-Buy
2.4.1.3. Functional Requirements

Various functional modules can be implemented by the system. it provides a
requirement overview of the system.
➢ Master Maintenance: -
Is the system that maintains the detail of the products and their hierarchy attributes
(size, weight, cost etc.) The two main components of master maintenance are as
follows.
➢ Product master: -
It’s included the information of the products, item no, size, categories etc. it’s is also
the admin of vendor or seller where they can put the information of the products in
websites.
➢ Price master: -
Only for the price of the products and applicable discount of the products.
2.4.2. System Feature 2

7 Key Features Online Shoppers Demand from an Online Store
➢ A mobile website options
➢ Free or competitive shipping options
➢ Advanced navigation and search functions
➢ Superior photos and image options
➢ A detailed product description
➢ Customer reviews of the product
➢ A fast guest check-out option

EZ-Buy
2.4.2.1. Description and Priority

Modern customers have more options on where to purchase a product than ever before. With
that knowledge, it’s changed their outlook on shopping. For example, it’s no longer based on the
product itself but the shopping experience instead.
Updating inventory regularly
➢ Easy-to-use search functionality
➢ Personalized experience
➢ A mobile-friendly website
➢ Rich content and product information
➢ Varied payment and delivery options
2.4.2.2. Stimulus/Response Sequences

This section provides requirement overview of the system.
Registration: If customer wants to buy the product, then he/she must be registered,
unregistered
user can’t go to the shopping cart.
Login: Customer logins to the system by entering valid user id and password for the shopping.
Changes to cart means the customer after login or registration can make order or
cancelorder of the product from the shopping cart
Payment: For customer there are many types of secure billing will be prepaid as debtor
credit card, post-paid as after shipping, checker bank draft. The security will provide by
the third party like HBL etc.
Report generation: After all transaction the system can generate a portable document
file and send one copy to the customer email-address and other one from the system
database to calculate the monthly transaction.
Logout: After the payment or surf the product the customer will logged out
2.4.2.3. Functional Requirements
Various functional modules can be implemented by the system. it provides a
requirementoverview of the system.
➢ Master Maintenance: -
EZ-Buy
Is the system that maintains the detail of the products and their hierarchy
attributes (size, weight, cost etc.) The two main components of master
maintenance are as follows.
➢ Product master: -
It’s included the information of the products, item no, size, categories etc. it’s is
also the admin of vendor or seller where they can put the information of the
products in websites.
➢ Price master: -
Only for the price of the products and applicable discount of the products.
2.5. Nonfunctional Requirements
➢ Usability:
No matter the size of your business, you want your website to be intuitive and easy- to-use. It
takes about 0.05 seconds for users to figure out if your website is worth their time and
attention. So, you’ll definitely want to work on your homepage design, calls-to-action, and
easy checkout to get past those milliseconds of doom.Website usability is also defined by
➢ how easily a user can achieve their goal in a single page visit.
➢ how quickly they perform the tasks in the store.
➢ how memorable and intuitive the design is.
➢ number and time of errors users make.
NFR #1 examples:
A customer should easily find the right product for them, understand what problems it solves, and
make a purchase without contacting us.

EZ-Buy
No multistep checkout: users must reach the “add to cart” button in one step from PDP.
2.5.1. Performance Requirements

➢ In order to maintain an acceptable speed at maximum number of
➢ uploads allowed from a particular customer as any number of users
➢ can access to the system at any time.
➢ Also, the connections to the servers will be based on the attributes of the
➢ user like his location and server will be working 24X7 times.
2.5.2. Safety Requirements

Use a Secure Computer
Make sure you are using a secure internet connection and not sending private information out
on public computers that could contain malware. Additionally, make sure that your anti-
virus, operating system, and web browser have the latest versions and security patches installed.
2.5.3. Security Requirements

Make sure you're buying from a real online address.
Access secure shopping sites that protect your information.
Stay safe using secure connections.
Update your browser, antivirus and operating system.
Keep an eye on your bank account.
Use antivirus protection for your PC.
2.5.4. Usability Requirements

The ease with which a visitor can read, navigate, and interact with a web application or website.
When setting up an eCommerce venture, the usability of your site is of vital importance to you;
a site which is not easy to navigate around will experience a higher bounce rate and a lower
conversion rate. Because of this ecommerce websites should always be heavily concerned with
usability, and should strive to improve the user experience whenever possible.

EZ-Buy
2.5.5. Reliability Requirements

➢ Online shopping websites operating in a large number in the country to provide variety
of dresses, shoes and other accessories to the citizens without any hassle have made their
life quite easier but reliability of many of these websites is still a question.
➢ A number of fake websites created on the names of famous brands are making the buyers
fool by showing the original branded pictures of dresses and other stuff with high charges
but delivering substandard stuff, replicas and copied items.
➢ “Those fake websites are even using exact names and logos of the famous brands that
anyone can hardly feel the difference between original and the fake ones”, Saman Rabab,
a regular online buyer said.
2.5.6. Maintainability/Supportability Requirements

➢ Speed.
➢ Mobile-friendliness.
➢ Ease of use in the checkout flow.
➢ Personalization.
➢ Accessibility.
2.5.7. Portability Requirements

Design Constraints:
➢ Both inputs should be reviewed for validation and messages should be issued for
erroneousresults. ...
➢ The information given by the vendor during registration should be maintained in the
database.
2.5.8. Efficiency Requirements

➢ Younger Consumers. The younger generations, Millennials and Generation Z, were
brought up in the digital age.
➢ Smartphones.
➢ Store Boredom.

EZ-Buy
➢ New Online Retailers.

➢ Credit Cards.
2.6. Domain Requirements

➢ STORE. As a simple, memorable domain extension, STORE is the perfect ending for
eCommerce URLs.
➢ SUPPLY.
➢ SHOP.
➢ BOUTIQUE. If you sell high-end or specialty merchandise,
➢ GIFTS. Perfect in time for the holidays, the

EZ-Buy
Chapter 3
Use Case Analysis

EZ-Buy
Chapter 3: Use Case Analysis

1. Identify who is going to be using the website.
2. Pick one of those users.
3. Define what that user wants to do on the site.
4. For each use case, decide on the normal course of events when that user is using the
site.
5. Describe the basic course in the description for the use case.
3.1. Use Case Model

EZ-Buy
3.2. Use Cases Description

Web Customer actor uses some web site to make purchases online. Top level use
cases are View Items, Make Purchase and Client Register. View Items use case could be
used by customer as top-level use case if customer only wants to find and see some
products. This use case could also be used as a part of Make Purchase use case. Client
Register use case allows customer to register on the web site, for example to get some
coupons or be invited to private sales. Note, that Checkout use case is included use
case not available by itself - checkout is part of making purchase.

EZ-Buy
Chapter 4
System Design

EZ-Buy
Chapter 4: System Design

4.1. Architecture Diagram
4.1.1 Architecture Diagram 1

EZ-Buy
4.2. Domain Model
4.2.1 Domain Model Diagram 1

EZ-Buy
4.3. Class Diagram
4.3.1 Class Diagram 1

EZ-Buy
4.4. Sequence / Collaboration Diagram
4.4.1 Sequence / Collaboration Diagram 1

EZ-Buy
4.5. Activity Diagram
4.5.1 Activity Diagram 1

EZ-Buy
4.6. State Transition Diagram
4.6.1 State Transition Diagram 1

EZ-Buy
4.7. Component Diagram
4.7.1 Component Diagram 1

EZ-Buy
4.8. Deployment Diagram
4.8.1 Deployment Diagram 1

EZ-Buy
Chapter 5
Implementation

EZ-Buy
Chapter 5: Implementation
1. Choose a niche and develop a business plan.
2. Select your domain name.
3. Pick your ecommerce website builder.
4. Design the look of your online store.
5. Add products to your online shop.
6. Set up shipping.
7. Market your online store.
8. Launch your online store.
5.1. Important Flow Control/Pseudo codes
➢ Shopping Item (item)
➢ Properties
➢ Product Object (the PID of the product is also the primary key of the shopping
item) product
➢ Purchase quantity (user input) Count
➢ Subtotal (Purchase quantity * Product Unit Price (product. getshop_price)) subtotal

Count*product.getprice ()
Cart (CART)
➢ Properties
➢ Map collection (product PID, shopping Item) map (String, item)
➢ Total amount (sum of subtotals for all shopping items, initial value of 0) total=0.0
➢ Action

EZ-Buy
➢ Add shopping items to Cart
5.2. Components, Libraries, Web Services and stubs
When we began searching for web components libraries to compose for our project, I initially
thought “Where can I find a cool lit-html lib?” This is because I’ve yet to grok the full potential of
web components. This is a framework/library way of thinking. It’s like asking, I want a cool html
library. All web components are interoperable by definition to play well with others.
Custom components and widgets that build on the Web Component standards, will work across
modern browsers, and can be used with any JavaScript library or framework that works with
HTML.
5.3. Deployment Environment

5.3.1. Understand the business case.
While it would seem that moving to the cloud is a technology exercise, the reality is that
the core business case should be understood as to the potential benefits of cloud
computing. This is the first step because there is no need to continue if we can’t make a
business case. Things to consider include the value of shifting risk to the cloud computing
provider, the value of on-demand scaling (which has a high value in the world of
ecommerce), and the value of outsourcing versus in-sourcing.
5.3.2. Understand your existing data, services, processes, and applications.
You start with what you have, and cloud computing is no exception. You need to have a
data-level, service-level, and process-level understanding of your existing problem domain,
also how everything is bundled into applications. I covered this in detail in my book, but the
short answer is to break your existing system or systems down to a functional primitive of
any architectural components, or data, services, and processes, with the intention being to
assemble them as components that reside in the cloud and on-premise.

EZ-Buy
5.3.3. Select a provider.
Once you understand what you need, it’s time to see where you’re going. Selecting a cloud
computing provider, or, in many cases, several, is much like selecting other on-premise
technologies. You line up your requirements on one side, and look at the features and
functions of the providers on the other. Also, make sure to consider the soft issues such as
viability in the marketplace over time, as well as security, governance, points-of-presence
near your customers, and ongoing costs.
5.3.4. Migrate.
In this step we migrate the right architectural assets to the cloud, including transferring
and translating the data for the new environment, as well as localizing the applications,
services, and processes. Migration takes a great deal of planning to pull off successfully
the first time.
5.3.5. Deploy.
Once your system is on the cloud computing platform, it’s time to deploy it or turn it into a
production system. Typically, this means some additional coding and changes to the core
data, as well as standing up core security and governance systems. Moreover, you must do
initial integration testing, and create any links back to on-premise systems that need to
communicate with the newly deployed cloud computing systems.
5.3.6. Test.
Hopefully, everything works correctly on your new cloud computing provider. Now you
must verify that through testing. You need to approach this a few ways, including functional
testing, or how your ecommerce system works in production, as well as performance
testing, testing elasticity of scaling, security and penetration testing.
If much of this sounds like the process of building and deploying a more traditional on-
premise system, you’re right. What does change, however, is that you’re not in complete

EZ-Buy
control of the cloud computing provider, and that aspect of building, deploying, and
managing an ecommerce system needs to be dialed into this process.
5.4. Tools and Techniques
5.4.1. Unbxd
Unbxd is a relatively new entry to the e-commerce marketer’s toolkit. Unbxd provides
intelligent, ‘context-aware’ site search and personalized recommendations. Unbxd is a one-
stop product discovery solution and gives marketers and merchandisers the tools to
optimize their site search and product recommendations.
5.4.2. Google AdWords
Organic search is an effective method for traffic acquisition and sales promotion, but its
conversion rates are not always high. Google AdWords is one tool that can help you
promote your e-commerce site more efficiently and also boost sales. You can create and
run ads using this tool in Google’s Search and advertising network.
5.4.3. Optimizely
This is one of the best tools for A/B testing, which is used to measure the impact of changes
of two variants in design. A/B testing helps you to test different layouts, colors, and copy on
your e-commerce website to determine what converts best and leads to higher revenue.
5.4.4. Search Spring
This is a popular site navigation solution that helps online retailers to connect shoppers with
relevant products and boost sales. Some of the largest eCommerce brands like Stanley Black

EZ-Buy
& Decker have used Search Spring for their advanced website search and category
navigations.
5.4.5. Crazy Egg
Heat-map and scroll-map are important insights for e-commerce sites. Tools like Crazy
Egg allow you to see which parts of your web pages your visitors click on so that you can
gain a better understanding of how your visitors engage with your online store. Such
insights play a significant role in improving your conversion rates.
5.4.6. Conclusion
These are only a few e-commerce tools that should be a part of your plan and there are
more. All of these tools have potentials to increase your sales in their own way.
However, remember that what works for one online store may not work for you. You need
to therefore experiment with various e-commerce tools and find out what works best for
your business. Don’t be afraid to test!
5.5. Best Practices / Coding Standards
Here are the top 9 coding standards best practices:
1. Know Why You're Using It
2. Choose the Best Coding Standard for Your Industry
3. Use Coding Rules and Follow Recommendations

EZ-Buy
4. Describe the Intent Behind the Rule
5. Update Coding Standards with Care
6. Consider Open vs. Closed Standards
7. Prioritize Coding Rules
8. Plan for Rule Deviations
9. Educate Programmers
5.6. Version Control
We just wondering if anyone can shine a light on why there isn't version control on anything
in the asset folder. For example, we were working on some scss. liquid and js. liquid files in
the asset folder, and the client would like to revert back to a prior version of the files that
were worked on, but alas, there is no version control on these files. It just seems odd that
there is version control on some of the files, but not all.

EZ-Buy
Chapter 6
Testing and Evaluation

EZ-Buy
Chapter 6: Testing and Evaluation

In EZ-Buy the test & evaluation (T&E) is the process by which a system or components are
compared against requirements and specifications through testing. The results are evaluated to
assess progress of design, performance, supportability, etc. Developmental test and evaluation
(DT&E) is an engineering tool used to reduce risk throughout the acquisition cycle. Operational
test and evaluation (OT&E) is the actual or simulated employment, by typical users, of a system
under realistic operational conditions
6.1. Use Case Testing

General Test Cases for EZ-Buy
1. Verify that the user is able to navigate through all the products across different categories.
2. Verify that all the links and banners are redirecting to correct product/category pages and
none of the links are broken.
3. Verify that the company logo is clearly visible.
4. Verify that all the text – product, category name, price, and product description are clearly
visible.
5. Verify that all the images – product and banner are clearly visible.
6. Verify that category pages have a relevant product listed specific to the category.
7. Verify that the correct count of total products is listed on the category pages.
8. Search – Verify that on searching all the product satisfying the search criteria are visible
on the search result page.
9. Search – Verify the more relevant product for the search term is displayed on the top for
a particular search term.
10. Search – Verify that count of products is correctly displayed on the search result page for
a particular search term.
11. Filtering – Verify that filtering functionality correctly filters products based on the filter
applied.
12. Filtering – Verify that filtering works correctly on category pages.
EZ-Buy
13. Filtering – Verify that filtering works correctly on the search result page.
14. Filtering – Verify that the correct count of total products is displayed after a filter is
applied.
15. Sorting – Verify that all the sort options work correctly – correctly sort the products based
on the sort option chosen.
16. Sorting – Verify that sorting works correctly on the category pages.
17. Sorting – Verify that sorting works correctly on the search result page.

EZ-Buy
Sorting – Verify that sorting works correctly on the pages containing the filtered result, after
applying filters.
Sorting – Verify that product count remains intact irrespective of sorting option applied.
Product Buy Flow – Test cases for EZ-Buy

1. Verify that on the product page, the user can select the desired attribute of the product
e.g., size, color, etc.
2. Verify that the user can add to cart one or more products.
3. Verify that users can add products to the Wishlist.
4. Verify that the user can buy products added to the cart after signing in to the application
(or as per the functionality of the website).
5. Verify that the user can successfully buy more than one product that was added to his/her
cart.
6. Verify that the user cannot add more than the available inventory of the product.
7. Verify that the limit to the number of products a user can by is working correctly by
displaying an error message and preventing the user from buying more than the limit.
8. Verify that the delivery can be declined for the places where shipping is not available.
9. Verify that the Cash on Delivery option of payment is working fine.
10. Verify that the different pre-paid methods of payments are working fine.
11. Verify that product return functionality works fine.
User (Buyer) Registration – Test cases

1. Verify that all the specified fields are present on the registration page.
2. Verify that the required/mandatory fields are marked with * against the field.
3. Verify that for better user interface dropdowns, radio buttons and checkboxes, etc fields
are displayed wherever possible instead of just textboxes
4. Verify the page has both submit and cancel/reset buttons at the end.
5. Verify that clicking submits button after entering all the required fields, submits the data

EZ-Buy
to the server.
6. Verify that clicking cancels/reset button after entering all the required fields, cancels the
submit request, and reset all the fields.
7. Verify that whenever possible validation should take place at client side

EZ-Buy
8. Verify that not filling the mandatory fields and clicking the submit button will lead to
validation error.
9. Verify that not filling the optional fields and clicking the submit button will still send data
to the server without any validation error.
10. Check the upper limit of the textboxes.
11. Check validation on the date and email fields (only valid dates and valid email Ids should
be allowed.
12. Check validation on numeric fields by entering alphabets and special characters.
13. Verify that leading and trailing spaces are trimmed.
14. Verify that entering blank spaces on mandatory fields leads to validation error.
15. Verify that after making a request to the server and then sending the same request again
with the same unique key will lead to server-side validation error.
Seller – Product creation Test cases

1. Verify that authenticated sellers get access to product creation panels specific to the
authorized categories.
2. Verify that the product creation panel is working fine for single product creation.
3. Verify that the product creation panel is working fine for multiple product creation.
4. Verify that the maximum product creation limit for the seller is working fine, limiting
the seller to create more than the desired number of products.
5. Verify panel validation for checking mandatory fields.
6. Verify that duplicate product creation is restricted through the panel.
7. Verify that seller can update the information and price of existing products.
8. Verify that products created by sellers get visible on the website after a certain period
of time.
9. Verify that updates made by the seller get visible on the website after a certain period
of time.

EZ-Buy
6.2. Equivalence partitioning

Equivalence Partitioning Method is also known as Equivalence class partitioning (ECP). It is a
software testing technique or black-box testing that divides input domain into classes of data,
and with the help of these classes of data, test cases can be derived. An ideal test case identifies
class of error that might require many arbitrary test cases to be executed before general error is
observed.
In equivalence partitioning, equivalence classes are evaluated for given input conditions.
Whenever any input is given, then type of input condition is checked, then for this input
conditions, Equivalence class represents or describes set of valid or invalid states.
Guidelines for Equivalence Partitioning:

1. If the range condition is given as an input, then one valid and two invalid equivalence
classes are defined.
2. If a specific value is given as input, then one valid and two invalid equivalence classes are
defined.
3. If a member of set is given as an input, then one valid and one invalid equivalence class is
defined.
4. If Boolean no. is given as an input condition, then one valid and one invalid equivalence
class is defined.
6.3. Boundary value analysis

Boundary Value Testing is one of the popular software testing mechanisms, where testing of data
is done based on boundary values or between two opposite ends where the ends may be like
from start to end, or lower to upper or from maximum to minimum. This testing process was
introduced to select boundary values that came from the boundary based on the inputs at
different ends of testing values. This black box testing strategy was introduced after equivalence
class partitioning where the partition of classes takes place first followed by a partition at the
boundaries.
1. The testing is an analysis testing process that does testing practices at the boundaries of
the partition covering all the testing defects where equivalence testing alone was

EZ-Buy
difficult to handle those defects.

2. This testing machine is in conjunction with an equivalence testing mechanism that
provides valid testing scenarios when there is ordered partition and the data consists of
numeric format.
3. The boundary values of such a testing mechanism are identified by the values present at
the extreme boundaries, i.e. minimum and maximum value.

EZ-Buy
4. This is used mainly to analyze the testing at the partition boundaries and also to detect
anomaliesthat may occur during testing cases.
5. The black box testing techniques are helpful for detecting any errors or threats that
happened at the boundary values of valid or invalid partitions rather than focusing on
the center of the input data.
6.3 Data flow testing

• The programmer can perform numerous tests on data values and variables. This type of
testing isreferred to as data flow testing.
• It is performed at two abstract levels: static data flow testing and dynamic data flow testing.
• The static data flow testing process involves analyzing the source code without executing it.
• Static data flow testing exposes possible defects known as data flow anomaly.
• Dynamic data flow identifies program paths from source code.
6.4 Unit testing

Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation. This
testing methodology is done during the development process by the software developers and
sometimes QA staff.
A unit test typically comprises of three stages: plan, cases and scripting and the unit test itself. In
the first step, the unit test is prepared and reviewed. The next step is for the test cases and scripts
to be made, then the code is tested.
Test-driven development requires that developers first write failing unit tests. Then they write
code and refactor the application until the test passes. TDD typically results in an explicit and
predictable code base.
Each test case is tested independently in an isolated environment, as to ensure a lack of
dependencies in the code. The software developer should code criteria to verify each test case,
and a testing framework can be used to report any failed tests. Developers should not make a

EZ-Buy
test for every line of code, as this may take up too much time. Developers should then create
tests focusing on code which could affect the behavior of the software being developed.
Unit testing involves only those characteristics that are vital to the performance of the unit under
test. This encourages developers to modify the source code without immediate concerns about
how such changes might affect the functioning of other units or the program as a whole. Once
all of the units in a program have been found to be working in the most efficient and error-free
manner possible, larger components of the program can be evaluated by means of integration
testing. Unit tests should be performed frequently, and can be done manually or can be
automated.
6.5 Integration testing

Integration Testing is the process of testing the connectivity or data transfer between the couple
of units tested modules. It is AKA I&T (Integration & Testing) or String Testing
It is sub divided into Big Bang Approach, Top-Down Approach, Bottom-Up Approach and
Sandwich or Hybrid Integration Approach (Combination of Top Down and Bottom Up). This
process is carried out by using dummy programs called Stubs and Drivers. Stubs and Drivers do
not implement the entire programming logic of the software module but just simulate data
communication with the calling module.
Objectives of integration testing include:
1. To reduce risk
2. To verify whether the functional and non-functional behaviors of the interfaces are as designed
and specified
3. To build confidence in the quality of the interfaces
4. To find defects (which may be in the interfaces themselves or within the components or systems)
5. To prevent defects from escaping to higher test levels
6.6 Performance testing

Load testing is an effective way to measure your website performance against various
parameters under huge user traffic conditions. Load testing is done by simulating a high number
of virtual users performing different actions on your website. User actions are guided by creating

EZ-Buy
simple user scripts in the load testing environment. Load testing gives useful information about
memory utilization, CPU utilization, disk I/O, load balancers, page issues, etc.
An e-commerce website has more chances of going down under high traffic due to the nature of
browsing and transactions happen on it. And that’s a negative impact on revenue as well as
credibility. For example, if you are running an end-of-season sale and don’t test your website for
the expected number of users during the sale, your users may experience downtime, slow
loading, and failed transactions. This can totally ruin your sales goal.
E-commerce websites require load testing to make sure that users on your website experience
smooth experience in high traffic scenarios and able to make purchases without any trouble.
Load testing for an e-commerce website is equivalent to business risk mitigation. It identifies and
resolves all bottleneck issues that can be a blocker for sales during peak traffic times.
6.7 Stress Testing

Stress testing (sometimes called torture testing) is a form of deliberately intense or thorough
testing used to determine the stability of a given system, critical infrastructure or entity. It
involves testing beyond normal operational capacity, often to a breaking point, in order to
observe the results.
Software commonly used in stress testing
• Aida
• IBM Teleprocessing Network Simulator
• IBM Workload Simulator
• Intel processor diagnostic test
• Intel Burn Test
• Linux (AVX)
• Memtest86+ – memory
• OCCT
• Passmark Burn-in
• Prime95, and derivatives such as HyperPi – CPU/heat
• Siege
• S&M
• Tsung - free software tool
EZ-Buy
Chapter 7
Summary, Conclusion and
Future Enhancements

EZ-Buy
Chapter 7: Summary, Conclusion & Future Enhancements
7.0 Project Summary

7.1 Achievements and Improvements

Achievements of EZ-Buy are given below:
1. Platform and theme

Selecting an appropriate platform is the first important step you have to do to construct a sales-
driven e-commerce site. There are different platforms to look over: WordPress, Magento,
Shopify, Joomla, Drupal, Zen Cart, OpenCart, and so forth.
WordPress is viewed as a standout amongst the best platforms for e-commerce websites. These
days, WordPress isn’t utilized for blogging; it is additionally utilized for news magazine, portfolio
and internet business purposes. WordPress effectively coordinates e-commerce themes and
plugins to alter the presence of the frontend and functionality in the backend, and in this manner
boost e-commerce functionalities.
2. E-commerce plugins
E-commerce plugins are basic for any online store. In general, they help with adding a shopping
store to your site, introducing payment gateways, and monitoring sales performance.
There are a few plugins which empower the full functionality of an e-commerce website, for
example, WP online business, WooCommerce, Shopp, Ecwid, and so on. We propose you pick

EZ-Buy
WooCommerce for designing an Internet shopping cart, assigning products, and executing the
check-out process. WooThemes additionally offer some extraordinary augmentations and
additional items. Another great choice is WP internet business.
3. Search engine optimization

Sales are unquestionably the essential reason for running an internet business site. If you need
to expand your sales and outpoint your rivals, SEO is an unquestionable need. Search Engine
Optimization encourages your webpage to show up when somebody looks for your product, and
in this manner increases your visibility and the possibility of conversion. The higher your position
on the list items page, the more potential clients are come to.
4. Website content
Ensure that your data is exact, exceptional and accommodating. Your customers need a
reasonable, detailed and easy-to-understand content, so attempt not utilizing long sentences or
scholarly terms in item portrayals, bolster areas or some other piece of the site. “Words generally
can’t do a thousand words”. Rather than an entire bunch of content, using images will make the
site all the more engaging and enthusiastic.
Remember, a steady and unmistakable message is the thing that transforms a typical business
into a genuine brand. If you need to be heard, your image should talk in a one of a kind voice.
5. Check-out Process
Primarily, focus on budget allocation. Ensure that you have recorded down all the anticipated
costs; for example: facilitating charges, permit expenses, and securing costs through publicizing
(Facebook Ads, Google Ads, and so on). At that point, characterize a definitive cost for everything.
At long last, explain what number of stages in the check-out process you need your customers to
go through.
Try not to “challenge” your customers with a long and confounding registration process. Nobody
likes to experience pages and pages before achieving the confirmation section. As indicated by a
review by The Big Picture, 11% of purchasers surrender their shopping cart because of an intricate
check-out process.

EZ-Buy
6. Marketing strategy
When your site is prepared, you should pursue a few steps to carry it closer to your clients. There
are various approaches to start and run a showcasing methodology: without anyone else’s input
or through a promoting office, natural or paid pursuit, Google Ads or Facebook Ads, Mobile
Search or Desktop Search, and so on. Every strategy has its very own Pros and Cons. Contingent
upon your scale and business type, pick the most appropriate ones.
A well-structured site with a key advertising plan will result in better rush hour gridlock, brand
personality, and an expansion in deals. Thus, exploit accessible online marketing tools, for
example, mobile and desktop applications, social media applications and systems.
The facts demonstrate that building a web-based business site requires a great deal of time,
exertion, and cost. In any case, if you know the basic procedures, a great web-based business
webpage can cultivate deals and connect more long term clients than you at any point
anticipated.
We need some Improvements in EZ-Buy to enhance ecommerce business are given below:
1. Upsell and Cross-sell

Nearly every EZ-Buy platform offers some way for online sellers to feature related products.
If a small or mid-sized EZ-Buy business owner or manager is overlooking this opportunity, either
not bothering to add upsell and cross-sell products or not putting a lot of thought into the
products they list, sales could be missed.
Upselling is the act of encouraging a customer to purchase a product similar to the one she is
looking at, but which has either a higher selling price or a higher margin. Cross-selling is the
process of encouraging shoppers to buy complementary products after they have purchased or
indicated that they have an intention to purchase.
Practically, upsell and cross-sell offers in EZ-Buy are made on product detail pages or during the
checkout process.

EZ-Buy
Using sales affinity (relationship) data, make an effort to pick upsell and cross-sell products that
are likely to encourage shoppers to add items to their shopping cart, boosting the value of their
order.
Often online sellers can improve upsells and cross-sells without any change in software. It just
takes a little bit of research.
2. Close Out Slow-moving Products

Products that sit on your shelf and sell very slowing can, in many instances, reduce cash flow and
actually slow down a business’s growth. It is for this reason that many brick-and-mortar retailers
have closeout sales, and it is the reason that ecommerce business ought to have closeout sales
too.
Look for products in your inventory that:
• Sell-through less than once each quarter;
• Are seasonal;
• Are perishable;
• Have been replaced with a newer model or version;
• Or that have not sold online in a month or more.
Offer these items at special prices on your site, in marketplaces, or even in classifieds like
Craigslist.
Depending on the size of your business, closing out aging inventory might take an afternoon or,
perhaps, a few days, but the result should be a cash boost and the opportunity to get in new,
faster selling items.
3. Add Live Chat

Live chat allows customers to ask questions or express concerns just as they are in the process of
making a buying decision, potentially boosting conversion rates or improving the customer
shopping experience for your business.
What’s more, once you have live chat, you will find that you can discover common problems with
your site or common customer concerns. Addressing these common problems and concerns can
lead to an overall increase in conversions.

EZ-Buy
Adding live chat to most ecommerce platforms is a relatively simple task that requires very little
technical expertise. What’s more, live chat can also be very inexpensive, and it can be turned on,
if you will, when it is convenient.
4. Add a Phone Number

For many of the same reasons that live chat can help merchants connect with customers and
improve conversion rates, the simple act of adding a phone number to your website can also help
with some customers.
Merchants might also list “call center hours” or use a simple script to hide the phone number on
the site when no one is available.
In most cases, even if you are getting a new phone number, this is a tiny improvement that you
can have done in a few hours at most.
5. Proofread Your Website

Even the largest of companies can make errors on their ecommerce websites and taking just a
few minutes to proofread your site can make a significant improvement.
In fact, sometimes you may not even know how bad it is until to start to proofread. Simply take
a few minutes each day to use your website in a way similar to how your customers would use
the site, reading your way through each page.
It may also be necessarily to try to get to your site from other sites or search engines in order to
ensure that customers are seeing what you expect.
As an example, at the time of writing, brick-and-click retailer Fred Meyer’s bike tire category was
not necessarily working as the retailer probably hoped.
Critical Review
The nature and future of electronic commerce is considered. Four areas of the new economy and
its effects on retailers are explained; first the extent to which the emergence of new electronic
channels to market has led to distinctive means of businesses differentiation, secondly how
business-to-business companies use electronic channels to improve their supply chain, thirdly
how companies are dealing with organizational changes, and lastly the future of electronic-
commerce is considered.

EZ-Buy
Lessons Learnt
• EZ-Buy is built on repeat customers. Even though you are online, you can still foster long-
term relationships.
• Word of mouth really works online. Most of Zappos’ new customers come from offline
word of mouth.
• Don’t compete on price.
• Make sure your web site inventory is 100% accurate. Customer expectations can be
shattered if you don’t deliver what they saw available on your web site.
• Centrally locate your distribution to speed shipping and delivery times.
• Customer Service is an investment, not an expense. The relationships that you form via
great service will pay for themselves in repeat business.
• Start small & stay focused. Don’t try to get too big, too fast.
• Don’t be secretive. Don’t worry about competitors.
• Actively manage your company culture. Zappos has a culture book they give to employees
and they immerse every new hire in the call center and distribution world for several
weeks before they begin their “real” jobs.
• Be wary of so-called experts. You know your company and your culture best. As Hamlet
said, “To thine own self be true.”
Future Enhancements/Recommendations
There have never been as many opportunities in the EZ-Buy/ecommerce industry, nor has there
been as much competition. Plummeting return on ad spend is pushing brands to prioritize
customer lifetime value and promote brand loyalty.
Trust is the main currency of the future of EZ-Buy. Brands must be transparent, authentic, and
readily available to their customers, especially where online consumers spend most of their time:
on social media. Social ecommerce trends are at the center of online shopping for tomorrow’s
consumer, with brands investing in video and live shopping.

EZ-Buy
Direct-to-consumer (DTC) companies are also investing in online communities to humanize their
brands, increase customer retention, and overcome skyrocketing advertising costs.
Thriving in this new ecommerce landscape will require unique insight and action. We conducted
extensive research with hundreds of DTC brands and thousands of consumers to identify the
most important EZ-Buy trends for 2022, as well as the strategies and products your business
needs to stay ahead of the competition.

EZ-Buy
Reference and
Bibliography
Reference and Bibliography
[1] M. Sher, M. Rehman, “E-Commerce” Conference name/Journal Name, Edition, Volume,

Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] Internet with a different site
[3] Standards Customer Council 2015, Customer Architecture for Mobile

http://www.cloud-council.org/deliverables/cloud-customer-architecture-for-mobile.htm
[4] Standards Customer Council 2016, Cloud Customer Architecture for IoT, Version
http://www.cloud-council.org/deliverables/cloud-customer-architecture-for-iot.htm
[5] Accenture Interactive, “Today’s Shopper Preferences: Channels, Social Media, Privacy and
the Personalized Experience,” (November 2012),
http://bit.ly/MrUBPf
[6] Ecommerce functional requirements for its planning and execution

https://elogic.co/blog/functional-and-non-functional-requirements-for-ecommerce-
websites/

EZ-Buy
Appendix
Appendix A: Literature Review/Existing Solutions

Our shopping indicates electronic commerce to buy products or services directly from the seller
through the Internet. Internet-based or Click and Order business model has replaced the
traditional Brick and Mortar business model.
Appendix B: Motivations and Challenges

Convenience shoppers those motivated to shop online because of convenience have the
strongest influence on scarcity, while store-oriented shoppers those who are motivated by the
need for social interaction and immediate possession of goods have the strongest influence on
consensus. Another problem faced in online shopping is issues with delivery and logistics.
Products are often lost or damaged while in transit, and order tracking systems are unable to
accurately locate the product. People choose the same-day. one-day or two-day delivery, paying
extra money to get their product delivered.

EZ-Buy
Appendix C: Equivalence partitioning
Equivalence Partitioning Method is also known as Equivalence class partitioning (ECP). It is a

software testing technique or black-box testing that divides input domain into classes of data,
and with the help of these classes of data, test cases can be derived. An ideal test case identifies
class of error that might require many arbitrary test cases to be executed before general error is
observed.
In equivalence partitioning, equivalence classes are evaluated for given input conditions.
Whenever any input is given, then type of input condition is checked, then for this input
conditions, Equivalence class represents or describes set of valid or invalid states.

EZ-Buy
Splash Screen

EZ-Buy

EZ-Buy

EZ-Buy
Login

EZ-Buy
Profile

EZ-Buy
Register Account

EZ-Buy
OTP Verification

EZ-Buy
Forgot Password

EZ-Buy
Login Successfully

EZ-Buy
Main Screen

EZ-Buy
Your Cart

EZ-Buy
User Profile

EZ-Buy
Product page

EZ-Buy (Temp # 6 & 7)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EZ-Buy (Temp # 6 & 7)

Uploaded by

Copyright:

Available Formats

EZ-Buy

Final Year Project

A project submitted in partial fulfillment of the degree of

Department of Software Engineering

Type (Nature of project) [ ✓ ] Development [ ] Research [ ] R&D

Area of specialization E-Commerce

Project Group Members

Sr.# Reg. # Student Name Email ID *Signature

Bsem-f18- Huraira bin Zahid Bsem-f18-135@superior.edu.pk

Bsem-f17- M-Zia-ul-Haq Bsem-f17-114@superior.edu.pk

Plagiarism Free Certificate

Date: 13/6/2022 Name of Group Leader: Huraira Bin Zahid Signature:

Name of Supervisor: Mr. Muhammad Ahmad Co-Supervisor: Mr. Saleem Zubair

HOD: Dr. Tehreem Masood

Faculty of CS&IT, The Superior University Lahore, Pakistan ii

Faculty of CS&IT, The Superior University Lahore, Pakistan iii

HEAD OF THE DEPARTMENT

Faculty of CS&IT, The Superior University Lahore, Pakistan iv

This work is dedicated to my parents and friends

Faculty of CS&IT, The Superior University Lahore, Pakistan v

Faculty of CS&IT, The Superior University Lahore, Pakistan vi

Faculty of CS&IT, The Superior University Lahore, Pakistan vii

Faculty of CS&IT, The Superior University Lahore, Pakistan viii

2.3.3. Software Interfaces ......................................................................................................... 14

Faculty of CS&IT, The Superior University Lahore, Pakistan ix

5.4.3. Optimizely ................................................................................................................................. 39

Faculty of CS&IT, The Superior University Lahore, Pakistan x

Chart 1.7.1 Gantt Chart 1 ................................................................................................................ 5

Map 1.9.1 Empathy Map 1.............................................................................................................. 7

4.1.1 Architecture Diagram 1 ........................................................................................................ 27

4.2.1 Domain Model Diagram 1 .................................................................................................... 28

4.3.1 Class Diagram 1 .................................................................................................................... 29

4.4.1 Sequence / Collaboration Diagram 1 ................................................................................... 30

4.5.1 Activity Diagram 1 ................................................................................................................ 31

4.6.1 State Transition Diagram 1................................................................................................... 32

Appendix B /Architecture Diagram 1. ........................................................................................... 61

Faculty of CS&IT, The Superior University Lahore, Pakistan xi

Faculty of CS&IT, The Superior University Lahore, Pakistan xii

Faculty of CS&IT, The Superior University Lahore, Pakistan xiii

1.2. Motivations and Challenges

Faculty of CS&IT, The Superior University Lahore, Pakistan xiv

1.3. Goals and Objectives

1.4. Literature Review/Existing Solutions

1.5. Gap Analysis

1.6. Proposed Solution

Faculty of CS&IT, The Superior University Lahore, Pakistan 15

also expand their business.

1.7. Project Plan

1.7.1. Work Breakdown Structure

WBS# WBS #Activity Activity to Complete the Duration Responsible

Faculty of CS&IT, The Superior University Lahore, Pakistan 16

3 Requirement 3 Documentation 4days Muhammad

Table 1.7.1 Work Breakdown Structure 1

1.7.2. Roles & Responsibility Matrix

Faculty of CS&IT, The Superior University Lahore, Pakistan 17

1.7.3. Gantt Chart

Chart 1.7.1 Gantt Chart 1

1.8. Report Outline

Faculty of CS&IT, The Superior University Lahore, Pakistan 18

1.8.3. Goals and Objectives

1.8.4. Project Plan

Faculty of CS&IT, The Superior University Lahore, Pakistan 19