COMSATS University Islamabad

Sahiwal, Pakistan

My Fashion Swap

A project presented to

COMSATS University Islamabad Sahiwal, Pakistan

In partial fulfillment

of the requirement for the degree of

Master of Computer Science (2017-2019)

By

Amna Rafique FA17-MCS-003

Aqsa Aziz FA17-MCS-004
Mariyam Malik FA17-MCS-015

Supervisor
Mr. Taimor Sajjad
 DECLARATION
We hereby declare that this software, neither whole nor as a part has been copied out from any
source. It is further declared that we have developed this software and accompanied report
entirely on the basis of our personal efforts. If any part of this project is proved to be copied
out from any source or found to be reproduction of some other. We will stand by the
consequences. No Portion of the work presented has been submitted of any application for any
other degree or qualification of this or any other university or institute of learning.

Amna Rafique Aqsa Aziz

--------------------------- ---------------------------

Mariam Malik

-----------------------------

i
 CERTIFICATE OF APPROVAL

It is to certify that the final year project of MCS “E-commerce online shopping portal (My
Fashion Swap)” was developed by

Amna Rafique (CIIT/FA17-MCS/B13-003), Aqsa Aziz (CIIT/FA17-MCS/B13-004) and

Mariyam Malik (CIIT/FA17-MCS/B13-015) under the supervision of “Mr. Taimor Sajjad”
and that in his opinion; it is fully adequate, in scope and quality for the degree of Masters in
Computer Sciences.

---------------------------------------

Supervisor
Mr. Taimor Sajjad
Lecturer, CUI, Sahiwal

---------------------------------------

External Examiner
Dr. Sohail Jabbar
Assistant Professor
National Textile University Faisalabad

---------------------------------------

Head of Department

(Department of Computer Science)

Dr. Javed Furzand

ii
 Executive Summary
Internet is the rapidest growing media during the past decade. Especially, online shopping is a
rapidly growing e-commerce area. Online stores are usually available 24 hours a day, and many
consumers have Internet access both at work and at home. A successful web store is not just a
good-looking website with dynamic technical features, listed in many search engines. This
study aims to establish a preliminary assessment, evaluation and understanding of the
characteristics of online shopping. Although the benefits of online shopping are considerable,
when the process goes poorly it can create a thorny situation. A few problems that shoppers
potentially face include identity theft, faulty products, and the accumulations of spyware, as
well as the precautions to be taken are studied in this paper.

iii
 Acknowledgement
All praise is to Almighty Allah who bestowed upon us a minute portion of His boundless knowledge
by virtue of which we were able to accomplish this challenging task.

We are greatly indebted to our project supervisor “Mr. Taimor Sajjad”. Without their personal
supervision, advice and valuable guidance, completion of this project would have been doubtful. We
are deeply indebted to them for their encouragement and continual help during this work.

And we are also thankful to our parents and family who have been a constant source of encouragement
for us and brought us the values of honesty & hard work.

Amna Rafique Aqsa Aziz

----------------- ----------------

Mariam Malik

------------------

iv
 Abbreviations

HTML Hypertext markup language

CSS Cascading style sheet

OSP Online shopping portal

MFS My fashion swap

v
 Table of Contents
Chapter#1 Introduction ................................................................................................ 1
1.1 Brief Introduction ................................................................................................................................. 1

1.1.1 Product Perspective....................................................................................................................... 1

1.1.2 Product Functions ......................................................................................................................... 1

1.1.2.1 Products .................................................................................................................................... 1

1.1.2.2 Registered Member ................................................................................................................... 2

1.1.2.3 Admin ....................................................................................................................................... 2

1.1.2.4 Data ........................................................................................................................................... 2

1.1.2.5 Product Title & Image .............................................................................................................. 2

1.1.2.6 Product Display page ................................................................................................................ 2

1.1.2.7 View Cart .................................................................................................................................. 3

1.1.2.8 Registration ............................................................................................................................... 3

1.1.2.9 User Login ................................................................................................................................ 3

1.1.2.10 My Orders ............................................................................................................................. 3

1.2 Design methodology and software process model ................................................................................ 3

1.2.1 Design methodology ..................................................................................................................... 3

1.3 Relevance to Course Modules .............................................................................................................. 4

1.4 Project Background............................................................................................................................... 4

1.5 Literature Review ................................................................................................................................. 4

1.5.1 Analysis from Literature Review .................................................................................................. 5

1.6 Methodology and Software Lifecycle for This Project ......................................................................... 5

1.6.1 Rationale behind Selected Methodology ...................................................................................... 5

Chapter #2 Problem Definition .................................................................................... 8

2.1 Definition .............................................................................................................................................. 8

2.2 Problem Statement ................................................................................................................................ 8

2.3 Deliverables and Development Requirements ...................................................................................... 8

vi
 2.3.1 Project Deliverables ...................................................................................................................... 8

Chapter # 3 Requirement Analysis ............................................................................ 11

3.1 Use Cases Diagram of the system....................................................................................................... 11

3.2 Detailed Use Case ............................................................................................................................... 13

3.2.1 Use Case of the customer in below that interact with the system ............................................... 15

3.3 Function requirements ........................................................................................................................ 17

3.4 Non-Function requirement .................................................................................................................. 17

3.5 Sequence diagram of all the Use Cases .............................................................................................. 17

3.5.1 Sequence diagram of all the Use Cases ...................................................................................... 19

Chapter # 4 Design and Architecture ........................................................................ 21

4.1 System Architecture ............................................................................................................................ 21

4.2 Data Representation ............................................................................................................................ 22

4.3 Process Flow/Representation .............................................................................................................. 23

4.4 Design Models .................................................................................................................................... 23

Chapter # 5 Implementation ...................................................................................... 26

5.1 User Interface...................................................................................................................................... 26

5.2 User View ........................................................................................................................................... 28

Chapter # 6 Testing and Evaluation .......................................................................... 33

6.1 System testing ..................................................................................................................................... 33

6.2 Unit Testing ........................................................................................................................................ 33

6.2.1 Functional Testing ...................................................................................................................... 35

6.2.2 Integration Testing ...................................................................................................................... 36

6.3 Manual Testing ................................................................................................................................... 37

Chapter # 7 Conclusion and Future Work ................................................................ 39

7.1 Conclusion .......................................................................................................................................... 39

7.2 Future Work ........................................................................................................................................ 39

vii
 List of Figures

Figure 1.1 Software Process Model ...................................................................................................................... 6

Figure 3.1 System use case ................................................................................................................................. 11
Figure 3.2 Use Case of the administrator ........................................................................................................... 14
Figure 3.3 Use Case of the customer .................................................................................................................. 15
Figure 3.4 Use Case of the visitor....................................................................................................................... 16
Figure 3.5 Sequence Diagram ............................................................................................................................. 18
Figure 3.6 Sequence diagram of the customer .................................................................................................... 19
Figure 4.1 System Architecture .......................................................................................................................... 21
Figure 4.2 Class Diagram ................................................................................................................................... 22
Figure 4.3 Data flow ........................................................................................................................................... 23
Figure 5.1 Admin Panel ...................................................................................................................................... 26
Figure 5.2 Family Order ..................................................................................................................................... 26
Figure 5.3 Add Products ..................................................................................................................................... 27
Figure 5.4 Customer Order ................................................................................................................................. 27
Figure 5.5 Signup Form ...................................................................................................................................... 28
Figure 5.6 Home Page ........................................................................................................................................ 28
Figure 5.7 Men's Items ....................................................................................................................................... 29
Figure 5.8 Women's Items .................................................................................................................................. 29
Figure 5.9 Items Description .............................................................................................................................. 30
Figure 5.10 Shipping Detail ................................................................................................................................ 30
Figure 5.11 Family/Friend Shipping Detail ........................................................................................................ 31
Figure 5.12 Family Cart Items ............................................................................................................................ 31

viii
 List of Tables

Table 6.1 Login ................................................................................................................................................... 33

Table 6.2 Signup ................................................................................................................................................. 34
Table 6.3 Add to Cart ......................................................................................................................................... 34
Table 6.4 View Item Details ............................................................................................................................... 35
Table 6.5 Order ................................................................................................................................................... 35
Table 6.6 Login ................................................................................................................................................... 36
Table 6.7 Integration Testing .............................................................................................................................. 37

ix
Chapter # 1
Introduction
1. Introduction
1.1 Brief Introduction
The online shopping system is fast gaining media for to sale or purchase items from anywhere and
anytime. It is basically based on Internet; it is related with B2C (Business to Customer). It can not only
save the operating costs of enterprises as well as save the time of customer to go shopping at mall and
it is increasing the efficiency of business.
if we want to buy anything it may be cloths or accessories, then we need to go shopping mall and search
for product. Ask to others to know the details about the product which we want to buy. Need to wait in
a queue. Our project will help to simplify these problems by providing all information in one place. In
this project we achieve the main goal to provide maximum output and remove above difficulties faced
by women and men.
1.1.1 Product Perspective
This system allows the customer’s to maintain their cart for add or remove the product over the
internet. This system provides an easy to solution customer’s to buy the product without go to the shop
and also shop owner to sale the product.
OSP(online shopping portal) is aimed towards the vendors who want to reach out to the maximum
cross-section of customer and common people who can be potential customer. This project envisages
bridging the gap between the seller, the retailer and the customer. OSP should be user-friendly, quick
to learn, and reliable software for the customers. OSP is intended to be a stand-alone product and should
not depend on the availability of other software. It should run on both UNIX , windows , Mac book
based platform.
1.1.2 Product Functions
1.1.2.1 Products
• Products name and catalogue number (Unique)
• Its details or specification
• Size picker (Drop down).
• Quantity picker (Drop down).
• Color Picker (Drop down)
• Availability
• Gallery

1
 • Zoom View
• Customer review
• Delivery Options.
Once customer decided to buy item they can add to Cart (Zen Cart). When customer goes for
checkout registration required.
1.1.2.2 Registered Member
• Login to site
• My Profile
• Manage Account
• My Orders
• Buy Product (Checkout)
• Logout
1.1.2.3 Admin
• Login
• Administrator User Management
• Product Attribute Management
• Product Management
• Price Chart Management
• Banner Manager
• Order Manager
• Shipping Management
1.1.2.4 Data
Home Page
View Website Logo, Banners or Slideshow which are integrated with Home Page. View list of
Latest Products available with details like.
1.1.2.5 Product Title & Image
View links for Login and Sign Up.
Clicking on any link, User will navigate that particular Page.
1.1.2.6 Product Display page
• Displays products
• Product Name & Unique product number
• Click on image will display information of product as well as choice of different sizes if
available

2
 • View the details of the products, with Image on Product.
• Product size, Image also customer able to zoom in and zoom out the product
• Add to cart.
1.1.2.7 View Cart
After added to the shopping cart with small product image, subtotal and shopping amount. In view carts
link to Update and checkout, link to see entire shopping cart, remove product from cart and update
quantity and recalculate subtotal.
1.1.2.8 Registration
This section allows New Users to create new registration account on the Site Fill the registration form
with all required fields Enter Profile details like name, email id, password Enter address details like
Country, State and Zip Code Submit Form.
1.1.2.9 User Login
This section allows User to enter the website by adding login details created during registration. Enter
authenticated Email Address and Password to login. A link for Forgot Password. Recover password
through mail.
New User? Sign up link available
* After creating login, the Customer enters the account with authenticated username and password and
can perform the following tasks: * My Account
Personal Information
Change Name, Login, E-mail Address, or Password
Manage Address Information
1.1.2.10 My Orders
View all Orders
View order no/ order date/ amount/ quantity
1.2 Design methodology and software process model
1.2.1 Design methodology
Microsoft Visio 2013
Microsoft visual studio 2013
Dreamweaver
HTML (source code)
PHP MY SQL
JSP

3
1.3 Relevance to Course Modules
Modules:
Admin
Customer
visitor
order item
1.4 Project Background
Online shopping is defined as purchasing items from Internet retailers as opposed to a shop or store.
Buying books at Amazon.com & other websites instead of your local book store is an example of online
shopping.
Online shopping or e-shopping is a form of electronic commerce which allows consumers to directly
buy goods or services from a seller over the Internet using a web browser. Alternative names are: e-
web-store, e-shop, e-store, Internet shop, web-shop, web-store, online store, online storefront and
virtual store. Mobile commerce (or m-commerce) describes purchasing from an online retailer's mobile
optimized online site or app.
An online shop evokes the physical analogy of buying products or services at a bricks-and-mortar
retailer or shopping center; the process is called business-to-consumer (B2C) online shopping. In the
case where a business buys from another business, the process is called business-to-business (B2B)
online shopping. The largest of these online retailing corporations are Alibaba, Amazon.com and eBay.
Retail success is no longer all about physical stores. This is evident because of the increase in retailers
now offering online store interfaces for consumers. With the growth of online shopping, comes a wealth
of new market footprint coverage opportunities for stores that can appropriately cater to offshore market
demands and service requirements.

1.5 Literature Review

Shopping online has never been so easy. With the flourishing numbers of online merchants, people
nowadays have various choices to do their shopping. Big companies such as eBay and amazon.com
have introduced many values added features to help the customers to decide what to shop for. With
features such as price comparison, product photos and user reviews, consumers can shop easily and
smartly without even going to the stores and having such a hard time looking for the products they
want. All they have to do are just browse for the product they want in the website and within a few
clicks they are off. Such simplicity is what makes online shopping appealing for consumers. The
question is, why do many people still deny to shop online? Well, for most people, privacy and security

4
issues are their concerns. Hence, here I will discuss customers’ perception of privacy and security
issues, the reality of such issues and ways to avoid those issues, all based on some trustworthy sources
I have found.

1.5.1 Analysis from Literature Review

Shopping online has never been so easy. With the flourishing numbers of online merchants, people
nowadays have various choices to do their shopping. Big companies such as eBay and amazon.com
have introduced many values added features to help the customers to decide what to shop for. With
features such as price comparison, product photos and user reviews, consumers can shop easily and
smartly without even going to the stores and having such a hard time looking for the products they
want. All they have to do are just browse for the product they want in the website and within a few
clicks they are off. Such simplicity is what makes online shopping appealing for consumers. The
question is, why do many people still deny to shop online? Well, for most people, privacy and security
issues are their concerns. Hence, here I will discuss customers’ perception of privacy and security
issues, the reality of such issues and ways to avoid those issues, all based on some trustworthy sources
I have found.
In this project the drawbacks of other websites like Alibaba , Amazon.com , eBay etc.

• First of all online payment problem is solve in this project.

• 3D view of the project is provided.
• Family and friend order are introduced.
• Best quality.
• No privacy issues.

1.6 Methodology and Software Lifecycle for This Project

1.6.1 Rationale behind Selected Methodology
Software process model
For our proposed application we have to use the method of Incremental approach which is best suitable
for such kinds of applications. Because of the following benefits from it:
▪ Generates working software quickly and early during the software life cycle.
▪ More flexible less costly to change scope and requirements.
▪ Easier to test and debug during a smaller iteration.

5
▪ Each iteration is an easily managed milestone.
▪ Due to iteration each phase complete within time period.

Figure 1.1 Software Process Model

6
 Chapter #2
Problem Definition
2. Problem Definition
2.1 Definition
If we want to buy anything it may be cloths or accessories, then we need to go shopping mall and search
for product. Ask to others to know the details about the product which we want to buy. Need to wait in
a queue.
• Reservation order.
• 3D view of products
• Exact location of the customer
Our project will help to simplify these problems by providing all information in one place.
This system allows the customers to maintain their cart to add or remove the product over the internet.
2.2 Problem Statement
In current scenario, if we want to buy anything it may be cloths or accessories then we need to go
shopping mall and search for product. Ask to others to know the details about the product which we
want to buy. Need to wait in a queue. There is no online shopping portal that’s specific for women.
Reduce time and effort of customers.
2.3 Deliverables and Development Requirements
We are responsible to create an Online Shopping Software System for our client Metro Super Stores.
The main idea of online shopping is not just in having a good-looking website that could be listed in a
lot of search engines or the art behind the site. It’s not only just about disseminating information,
because it is also about building relationships and making money. Organizations that want to keep
their customers or gain new ones should try to get rid of all mistakes and be more appealing to be more
desirable for online shoppers.
2.3.1 Project Deliverables
The products of the project will be:
Management & Quality:
M1 – Project Brief
M2 – Project Initiation Document
M3 – Highlight Reports
M4 – End of Project Report
Business:
B1 – Communications plan
B2 – Questionnaire (to support information gathering & ensure consistency)

8
B3 – Report for Project Board on current requirements/arrangements, and areas identified for further
investigation/potential change
B4 – Report for Executive Board with recommendations for change
B5 – Implementation proposals
Actual Product of the project:
An user-friendly Online Shopping Software System
The major deliverables are broken down in the project plan into smaller deliverables and activities.
User documentation
User training

9
 Chapter #3
Requirement Analysis
 3. Requirement Analysis
3.1 Use Cases Diagram of the system
Here is a use case that represent the whole system, in which customer, visitor, administrator interact
with each other

Figure 3.1 System use case

Use Case Name: Place Order, whole system working

Actors
▪ Shopper
▪ Fulfillment System
▪ Billing System
▪ Customer and visitor login system
Description
This use case begins when a customer, while browsing, finds an item he or she would like to purchase.
Actors
▪ Registered Shopper (Has an existing account, possibly with billing and shipping information)
▪ Non-registered Shopper (Does not have an existing account)
▪ Fulfillment System (processes orders for delivery to customers)

11
 ▪ Billing System (bills customers for orders that have been placed)

Triggers
• The user indicates that she wants to purchase items that she has selected.
Preconditions
▪ For the member, he/she must have to register in website.
▪ If he/she is no already registered he can register by clicking on sign up button.
▪ The actor must add complete mandatory details.
▪ User has selected the items to be purchased.
Post-conditions
▪ The order will be placed in the system.
▪ The user will have a tracking ID for the order.
▪ The user will know the estimated delivery date for the order.
▪ User can access to website main features.
▪ User account should be created successfully.
▪ Member particular folder is created in project directory.
Normal Flow
▪ The user will indicate that she wants to order the items that have already been selected.
▪ The system will present the billing and shipping information that the user previously stored.
▪ The user will confirm that the existing billing and shipping information should be used for
this order.
▪ The system will present the amount that the order will cost, including applicable taxes and
shipping charges.
▪ The user will confirm that the order information is accurate.
▪ The system will provide the user with a tracking ID for the order.
▪ The system will submit the order to the fulfillment system for evaluation.
▪ The fulfillment system will provide the system with an estimated delivery date.
▪ The system will present the estimated delivery date to the user.
▪ The user will indicate that the order should be placed.
▪ The system will request that the billing system should charge the user for the order.
▪ The billing system will confirm that the charge has been placed for the order.
▪ The system will submit the order to the fulfillment system for processing.
▪ The fulfillment system will confirm that the order is being processed.
▪ The system will indicate to the user that the user has been charged for the order.
12
 ▪ The system will indicate to the user that the order has been placed and then exit the system.

Alternate Flows
1: The user enters billing and shipping information for the order. The user desires to use shipping and
billing information that differs from the information stored in her account. This alternate flow also
applies if the user does not maintain billing and / or shipping information in their account, or if the user
does not have an account.
▪ The user will indicate that this order should use alternate billing or shipping information.
▪ The user will enter billing and shipping information for this order.
▪ The system will validate the billing and shipping information.
▪ The use case continues
2: The user will discover an error in the billing or shipping information associated with their account,
and will change it.
▪ The user will indicate that the billing and shipping information is incorrect.
▪ The user will edit the billing and shipping information associated with their account.
▪ The system will validate the billing and shipping information.
▪ The use case returns to step 2 and continues.
3: The user will discover an error in the billing or shipping information that is uniquely being used for
this order, and will change it.
▪ The user will indicate that the billing and shipping information is incorrect.
▪ The user will edit the billing and shipping information for this order.
▪ The use case returns to step 3A1 step 3.
4: The user will determine that the order is not acceptable (perhaps due to dissatisfaction with the
estimated delivery date) and will cancel the order.
▪ The user will request that the order be cancelled.
▪ The system will confirm that the order has been cancelled.
▪ The use case ends.
3.2 Detailed Use Case
In figure:2 use case of the administrator and figure:3 the use case of the customer that is directly
involved in the system

13
 Figure 3.2 Use Case of the administrator
Actors: admin
Brief description
Project Administrators assist with project management duties. They oversee and performing
administrative functions concerned with a project. This may include calling contractors, making
appointments, ordering supplies, doing site visits and preparing reports. Administrators work in several
industries including engineering, pharmaceutical, health care, and research. They can succeed project
managers.
Pre-Condition
▪ For the member, he/she must have to register in website.
▪ If he/she is no already registered he can register by clicking on sign up button.
▪ The actor must add complete mandatory details.
Post-Condition
▪ User can access to website main features.
▪ User account should be created successfully.
▪ Member particular folder is created in project directory.

14
Basic Path
▪ Admin login in website.
▪ Add /remove products.
▪ View shipping detail
▪ View order detail
▪ Maintain and modify products detail
▪ Accept user requests
▪ Whole system is control by admin.
3.2.1 Use Case of the customer in below that interact with the system

Figure 3.3 Use Case of the customer

Use Case Title: customer login to order product process

Actors: Customer, Credit Bureau
Description
This use case begins when a customer, while browsing, finds an item he or she would like to purchase.
Basic Path
1. While browsing the customer selects an item for purchase. The customer may select multiple items
for purchase while browsing and each item is placed in a virtual shopping cart.
15
2. When the customer is ready to purchase the items in the virtual shopping cart he or she indicates this
and is presented with a summary of items purchases. The customer may remove items from the virtual
shopping cart or change the quantity of each item in the cart.
3. The customer confirms the summary.
4. The system asks the customer for his or her name, shipping address and credit card number.
5. The customer’s credit is checked as described by the abstract use case Verify Credit. If the customer
has sufficient credit the system sends a confirmation number to the customer and schedules the items
to be shipped.
Alternate Paths
In step 5 if the customer has insufficient credit or the credit card information was incorrect the system
will notify the customer and return to step 4 so the customer can reenter the data.
At any time during steps 1-4 the customer may exit the use case without completing the purchase.
➢ Use Case
Use case of the visitor in the system, the visitor is the customer that is firstly visit the website and gives
feedback and comment about the MyFashionSwap system

Figure 3.4 Use Case of the visitor

Actor: Visitor
Description
Use case of the visitor in the system, the visitor is the customer that is firstly visit the website and gives
feedback and comment about the MyFashionSwap system
16
 Pre-Condition
▪ For the member, he/she must have to register in website.
▪ If he/she is no already registered he can register by clicking on sign up button.
▪ The actor must add complete mandatory details.

Post-Condition
▪ User can access to website main features.
▪ User account should be created successfully.
▪ Member particular folder is created in project directory.
Basic Path
▪ Firstly, login into the system.
▪ The use case states clearly the starting condition and ending condition.
▪ This use cases are used by a customer to shop for items to purchase.
▪ This use case is used by a customer to purchase an item.
▪ This use case is used by an affiliate to make an item available for purchase.

3.3 Function requirements

▪ Login page
▪ Administrator control page
▪ Item selection
▪ Registration
▪ User profile

3.4 Non-Function requirement

▪ performance
▪ Usability (easy to use, efficient to use)
▪ Reliability, availability
▪ Security

3.5 Sequence diagram of all the Use Cases

A system administrator, or sysadmin, is a person who is responsible for the upkeep, configuration, and
reliable operation of computer systems; especially multi-user computers, such as servers.

17
Figure 3.5 Sequence Diagram

18
3.5.1 Sequence diagram of all the Use Cases
Sequence diagram of the customer as shown below:

Customer Browse category Account Product catelog Billing

Login

Authorization

View account details

Search for product

Product info

Add and Remove item from cart

Confirmation

Place order billing info

Billing info

Payment

Figure 3.6 Sequence diagram of the customer

19
 Chapter #4
Design & Architecture
4. Design and Architecture
4.1 System Architecture

Figure 4.1 System Architecture

21
4.2 Data Representation

Figure 4.2 Class Diagram

22
4.3 Process Flow/Representation
Start

Login

Visitor &
Registered
Customer Visitor Creat Account
member
& Admin
Visitor
Admin

Main page Main page Main page

Add item
Update
View
Dress
Jewelry
Dress
Shoes Update item
Makeup Sunglasses
View page Add item

Sandal High hill School shoes

Select item
View detail

Place order

Acknowledge

Figure 4.3 Data flow

4.4 Design Models

For our proposed application we have to use the method of Incremental approach which is best suitable
for such kinds of applications. Because of the following benefits from it:

23
• Generates working software quickly and early during the software life cycle.
• More flexible less costly to change scope and requirements.
• Easier to test and debug
• during a smaller iteration.
• Each iteration is an easily managed milestone.
• Due to iteration each phase complete within time period.

24
 Chapter # 5
Implementation
5. Implementation
5.1 User Interface
Admin panel
Admin is the person that is responsible for everything

Figure 5.1 Admin Panel

Family Orders

Figure 5.2 Family Order

26
Add Products

Figure 5.3 Add Products

Customer Order

Figure 5.4 Customer Order

27
5.2 User View
Signup Form

Figure 5.5 Signup Form

Home Page

Figure 5.6 Home Page

28
Men’s Items

Figure 5.7 Men's Items

Women’s item

Figure 5.8 Women's Items

29
Items Description

Figure 5.9 Items Description

Shipping Detail

Figure 5.10 Shipping Detail

30
Family/Friend Shipping Detail

Figure 5.11 Family/Friend Shipping Detail

Family Cart Items

Figure 5.12 Family Cart Items

31
 Chapter # 6
Testing & Evaluation
6. Testing and Evaluation
6.1 System testing
Once the system has been successfully developed, testing has to be performed to ensure that
the system working as intended. The process of testing of an integrated hardware and software
system to verify that the system meets its specified requirements. To test the system as a whole,
requirement and expectations should be clear and tester need to understand real time usage of
applications too. System testing will help in finding the errors that may be hidden from the
user. There are few types of testing which includes the unit testing, functional testing
and integration testing. The testing must be completed before it is being deploy for user to
use.
• Installation of computing
• Technology computing testing
• Program testing
• Input testing
• Output testing
6.2 Unit Testing
Unit Testing 1: Login
Testing Objective: To ensure the login form is working correctly.
Table 6.1 Login
No Test case/Test Attribute and value Expected result Result
. script
1. Verify user login after Email: Maryam@gmail.com Successfully log Pass
click on the „Login‟ Password: 890 into the main page of the
system.
2. Verify use login after Email: Alia12@gmail.com Successfully log Pass
click on the „Login‟ Password: 123 into the main page of the
system.
3 Verify user login after Email: Successfully log Pass
click on the „Login‟ Amnarafiq652@gmail.com into the main page of the
Password: Amnarafiq6 system.

Unit Testing 2: Signup

Testing Objective: To ensure the Signup form is working properly.

33
 Table 6.2 Signup
No. Test case/Test script Attribute and value Expected result Result
1. Verify user signup after Name: Amna Successfully signup Pass
click on the „ signup ‟ Email:Amnarafiq652@gm the main page of the
ail.com system.
Password: Amnarafiq6
Confirm password:
Amnarafiq6
2. Verify user signup after Name: aqsa Successfully signup Pass
click on the „ signup ‟ Email: the main page of the
Alia12@gmail.com system.
Password: 123
Confirm password:
123
3. Verify user signup after Name: Maryam Successfully signup Pass
click on the „ signup ‟ Email: the main page of the
Maryam@gmail.com system.
Password: 890
Confirm password: 890
Unit Testing 3: Add to Cart
Testing Objective: To ensure the Add to Cart form is working properly.

Table 6.3 Add to Cart

No. Test case/Test script Attribut and value Expected result Result

1. Verify user Add to Cart Item Name: Formal blue Successfully Add to Pass
after shirt Cart the main page of
click on the „ Add to Cart ‟ Quantity: Manual=2 the system.
Item price: 700
2. Verify user Add to Cart Item
TotalName: Analog Watch Successfully Add to Cart Pass
price: 1400
after Quantity: Manual=1 the main page of the
click on the „ Add to Cart ‟ Item price: 1600 system.
Total price: 1600

34
Unit Testing 4: View item with Shipping detail description
Testing Objective: To ensure the View item with description form is working properly.
Table 6.4 View Item Details
No. Test case/Test script Attribute Expected result Result
and value
1. Verify user View item Full name: Amna Successfully View item with Pass
with description Phone: 01234567 Shipping detail description
Shipping detail after Email: the main page of the system.
click on the „ View item Amna12@gmail.com
with Shipping detail Address: Swl
description ‟

Unit Testing 5: Order

Testing Objective: To ensure the Order form is working properly.
Table 6.5 Order
No. Test case/Test script Attribute Expected result Result
and value
1. Verify user Order Quantity: Manual: 1 Successfully Order Pass
after Total: 700 the main page of the system.
click on the „ Order” Discount: 100
Grand Total: 600

6.2.1 Functional Testing

The functional testing will take place after the unit testing. In this functional testing, the functionality
of each of the module is tested. This is to ensure that the system produced meets the specifications and
requirements. Validating an application or Web site conforms to its specifications and correctly
performs all its required functions. This can involve testing of the product's user interface, APIs,
database management, security, etc. Functional testing can be performed on an automated or manual
basis using black box or white box methodologies ions
Functional Testing 1: Login with different roles
Objective: To ensure that the correct page with the correct navigation bar is loaded.

35
 Table 6.6 Login
No. Test case/Test Attribute and value Expected result Result
script
1. Verify user login Email: Successfully log Pass
after Amnarafiq652@gmail.com into the main page of the
click on the “Login‟ Password: Amnarafiq6 system.

2. Verify user signup Name: Amna Successfully signup Pass

after Email: the main page of the
click on the “signup Amnarafiq652@gmail.com system.
“ Password: Amnarafiq6
Confirm password:
Amnarafiq6

3. Verify user Add Item Name: Successfully Add to Pass

to Cart afterclick Formal blue shirt Cart the main page of
on the „ Add to Quantity: Manual=2 the system.
Cart ‟ Item price: 700
Total price: 1400

4. Verify user View Full name: Amna Successfully View Pass

item with Phone: 01234567 item with Shipping
description Email: detail description the
Shipping detail Amna12@gmail.com main page of the
afterclick on the „ Address: Swl system.
View item with
Shipping detail
description ‟
5. Verify user Order Quantity: Manual: 1 Successfully Order Pass
after Total: 700 the main page of the
click on the „ Order‟ Discount: 100 system.
Grand Total: 600

6.2.2 Integration Testing

Testing in which modules are combined and tested as a group. Integration Testing follows unit testing
and precedes system testing.

36
 Table 6.7 Integration Testing
No. Test case/Test Attribute and value Expected result Result
script
1. Verify user login after Email: Amnarafiq652@gmail.com Successfully log into the Pass
click on the „Login‟ Password: Amnarafiq6 main page of the system.
2. Verify user signup after Name: Amna Successfully signup the Pass
click on the „ signup ‟ Email:Amnarafiq652@gmail.com main page of the system.
Password: Amnarafiq6
Confirmpassword: Amnarafiq6

3. Verify user Add to Cart Item Name: Formal blue shirt Successfully Add to Pass
after Quantity: Manual=2 Cart the main page of
click on the „ Add to Cart Item price: 700 the system.
‟ Total price: 1400
4. Verify user View item Full name: Amna Successfully View item Pass
with description Phone: 01234567 with Shipping detail
Shipping detail after Email: Amna12@gmail.com description the main
click on the „ View item Address: Swl page of the system.
with Shipping detail
5. Verify user Order Quantity: Manual: 1 Successfully Order Pass
description ‟
After click on the „ Order‟ Total: 700 the main page of the
Discount: 100 system.
Grand Total: 600

6.3 Manual Testing

There are two ways that software can be tested; manually by a human, and automatically by a
computer. Each method has its advantages and disadvantages but they share the underlying goal of
ensuring quality and buy products in online shopping portal for women’s and men’s in the software. In
this article, we’re going to focus on manual testing.
Manual testing is the process of using the functions and features of an application as an end-user would
in order to verify the software is working as required. With manual testing, a tester manually conducts
tests on the software by following a set of pre-defined test cases. Let’s take a close look at how this is
done.

37
 Chapter # 7
Conclusion & Future Work
7. Conclusion and Future Work
7.1 Conclusion
Technology has made significant progress over the years to provide consumers a better online
shopping experience and will continue to do so for years to come. With the rapid growth of
products and brands, people have speculated that online shopping will overtake in-store
shopping. While this has been the case in some areas, there is still demand for brick and mortar
stores in market areas where the consumer feels more comfortable seeing and touching the product
being bought. However, the availability of online shopping has produced a more educated
consumer that can shop around with relative ease without having to spend a large amount of
time. In exchange, online shopping has opened up doors to many small retailers that would never
be in business if they had to incur the high cost of owning a brick and mortar store. At the end, it
has been a win-win situation for both consumer and sellers.
In the end the system meets the user requirements also meet functional and non-functional
requirements.
This will allow customers to place order without even visiting the shops.
Being able to buy any time, any place, anywhere.
Site enable them to browse before they shop, and to research the product so they have more confidence in
what they are buying.
Online shopping become more enjoyable.
7.2 Future Work
We will develop android app.
Tracking system of order.

39
References
1 https://srs-onlineshopping.blogspot.com/
2 https://l.facebook.com/l.php?u=http%3A%2F%2Fdspace.cusat.ac.in%2Fjspui%2Fbitstre
am%2F123456789%2F8252%2F1%2Fonlineshoppingsystem.pdf%3Ffbclid%3DIwAR3-
omMVzZ7aOH-
FM83y09doNPIxAs9vBpXpObbkrKy3S34S3OPzhmAvZCM&h=AT2mp0pOBKwv6jfl
8qkhZmVIS2XLeO1RlQepYCqM-P-
dUbLj19XNbbT_UwgqvH7p1V9uarHQphoCUxk4dyaT4KIIstt4nN0AYKAqbD0A9IEG
Tjti5DWLINa1ag2-Iyx7-hK_CQ
3 https://www.google.com/search?q=class+diagram+of+online+shopping+system&source=
lnms&tbm=isch&sa=X&ved=0ahUKEwiu9MLV37_iAhVH_qQKHUNrDWcQ_AUIDig
B&biw=1366&bih=657
4 https://www.ooportal.com/project-life-cycle/module5/pre-conditions-post-conditions.php
5 http://sce2.umkc.edu/BIT/burrise/pl/usecasemodeling
6 http://sce2.umkc.edu/BIT/burrise/pl/usecasemodeling/
7 https://www.softwaretestinghelp.com/use-case-testing/
8 http://tynerblain.com/blog/2007/04/09/sample-use-case-example/

40