1

Abstract

The business-to-consumer aspect of electronic commerce (e-commerce) is the most

visible business use of the World Wide Web. The primary goal of an e-commerce
site is to sell goods and services online. This project deals with developing an
ecommerce website for online shopping. It provides the user with a catalog of
different product available for purchase in the store. In order to facilitate online
purchase a shopping cart is provided to the user. The system is implemented using
a 3-tier approach, with a backend SQL Server database, a middle tier apache server
and a web browser as the front end client. In order to develop online shopping
application use HTML, CSS, JAVA Script, server side scripting language ASP.Net
and relational database SQL Server. This is a project with the objective to develop a
basic website where consumer is provided with a shopping cart application and also
to know about the technologies used to develop such an application.
2

ACKNOWLEDGEMENT

I would like to express my deepest appreciation to all those who provided me the possibility to
complete this report. A special gratitude I give to our course
instructor, Dr. Nadeem Ahsan, whose contribution in stimulating suggestions and
encouragement, helped me to coordinate my project especially in writing this report.

Furthermore, I would also like to acknowledge with much appreciation the crucial role of the staff,
who gave the permission to use all required equipment and the
necessary materia.ls to complete the task “Online Shopping System”. A special
thanks goes to my teammate, [Muhammad Huzaifa Khan, Muhammad Usama Sohail, Shehroz
Lodhi], who help me to assemble the parts and gave suggestion about the task “Online
Shopping System”. Finally yet importantly, many thanks go to the head of the project,
[Muhammad Huzaifa Khan] whose have invested his full effort in guiding the team in achieving
the goal.
3

About Team
Team Profile:
We are three members in the team, namely: Muhammad Huzaifa Khan,
Muhammad Usama Sohail, and Shehroz Lodhi.

• Muhammad Huzaifa Khan

Email address: [email protected]
Reg #: 34856
Mobile #: +92 312 2282334
Signature: _____________
• Muhammad Usama Sohail
Email address: [email protected]
Reg#: 34836
Mobile#: +92 347 2748779
Signature: _____________
• Shehroz Lodhi
Email address: [email protected]
Reg#: 35049
Mobile#: +92 332 1346756
Signature: ______________
4

Introduction
Purpose
The purpose of this SRS document is to provide a detailed overview of our Online shopping
system, its parameters, functionalities and goals. This document describes the project's target
audience and its user interface, hardware and software requirements. This document is intended
for understanding the definition of requirements that are necessary for the development of the
system. Shopping has long been considered as a refreshment by many. Shopping in online
became a recreational activity of life. The reason of developing web based online shopping
system is everyone walking down the street has some difficulties, also some people are so much
busy and not able to go out for shopping, some don’t like to shop in crowd. There is another
reason that it’s not possible to see all the product of a store, also its hazardous for both the
customer and the seller. The world of software development there lots of improvement in this
area and to reduce the complexity of people of life online shopping system development. Online
shopping system is a virtual store on Internet where customer can browse the product and select
the product of interest. The selected product may be collected in shopping cart. At checkout time
the items in the shopping care will be presented as an order. At that time shipping information
and payment method have to select to the customer. Finally by confirming the order have to
complete the shopping and the product will deliver to customer via currier, post office or by
direct agent of company.
This document act as basis for:
• Needs to be satisfied in the architectural and detailed design of the Online shopping
system Project.
• Needs to be satisfied in the verification, validation and acceptance testing for the online
shopping project.

Objectives
The objective of the Shopping systems is to increase the point of customer choice, reduce time
used in shopping and efficiency in buying product.
• To develop an easy way to use web based interface where users can search for product
view the details of the product and order it without going to market.
• The searching product can be done by product category, manufacturer as well as latest
product, view it purchase it become a convenient way for customer.
• Customer can add product to cart to purchase, delete the product from cart before
selecting the final submission.
• A user can view the complete specification of the product with various images and also
view the customer review the product.
5

• It minimize the shopping time of customer, increase the point of choice. 2

• It also facilitate the service provider to know the current stats of market and take decision
which product are selling more now a days and have to keep in store.

Intended Audience and Reading Suggestions

This document is intended to be read by the developer team, project, stakeholders, and users. This
is technical document and terms should be understood by the customer. This SRS is designed for
the persons present in this whole project so that they come to know about project and what to
change in the project in future if want, such as

 Developers: As different modules of a project are developed by different members of a

team. So to have knowledge of other modules of the project SRS are designed. So that an
individual member of a team come to know about the whole modules of the project.

 Project Managers: Members who are going to manage this project must know about
the project that’s why this SRS is designed. So that the members can manage the project
according to its design.

 Marketing Staff: What the developed software/project can do, what was its need, how
it can be helpful to the users all this information’s are provided to the marketing staff
through this SRS. Through that a good marketing can be provided to the project and its
marketing price will be good.

 Users: Through this SRS the user come to know about the benefits of the project and
how to gain full performance from the project.

 Testers: The different tests through which the software/project must undergo are
described in SRS.
6

Project scope:
The people faces problem in shopping , they suffers from traffic and travelling in multiple shops
of multiple brands and if they wanted any desire product then have to search in multiple shops,
this make people frustrated and in case the item founded then its prize are high in cost. The scope
of online shopping system is to facilitate user with shopping in hand, have various product of
various brand with best price rates, the product are categorized. The specific product user wanted
and is not visible in product then there is search bar where user can search any product by its
name.

Following are the scope of the developed systems:

For Customer:
Online registration: Customer have to register to buy product online.

View Product: Customer can view product according to category, manufacturer and latest
product. Select the items to cart, also can delete from cart before final submission, he can also
view product details, shipping info and price that means all in invoice.

Shipping Information: Customer have to give the product delivery location.

Payment Method: Customer can select the payment method what is easy for him for payment
the cost.

For admin:
Category: admin can add category, view, publish, unpublished, edit and delete category.

Manufacturer: admin can add manufacturer, view, publish, unpublished, edit manufacturer and
delete manufacturer.

Product: admin can add product, view, publish, unpublished, edit manufacturer and delete
product. Product delivery status: Admin can update sold product status.
7

Problem Description:
Need of the application
There are large numbers of commercial Online Shopping websites offering large number of
products tailored to meet the shopping interests of large number of customers. These online
marketplaces have thousands of products listed under various categories.

Problems:
• Going from store to store and comparing products and prices is a challenging and time
consuming procedure
• The quality of service is poor and most of the time, retailers aren’t that much interested in
customer because the retailer loses interest when the customer didn’t choose any items
and the retailer shows all stocks.

• To change your mind after a purchase is an issue, but to go through all the hassle of
taking the product back to that store again. On top of that, that dread that you’ve already
lost the receipt so there would be no hope for any returns.

• When it comes to occasion then there is too crowded out there. Shopping in malls gets a
little overwhelming, especially with all the weekend hustle and bustle and in occasions.

• Confusion create in retail shopping because everything looks the same, each retail shop
sells exactly the same item from the next, but different in price with blaming other
retailer, so where’s the luxury of diversity in this.

Solutions:
• The online shopping system provide the platform where anyone can purchase desire items
from anywhere.
• Provide Interactive interface through which a user can interact with different areas of
application easily.
• A search engine that provides an easy and convenient way to search for products specific
to their needs.
• Provide Drag and Drop feature thereby allowing the user to add products to or remove
products from the shopping cart by dragging the products in to or out of the shopping
cart.
• If the product deliver have problem or defect in product then the product will be return
with no charges.
• Web-based stores are open 24/7; this means you can make purchases when you have the
desire and spare time. Thus you can make purchases at any time of day and night.
8

Requirement Elicitation
9

Questionnaires:
Background:
1. What type of system application you required?
2. Is this system is new?
3. It must keep data.
4. Is user view product without register?
5. Information must keep confidential.

Functional:
1. How would you like to brand your store?
2. What types of products do you sell?
3. Who are your competitors?
4. Do you need sales tax calculated?
5. Do you need to offer coupons?
6. Do you need to compute shipping?
7. How would you like products organized?
8. Do you have product descriptions available?
9. Do you sell digital products (movies, music, e-books)
10. Do you want to have product reviews?
11. Are there product photos organized?
12. Do you need professional photographs taken?
13. How would you like products organized?
14. What forms of payment do you accept (e.g. Visa, PayPal, Master-Card, COD)
15. What features should your ecommerce website contain (user registration, file upload,
contact form, photos, videos, etc.)?
16. How is your sales funnel represented in your site?
17. Do you need custom sales reporting?
18. What keywords do people use in search engines to find your site?
19. How do people contact you for inquiries?
20. Do you have built-in support (e.g. on-site chat, phone?)
21. -How do you plan to host the site?
22. optional (what technology you want to use in site (.net, php)
23. What is your budget and your deadline for completing the shopping website?
24. Do you have any color preferences or look and feel for the ecommerce website orange,
green, violet?
25. What do you NOT want on your ecommerce website in terms of content, colors, graphic
elements, etc.?
26. Do you have existing marketing efforts that this needs to tie in to?
1
0

27. What types of marketing are you currently using? (SEO, Banner Ads, Print ads, Radio,
RV)
28. -Do you want social media integration with the shopping cart?
Non-Functional:
1. Is the system will be easy to use by user?
2. Time for verifying password to maximize performance?
3. Total number of client?
4. Typical expected timeframe for system active hours?
5. Are there security concerns related to data access?
6. Is the data recoverable if the system crash or network goes fail?
7. Which browser the system should support and show all features in low network?
8. Is the user inputs are confidential and provide safety?

Answers:
 What type of system application you required?
Web site
 Is this system is new?
Yes
 It must keep data.
Yes
 Is user view product without register?
Yes
 Information must keep confidential.
Yes
 How would you like to brand your store?
Ans: With a delightful designing, deliberate structure, come up with a good logo, and
research about my target audience and competitors, applying branding across my
business to evolve it to grow more.

 What types of products do you sell?

Ans: Clothes, All Electronic items, Furniture, Watch.

1
1

 Who are your competitors?

Ans: HomeShopping.pk, Symbios.pk, Daraz, Yayvo, iShopping.pk

 Do you need sales tax calculated?

Ans: Often.

 Do you need to offer coupons?

Ans: Yes, as it is a good marketing tool for business.

 Do you need to compute shipping?

Ans: Yes

 How would you like products organized?

Ans: According to the consumer’s choices, their needs and wants.

 Do you have product descriptions available?

Ans: Yes.

 Do you sell digital products (movies, music, e-books)

Ans: Only e-books.

 Do you want to have product reviews?

Ans: Yes

 Are there product photos organized?

Ans: Yes

 Do you need professional photographs taken?

Ans: Yes

 How would you like products organized?

1
2

Ans: According to the limit of number on a page, best sellers and by keeping it simple
with fewer but good options.

 What forms of payment do you accept (e.g. Visa, PayPal, Master-Card, COD)

Ans: I want PayPal and MasterCard and Visa

 What features should your ecommerce website contain (user registration, file upload,
contact form, photos, videos, etc.)?
Ans: Sign Up, Login, Customer Care, Departments, Order, Cart, Deals, Help etc.
 How is your sales funnel represented in your site?
Ans: Visitors enters website, visit product pages, add products to cart, fill out shipping
and billing info, buy.
 Do you need custom sales reporting?
Ans: Yes
 What keywords do people use in search engines to find your site?
Ans: Cabinat.pk.
 How do people contact you for inquiries?
Ans: Through the feature added in website called “HELP” which contains, email and
other contact details.
 Do you have built-in support (e.g. on-site chat, phone?) Ans: No.
 -How do you plan to host the site?
Ans: By choosing a good hosting server and a good website hosting plan.
 optional (what technology you want to use in site (.net, php) Ans: asp.net
 What is your budget and your deadline for completing the shopping website?
Ans: I want website in 2 months and my budget is 150000.
 Do you have any color preferences or look and feel for the ecommerce website orange,
green, violet?
Ans: I think White and Green looks good.
 What do you NOT want on your ecommerce website in terms of content, colors, graphic
elements, etc.?
1
3

Ans: Too much product offerings in one page (it should be in a number of limitations so
the consumer could not get confused while shopping), too much irrelevant or unnecessary
features, harsh colors, too much deals (discounted deals).
 Do you have existing marketing efforts that this needs to tie in to?
Ans: Yes with a good marketing strategies and “Seven P Formula”.
 What types of marketing are you currently using? (SEO, Banner Ads, Print ads, Radio,
RV)
Ans: Banner Ads.
 -Do you want social media integration with the shopping cart?
Ans: Yes.
 Is the system will be easy to use by user?
Yes, the system will be user friendly.
 Time for verifying password to maximize performance?
2 second.
 Total number of client?
20,000
 Typical expected timeframe for system active hours?
24/7.
 Are there security concerns related to data access?
Yes, the only admin can access the data.
 Is the data recoverable if the system crash or network goes fail?
Yes the system will recover all data input by user if system fails or network down.
 Which browser the system should support and show all features in low network?
The system supports all browser and yes show all feature in low network.
 Is the user inputs are confidential and provide safety?
The account detail of user should be confidential and only admin can access the data with
proper authentication.
1
4

Feasibility Study:-
A feasibility analysis usually involves a thorough assessment of the operational (need), financial
and technical aspects of a proposal. Feasibility study is the test of the system proposal made to
identify whether the user needs may be satisfied using the current software and hardware
technologies, whether the system will be cost effective from a business point of view and whether
it can be developed with the given budgetary constraints. A feasibility study should be relatively
cheap and done at the earliest possible time. Depending on the study, the decision is made whether
to go ahead with a more detailed analysis.
When a new project is proposed, it normally goes through feasibility assessment. Feasibility study
is carried out to determine whether the proposed system is possible to develop with available
resources and what should be the cost consideration. Facts considered in the feasibility analysis
were.

System Feasibility:
The system feasibility can be divided into the following sections:

Technical Feasibility
It is a study that checks if the system under consideration can be operated with available resources.
Here it checks whether the system can be operated efficiently with current equipment and existing
software technology and available manpower. Our System can satisfy this aspect of feasibility, the
environment of software is ASP.NET under C#. The web applications created with ASP.NET are
easier to create, debug, and deploy because those tasks all be performed within a single
development environment – Visual Studio .NET. To deploy the application, the only technical
aspects needed are mentioned below:

• Operating Environment Win 10/8.1 Platform

• .Net Framework & IIS
• Database SQL Server 2018
1
5

Economic Feasibility
The project is economically feasible as the only cost involved is having a computer with the
minimum requirements mentioned earlier. For the users to access the application, the only cost
involved will be in getting access to the Internet, and the cost involved will also be domain on which web
site will deploy

Operational / Behavioral Feasibility:

Our system is very user friendly and easy to operate that any person can easily operate / use it. If
the required information necessary for handling the system is given to the user. User would easily
be friendly with the system overall our system is operationally feasible. The application requires
no special technical guidance and all the views available in the application are self-explanatory.
The users are well guided with warning and failure messages for all the actions taken.

.
1
6

Tools for Requirements:

Software Components:
• Operating Environment Win 10/8.1
• Platform .Net Framework & IIS Visual Studio 2017.
• Database SQL Server 2018.

Hardware Components:
• Processor – i3

• Hard Disk – 5 GB

• Memory – 1GB RAM

1
7

Requirements Specification
1
8

FUNCTIONAL REQUIRMENT:

Login: -The system should have login so the user shall give their id and
password in field if user want to buy the product.
Search: -The system should have the search bar in which user can search any
type of desire product.
Product Description: -The system should have the description of product when
user click on the product image the page will open in which the description is
available of that product.
Add to Cart: -The system have the feature of cart in which the user wants to
buy multiple products so he can put each product into cart when the wish list
complete the user will go to cart and buy products.
Sign up: -The system should have create account feature with no repeat
username, which leads to buy product from system by user.
Payment Method: -The system should have payment method to facilitate user
to input info to selected method and purchase the desire item with generated
recipe and message on given number.
Feedback: -Further features include feedback option and a complain box. In
case of any mishap user can submit complain at the given email address or
contact number.
CRUD Operations: -The System should have feature in admin site to
create/add new product or update the existing product and if the product is out
of stock or old then delete the product.

Image uploading feature: -The system should have image upload feature in
admin site in which admin add the 5 image new product or upload 5 images of
existing product.

Product Categorization: -The system should facilitated user by an additional

and immensely useful feature of diving their products into sub categories by
selecting given option showing (winters, summers, vintage, modern, popular
etc.) for each product accordingly.
1
9

Coupons: -The system should have coupons feature in admin site which admin
offers the coupons to user for marketing on special days (father’s day, mother’s
day, Friday etc.).

Order: -The system should have the order page, the page shows all delivered
and in progress order (with duration of delivery).

Compute Shipping: -The system should shows the user how much time it will
take to reach product to user.

Contact/Help/Customer Care: -The system should have the page of contact us

which help user to ask queries if user have any problem related to the product or
in purchasing.
2
0

Non-Functional Requirement:

Access-Security: -The system should capable to safeguard against deliberate and

intrusive faults from internal and external sources, and secure with authentication
of admin username and password.

Efficiency: - The response time of the system shall be quick as it does not exceed 8
seconds, and the system will give access when there is low network.
Reliability: -The system will not crash/fail, in some condition if the system fails to
respond then it will recover in mentioned time that is 15 mint and have capability
to support 20,000 client per second.
Availability: - The system should be capable to give availability to mentioned time
that is 24/7 and in some condition the system not respond or network down the
system will show the last page as stored in cache.

Recoverability: -When the system fails in any condition (system crash or network
down) and when the system is recover, the system should have capability to
recovers with entered data, so there is no need to enter many times same data.

Usability: -The System should be friendly with user and very simple to understand
the operation/function which should be deployed to facilitate users.
Portability: -The system should compatible with all browser in user system.
Maintainability: -The system should capable of finding and fixing the bugs in
minimum resources and time.
2
1

Requirement Analysis
2
2

UML Use Case

2
3

Use Cases Description

The list of possible interactions between a user and the system are
mention here.

UC-01 Log In
Requirement To be able to Log In.
Initiating Actors User does initiative step.
Actor’s goal To access the system for purchasing the items.
Participating Actors User
Pre-conditions Clicking on the Log-In.
Post-conditions Be Log-In in to the system to see the products
and purchase desire item.
Flow of events  Visit the website
 Click on the Log-In menu
 Enter valid Name and password
 Click the log in button.
2
4

UC-02 Sign up/Create Account

Requirement To be able to sign up.
Initiating Actors User does initiative step.
Actor’s goal To be registered in the system for purchasing
the items.
Participating Actors User
Pre-conditions Clicking on the sign up.
Post-conditions Be signed in to the system to see the
products and purchase desire item.
Flow of events  Visit the website
 Click on the sign-up menu
 Enter valid information
 Be signed in after completion
of the signup procedure.
2
5

UC-03 Search Item

Requirement To be able to search the items.
Initiating Actors User does initiative step.
Actor’s goal To search desire product by product name in
search bar.
Participating Actors User
Pre-conditions Clicking in the Search bar.
Post-conditions To view the desire product which search by its
name.
Flow of events  Visit the website
 Click in the search bar
 Enter the name of desire item.
 Displayed the list of searched
item.
2
6

UC-04 View Item

Requirement To be able to view item by its category.
Initiating Actors User does initiative step.
Actor’s goal Not to search the items which are displayed in
front page of the system by its category.
Participating Actors User
Pre-conditions Visit the website.
Post-conditions Displayed the items by its category.
Flow of events  Visit the website
 Displayed the items.
2
7

UC-05 Add-to-cart
Requirement To be able to view the list of all selected item for
purchase.
Initiating Actors User does initiative step.
Actor’s goal To store the desire item in bucket and purchase
all items as Once.
Participating Actors User
Pre-conditions Clicking on the Add To Cart button.
Post-conditions The system will store the item in cart
Flow of events  Visit the website.
 Click on the product.
 Click the Add to cart below the product.
2
8

UC-06 Remove-From-cart
Requirement To be able to remove the items from the list of
all selected item for purchase.
Initiating Actors User does initiative step.
Actor’s goal To remove the item from cart list if does not
want to purchase.
Participating Actors User
Pre-conditions Clicking on the Cart Option and click on remove
option beside product.
Post-conditions The item remove from cart list
Flow of events  Visit the website.
 Click on the cart option.
 Click the remove option beside the
product.
2
9

UC-07 Buy
Requirement To be able to purchase the product direct or
purchase from cart list.
Initiating Actors User does initiative step.
Actor’s goal To purchase desire product from website.
Participating Actors User
Pre-conditions Clicking the buy option below the product
description.
Post-conditions The system displayed the payment method page
Flow of events  Visit the website.
 Click on the product.
 Click buy option below the product
description.
3
0

UC-08 Payment
Requirement To be able to do payment from selected method.
Initiating Actors User does initiative step.
Actor’s goal To make payment of selected method.
Participating Actors User
Pre-conditions Clicking the pay button below in cart and provide
necessary information.
Post-conditions The system will show the recipe and display the
date of delivery of item.
Flow of events  Visit the website.
 Click on any product.
 Click on buy option.
 Click on pay.
 Displayed dialog box.
 Provide necessary information.
3
1

UC-09 Review Product

Requirement To be able to write review about product.
Initiating Actors User does initiative step.
Actor’s goal To give feedback to product quality.
Participating Actors User
Pre-conditions Clicking on the rate/review option.
Post-conditions The system will display field for review and
shows the stars for rating.
Flow of events  Visit the website.
 Click on any product.
 Click on rate/review option.
 Click on field.
 Write review.
 Click the stars.
3
2

UC-10 Manage Order

Requirement To be able to cancel or update the order.
Initiating Actors User does initiative step.
Actor’s goal To cancel the order or add another purchase
item in same order.
Participating Actors User
Pre-conditions Clicking on manage order option.
Post-conditions The system will open the page of current order
with cancel and update button.
Flow of events  Visit the website.
 Click on manage order
option.
 Click on cancel button to
cancel.
 Click on update button for
add more item for
purchase.
 Write review.
3
3

UC-11 Log-Out
Requirement To be able to Log-out from system.
Initiating Actors User does initiative step.
Actor’s goal Provide authentication, the user can log-out
from system.
Participating Actors User
Pre-conditions Clicking on the Log-out option.
Post-conditions The system will come and show home/front
page.
Flow of events  Visit the
website.
 Click on Log-
out.
3
4

UC-12 Customer Detail

Requirement To be able to see the profiles of user.
Initiating Actors Admin does initiative step.
Actor’s goal To view the customer details/information except
account info.
Participating Actors Admin
Pre-conditions Clicking on User Detail option.
Post-conditions The system will display all user which are
registered in system with detail in different
fields.
Flow of events  Visit the website.
 Click on menu.
 Click on user detail.
3
5

UC-13 Product Description

Requirement To be able to add about product.
Initiating Actors Admin does initiative step.
Actor’s goal Add the description of product, for more detail
about item.
Participating Actors Admin
Pre-conditions Clicking on Add description.
Post-conditions The system will display field where the text
appear.
Flow of events  Visit the website.
 Click on menu.
 Click on products.
 Click on Add description.
3
6

UC-14 CRUD Operation

Requirement To be able to add, update and remove the
product from system.
Initiating Actors Admin does initiative step.
Actor’s goal Delete/remove old product which are out of
stock, update the product with diff image, color
and add new products.
Participating Actors Admin
Pre-conditions Clicking on Add, remove or edit in product.
Post-conditions The system will display dialog box with required
fields.
Flow of events  Visit the website.
 Click on menu.
 Click on product.
 Click on edit, remove or add.

\
3
7

Sequence Diagram
1. Register

For purchasing items from system the user have to log in the system, for log in the
system the user should have account in the system. The user have to register in
system by clicking create account, in registration page screen there will be multiple
field which is necessary to fill with unique username the user will register in
system database then he/she can purchase and add-to-cart items.
3
8

2. Login

In diagram the user will login the system, the system verifies the username and
password from database and return back the message if the username and password
are correct the user enter in system and if wrong the system shows message. The
user need to login if he want to purchase and add to cart the items.
3
9

3. Add-To-Cart

The diagram shows that the user want that product and not to find again and again
the user can add that product to cart, the system will add that product t cart and
assign a unique id as order no.
4
0

4. Submit/Checkout

The diagrams shows that the user add the items into cart and then he/she checkout
the cart, the cart will generate recipe of all items in cart with their quantity and
their prize and in last of recipe, generates total prize which are payable if user want
to purchase that all items.
4
1

5. Purchase

The diagram shows that the user want to purchase directly then the user will
browse item select the item click on purchase the system will shows him/her the
selected item with its prize and if he/she wanted to purchase he have to select the
method and provide information then the system will notify in email.
4
2

6. Add New Product

The diagram shows that the admin wants to add new product to the system then
he/she click the add product then upload images of product with product detail and
then save the product in database, and then the system display that item in
products.
4
3

7. Add New Category

The diagram shows that the admin wants to add new category to the system then
he/she click the add category with category detail and put product under that
category and then save the category in database, and then the system display that
product under new category.
4
4

8. Add New Brand

The diagram shows that the admin wants to add new brand to the system then
he/she click the add brand with brand detail and put product of that brands under
that brand and then save the brand in database, and then the system display that
product under new brand.
4
5

Entity Relationship Diagram

4
6

Data Flow Diagram

Context Level Diagram
4
7

Level 1 Diagram
4
8

Level 2 Diagram

Process 1 level 2
4
9

Process 2 Level 2
5
0

Requirement Validation
51

Test Case :1 Test Case title: Login based on different roles

(Admin, User).
Test Case Module ID: TC1 Test Designed by: Shehroz Lodhi
Test Priority: High Requirement Functional Testing

Testing Objective: To make sure the login page redirect user to the correct page based
on their roles.

Test Case ID Test Case Expected Result Reason Note

Result (Pass/Fail)

TC # 1.1 Verify login Redirect login Pass

user as admin user to the
role. admin page.
TC # 1.2 Verify login Redirect login Pass
user as user to the
customer role. home page.

Test Case :2 Test Case title: View, Edit, Insert, Delete

information of product.
Role (Admin).
Test Case Module ID: TC2 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing

Testing Objective: To make sure that admin can view register User detail and also
admin can perform CRUD operations on products.

Test Case ID Test Case Expected Result Result Reason Note

(Pass/Fail)
52

TC # 2.1 Verify that Redirect admin Pass

admin can view to the User
user detail. Detail page.
TC # 2.2 Verify that Redirect admin Pass
admin can to the
Edit user detail. User Detail
page.
TC # 2.3 Verify that Redirect admin Pass
admin can to the User
Delete user Detail page.
detail.
TC # 2.4 Verify that Redirect admin Pass
admin can View to the Product
Product Detail. Detail page.
TC # 2.5 Verify that Redirect admin Pass
admin can Edit to the Product
Product Detail. Detail page.
TC # 2.6 Verify that Redirect admin Pass
admin can to the Product
Delete Detail page.
Product Detail.
TC # 2.7 Verify that Redirect admin Pass
admin can Insert to the Product
Product Detail. Detail page.

TC # 2.8 Verify that Redirect admin Pass

admin can Edit to the Product
Product Image. Detail page.

TC # 2.9 Verify that Redirect admin Pass

admin can to the Product
Delete Detail page.
Product Image.
TC # 2.10 Verify that Redirect admin Pass
admin can Insert to the Product
Product image. Detail page.
53

Test Case :3 Test Case title: Manage information of Stock,

Account, Order, and Order History.
Role (Admin, User).
Test Case Module ID: TC3 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing

Testing Objective: To make sure that admin can manage stock of product, Users can
create and manage and Admin can Manage their Account, Order and order History.

Test Case ID Test Case Expected Result Reason Note

Result (Pass/Fail)

TC # 3.1 Verify that Redirect Pass

admin can admin to the
Manage stock stock Detail
detail. page.
TC # 3.2 Verify that Redirect Pass
admin can admin to the
Manage Its admin Profile
Account detail. page.

TC # 3.3 Verify that Redirect Pass

admin can admin to the
Manage Order Order Detail
history. page.
TC # 3.4 Verify that Redirect Pass
admin can admin to the
Manage new Order Detail
Order. page.
TC # 3.5 Verify that Redirect User Pass
User can to the User
Manage its Profile page.
profile.
54

TC # 3.6 Verify that Redirect User Pass

User can to the Mange
Manage its Order page
Order. where he or
she can
update or
cancel his
order.
TC # 3.7 Verify that Redirect User Pass
User can to the Sign-up
create its page.
Account.
TC # 3.8 Verify that Redirect User Pass
User can check to the Order
its Status page.
Order Status.

Test Case :4 Test Case title: Cart System.

Role (User).
Test Case Module ID: TC4 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing

Testing Objective: To make sure that User can Manage its Shopping Cart.
55

Test Case ID Test Case Expected Result Result Reason Note

(Pass/Fail)

TC # 4.1 Verify that Redirect User to Pass

User can Add the Product
items to the page.
cart and
continue
shopping.
TC # 4.2 Verify that User Redirect User to Pass
can remove the Product
items to the cart page.
and continue
shopping.
TC # 4.3 Verify that If Redirect User to Pass
the user adds the Product
the same item page.
to the cart while
continuing to
shop, the
item count in
the shopping
cart should get
incremented.
TC # 4.4 Verify that If the Redirect User to Pass
user deletes the the Product
same item to page.
the cart while
continuing to
shop, the item
count in the
shopping cart
should get
decremented.

TC # 4.5 Verify that all Redirect User to Pass

items and the
their totals Shopping Cart
should be page.
display in cart.
56

Test Case :5 Test Case title: Checkout and Payment Role

(User, Admin).
Test Case Module ID: TC5 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing
Testing
Objective: To make sure that User can Manage its Shopping Cart.

Test Case ID Test Case Expected Result Reason Note

Result (Pass/Fail)

TC # 5.1 Verify to Redirect User Pass

Check to the
different checkout
payment page.
options
TC # 5.2 Verify that if Redirect User Pass
customer is to the Login
log-in or not. page.
TC # 5.3 Verify that Redirect User Pass
Emails/Text to the
confirmation Payment
with the order successful
number page.
generated is
sent to the
User.

TC # 5.4 Verify that Redirect Pass

Payment is admin to the
successfully Payment page.
paid or not.

Testing
57

Test Case :6 Test Case title: Search and view product. Role
(User).
Test Case Module ID: TC6 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing

Objective: To make sure that User can view product and also search product.

Test Case ID Test Case Expected Result Reason Note

Result (Pass/Fail)

TC # 6.1 Verify that Redirect User Pass

User can to the
easily Search product
product by its page.
name or not.
TC # 6.2 Verify that Redirect User Pass
User can to the
view product Product
or not. page.
Test Case :7 Test Case title: Review product. Role
(User).
Test Case Module ID: TC7 Test Designed by: Shehroz Lodhi
Test Priority: Medium Requirement Functional Testing

Testing Objective: To make sure that User can review product.

Test Case ID Test Case Expected Result Reason Note

Result (Pass/Fail)

TC # 7.1 Verify that Redirect User Pass

User can to the
Review product
product. Detail page.
Requirement Management
Change Management

Stakeholder Request
Change Management Plan

SR# Requirement Description Priority Status

R1 Mobile App of the System High pass
R2 Wallet System Low pass

Details of Changes:

1 – Mobile App of the System

After meeting the clients for changing it was decided that not now but in future
there will be a mobile app of this system for stakeholders.
Status: Accepted.
2 – Wallet System.
The Wallet System should have added to the system, so the user can uses wallet
system instead of any payment method and should be deposit from any bank
account. The icon of wallet on menu bar which shows the amount.
Status: Accepted.
 Requirement Tracing:
Traceability Metric:
NO# Module Name Applicable Roles Description
1 Create Account Customer User have to Create account to buy any thing
2 Login Admin and Customer Admin and Customer Both have to login but in
a different context like admin have to login to
perform task like CRUD operation etc. and User
have to login in the system to buy anything.

3 Search Product Customer User can perform search operation on products.

4 Order Status Customer User can check order status that his/her order is
on his/her way or not.
5 View Items Customer User can view al items/Products on Home Page
of the Website.
6 Add To Cart Customer User can add item on cart.
1 Remove Item Customer User can remove item from his cart.
7 Buy Customer User can select any payment method to buy
anything.
8 Payment Admin and Customer User can also perform COD etc. And admin can
view it that payment is clear or not.
9 Manage Order Admin and Customer User can also perform Cancelation or Update
order and It is based on time Limit and admin
can view it that User canceled the order or
update the order or not.
10 Review Product Customer User can give reviews to products.
11 Order History Admin and Customer Admin and User both can check their previous
history.
12 Log Out Admin and Customer Admin and User Both can perform Logout.
13 Product Description Admin Only admin can add description of product.
14 Coupons Admin Only admin can add Coupons code. So that user
can get discount on some products.
15 Manage Account Admin and Customer Admin and User Both can Update his/her
profile.
16 Upload Image Admin Only admin can add Images of product.
17 CRUD Operation Admin Only admin can CRUD operation of product.
18 Manage Stock Admin Only admin can Manage Stock of product.
19 View Customer Admin Only admin can view detail of registered Users.
Detail
20 Wallet Option Customer User can Wallet their money and can use it.
Like Careem Mobile Application.
 Plan Of Work

Our group believes in dedication and hard work as its quoted that “hard work is the
key to success”. Our team consists of good web developers and our team members
are skilled enough to document the hard work we are putting into this project. It
would have been much more difficult to implement this project with less than three
people because team size matters. Every team member is going to have an
individual responsibility to take care of.
Programming cannot alone do the job; it needs proper methodology,
documentation, testing and management to bring the best out of the project. We
plan to give the client “the best”: The definition of “best” they believe in. Every
individual has a different choice and has different priorities in their lives.
Teamwork can either make a project up to mark or let it fall below the mark, so we
plan to work together and help each other out if any of the members faces a
difficulty in their individual responsibility.
These individual responsibilities are assign to each of the member of the group:

 Muhammad Huzaifa Khan: Programming, Database designing

and Management.
 Muhammad Usama Sohail: Programming, Documentation and
Presentation.
 Shehroz Lodhi: Documentation, Database designing and testing.