Online Clothing Store

Usama Butt Online Shopping
SESSION (2020-2022)
Submitted By
Name Usama Ayyaz Butt
ID S2020387012
QCA
Online Clothing Store
Supervised By
Mr. Gulfraz Naqvi

SCHOOL OF COMMERCE AND ACCOUNTANCY
UNIVERSITY OF MANAGEMENT & TECHNOLOGY, LAHORE
Project Title
A Report Submitted to the School of Commerce & Accountancy

In
Partial Fulfillment of the Requirements for the Associate Degree
In
Computer Science
By
Student Name Student-ID
Usama Ayyaz Butt S2020387012
Internal Examiner
(Supervisor)
Gulfraz Naqvi ---------------------------------------
External Examiner
---------------------------------------
Director
Mr. Muhammad Azeem Naz
School of Commerce & Accountancy

University of Management & Technology
(UMT), Lahore ----------------------------------------
I
DEDICATION
1. I thanked to my Allah Almighty who gave me confidence and courage to complete

my Final Project. My Mother is the motivator and Father is the first person who believed in
me.
2. The support of my Friends was a great spark for me that they always helped me to
keep charged and focus on this Final Project. Last push was only possible because of love
and hardworking of this field. I want to give a specific thanks to everyone who helped me a
lot directly and indirectly in this amazing and successful journey.
II
ACKNOWLEDGEMENT
I am thankful to ALMIGHTY ALLAH who gave me courage and passion and prayers of my
parents and teachers to achieve the goal that was necessary for the degree. Although it was not an
easy task, with the useful direction, kind supervision and co-operation of my Supervisor Mr.
Gulfraz Naqvi, it became easy for me to complete the research work.
I am using this opportunity to thank my friends and teachers who always helped whenever I
stuck in anything; they gave me the truthful and illuminating advices on the number of issues
related to my final project.
Last but not least, I extend my sincere appreciativeness and thankfulness to my Family for their
incredible encouragement. Their love and support means a lot to me.
Thanks,
Author: Usama Ayyaz Butt
III
UNDERTAKING
Usama Butt Online Shopping

SESSION (2020-2022)
This project is submitted to the School of Commerce Accountancy, University of Management &
Technology Lahore, for the partial fulfillment of the requirement for Associate Degree Program
in Computer Science.
Approved on: _________________
Submitted By:
Name: Usama Ayyaz Butt
(ID): S2020387012
Gulfraz Naqvi
S.C.A
UMT, Lahore
Project Supervisor
IV
SCHOOL OF COMMERCE AND ACCOUNTANCY
UNIVERSITY OF MANAGEMENT & TECHNOLOGY, LAHORE
V
ABSTRACT
Online Shopping is now on trending so that’s why I choose this subject. This is very convenient
website for everyone because of its easy and simple features. I can divide it in 3 sections means
Admin, Manager and Users (Visitor and Registered User). Users as a visitor can only viewing
the website on our social media pages but not used add to cart option. Registered user can view
the website as well as buy anything through add to cart option.
A registered user needs to login from his/her Username and Password then he will be able to
visit on website and buy anything from the website. If they have any problem and difficulty then
people ask anything.
These kind of website attract the people because now a days, people are so busy in their routine
and find no time to go outside and buy anything because of their busy schedule.
VI
PREFACE THE PREFACE CONTAINS AN INTRODUCTION TO THE
DOCUMENT. IT IS OPTIONAL AND CAN BE DELETED IF DESIRED.
VII
CONTENTS
New paragraphs formatted as Heading 1, Heading 2, and Heading 3 will be added to the table automatically. To
update this table of contents in Microsoft Word, put the cursor anywhere in the table and press F9. If you want the
table to be easy to maintain, do not change it manually.
DEDICATION..........................................................................................................................................II
ACKNOWLEDGEMENT......................................................................................................................III
UNDERTAKING....................................................................................................................................IV
ABSTRACT.............................................................................................................................................VI
1. INTRODUCTION.............................................................................................................................1
1.1 PROJECT OVERVIEW......................................................................................................................................1
1.1.1 Problem Statement................................................................................................................................1
1.1.2 Back Ground.........................................................................................................................................1
1.1.3 Proposed Solution.................................................................................................................................1
1.1.4 Customer...............................................................................................................................................2
1.1.5 Goals and Objectives............................................................................................................................2
1.1.6 Assumptions.........................................................................................................................................2
1.1.7 Dependencies/ External Systems..........................................................................................................2
1.1.8 Definitions and Acronyms....................................................................................................................2
1.1.9 Market Survey/ Domain Analysis........................................................................................................2
2. SYSTEM REQUIREMENT SPECIFICATION.............................................................................4
2.1 FUNCTIONAL REQUIREMENTS........................................................................................................................4
2.2 NON-FUNCTIONAL REQUIREMENT.................................................................................................................8
2.3 USE CASE MODELS........................................................................................................................................8
2.3.1 List of Actors........................................................................................................................................8
2.3.2 List of Use Cases..................................................................................................................................8
2.3.3 Use Case Diagram................................................................................................................................8
2.3.4 Usage Scenario.....................................................................................................................................9
3. SYSTEM DESIGN..........................................................................................................................27
3.1 SYSTEM ARCHITECTURE..............................................................................................................................27
3.2 CLASS DIAGRAM..........................................................................................................................................27
3.3 ENTITY RELATIONSHIP DIAGRAM................................................................................................................27
3.4 DATA FLOW DIAGRAM................................................................................................................................28
3.4.1 Level 0................................................................................................................................................28
3.4.2 Level 1................................................................................................................................................29
3.4.3 Level 2................................................................................................................................................29
4. IMPLEMENTATION.....................................................................................................................31
4.1 TOOLS........................................................................................................................................................31
4.1.1 Web Application.................................................................................................................................31
4.1.2 Database.............................................................................................................................................31
4.1.3 Documentation...................................................................................................................................31
4.2 LANGUAGES............................................................................................................................................32
4.3 SNAPSHOTS OF FROND ENDH......................................................................................................................32
5. TESTING.........................................................................................................................................35
5.1 TEST CASES.................................................................................................................................................35
5.2 TID TEMPLATE.............................................................................................................................................37
5.3 DECISION TABLE..........................................................................................................................................37
5.4 BLACK BOX TESTING..................................................................................................................................38
5.5 WHITE BOX TESTING...................................................................................................................................38
6. RESULTS/OUTPUT/STATISTICS...............................................................................................40
6.1 TRACEABILITY MATRIX (TID VS UID).......................................................................................................40
6.2 % COMPLETION...........................................................................................................................................40
6.3 % ACCURACY..............................................................................................................................................40
6.4 % CORRECTNESS.........................................................................................................................................40
7. CONCLUSION AND SUMMARY.................................................................................................42
7.1 CONCLUSION...........................................................................................................................................42
7.2 SUMMARY................................................................................................................................................42
7.3 LESSON LEARNED..................................................................................................................................42
8. FUTURE WORK.............................................................................................................................44
9. REFERENCES................................................................................................................................46
LIST OF FIGURES
New figures that are given captions using the Caption paragraph style will be added to the table automatically. To
This section can be deleted if the document contains no figures or if otherwise desired.
Figure 1: System Level Use Case Diagram......................................................................................................9
Figure 2: Registered User...............................................................................................................................10
Figure 3 Login................................................................................................................................................11
Figure 4 Add to Cart.......................................................................................................................................12
Figure 5 Complaint Box.................................................................................................................................13
Figure 6 Categorized List...............................................................................................................................14
Figure 7 Approval Message............................................................................................................................15
Figure 8 Registration......................................................................................................................................16
Figure 9 Edit Product......................................................................................................................................17
Figure 10 Add Product....................................................................................................................................18
Figure 11 Admin Use Case.............................................................................................................................19
Figure 12 Order and Checkout.......................................................................................................................19
Figure 13 Chat Bots........................................................................................................................................20
Figure 14 Product Attribute............................................................................................................................21
Figure 15 Recommended Items......................................................................................................................22
Figure 16 Data Security..................................................................................................................................22
Figure 17 Social Sharing................................................................................................................................23
Figure 18 Secure Payment Portal...................................................................................................................24
Figure 19 SEO................................................................................................................................................25
Figure 20: System Architecture......................................................................................................................27
Figure 21 ER Diagram....................................................................................................................................28
Figure 22 Data Flow Diagram........................................................................................................................29
Figure 23 Level 0............................................................................................................................................29
Figure 24 Level 1............................................................................................................................................30
Figure 25 Level 2............................................................................................................................................30
LIST OF TABLES
New tables that are given captions using the Caption paragraph style will be added to the table automatically. To
This section can be deleted if the document contains no figures or if otherwise desired.
Table 1: Categories of Requirement.................................................................................................................4
Table 2: List of System Function Requirements..............................................................................................5
Table 3: List of Functional requirements attributes..........................................................................................5
Table 4: UC_01 View Details...........................................................................................................................8
1
INTRODUCTION
School of Commerce and Accountancy (SCA) <Usama Butt Online Shopping>
1. INTRODUCTION
Online Shopping is now on trending so that’s why I choose this subject. This is very
convenient website for everyone because of its easy and simple features. I can divide it in
3 sections means Admin, Manager and Users (Visitor and Registered User). Users as a
visitor can only viewing the website on our social media pages but not used add to cart
option. Registered user can view the website as well as buy anything through add to cart
option. A registered user need to login from his/her Username and Password then he will
be able to visit on website and buy anything from the website. If they have any problem
and difficulty then people ask anything.
1.1 Project Overview

My Project is basically on Online Shopping named Usama Butt Online Shopping which is
completely online for users. Online Shopping is now very famous all around because people are
so lazy to go outside and buy something according to their need. Online Shopping gives them a
calm feeling because our quality is 100% original with no drawbacks. Anything that is on the
picture is as same as the product. Customers just need to login to buy their products from our
website. Users can give their correct Username and Password then adds anything into their cart.
The product reached to them within 5 days with no complaints.
1.1.1 Problem Statement
These kind of website attract the people because now a days, people are so busy in their
routine and find no time to go outside and buy anything because of their busy schedule.
People can find it lazy to buy physically. Only few of them go outside and buy physically
but 90% people buy from online websites. My ultimate problem statement is to make
convenience for the customers.
1.1.2 Back Ground

Physical shopping is on trend on present but now people are so much busy and tired due to their
busy schedule. They find no time for outing and want some convenience to buy products at home.
This facility saves them from wasting their energy and time.
The Online Shopping facility solves 90% of problems of customer. They are so happy to get the
online shopping with advanced features. With the passage of time, these features become more
advance to make it more convenient.
1.1.2.1 Existing Systems
The existing system of online shopping is very slow which a headache for the customers because
they need fast system with easy and simple features. The existing system takes more time to load
means accessing speed is very slow which irritates the person and security feature is not good.
1.1.2.2 Drawbacks
The drawbacks of existing system was security feature, accessing speed, reliability and
efficiency. These are the main features to make website attractive.
1.1.3 Proposed Solution
Now people have more advanced features as compared to existing system. People have more
security features as compared to before in form of username and password. The websites
accessing speed is very fast and reliable for the users.
1|Page
School of Commerce and Accountancy (SCA) <Usama Butt Online Shopping>
1.1.3.1 Merits of Proposed Solution

The database provides the accessing to users for the reliability. The website has more advanced
features then the previous websites. The new websites has security features, reliability with the
perfect and amazing accessing speed.
1.1.4 Customer
The management system should be an open system and MIS should be so designed that it
highlights the critical business, operational, technological and environmental changes to
the concerned level in the management, so that the action can be taken to correct the
situation.
1.1.4.1 Affected Groups
To make the system a success, we are making the system more convenient for the users.
The main reason of the success of the website is to attract the people on your website.
1.1.5 Goals and Objectives
The objectives of my website is to provide the good quality fabric on very low prices. Our main
focus is to provide different brands on 1 platform. Our revenue model is transaction and sales
revenue model means we provides the sale services.
1.1.6 Assumptions
As the transactions are taking place every day, the system stores all the data which can be
used later on when the website is in need of some financial help from financial institutes
or banks.
1.1.7 Dependencies/ External Systems
The external system for the website is basically database which is used as a backend for the html.
The categories banner and product details, and add to cart option works with the Database.
1.1.8 Definitions and Acronyms
The system should be defined according to our rules and regulations. In this paragraph, we can
explain that how our system is defined like first user need login and password, secondly he can
visit the website as user and visitor. Then only registered users can used add to cart option.
1.1.9 Market Survey/ Domain Analysis
It tells about the markets the market conditions that how it will be going? We can analyze the
market to see that how the business and markets gone. Which are the ups and downs that I can
face in future which makes it easier for me to recover my lose in markets.
2|Page
2
SYSTEM REQUIREMENT SPECIFICATION
2. SYSTEM REQUIREMENT SPECIFICATION
2.1 Functional Requirements

Functional requirements are basically the features and functions that the software must offer. It is used to enable
users to perform their task. Functional requirements are different for each user like Admin, User and Manager.
Functional Category has 3 types:
 Website has Add to Cart Option which has all the products you select to buy.
 Website has proper Log in Page where you can register yourself.
 Website has Complain Page which is responsible to take complaints regarding products.
 We have 24 Hours Chatting Page where you can talk with us anytime.
 We have Categorized Products in website which is convenient for users to select anything like men,
women, kids etc.
 The system sends an approval request after customers enter their personal information.
 A system sends an Approval Request when new customer enters.
 We have secured Login option because sometimes unauthorized persons can hack the account.
 Only Admin is able to edit the products.
 Only admin has an option to edit and reset the password and email.
ID: User_01
Name: Add to Cart
Description Input Output Requirements Basic Work Flow
User can select User can The product Internet User can select anything and then
anything and Select the can added to Connectivity click onto add to cart option to
product and required,
then add that cart which add that product into list and after
then click it correct
product into on Add to you can username and that customer can delete or add
cart to sell that Cart Button. select. password. anything into add to cart option.
product.
ID: User_02
Name: Login for User
User can G mail Id The Admin Internet User can register them by giving
register them by can send Connectivity them their g mail account. Then it
required,
giving them them an will send to admin to approve the
correct
their g mail approve username and customer.
account. request to get password.
registered.
ID: User_03
Name: Complaint Page
If users have Correct The admin Internet User can complaint our product if
any problem username and can receive Connectivity they feel any problem with fabric
Password required,
with our the quality, color, fabric shrinking
correct
product like complaint username and etc.
quality then can and then password.
complaint. resolve that
issue.
ID: Admin_01
Name: Chatting Page
If users have User can chat The admin Internet User can chat with us in case of
any problem with admin to can receive Connectivity any difficulty like how to order,
keep in touch required,
with our the Message how to register etc.
but first enter correct
product like his id and and then username and
quality then can password to reply as soon password.
chat with us. login. as possible.
ID: User_04
Name: Categorized Products
If user want to User can enter The user can Internet User can buy anything what they
buy only Men the login and see the Connectivity want. Want to buy Men Collection so
password then required,
Collection then categorized just click on it and add that products
buy anything correct
they click on from website to List where they username and into cart.
different click on can buy password.
Categorized
categories to get anything.
Products.
the desired
Product.
ID: Admin_02
Name: Approval Request
If users User can enter The admin Internet User can visit our website first
registered on their can receive Connectivity and then if they want to
identification required,
website then the Message registered, they registered their
like id and correct
they can send password then and then username and self on website and waits for the
an request to registered decide for password. acceptance of request.
admin for them on approval .
website.
approval.
ID: Admin_04
Name: Edit the Product
Admin can edit Admin can Admin can Internet Admin can edit/delete or update the
the product only enter his click on edit, Connectivity product to meet the requirements.
password and required,
because he is the delete product
correct login. correct
main owner of Admin can to change the username and
the website. change/edit the requirement. password.
product price,
quality etc.
ID: Admin_05
Name: Edit/Reset the Login and Password

Admin can edit Admin can Admin Internet Admin can edit and reset the
and reset the enter his change the Connectivity login and password in case of
password and required,
password and id login and forget password.
correct login. correct
in case of password of username and
forget. specific user password.
ID: Visitor_01
Name: Contact through Social Media
Visitor can visit Visitor can Visitor in on Internet Visitor can visit our website by
the website then add the link of our website Connectivity proper link and click on our
our website. required,
click on social and on social media links to visit our
correct
media links to footer, he/she username and social media pages.
contact with us have links of password.
for information. social media.
ID: Admin_06
Name: Different Identity
Admin can give Admin can Admin can Internet Admin can enter his login and
different enter his see the list, Connectivity password and see the list, giving
Username and required,
password and giving different username and
Password correct
username to correctly. different username and passwords to each user for
every user for username password. security purpose.
security. and pass.
ID: Admin_03
Name: Chatting Page

After the Admin can The user can Internet . Admin can accept the approval
Approval accept the receive a Connectivity request and then send that
approval required,
Request, user message message to user to join our self.
request and correct
receives a then send that from admin username and User can join the website by
different message to to join the password. following id and password.
password. user to join website.
our self.
2.2 Non-Functional Requirement
 Website should take very less time to load so that it saves the time of user.
 The website should handle 20 million users at a time easily.
 Website is well maintained with proper working features.
 Our website has quick and better search result.
 Our website has accessibility standards on every device like mobile, laptops, pc etc.
 Website must have Security Features.
2.3 Use Case Models

 Actors & use cases
 Use case diagrams
 High level, essential use cases
2.3.1 List of Actors
 Admin
 Manager
 User
 Rider
 System
2.3.2 List of Use Cases
Admin can handle the approval list, management and validation. Manager can handle the overall process of buying. Users
can registered them and used add to cart option. Rider is responsible for delivering the product on time. System can behave
as secondary actor where flow ends.
 System Use Case
 Registration Use Case
2.3.3 Use Case Diagram
Figure 1: System Level Use Case Diagram

The above diagram shows the overall process of website and working of each actor which are included in the website.
 Admin can handle the approval list, management and validation.
 Manager can handle the overall process of buying.
 Users can registered them and used add to cart option.
 Rider is responsible for delivering the product on time.
 System can behave as secondary actor where flow ends.
2.3.4 Usage Scenario
In the usage scenario, each functional requirement can be describe separately to easily understand the overall functionality
of the website.
2.3.4.1 Use Case Scenario

Login
Add To Cart
Complaint Box
Chatting
Approval
Categorize Pro
SecuredLogin
Edit Product
Edit/Reset password
Click On Links
Different Username/password
Refunding
Cash on Delivery
Delete Product
Update product
Figure 2: Registered User

Login Visits on Website
Figure 3 Login
USE CASE 01 Login
Description User enters the information to login into website.

Preconditions User must have username and password.
Post-conditions Successfully login to admin panel.
Failed End User didn’t login to website and message is displayed “Incorrect username or
Condition password”
Actors Registered User
Trigger Login request comes in.

Basic Events Flow Step Action
1 User enters username

2 User enters password
3 Click on “Login” button.
4 Successfully login to website.
EXTENSIONS Step Alternative Flow (Branching Action)

1 User enters wrong username.
1. Display error message “Incorrect username”.
User enters wrong password.
2 1. Display error message “Incorrect password”.
Choose Add To
Login
Product Cart
Figure 4 Add to Cart

USE CASE 02 Add to Cart
Description Users select the following product and add that product into cart.
Preconditions User selects on any product.
Post-conditions Product added into cart successfully.
Failed End User didn’t add product and message displayed “Unable to add product”
Condition
Trigger Product added request comes in.

1 User clicks on categorized product.
2 User clicks on following product.
3 Click on “Add to Cart” button.
4 Successfully Product added into cart.
1 User enters on categorized products.
1. Display error message “unable to display”.
2 User enters on add into cart option.
1. Display error message “unable to add product”.
Superordinate Login authentication (use case 01)
Complaint
Login
Box
Figure 5 Complaint Box

USE CASE 03 Complaint Box
Description Users select the Complaint Box.
Preconditions User click on button of Complaints.
Post-conditions Complaint added successfully.
Failed End User didn’t add Complaint and message displayed “Unable to add product”
Condition
Trigger Complaint added request comes in.

1 User logins to website.
2 User clicks on complaint box.
3 Click on “Complaint Icon” button.
4 Successfully complaint added.
1 User selects complaint box.
1. Display error message “unable to select”.
2 User enters on complaint box.
1. Display error message “unable to add your complaint”.
Click on
Login
Categorized List
Figure 6 Categorized List

USE CASE 04 Categorized Products
Description Users select the following product according to categorization.
Preconditions User selects on any product.
Post-conditions Categorized Products page successfully opens.
Failed End User didn’t open product page and message displayed “Unable to open”
Condition
Trigger Product page open request comes in.

1 User clicks on products from navigation menu.
2 User clicks on categorized product.
3 Click on “Men Fashion” from the list.
4 Successfully Product page is opened.
1 User enters on categorized products.
1. Display error message “unable to display”.
2 User enters on Men Fashion,
1. Display error message “unable to open list”.
Registere Approval Msg
d
Figure 7 Approval Message

USE CASE 05 Registration
Description User can register himself and get approved by admin
Preconditions User must have internet connectivity
Post-conditions Registered successfully.
Failed End User didn’t get registered and message is displayed “Invalid/Incorrect
Condition Information”
Trigger Registration request comes in.

1 User enters all the required input.
2 Click “Register” button.
3 User registers successfully. Redirect to login page.
1 User enters wrong information.
1. Display error message “Invalid/Incorrect Information”.
2 User click “Cancel” button.
1. Clear data of all fields.
Superordinate No Superordinate
Registration Approval
Figure 8 Registration
USE CASE 06 Registration
Description User can register himself and get approved by admin
Preconditions User must have internet connectivity
Post-conditions Registered successfully.
Failed End User didn’t get registered and message is displayed “Invalid/Incorrect
Condition Information”
Trigger Registration request comes in.

1 User enters all the required input.
2 Click “Register” button.
3 User registers successfully. Redirect to login page.
1 User enters wrong information.
1. Display error message “Invalid/Incorrect Information”.
2 User click “Cancel” button.
1. Clear data of all fields.
Login Click Final Result
Figure 9 Edit Product

USE CASE 7 Change Information
Description User can change the information of his product.
Preconditions User must be login first and change the information.
Post-conditions Information changed successfully.
Failed End Condition Product information didn’t change and message is displayed “Invalid Information”.
Trigger Change Information request comes in.

1 Click on product.
2 Click on Edit option.
3 Enter Information.
3 Click “Saved” button.
4 Successfully information changed.

1 User enters Information.
1. Display error message “Unable to edit”.
2. Redirect to edit information page again.
2 User enters click “Back” button.
1. Information is clear.
2. Redirect to Previous module.
Login Click Final Result
Added
Figure 10 Add Product

USE CASE 8 Add Information
Description User can add the information of his product.
Preconditions User must be login first and add the information.
Post-conditions Information added successfully.
Failed End Condition Product information didn’t added and message is displayed “Invalid Information”.
Trigger Added Information request comes in.

1 Click on product Page.

2 Click on Add option.
3 Enter Information.
3 Click “Saved” button.
4 Successfully information added.

1 User enters Information.
1. Display error message “Unable to add”.
2. Redirect to add information page again.
2 Admin click “Back” button.
1. Information is clear.
2. Redirect to Previous module.
Figure 11 Admin Use Case
Use case diagram details:
Order&
Checkout
Admin
Figure 12 Order and Checkout
USE CASE 13 Order & checkout
Description Place order and after payment checkout is done.
Preconditions Order items, billing address, shipping address, Payment method
Post-conditions Order is places and delivered.
Failed End Order is not delivered.

Condition
Actors Admin
Trigger Order is received.

1 Items are selected and all the details are filled then order is preceded to
checkout.
1 Order is not delivered.
Chat Bots
Admin
Figure 13 Chat Bots
USE CASE 14 Chat Bots
Description Chat-bot is a program which generates automated text on behalf of a company to other
person.
Preconditions Text integrated in program of chat-bot.
Post-conditions Gives answer to other person on behalf of the company.
Failed End Message will not display.

Condition
Actors Admin
Trigger Gives an appropriate message

1 Auto generate text to a person on behalf of the company.

1 Message will not display.
Product-Attribute
Admin
Figure 14 Product Attribute
USE CASE 15 Product Attributes
Description Product attributes refer to the characteristics that define a service or product and
influence customer buying decisions.
Preconditions Product details
Post-conditions Products positive impression.
Failed End Failure in product display.

Condition
Actors Admin
Trigger Product details are managed.

1 Products are displayed and better presentation puts influence on buyer’s

decision.
1 Failure in product display.
Recommended
Items
Admin
Figure 15 Recommended Items
-
USE CASE 16 Recommended Items
Description Similar items are displayed under product user opens
Preconditions Similar products entries
Post-conditions Displayed similar product under product page

Failed End Recommended item will not show.
Condition
Actors Admin
Trigger Similar products are shown under the product details.

1 Similar products are shown under the products user opens.

1 Recommended item will not show.
User data
security
Figure 16 Data Security

Admin
USE CASE 17 User data security
Description We send confirmation massage to users to check their authenticity.

Preconditions User confirmation message
Post-conditions User data is secure.
Failed End User data leaked.

Condition
Actors Admin
Trigger User data is secured.

1 We secure the data of user though security systems applied in our website.

1 User data may leak.
Social sharing
Admin
Figure 17 Social Sharing
USE CASE 18 Social Sharing
Description Share the app link and products you like on different social media platform.
Preconditions Product and app links for sharing

Post-conditions Traffic for the website/app will increase.
Failed End Cannot share products on social media.

Condition
Actors Admin
Trigger Generates a link of product.

1 People share the products and the reach of website will increase and also the
popularity will surely increase.
1 Cannot share products on social media.
Secure payment
portal
Admin
Figure 18 Secure Payment Portal
USE CASE 19 Secure payment portal
Description We secure you bank details and Credit card details. So, we can provide secure
payment portal to our users
Preconditions Payment’s portals APIs are integrated in website
Post-conditions Secure transactions are done.
Failed End Transection is not done.

Condition
Actors Admin
Trigger Online money transfer is done
1 Payments for the products are done though payment portals.

1 Transection is not done.
SEO
Admin
Figure 19 SEO
USE CASE 20 SEO
Description SEO is done to rank your website or ecommerce store on first page of google.
Preconditions Tags, attractive heading and thumbnail.

Post-conditions Website’s ranking will improve.
Failed End Traffic cannot be generated on website.

Condition
Actors Admin
Trigger Online money transfer is done
1 Put targeted keywords, detect on-site issue and detect them, optimize your
website.
1 Traffic cannot not be generated on website.
3
SYSTEM DESIGN
3. SYSTEM DESIGN
3.1 System Architecture

Describe the system architecture, or simply provide the architecture diagram. For School
system it may include web based front end, web server, database etc. Don’t worry too
much about it just give a simple diagram of a typical web based project?
System Architecture Diagram
Figure 20: System Architecture

3.2 Class Diagram
Admin User
Login
Login
Logout
Logout
Add Product
Add Product
Reset Email
Delete Product
Update Product
Refund Money
Reset Password
Group Chatting
Add User
Cart Product
Name
Price Name
Description Price
Description
3.3 Entity Relationship Diagram
Delete Update
product/user product/user
Login or Reset Reset

Logout Email Password
Add
product/user
Admin Registered
Login
Add/Del User
Products
Chatting Logout
Refund
Money
Name
Price
Product Selects
Description
Add to
Name
Price
Cart
Description
Figure 21 ER Diagram
3.4 Data flow Diagram
Figure 22 Data Flow Diagram
3.4.1 Level 0
Figure 23 Level 0
3.4.2 Level 1
Figure 24 Level 1
3.4.3 Level 2
Figure 25 Level 2
4
IMPLEMENTATION
School of Commerce and Accountancy (SCA) <Project Name>
4. IMPLEMENTATION
We all know that database provides quick access. In my website, we are using database in
products and banners that users track each and every product from the categorized list
and each product from database.
4.1 TOOLS
I used Sublime Text, Wamp Server, Html5 Markers, CSS3, SQL, and PHP.
4.1.1 Web Application
 SUBLIME TEXT
It is suitable editor for Web Based Application. It has many functions like Multiple
Selections, Page Linking, and other emits which helps the programmer to complete the
coding in a convenient manner.
 HTML5
It is a Hyper Text Markup Language which is used to build the structure of the website. It
is the core of Web Based Application. HTML5 is the latest version which has very easy
tags to implement.
 CSS
tags to implement.
4.1.2 Database
 SQL
Structured Query Language is used to add, update or delete something from the website.
We can used SQL to Add, Update, and Delete the products from the website.
 WAMP SERVER
We can used Wamp Server as to connect the html with database. It needs no internet to
connect it. For the purpose of connection, we can used this server. It creates a host on the
local machine in which we are working.
4.1.3 Documentation
 MICROSOFT WORD
It is used in documentation of the website in which the detailed explanation is done. It
can also be used to verify the functions used in website.
33 | P a g e
 Adobe Photoshop
I used Photoshop to make my logo and About Us page boxes which will display with the
display picture.
 Visual Paradigm
Visual Paradigm is used to make UML means Use Case Diagrams. It helps to make quick and
easy making of the system diagram. It is easy to use and manage because of drag and drop option
of the elements like Actors, Lines and Shapes.
TECHNIQUES
 MYSQL
Structured Query Language is used to add, update or delete something from the website.
We can used SQL to Add, Update, and Delete the products from the website.
 PHP
It is used to connect the html with database. It needs no internet to connect it. For the
purpose of connection, we can used this server..
4.2 LANGUAGES
 HTML
tags to implement.
 CSS
tags to implement.
4.3 Snapshots of Frond Endh

Form Title: Heading of the form
Interface Id: UI – 01
Description: When user opens the website, it will display the page.
Snapshot:
34 | P a g e
35 | P a g e
5
TESTING
5. TESTING
5.1 Test Cases

Test Cases should be at least against use cases
Test Case Id User_02
Test Engineer Names of testers
Functional Login page

Area
Test Name Verification of login fields
Objective The purpose of this test is to ensure that the system is not allowing
the user to login if valid username and password is not given.
Environment .Net, PHP, SQL
Strategy 1. Enter invalid login details

2. Press login
Expected Error message displayed indicating the missed fields and/or invalid
Result data
Test Result Pass
Functional Add to Cart

Area
Test Name Verification of login fields
Objective The purpose of this test is to ensure that how much products are
added into cart to get the total amount.
Strategy 1. Select the Product
37 | P a g e
2. Press on Add to Cart Button
Expected Error message displayed indicating the missed fields and/or invalid
Result data
Test Result Pass
Functional Complaint page

Area
Test Name Verification of complaints
Objective The admin can receive the complaint and then resolve that issue.
Strategy 1. Select the Complaint Icon.

2. Press on Button of Whatsapp.
Expected The message is shown about the disconnection of internet.

Result
Test Result Pass
Functional Categorized Products

Area
Test Name Categorization of Products
Objective The user can see the categorized List where they can buy anything.
38 | P a g e
Strategy 1. Select the Categorized list.

2. Click on Categorize Product.

Result
Test Result Pass
Test Case Id Admin_01
Functional Approval Request

Area
Test Name List of Approvals
Objective The admin can receive the Message and then decide for the approval
Strategy 1. Click on Approval List.

2. Select the users to add into website.

Result
Test Result Pass
Functional Edit/Reset the Login and Password

Area
39 | P a g e
Test Name List of Customers Request
Objective Admin can edit and reset the login and password in case of forget
password.
Strategy 1. Click on specific customer.

2. Select the customer and reset/edit the options.
Expected The message is shown about error.

Result
Test Result Pass
Functional Order and Checking

Area
Test Name List of Orders
Objective Order items, billing address, shipping address, Payment method.
Strategy 1. Click on specific customer.

2. See the customer full information of orders.
Expected The message is shown about error.

Result
Test Result Pass
5.2 TID template

While the database provides quick access and track for the entire work history, every
employee can be able to view only their personal information over systematic human
resource information system.
40 | P a g e
5.3 Decision Table
5.4 Black Box Testing

Black box testing means that only specific features are shown to users foe the security
and privacy purpose like only admin can reset/update the password and see list of
customers.
5.5 White Box Testing

White box testing is basically the features that are displaying on the screen means the
entity and its attributes like customers can see the product and they can also see the
options of colors and size of different brands.
41 | P a g e
6
RESULTS/OUTPUT/STATISTICS
6. RESULTS/OUTPUT/STATISTICS
6.1 Traceability Matrix (TID vs UID)
6.2 % Completion
About 80% is current completion rate.
6.3 % Accuracy
About 90% is current accuracy rate.
6.4 % Correctness
About 90% is current correctness rate.
43 | P a g e
7
CONCLUSION & SUMMARY
7. CONCLUSION AND SUMMARY
7.1 CONCLUSION
My Final Project is on Usama Butt Online Clothing Website in which we are using
different languages like HTML, CSS and PHP which is connected with Database. I am
taking clothes from different brands and sell them on 1 Platform for customer
convenience. It gives satisfaction to those people who have no time to go outside for
shopping.
7.2 SUMMARY
When you open your website home page is displayed. We have 6 subpages like Home
page, Product Page, Login Form, Location, Services and Contact Us Page. The home
page contains the Navigation Bar, Categories List and Product List with Banner and
Footer. Product Page basically has the album of Products to make the website more
attractive. Login form page contains the proper form which has your proper details like
name, age, address, password etc. Location page has the pin location of our company
of online clothing. The services page has 3 things which are Services, Quality and
History means About Us page. We have 24 hours of services and we entertain every user
of our website. Quality page contains the information about our cloth that how they
make with original soft cotton. Services Page contains that in how many days your order
is delivered with charges. About us page contains the history like when we starts our
company and what is our objective. The Last is our Contact us page which has our
email address, Whatsapp Cell no with 24 hours services.
7.3 LESSON LEARNED

I have learned a lot from this final project. Because when I start this project, I learned that how
much I didn’t know about the website. This final project gives me a chance to prove my
hardworking efforts.
45 | P a g e
8
FUTURE WORK
8. FUTURE WORK
 The first thing is to make the website easier.

 The second thing is to make email notification.
 To make the website more advance and attractive.
 To add more webpages into the website.
 One proper registration module.
 To viewable for the visitors.
 To make the website with more fun features.
 To increase the brands list to our website.
 The congratulating messages on 10,000 shopping with fireworks.
 Website will be more efficient and reliable with perfect speed.
47 | P a g e
REFERENCES
9
48 | P a g e
9. REFERENCES
 [ CITATION Abi21 \l 1033 ]

 [ CITATION Var21 \l 1033 ]
 [ CITATION Bja21 \l 1033 ]
49 | P a g e

Online Clothing Store

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Clothing Store

Uploaded by

Copyright:

Available Formats

Usama Butt Online Shopping

Name Usama Ayyaz Butt

Online Clothing Store

Mr. Gulfraz Naqvi

A Report Submitted to the School of Commerce & Accountancy

Student Name Student-ID

Usama Ayyaz Butt S2020387012

Gulfraz Naqvi ---------------------------------------

Mr. Muhammad Azeem Naz

School of Commerce & Accountancy

1. I thanked to my Allah Almighty who gave me confidence and courage to complete

Author: Usama Ayyaz Butt

Usama Butt Online Shopping

Approved on: _________________

Name: Usama Ayyaz Butt

1.1 Project Overview

1.1.2 Back Ground

1.1.3.1 Merits of Proposed Solution

2.1 Functional Requirements

Name: Add to Cart

Description Input Output Requirements Basic Work Flow

Name: Login for User

Description Input Output Requirements Basic Work Flow

Name: Complaint Page

Description Input Output Requirements Basic Work Flow

Name: Chatting Page

Description Input Output Requirements Basic Work Flow

Name: Categorized Products

Description Input Output Requirements Basic Work Flow

Name: Approval Request

Description Input Output Requirements Basic Work Flow

Name: Edit the Product

Description Input Output Requirements Basic Work Flow

Name: Edit/Reset the Login and Password

Description Input Output Requirements Basic Work Flow

Name: Contact through Social Media

Description Input Output Requirements Basic Work Flow

Name: Different Identity

Description Input Output Requirements Basic Work Flow

Name: Chatting Page

Description Input Output Requirements Basic Work Flow

2.2 Non-Functional Requirement

2.3 Use Case Models

Figure 1: System Level Use Case Diagram

2.3.4.1 Use Case Scenario

Figure 2: Registered User

Description User enters the information to login into website.

Trigger Login request comes in.

1 User enters username

3 Click on “Login” button.

4 Successfully login to website.

EXTENSIONS Step Alternative Flow (Branching Action)

Figure 4 Add to Cart

Trigger Product added request comes in.

Figure 5 Complaint Box

Trigger Complaint added request comes in.

Figure 6 Categorized List

Trigger Product page open request comes in.

Figure 7 Approval Message

Trigger Registration request comes in.

Trigger Registration request comes in.

Figure 9 Edit Product

Actors Registered User

Trigger Change Information request comes in.