Software Requirements Specification Online Shopping System

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7

Software Requirements Specification

Online shopping system

Submitted by

Ali Hassan 70070890

Ghulam Mahio Din 70067397

Muhammad Kashif 70067946

Rana Ammar Talat 70070400


Software Requirements Specification for <Project> Page

Table of Contents
Table of Contents.............................................................................................................................
Revision History...............................................................................................................................
1. Introduction................................................................................................................................
1.1 Purpose.............................................................................................................................................
1.2 Document Conventions.....................................................................................................................
1.3 Intended Audience and Reading Suggestions...................................................................................
1.4 Product Scope...................................................................................................................................
1.5 References........................................................................................................................................
2. Overall Description....................................................................................................................
2.1 Product Perspective..........................................................................................................................
2.2 Product Functions.............................................................................................................................
2.3 User Classes and Characteristics.......................................................................................................
2.4 Operating Environment.....................................................................................................................
2.5 Design and Implementation Constraints...........................................................................................
2.6 User Documentation.........................................................................................................................
2.7 Assumptions and Dependencies........................................................................................................
3. External Interface Requirements.............................................................................................
3.1 User Interfaces..................................................................................................................................
3.2 Hardware Interfaces..........................................................................................................................
3.3 Software Interfaces...........................................................................................................................
3.4 Communications Interfaces..............................................................................................................
4. System Features.........................................................................................................................
4.1 Description.........................................................................................................................................
4.1.1 Registeration...................................................................................................................................
4.1.2 Login..............................................................................................................................................
4.1.3 Changes to Cart...............................................................................................................................
4.1.4 Payment..........................................................................................................................................
4.1.5 Logout…………………………………………………………………………………………….
5. Other Nonfunctional Requirements.........................................................................................
5.1 Performance Requirements...............................................................................................................
5.2 Safety Requirements.........................................................................................................................
5.3 Security Requirements......................................................................................................................
5.4 Software Quality Attributes..............................................................................................................
5.5 Business Rules..................................................................................................................................

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> page 2

1. Introduction

1.1 Purpose
The Robo shop Store (RS) web application is intended to provide complete solutions for customers
using the internet as the sole medium. It will enable customers to browse through the shop and
purchase them online without having to visit the shop physically. The administration module will
enable a system administrator to add, remove or maintain various products of shop.

1.2 Document Conventions


 Convention for main title:
o Font Face: Times New Roman.
o Font Style: Bold.
o Font Size: 32

 Convention for sub title:


o Font Face: Times New Roman.
o Font Style: Bold.
o Font Size: 32

 Convention for body:


o Font Face: Times New Roman.
o Font Style: Normal.
o Font Size: 11.

1.3 Intended Audience and Reading Suggestions


While the software requirement specification (SRS) document is written for a more general
audience, this document is intended for individuals directly involved in the development of
SplitPay. This includes software developers, project consultants, and team managers. This
document need not be read sequentially; users are encouraged to jump to any section they find
relevant.

1.4 Product Scope


 Secure registration and profile management facilities for Customers.
 Creating a Shopping cart so that customers can shop ‘n’ no. of items and checkout finally
with the entire shopping carts. Customers can add or delete items in the cart.
 Admins are responsible for internal affairs like processing orders, assure home delivery,
updating order's status.
 Feedback mechanism, so that customers can give feedback for the product they have
purchased. Also facility rating of individual products by relevant customers.
 Adequate payment mechanism for credit cards or PayPal.
Software Requirements Specification for <Project> page 2

1.5 References
 https://www.hostgator.com/blog/get-ecommerce-website-running/
 https://www.webalive.com.au/ecommerce-website-features/
 https://www.hostgator.com/blog/what-is-ecommerce/?
utm_source=google&utm_medium=genericsearch&gclid=CjwKCAiAp8iMBhAqEiwAJb94
z0UACGPMIxvTFTdiIurjM7YrA72PB3xOxeLCW6q-
mjFxLbld7vukqhoC6DIQAvD_BwE&gclsrc=aw.ds

2. Overall Description

2.1 Product Perspective


The Online Shopping system (OSS) web application enables customers to browse through the
products, and a system administrator to maintain products. Also the developer is designing an
online shopping site to manage the items in the shop and also help customers to purchase them
online without visiting the shop physically.The online shopping system will use the internet as the
sole method for selling goods to its consumers.

2.2 Product Functions


 Full featured shopping cart
 Product reviews and ratings
 Top products carousel
 Product pagination
 Product search feature
 User profile with orders
 Admin product management
 Admin user management
 Admin Order details page
 Mark orders as delivered option
 Checkout process (shipping, payment method, etc)
 PayPal / credit card integration
 Database seeder (products & users

2.3 User Classes and Characteristics


The user should be familiar with the Shopping Mall related terminology like Shopping
cart/ Checking out/ Transaction etc. The user should be familiar with the Internet and terms like
login, ordering system.

2.4 Operating Environment


The product supports all known operating systems, such as windows, linux. Roob shop system is a
website and shall operate in all famous browsers, for a model we are talking Microsoft Internet
Explorer, Google Chrome and Mozilla Firefox. Also it will be compatible with the IE 6.0. Most of
the features will be compatible with the Mozilla Firefox and Opera 7.0 or higher version. The only
requirement to use this online product would be the internet connection.
Software Requirements Specification for <Project> page 2

2.5 Design and Implementation Constraints


An online store is a virtual store on the Internet where customers can browse the catalog and select
products of interest. The selected items may be collected in a shopping cart. At checkout time, the
items in the shopping cart will be presented as an order. At that time, more information will be
needed to complete the transaction. Usually, the customer will be asked to fill or select a billing
address, a shipping address, a shipping option, and payment information such as credit card number.
An e-mail notification is sent to the customer as soon as the order is placed

2.6 User Documentation


There will be no need of user manual because everybody is familiar with internet and websites.

2.7 Assumptions and Dependencies


The assumptions are:-

1) The coding should be error free.

2) The system should be user friendly so that it is easy to use for the users.

3) The system should have more capacity and provide fast access to the database.

4) The system should provide search facility and support quick transactions.

5) The robo shop system is running twenty four hours a day.

6) Users may access from any computer that has internet browsing capabilities and an internet
connection.

7) User must have their correct usernames and passwords to enter into their online accounts
and do actions.

The dependencies are:-

1) The specific hardware and software due to which the product will be run.

2) On the basis of listing requirements and specification the project will be develop and run.

3) The admin should have proper understanding to the product.

4) The information of all users must be stored in a database that is accessible by the robo shop
system. .
Software Requirements Specification for <Project> page 2

3. External Interface Requirements

3.1 User Interfaces


Admin can view, delete or update product’s details or user’s details. User can only view product’s
details. If a user enter wrong email or password there will be an alert message and when user
successfully login or registered there should appear an alert message success.

3.2 Hardware Interfaces


 Any known operating system such as Windows, Linux or MacOS.
 Ram should be minimum 512 MB.
 A keyboard and a mouse.

3.3 Software Interfaces


Web Application is designed to run on any platform.

3.4 Communications Interfaces


The Customer must connect to the Internet to access the Website:

 Dialup Modem of 52 kbps


 Broadband Internet
 Dialup or Broadband Connection with a Internet Provider.

4. System Features
This section provides requirement overview of the system. Various functional modules that can be
implemented by the system will be

4.1 Description

4.1.1 Registration

If customer wants to buy the product then he/she must be registered, unregistered user can’t go to
the shopping cart.

4.1.2 Login

Customer logins to the system by entering valid user id and password for the shopping.
Software Requirements Specification for <Project> page 2

4.1.3 Changes to Cart

Changes to cart means the customer after login or registration can make order or cancel order of the
product from the shopping cart.

4.1.4 Payment

In this system we are dealing the mode of payment by credit card and PayPal.

4.1.5 Logout

After ordering or surfing for the product customer has to logout.

5. Other Nonfunctional Requirements

5.1 Performance Requirements


There is no performance requirement in this system because the server request and response is
depended on the end user internet connection.

5.2 Safety Requirements


Information transmission should be securely transmitted to server without any change in
information

5.3 Security Requirements


 System will use secured database.
 Normal users can just read information but they cannot edit or modify anything except their
personal and some other information.

5.4 Software Quality Attributes


 There may be multiple admin’s creating the project, all of them will have the right to create
changes to the system. But the members or other users cannot do changes.
 The project should be open source.
 The quality of the database is maintained in such a way so that it can be very user friendly to
all the users of the database.

5.5 Business Rules


A business rule is anything that captures and implements business policies and practices. A rule can
enforce business policy, make a decision, or infer new data from existing data. This includes the
rules and regulations that the system users should abide by. This includes the cost of the project and
the discount offers provided. The users should avoid illegal rules and protocols. Neither admin nor
members should cross the rules and regulations

You might also like