SOFTWARE REQUIREMENTS SPECIFICATION

WEB BASED SHOPPING CART APPLICATION

FOR
CR COMPUTER STORE

Version 01

Prepared by

Code Revolution

Created: 2022/02/08
 Table of Contents

Table of Contents.........................................................................................................................................i
List of Tables.............................................................................................................................................iii
List of Figures............................................................................................................................................iv
1 Introduction.........................................................................................................................................1
1.1 Purpose........................................................................................................................................1
1.2 Scope...........................................................................................................................................1
1.3 Definitions, abbreviations and acronyms.....................................................................................1
1.3.1 Definitions...........................................................................................................................1
1.3.2 Abbreviations and acronyms................................................................................................1
1.4 References...................................................................................................................................2
1.5 Overview.....................................................................................................................................2
2 Overall Descriptions............................................................................................................................3
2.1 Product Perspective.....................................................................................................................3
2.1.1 User Interfaces.....................................................................................................................3
2.1.2 Hardware interfaces.............................................................................................................3
2.1.3 Software interfaces..............................................................................................................3
2.1.4 Communication interfaces...................................................................................................3
2.1.5 Memory...............................................................................................................................3
2.2 Product functions.........................................................................................................................3
2.3 User characteristics......................................................................................................................4
2.4 Constraints...................................................................................................................................4
2.5 Assumptions and dependencies...................................................................................................5
3 Specific Requirements.........................................................................................................................6
3.1 Functional Requirements.............................................................................................................6
3.1.1 User Management................................................................................................................6
3.1.2 Product Management...........................................................................................................6
3.1.3 Order Management..............................................................................................................7
3.1.4 Order Placement..................................................................................................................7
3.2 External Interface Requirements..................................................................................................8
3.2.1 User interfaces.....................................................................................................................8
3.2.2 Hardware interfaces.............................................................................................................8
 3.2.3 Software interfaces..............................................................................................................8
3.2.4 Communications interfaces..................................................................................................8
3.3 System Features...........................................................................................................................8
3.4 Nonfunctional Requirements.......................................................................................................9
3.5 Design Constraints.......................................................................................................................9
3.6 Other Requirements.....................................................................................................................9
Appendix...................................................................................................................................................10
List of Tables
 List of Figures

Figure 1: Block diagram of proposed System..............................................................................................3

1 Introduction

1.1 Purpose

In the face of the current corona situation, many businesses have to face various difficulties. Many
customers are reluctant to come to businesses thinking that they will have to maintain social remoteness
and stay in queues. Therefore, are seeing a decline in selling price. The same situation affected to the CR
computer stores. Therefore, they expect a solution to reduce the cost of running in their business and to
improve their business needs. So, we hope to create a web-based shopping cart as a solution to that.
The SRS document can be used as a reference document to help developers to understand the client
needs and the quality assurance team can be used it as a reference document to create the test code.
Marketing and other departments use this as a reference document to get some idea about this project.

1.2 Scope
This is a system for ordering computers and accessories. We plan to market the device by
manipulating it under three categories. That is, desktop parts, laptop parts and other accessories. In
addition, more sub-categories will be added under this category as mentioned earlier and it is hoped
to submit items for sale within that sub-category. You will also be given a unique item code to
identify the item separately. Clicking on the desired item allows the client to view a description of
the desired item. Mainly a shopping cart option will be provided and the customer will be provided
with the facilities required to retain temporary items and to vimu and update the item when it is no
longer needed. Shopping details are obtained from the customer before placing an order and will
vary depending on the area where the shopping cost is increased. Although the online order auction
is given here, the online payments concept is not used and payments are made for cash on delivery.
Customer checkout sends order details via email and does not use the SMS alert option. Customers
do not have to wait in long queues and can save time by leaving the desired item anu anu on the
website. Therefore, the spread of covid 19 can be minimized as it can create social isolation

1.3 Definitions, abbreviations and acronyms

1.3.1 Definitions
 Customer: -
 Order cancellation: -

1.3.2 Abbreviations and acronyms

 CR: - Code Revolution
 SCA: - Shopping Cart Application
 SRS: - Software requirements specification
 N/A: – Not Applicable
1.4 References

1.5 Overview
2 Overall Descriptions
2.1 Product Perspective
2.1.1 User Interfaces

Front end: -
login, Home, product search, Product details, Shopping Cart, Checkout

Back-end
Login, Dashboard, report, Add product

2.1.2 Hardware interfaces

 Processor (CPU): Intel Core i3
 Operating System: Microsoft Windows 7-10 Professional x64
 Storage:80 GB internal storage drive or higher
 Monitor/Display:17"
 Network Adapter: 100mbps or higher LAN connection or Wi-Fi adapter
 Other: Mouse, Keyboard

2.1.3 Software interfaces

 Xampp
 MySQL
 Visual Studio Code
 Notepad++

2.1.4 Communication interfaces

stable network Connection & Bandwidth above 1mbps.
2.1.5 Memory
4GB or higher

2.2 Product functions

 User Management –
 Staff - Staff registration will be done by the admin. Admin can add and delete users.
Staff can login to the system by using admin provide details.
  Customer - Customer can create their own account by using the user registration
feature and they can add, edit, and view details related to them.

Product Management (Inventory) –

 Admin/Staff users can create categories using the category adding form.
 Admin/Staff users can create, edit, delete and view product details.

• Order Management -
 Admin/Staff User can view the Already placed orders and they are able to change order
status as well. (Waiting for approvals, Order Processing, Delivered, Order Cancel)

• Product page / Home Page -

 Product page / Homepage - Customers can view the Featured and latest product on the
home page and they can view individual product details by clicking on the product (Product
page)

• Report –
 Admin/Staff users can see the sale reports (Daily Sale, Top Selling Product and etc.)

• Order Placement (Checkout/Payment and delivery)

 Customers can add, edit or remove products from checkout
 Customers can make payment method
 Customers can add delivery details

2.3 User characteristics

 Customer should have basic English knowledge.
 Customer Should have knowledge about Add, Edit, Delete and view functions.
 Customer should have ability to search product or category.
 Admin/Staff Member should have Basic English knowledge.
 Admin/Staff Member Should have knowledge about Add, Edit, Delete and view
functions.
 Admin/Staff Member should have ability to search product or category.
 Admin/Staff Member should have ability to generate the report and sort report data.
 Admin/Staff Member should have ability to understanding the error messages popup by
the system.

2.4 Constraints
 Website only include cash on delivery payment method. Online payment (payment
Gateway) system is not implemented.
  Customer will be able to cancel the order if the order status “Waiting for Approval” Only.

2.5 Assumptions and dependencies

 This web Application run on the localhost therefore application will not be able to run
mobile devises and over the internet.
 Administrator is created in the system already.
3 Specific Requirements
3.1 Functional Requirements
3.1.1 User Management
i. Create/ Register User
1. Customer should be able to create account using registration form
on the front end by filling required details. (Name, Email, Mobile,
Password)
2. Admin should be able to create staff users on the dashboard
ii. Login to system
1. Customer should be able to login to the system using email and
password.
2. Staff should be able to login to the system using credentials that
provide by admin.
3. Admin should be able to login system using admin user details
(email & Password)
iii. Maintain Profile
1. Customer should be able to add new details in the profile section
2. Customer should be able to edit the details in the profile section
3. Customer should be able to view the details in the profile section
4. Customer should be able to change password in the profile section
5. Staff member should be able to change password in the profile
section.
6. Staff member should be able to edit the details in the profile
section.
7. Staff member should be able to view the details in the profile
section.
8. Admin should be able to change password in the profile section
9. Admin should be able to edit the details in the profile section.
10. Admin should be able to view the details in the profile section.
11. Admin should be able to delete the staff users on the dashboard
(staff user section)

3.1.2 Product Management

iv. Create / Modify Category
1. Admin should be able to Create category on the system
2. Admin should be able to edit category on the system
3. Admin should be able to Delete category on the system
v. Product and Quantity Allocation
1. Admin should be able to Create product on the system by filling
required details
2. Admin should be able to edit product details on the system.
 3. Admin should be able to view product details on the system.
4. Admin should be able to delete product details on the system.
5. Admin should be able to add product quantity on the system.
6. Staff member should be able to Create product on the system by
filling required details
7. Staff member should be able to edit product details on the system.
8. Staff member should be able to view product details on the system.
9. Staff member should be able to add product quantity on the
system.

3.1.3 Order Management

vi. View Orders
1. Admin should be able to view order details on the system.
2. Staff member should be able to view order details on the system.

vii. Change order status

1. Admin should be able to approve orders in the order section.
2. Staff member should be able to approve orders in the order section.
3. Admin should be able to change order status to Processing,
Delivered, Cancel in the order section.
4. Staff member should be able to change order status to Processing,
Delivered, Cancel in the order section.

3.1.4 Order Placement

viii. Checkout
1. Customer should be able to add the product to the checkout
2. Customer should be able to edit the product quantity in the
checkout
3. Customer should be able to remove product from the checkout
4. Customer should be able to proceed the next step in the checkout.
ix. Payment
1. Customer should be able select Cash on delivery payment method
in the payment area.
x. Delivery details
1. Customer should be able to add the delivery address on the
delivery area.
3.2 External Interface Requirements
3.2.1 User interfaces

3.2.2 Hardware interfaces

Since we are running the system on the localhost, we need a PHP engine and MySQL
database server. To install the above software (Xammp), we need a PC with the operating system.
We are using I3 Processor with 4GB Ram to run the system smoothly.

3.2.3 Software interfaces

All software that we are using to develop this project is free and open-source software,
they are Notepad++, Visual Studio Code, Xampp, MySQL, Bootstrap.
Notepad ++ and Visual Studio Code are used as IDEs to create the system, and it helps to
do code. Also, it gives suggestions to developers, helps to debug, and more. It helps improve the
efficiency of developers.
This system is based on localhost. Therefore, we are using Xampp software. Furthermore,
PHP is a server-side scripting language, and Xampp helps run PHP language on computers.

Bootstrap is used as a CSS styling framework. Also, we have used custom CSS to create
unique styles.

We have used jQuery and JavaScript for Calculation, Validations and animation.

3.2.4 Communications interfaces

We need a stable network connection to access the system from different Pc in the
local area network. It will be better to have good bandwidth Over 1mbps.

3.3 System Features

User Management -
The customer should be using a unique email address to register the user.

Order Placement:
The customer should u
se the correct Province in the delivery address. A delivery address will be calculated based on
Province.
3.4 Nonfunctional Requirements
Security -
The system should have client-side validation. We can use JavaScript and jQuery to achieve the
requirement.
We can force the customer to enter valid data into the system by using validation.

Usability -
The user interface should be designed as a user-friendly design. The user should be able to perform
operations without navigating through multiple pages/links (easily Navigating to the system
option).

Performability –
Increase page loading speed and calculations using JavaScript and jQuery

3.5 Design Constraints

3.6 Other Requirements

N/A
Appendix