ONLINE GARMENTS SALE

Fozia BiBi
Javeria Jabeen

24th May 2019

Department of Computer Science

COMSATS UNIVERSITY ISLAMABAD
ATTOCK – PAKISTAN
 Submission Form for Final-Year
PROJECT REPORT

NUMBER OF
PROJECT ID 2
MEMBERS

TITLE

SUPERVISOR NAME

MEMBER NAME REG. NO. EMAIL ADDRESS

CHECKLIST:
Number of pages in this report

I/We have enclosed the soft-copy of this document along-with the

YES / NO
codes and scripts created by myself/ourselves
My/Our supervisor has attested the attached document YES / NO

I/We confirm to state that this project is free from any type of
YES / NO
plagiarism and misuse of copyrighted material

MEMBERS’ SIGNATURES

Supervisor’s Signature

COMSATS Institute of Information Technology, Attock Campus Department of Computer Science

 This work, entitled “ONLIEN GARMENTS SALE” has been approved
for the award of

Bachelors of Science in Software Engineering

Date:- 24th May 2019

External Examiner:

Head of Department: Dr. Khalid Awan

Department of Computer Science

COMSATS UNIVERSITY ISLAMABAD
ATTOCK – PAKISTAN
 Declaration
“No portion of the work referred to in the dissertation has been submitted in support of
an application for another degree or qualification of this or any other university/institute
or other institution of learning”.

MEMBERS’ SIGNATURES

ii
 Acknowledgements
We are exceedingly thankful to ALLAH ALMIGHTY, most gracious and merciful,
who enabled us to finalize our project effectively. We have placed our entire efforts in
this project. However, it would not have been possible without the faithful support of so
many others. The help and assistance of many individuals is involved. We would like to
extend our sincere thanks to everyone associated with this project in any way.

We are cordially grateful to our parents, family and friends who kept backing us up in
all the times. We are immensely thankful to them for supporting us, both financially and
morally.

I would also like to thank Miss.Mehreen Wahab for his guidance and encouraging me to work
hard and smart. I have found him very helpful while discussing the optimization issues in this
dissertation work. His critical comments on my work have certainly made me think of new
ideas and techniques in the fields of optimization and software simulation.

iii
 Abstract

Internet and web have fascinated the people in all fields of life. The use of internet has become
popular in commerce, education, banking and industry. This increase has created a demand for
professionals to create a website that provide interaction between customer and industry. People
have been spending more time on internet and purchasing items online. This project is also
design for online shopping system. The purpose of this project “online shopping website” is to
provide a platform for different types of vendors and customers, where they can easily sell and
buy products at Home with help of shopping cart. An important aspect of this project is
providing recommendations to customer based on his/her order history. The top sale products
and the products on which discounts are offered are displayed on home page.so that the
customer and vendor both get benefit. The name of registered vendors and the names of product
categories are also provided on home page. The search box is also provided on home page
where customers can search products. Customer will right the name of respective product in
search box and the product will appear on home screen if available. User can click on vendor’s
name to see the products uploaded by respective vendor. The vendor will be notified through
email when his/her product quantity becomes less than five. The vendor can also send email to
his respective buyers only. Vendors are welcome to send feedback through feedback option.
Registered customers can also give comment on products. To make comment it is necessary for
the customer to login first.

iv
 Table of Contents
1 INTRODUCTION...............................................................................................................................2

1.1 PROBLEM DOMAIN.......................................................................................................................2

1.2 SOLUTION.....................................................................................................................................3
1.3 PROJECT OBJECTIVE.....................................................................................................................3

2 LITERATURE REVIEW...................................................................................................................5

2.1 COMPARISON TABLE.....................................................................................................................7

3 REQUIREMENT SPECIFICATION................................................................................................9

3.1 FUNCTIONAL REQUIREMENTS.......................................................................................................9

3.1.1 Admin Services........................................................................................................................9
3.1.2 Vendors Services....................................................................................................................10
3.1.3 Visitor Services......................................................................................................................11
3.1.4 Customer Services.................................................................................................................11
3.2 NON FUNCTIONAL REQUIREMENTS:...........................................................................................12
3.2.1 Availability:...........................................................................................................................12
3.2.2 Maintainability:.....................................................................................................................13
3.2.3 Security:.................................................................................................................................13
3.2.4 Usability:...............................................................................................................................13
3.2.5 Reliability:.............................................................................................................................13
3.2.6 Compatibility:........................................................................................................................13

4 PROJECT DESIGN..........................................................................................................................15

4.1 METHODOLOGY..........................................................................................................................15
4.1.1 Requirement Elicitation.........................................................................................................15
4.1.2 Requirement Analysis............................................................................................................16
4.1.3 Design....................................................................................................................................16
4.1.4 Implementation......................................................................................................................16
4.1.5 Testing:..................................................................................................................................16
4.1.6 Maintenance:.........................................................................................................................17
4.2 USE CASE DIAGRAM:.................................................................................................................17
4.2.1 Use Case For Admin:............................................................................................................17
4.2.2 Use Case For Customer:.......................................................................................................18
4.2.3 Use Case For Vender:...........................................................................................................19
4.2.4 Use Case For Visitor:............................................................................................................20
4.3 SEQUENCE DIAGRAM..................................................................................................................21
4.3.1 Sequence diagram for Customer:..........................................................................................21

v
 4.3.2 Sequence diagram for Vendor:..............................................................................................22
4.3.3 Sequence diagram for Shopping Cart:..................................................................................23
4.4 ACTIVITY DIAGRAM...................................................................................................................24
4.4.1 Activity diagram for Admin:..................................................................................................24
4.4.2 Activity Diagram for Customer:............................................................................................25
4.5 CLASS DIAGRAM:..................................................................................................................26
4.6 DATA FLOW DIAGRAM................................................................................................................27
4.6.1 DFD for Admin:....................................................................................................................27
4.6.2 DFD for Vendor:...................................................................................................................28
4.6.3 DFD for Customer:...............................................................................................................29
4.7 DESIGN DESCRIPTION........................................................................................................................30
4.7.1 MODULE 1...........................................................................................................................30
4.7.2 MODULE 2...........................................................................................................................30
4.7.3 MODULE 3...........................................................................................................................30
4.7.4 MODULE 4...........................................................................................................................30

5 IMPLEMENTATION.......................................................................................................................32

5.1 TOOLS AND TECHNIQUES............................................................................................................32

5.2 USER INTERFACES:......................................................................................................................33
5.2.1 Main Menu:...........................................................................................................................33
5.2.2 Customer Functionalities......................................................................................................34
5.2.3 Vendor Functionalities..........................................................................................................35
5.2.4 Admin Functionalities...........................................................................................................35

6 EVALUATION..................................................................................................................................37

6.1 TESTING......................................................................................................................................37
6.1.1 Functional Testing.................................................................................................................37
6.1.2 Sign Up System:.....................................................................................................................37
6.1.3 Login in..................................................................................................................................38
6.1.4 User:......................................................................................................................................39
6.1.5 Add Products:........................................................................................................................39
6.2 SYSTEM TESTING:.......................................................................................................................39

7 CONCLUSION AND FUTURE PLANS........................................................................................41

7.1 CONCLUSION...............................................................................................................................41
7.2 FUTURE WORK...........................................................................................................................41

REFERENCES..........................................................................................................................................42

vi
 List of Figures
FIGURE 4. 1 FIGURE FOR PROTOTYPE APPLICATION....................................................................................15
FIGURE 4. 2 ADMIN USE CASE.....................................................................................................................17
FIGURE 4. 3 CUSTOMER USE CASE..............................................................................................................18
FIGURE 4. 4 VENDOR USE CASE..................................................................................................................19
FIGURE 4. 5 VISITOR USE CASE...................................................................................................................20
FIGURE 4. 6 SEQUENCE DIAGRAM CUSTOMER............................................................................................21
FIGURE 4. 7SEQUENCE DIAGRAM OF VENDOR..............................................................................................22
FIGURE 4. 8 SEQUENCE DIAGRAM OF SHOPPING CART.................................................................................23
FIGURE 4. 9 ACTIVITY DIAGRAM OF ADMIN................................................................................................24
FIGURE 4. 10 ACTIVITY DIAGRAM OF CUSTOMER.......................................................................................25
FIGURE 4. 11 CLASS DIAGRAM....................................................................................................................26
FIGURE 4. 12 ADMIN DFD...........................................................................................................................27
FIGURE 4. 13 VENDER DFD.........................................................................................................................28
FIGURE 4. 14 CUSTOMER DFD.....................................................................................................................29
FIGURE 5. 1 WAMP SERVER.........................................................................................................................32
FIGURE 5. 2 MAIN MENU..............................................................................................................................33
FIGURE 5. 3 LOGIN.......................................................................................................................................34
FIGURE 5. 4 VENDOR SIGN UP.....................................................................................................................35
FIGURE 5. 5 UPLOAD PRODUCTS..................................................................................................................35

vii
 List of Tables
TABLE 2. 1 COMPARISON TABLE....................................................................................................................7
TABLE 6. 1 TEST CASE FOR SIGN UP.............................................................................................................38
TABLE 6. 2 TEST CASE FOR LOGIN...............................................................................................................38
TABLE 6. 3 TEST CASE FOR USERS:............................................................................................................39
TABLE 6. 4 TEST CASE FOR ADD PRODUCTS................................................................................................39

viii
Chapter No 1
Introduction

1
1 Introduction
Internet and web have fascinated the people in all fields of life. The use of internet has
become popular in commerce, education, banking and industry. This increase has
created a demand for professionals to create a website that provide interaction between
customer and industry. People have been spending more time on internet and purchasing
items online. Purchasing and selling goods over the internet without need of going
physically to the market is what online shopping all about. This project is also design
for online shopping system. For this we experienced various websites but the area where
mostly websites lack is user friendly interface and user’s and vendor’s mutual
collaboration. The main purpose of this project is to provide an interface for online
shopping which is very easy to use. Users or vendors will register themselves with the
website to buy and sell different products and goods, receiving awareness of new trends
and fashions in the markets. The research includes devising possible improvements in
online shopping. Shopping cart is one of the most important feature of any online
shopping system. This website also provides shopping cart facility in which once user
selects an item for purchase he or she can add or delete it from the cart. User is provided
the option of recommendations based on his/her experiences. User can communicate
with vendor about new ideas and new suggestions. Vendor can also place discounted
product upfront. Top sale products are shown on home page so that customer and
vendor both get benefit. Search bar is also provided on main menu to facilitate
customer. The vendor will be notified through email when his/her product quantity
becomes less than five. Registered users will have chances to win multiple offers and
prizes and can get special discounts as well.
The busy people that have not much time to go to market for shopping to purchase
everything in short span of time. They need more convenient way to purchase
everything on a single click. Some people wander here and there in search of latest
things when they are not able to acquire items when they need it.

1.1 Problem Domain

Everyone is busy to meet their requirements of life. Everyone is spending very hectic
life. Many people cannot go to market for purchasing quality materials and accessories.
It is very difficult to purchase everything at the same time at same place. It consumes lot

2
of time and very exhausting activity finding everything from a market. Many people
remain busy in their jobs and have no idea about latest trends. They cannot give much
time to their dressing and accessories. This website will resolve all those problems of all
type of people.

1.2 Solution
This website is designed for all those people who cannot pay attention on their outfits.
This website will provide guidance and help to everyone who are more busy or do not
know about fashions and trends. This website is user friendly .It will fascinate people to
get more chances of winning prizes and gifts. Users are offer to communicate with
vendors directly and discuss their related issues and also their creative ideas about
improvements and developments in the fashion era.

1.3 Project Objective

1: This website will provide the easiest way for customers to purchase everything on a
single store in a very convenient and less anxious way of shopping.

2: Main objective of this website is to save time and provide information of latest
trends and fashion.

3: To make the vendors aware of user’s choice and their recommendations, for making
changes in their products according to the customers and users.

4: To facilitate the registered users special discount and prizes for promoting existing
products or to launch new trends.

5: Registered users can also get more benefits along with their shopping.

3
 Chapter No 2
Literature review

4
2 Literature Review
We have studied, which shows a lot of websites of online garments sale and top ten
websites are “Affordable.pk” , “Daraz.pk ”, “nishatlinen” , “Symbios.pk” ,
“EMMACLOTH” “Kaymu.pk” , “Shopdaily.pk” but each of them is developed for
specific purpose and none of them is giving the complete features.
Affordable.pk is a commercial website which is developed for convenient online
shopping. Features of Affordable.pk are different categories of shopping materials,
discounts and notification bulb. There is also available facility of offline messaging. But
it lack of other accessories categories and any prizes offers for their registered users.
Online website Daraz.pk is one of the best online shopping website which is offer goods
and products ranges from mobile and computer, books to beauty and fashion
accessories, clothing, kid’s products and much more. The delivery payment and
warranty system of Daraz.pk is very easy and simple.

Nishatlinen gives the feature of online saving time, purchasing everything at one
platform. It gives facility of location to find different branches in different cities. It does
not allow customers to communicate with vendors. It is not much user friendly. If
customer wants to purchase anything then he has to re-enter data many times.
Customers are not easy to order anything in a simple way.

In Symbios.pk is platform of buying high quality products. Symbioses deals almost

every products and it’s a best online shopping-website for buying electrical materials
like laptops, computers, watches, smartphones and much more.
But this website is very criticized by the users and one of the main reason according to
them is “too much slow website”. As this website is shopping specific so if the user of
the website is not from that specific higher class he/she cannot purchase the product, on
other hand our website is really general and less expensive that any customer can
purchase their items on the website.
EMMACLOTH gives features of add to cart different things. It facilitates foreigners to
purchase anything. It has no notification icon for any new item or product arrival. It is
user friendly .It does not provide any facility to customer for any
recommendation/comments. Registered customers has no opportunity to win any prize.
Offers are very limited.

5
Kaymu.pk is an online platform for selling and purchasing a lot of goods. In addition to
sell its own products. It allows the vendors and customers to trade directly with each
other. Kaymu offers products of clothing, fashion accessories, electronic, mobile or
computers, healthy & beauty, outdoors games, kitchen products etc.

Shopdaily.pk an online shopping system of buying only fashion and cloth products.
Shop daily provides the product of affordable prices. It allow the users can shopping
easily and get the order at their doorstep with home delivery system. Shop daily an
online shopping platform for selling beauty, fashion accessories for women, men and
kids.

All of the websites that we studied offer a common range of features but in our
proposed website we have included some more features to make it more useful and
efficient. These features will enhance the performance of website and will also help the
vendors to manage their work more efficiently. Through this, vendors can save their
time and effort by uploading their latest products on website instead of selling on
different stores and shops. It will give vendors a platform to sale all their products
related to latest fashion and trends. Only registered vendors can upload their products
and can “take comments” of their customers directly but in case of fake vendors or
their fake products admin can “cease” their accounts and would not allow to upload
their products anymore. There is no website that allows a vendor to “collaborate” with
their customers directly, take comments and suggestions for product improvements.
Customers can also post queries and can give feedback. One key feature that
differentiate our website from other is that we are giving the features of “Notification
Bulb” through which registered customers will directly get notifications about new
latest trends and fashions which will help customer to be aware of latest trends.
Customer are also facilitated with different attractive “offers and prizes” by admin that
will fascinate customers and viewers. We have developed this website to ease the work
of vendors and customer.

6
2.1 Comparison Table
On the basis of the features that are provided by our website and are not present in
other websites here is a table that make a difference between them.

Name Chat User Prizes Discount Notific- Multi- Reasonable Comment

friendly Offers ations Categories Prices

Affordable.pk × × ×  ×   
Daraz.pk   ×  ×   ×
Nishatlinen × × ×  ×  × ×
Symbios.pk ×  ×  ×  × 
EMMACLOTH × × ×  ×  × ×
Kaymu.pk   ×  ×   ×
Shopdaily.pk × × ×  ×   ×
Online-        
Garments sale

Table 2. 1 Comparison Table

7
 Chapter No 3
Requirements Specification

8
3 Requirement specification
Software Requirement Specification is a description of software system to be
developed and environment for software under developed. SRS fully describes that
what the software system will do without describing how it will do it is represented
by the software requirements. SRS makes less the time and effort required by
developers to achieve their desired goals and also makes less the development cost.
SRS explain how an application will interact with system hardware, other programs
and users in a wide variety of real-world situations. Parameters like speed of
operating, response time, availability, portability, maintainability, security, and
recovery of speed from adverse events are evaluated.
SRS is a formal document which perform as a representation of software system
which enables the users to review whether it is according to their requirements. In
addition it also includes user requirements for a system as well as detailed
specifications of the system requirements.

3.1 Functional Requirements

Functional requirements are the details of services that the system should provide,
how the system will react to particular inputs and how the system will behave in
particular situations. They may state what the system should not do.

3.1.1 Admin Services

 Add Users

Admin can add new vendors and customers whenever they made a request to the system will
create an account. After registration they are allowed to communicate with each other and can
also suggest their suggestions.
 Delete Users

Admin can delete the any user from the available list of users if he/she feels any fraud or fake
user. When Admin delete those users and system will remove all those accounts of users from
the database.
 Verify Vendors

9
Whenever the vendor of any brand wants to sign up in the website, he/she should send a request
to admin for sign up. The admin will verify the request of vendor by changing his/her status so
that the vendors can log in to the system.
 Manage Accounts

Admin can manage the records of all users and vendors that are registered. When user will make
any changes then the admin will update the information.
 Notify The Customers
Admin will notify the registered customers via mobile sms, emails and through “Bell Icon” on
customer’s account about any latest trends and fashions and special offers. Admin will also trace
the record of his customer’s purchases and will decide prizes and offers for those specific
customers. Only admin will allow the vendors to upload their products whatever admin will
finalize.
 Manage Orders
Admin can manage orders of customers and will send that product to them. Admin will
confirm the delivery and payment and will notify customers. He/she can cancel orders as
well.

3.1.2 Vendors Services

 Sign Up

Whenever the vendors of any brand wants to sign up in the website, he/she should send a
request to admin for sign up. The admin will verify the request of vendors by changing his /her
status. Then vendor would be able to sign up after the status has been changed.
 Log In

After the status has been changed by verification of admin, the vendor will be able to login to
the website. Vendor can login to the website by entering user-name and password. If password is
match then he/she will be allow to access the system and if password is incorrect then he/she
will be asked to re-enter the password. He/she will be given three chances to re-enter the
password by clicking on forgotten password option.

 Add Products

Vendor can add new products whenever newly fashioned material is ready for sale. Vendor will
add any product by providing its information (colour, size, stitched/unstitched, price, discounts
etc.).
 Delete Products

10
Vendor is not allowed to delete any product. Only admin can delete and modify the prices of
products.

 View Orders

Vendor can view orders and their delivery reports and comments about that orders. Vendors are
free to communicate with customers regarding customer’s recommendations after using that
product.

3.1.3 Visitor Services

 View Product Details

Viewer can view the website and its products details. He/ she can view products prices and
discounts. He / she can view offers and prizes offered by admin.

 View Comments

Viewer can see comments of customers and vendors about those products. Viewer can view the
delivery responses as well as comments of products.

 Request for registration

Viewer can make request for registration if he/ she likes website and to purchase products

3.1.4 Customer Services

 Sign Up

He/she can register themselves by filling the fields of Name, Email, Mobile Number, Password,
City and user name in order to create his/her account in website.
 Log In

To use the website customer can login to the system. If password is correct then he/she will be
granted the permission to access the system and if password is incorrect then he/she will be
asked to re-enter the password. He/she will be given three chances to re-enter the password by
clicking on forgotten password option.
 Edit Profile

11
When customer is registered then he/she can edit his/ her profile. He/ she can leave website
account anytime. Customer can modify his/her account.
 View Products

Customer can view products and its details of different categories. He/she can view product’s
prices and discounts.
 Select Product
When customer selects any product he/she will add to cart. He/she will checkout for his/her
order he will add to cart items and can select colour and size and colour verities.
 Make Order
Customer will select items and will give order and can edit the order. Customer can select and
remove items from cart.
 Checkout

Customer finalize his/her order through checkout. To check his/her cart he/she will make sure
about address and payment procedure. He/she will have to enter his/her exact and permanent
address and his/her correct required information for delivery services.

 Feedback

System will provide a facility of customer’s feedback for regarding product purchased by
customer. It will help the vendors to improve its products and also help to admin to improve its
services. If customer has any complaints about any service he/she will be allowed to mention in
the comments section.

 Get Notifications

Whenever the admin upload any product or they add any offer, customers will be notified.
Notification will be a pop up “Bell Icon” message for the customers

3.2 Non Functional Requirements:

Non-functional requirements are the constraints on the services or functions offered by
the system such as timing constraints, constraints on the development process and
standards. These are applied to the system as a whole rather than individual features.

3.2.1 Availability:
The system will available at all times user can access it through a web browser. If
hardware or database is not working and alternative pages are show. The database

12
failure or corrupted, backup of the database will available the retrieved from the server.
The services will restart again.

3.2.2 Maintainability:
A Trading database is used for maintain the database and the server takes care of the
site. In case of mishap, a reset of the program will be done. Also, the software
maintainability can be done efficiently.

3.2.3 Security:
Only authenticated users should login to the website and the personal information of the users
will be secured from illegal access. Security is important for any website. Any
modification regarding product (insertion, deletion, updating) for the database is only
done by the admin who has uploaded the respective product. Only owner of the website
has rights to view uploaded products, registered customer and registered admin.

3.2.4 Usability:
The website will have a user friendly interface or the users should able to use the website
very easily. After using it once without any help or training.

3.2.5 Reliability:

The website can be used by multiple users concurrently. Any user can access the
website with using even a low performance PC. The main point of reliability is the
system is the backup of the database. We can change in database continuously
maintained and update then save the changes.

3.2.6 Compatibility:
Website will be compatible with all operating

13
Chapter No 4
Project Design

14
4 Project Design

4.1 Methodology
The method we have used for our website is agile model.
When we talk about Agile Model, we refers to the methodology where a product is
developed to accomplish specific goals in a short period of time.

At the beginning, the basic components that can satisfy the user, in order to develop a
prototype. After this, the team tests and improves it continuously to evaluate what needs to
be changed, fixed, or added to the final product in order to be a market success.
Agile Method can be used simultaneously on different domains allowing us to run many
affiliate e-commerce websites using one single control panel to manage data and maintain
settings.

Figure 4. 1 Figure for Prototype Application

15
4.1.1 Requirement Elicitation
 This includes task of identifying various requirements from project stakeholders as
there are no stakeholder involve we collect requirements through proper research. We
study different online systems which help us to elicit requirements upfront. In our case
requirements are clear.
 The system shall provide registration process for vendors and customers
 The system should provide the login form for vendors and customers
 The system should provide shopping cart for customers. The cart must have add, delete
or edit product functions
 The system must maintain sessions for both customers and vendors.
 System should provide product upload facility for vendor
 The system must provide top sale product upfront
 The system must provide the discount product upfront
 The system should provide related products luxury for customers
 The system should notify user when his product quantity becomes less. The notification
must send through email.

4.1.2 Requirement Analysis

Requirement analysis involve determining that the gathering of requirements are properly clear,
complete and consistent. The analysis also handles ambiguity requirement that do not clearly
state what need to be implementation.. There are no ambiguous requirements involve and the
requirement are clear in our project

4.1.3 Design
The design involves documenting a requirement in various forms include use cases, sequence
diagrams and DFD.

4.1.4 Implementation
The implementation involves coding or development. In this step design is translated into
machine readable form. We have used WAMP server as localhost WAMP abbreviated form of
Window Apache MySQL PHP.The coding of this website is done in PHP abbreviation of
personal home page. We have used PHP for creating this website embedded into HTML. HTML
stands for hypertext mark-up language.

16
4.1.5 Testing:
In this, the system is verified and validated through testing. Verification is a process of checking
that the software meets the specification and validation is a process of checking that the
specifications capture the customer needs.

4.1.6 Maintenance:
The final phase of model in which the completed software is handed over to client. After the
software has been deployed on the client site it is duty of development team to undertake
routine maintenance activities

17
4.2 Use Case Diagram:

4.2.1 Use Case For Admin:

Figure 4. 2 Admin Use Case

Above figure illustrates how the admin or owner will interact with his websites. Admin
can manage customers and vendors of his website. Admin can also manage products
uploaded on his website. Admin can add category and items. Admin can manage,
confirmation and cancel all the orders. Admin call manage history of user and vendors.
Admin can offer prizes, tickets and special discount for regular customers. Admin can
also send notification via sms and email.

18
4.2.2 Use Case For Customer:

Figure 4. 3 Customer Use Case

Customer login to this app. If the customer can visit first time then he/she must register
on this app. Customer can edit profile. Customer can view product categories.
Customer can select category, select product, give order and give feedback. Customer
can select products for purchase and can add that product to cart for purchase. He or she
can empty cart or continue ordering. Customer can also click on checkout after
completing order.

19
4.2.3 Use Case For Vender:

Figure 4. 4 Vendor Use Case

In the above figure we have describe the specific interaction of vendor with our project.
Vendor can manage category, manage products he has uploaded, manage orders made
on his products, and can give feedback and can view payments. Vender can also chat
with customers.

4.2.4 Use Case For Visitor:

20
 Figure 4. 5 Visitor Use Case

Above figure illustrates how the visitor will interact with our website. They can view
products, products category, products prizes. Visitors can view comments and response
delivery. Visitors can also request for registration.

21
4.3 Sequence diagram

4.3.1 Sequence diagram for Customer:

Figure 4. 6 Sequence Diagram Customer

4.3.2 Sequence diagram for Vendor:

22
Figure 4. 7Sequence diagram of vendor

23
4.3.3 Sequence diagram for Shopping Cart:

Figure 4. 8 Sequence diagram of shopping cart

24
4.4 Activity Diagram

4.4.1 Activity diagram for Admin:

Figure 4. 9 Activity Diagram of Admin

25
4.4.2 Activity Diagram for Customer:

Figure 4. 10 Activity Diagram of Customer

26
4.5 CLASS DIAGRAM:

Figure 4. 11 Class Diagram

27
4.6 Data Flow Diagram

4.6.1 DFD for Admin:

Figure 4. 12 Admin DFD

28
4.6.2 DFD for Vendor:

Figure 4. 13 Vender DFD

29
4.6.3 DFD for Customer:

Figure 4. 14 Customer DFD

30
4.7 Design Description
Following modules are constituting the product of development. Please note that we are
documenting only the salient properties and methods of each module to keep the description
simple and readable.

4.6.4 MODULE 1
Description: Admin
 Admin can log in to system and can add, delete and manage vendors and user’s account.
 Admin can provide verification when any vendor and user made a request to sign up.
 Admin can notify registered users about new offers, discounts and latest trends.
 Admin can manage products, their prices and orders.
 Admin can manage record of every user of their purchases and can offer those prizes,
tour tickets and special discounts.

4.6.5 MODULE 2
Description: Vendor
 Vendor can register his/her self and can upload its goods after verified by admin.
 Vendor can add products for selling.
 Vendor can edit or delete their respective products.
 Vendor can see the orders made on his products.
 Vendor can see the feedback for his products.

4.6.6 MODULE 3
Description: Customer
 Customer can sign up, login to the system.
 He/ She can add, delete and modify his record.
 Customer can add to cart their selected items for purchase and also can remove and edit.
 Customer can give feedback.

4.6.7 MODULE 4
Description: Visitor
 Visitors can visit the site.
 They can view details of every product and its delivery responses.
 They can view comments and suggestions of users and vendors.
 He/ She can request for registration.

31
 Chapter No 5
Implementation

5 Implementation
Implementation of design using WAMP Server is used. WAMP stands for Windows
Apache, MySQL, and PHP, comparing to LAMP (Linux Apache, My SQL, and PHP).
WAMP provides a development environment for Windows. Instead of requiring access
to a server which has features of Apache, MySQL, and PHP, then it will create a local
environment. The local environment allows developers to keep their work continue
while offline as well as test features before rolling them out into provided environments.

32
WAMP is a web development platform on Windows that lets to create dynamic website
with Apache2, PHP, and MYSQL. Everything is installed automatically need to
intuitively develop a website. Best of all, Wamp Server is free (under GPML license) in
both 32 and 64 bit versions.

5.1 Tools and Techniques

We have used WAMP server for database and languages used for creating a website are HTML,
PHP, CSS and java script.

Figure 5. 1 Wamp Server

5.2 User Interfaces:

User interface is a view for user. User interacts to website through interfaces. Interactive and
easy interfaces are the basic need for user.

33
5.2.1 Main Menu:
In our website front page provides all menus to any visitor. It will provide all information of
everything in our website. When visitors will visit our website there will be a main menu and
sub categories of website. It will provide easy ways to purchase everything and payment
systems as well. If any visitor want to buy anything, he will have to register and then further
he/she can verify his purchased materials.

Figure 5. 2 Main Menu

5.2.2 Customer Functionalities

Customer will have to register himself before any order. He/she will provide all required
necessary information and also will provide information for delivering orders. If customer is
registered already then he/she will only log in for making any order.

34
 Figure 5.2 Sign Up

Figure 5. 3 Login

5.2.3 Vendor Functionalities

Vendor will signup first and can create his/her account. Before uploading any product must to
login. Vendor can view customer’s messages and feedback about their product.

35
 Figure 5. 4 Vendor Sign Up

5.2.4 Admin Functionalities

Admin will view all orders and delivery reports. Admin will check feedback of customers and
vendors about products and services. Admin can update records of vendors and customers.
Admin can update products and allow vendors to upload their products but can also restrict
vendors if they are fake or not true with their commitments.

Figure 5. 5 Upload Products

36
Chapter No 6
Evaluation

37
6 Evaluation

6.1 Testing
Software testing is a process of running with intent of finding errors in software. Software
testing satisfies the quality of software and provides final review of other used phases of
software i.e. specification, design, code generation etc. We use two types of testing in our
system that are functional and system testing by this evaluation.

6.1.1 Functional Testing

The system is tested against functional requirements through functional testing. Some input is
given and system is tested. Here we check functionality of system that system is working
according to the requirements or not. In order to perform functional testing we make some test
cases.

6.1.2 Sign Up System:

Registering a user:
No Test condition Expected Actual output Result
result (Pass,
Fail)

Test 1 Tap on the done button after System will Result as Pass
adding any product in cart for show expectations
registration registration
form.
Test 2 To fill the registration form, Enter System will Same as Pass
name, password, email, phone register the mentioned in
number, address, and user name. user. And expected
system will result.
save same
data on the
firebase
database.

38
Test 3 After registration, user can must System will Result as Pass
login. show login expectations
page

Table 6. 1 Test case for sign up

6.1.3 Login in
Login:
No Test condition Expected result Actual output Result
(Pass, Fail)
Test 1 If the user is System will Same as expected Pass
registered in show login page. result
website. After
add any product
in cart. User can
Tap on the done
button.
Test 2 Enter user name The system will Same as expected Pass
or password and successfully result.
tap on login login
button.

Test 3 If the username Should not allow Same as expected Pass

or password is next activity. result.
incorrect, user
cannot login.
Test 4 Press logout The user who is User got log out. Pass
button. logged in should
be logged out.

Table 6. 2 Test case for Login

39
6.1.4 User:
No Test condition Expected result Actual output Result
(Pass, Fail)
Test 1 User can order System will Same as expected Pass
any product after allow the user to result
login order products.
Test 2 When user can System will save Result as Pass
order any all the orders in expectation
product, user database.
should enter user
name, Ph. No,
address and city
name.
Test 3 User can chat Chatting is Same as expected Pass
with vendor activated result
directly

Table 6. 3 Test case for Users:

6.1.5 Add Products:

No Test condition Expected result Actual output Result
(Pass, Fail)
Test 1 Admin can add Should allow Result as Pass
any products any expectation
time.

Table 6. 4 Test case for Add Products

6.2 System Testing:

System testing includes the testing of system as whole. A complete and integrated software is
tested at this level. The main purpose of this testing is to evaluate the system functions with the
requirements that we have defined. Normally independent people performs system testing.

40
 Chapter No 7
Conclusion and Future Work

41
7 Conclusion and Future plans

7.1 Conclusion
Conclusion of Online Shopping is that this website is to provide users a best online
shopping experience. With the more rapid growth of products and brands, people are
wondered that online shopping will overtake in store shopping. However, the
availability of online shopping has produced a more educated customers that can shop
around with their relative ease and convenient without having to spend amount of time.
At the end, it has facilitated easiest situation for both sellers and buyers.

7.2 Future Work

 In future there can be develop an application for this website.

42
References
[1] https://www.aliexpress.com/?src=google&albch=fbrnd&acnt=304-410-
9721&isdl=y&aff_short_key=UneMJZVf&albcp=229122388&albag=525614471
25&slnk=&trgt=kwd295235739027&plac=&crea=263305003907&netw=g&devi
ce=c&mtctp=b&memo1=1t3&albbt=Google_7_fbrnd&aff_platform=google&alba
gn=888888&gclid=EAIaIQobChMI5IOBwtOz4gIVia3tCh2nygDWEAAYAyAAE
gJw_PD_BwE
[2] http://www.chasevaluecentre.com/
[3] https://homeshopping.pk/
[4] https://www.pakstyle.pk/s
[5] https://en.wikipedia.org/wiki/Online_shopping
[6] https://www.slideshare.net/Kkushum/online-shopping-system-69945887
[7] https://www.web-ideas.com.au/online-shopping-system
[8] https://www.ukessays.com/essays/information-technology/the-online-shopping-
system-information-technology-essay.php

43
 Project Timeline:
DATE

TOTAL NUMBER
PROJECT ID OF WEEKS IN
PLAN

TITLE

STARTING
No. DESCRIPTION OF MILESTONE DURATION
WEEK
1 Requirements gathering and improving the idea 4 weeks

2 Software and Architecture Design 4 weeks

3 Interface designing 6 weeks

4 Database creation 5 weeks

5 Implementation of the project 10 weeks

6 Software Testing 3 weeks

7 Fully Functional product

* You can provide Gantt chart instead of filling this form, if you like

44
45
46
47