l

2
Software Requirements Specification for QuickPay Page 1

SOFTWARE REQUIREMENT
SPECIFICATION
DOCUMENT

QUICKPAY
Software Requirements Specification for QuickPay Page 2

By:
Prasuk Jain (IT-66)
Raj Verma (IT-71)
Tanya Shrivas (IT-88)

1. Introduction

1.1 Purpose
QuickPay is an e-commerce website which offers mobile recharging, and adding bill
payment, with products similar to businesses such as Amazon,Flipkart,Snapdeal.

1.2 Product Scope

With the current payments ecosystem and infrastructure, wallets cannot be a
wholesome payment instrument anytime soon. Instead of getting into the consumer
wallet business, it would be worthwhile to create a smartphone friendly payment
network which will address interoperability issues for banks and merchants.

1.3 Intended Audience and Reading Suggestions

The intended audience for this QuickPay software are consumers, merchants,
freelancers, small business owners, entrepreneurs and other users who need a secure
and convenient way to manage their finances online.
Software Requirements Specification for QuickPay Page 3

1.4 References

1.4.1 www.google.com

1.4.2 scribd.com

1.4.3 wikipedia.com

1.4.4 softwareanalysis.com

2. Overall Description

2.1 Product Perspective

The QuickPay network doesn't work independently. It has to work with the computer
/software owned by QuickPay. They are clearly defined interfaces for the different
systems.

2.2 Product Functions

The software should support a mobile payment network. Each paytm account has its
own data in the database to maintain its accounts and process transactions. When we
Login a QuickPay account it communicates with the QuickPay's database.In QuickPay
wallet we can add money by Debit card , Credit Card, NetBanking.The QuickPay
account requires appropriate details to keep our wallet secure. We can also transfer
our wallet money to a bank account.

2.3 User Classes and Characteristics

There are several users of the QuickPay Network :

● Customers
Customers interact with the QuickPay network via app/website. It must be very easy to
use QuickPay. Everyone who uses a smartphone can easily use QuickPay.

● Maintainer
Using QuickPay is easy but to maintain it is a bit difficult. We have been working
together to maintain the database and the internal functions that users can't see.
Software Requirements Specification for QuickPay Page 4

2.4 Operating Environment

The online transaction app is designed to operate in a variety of environments to enable

seamless transactions for users. The following are the operating environments that are
supported:

1. Operating Systems: The app is compatible with the following operating systems:
 Android OS (version 5.0 and above)
 iOS (version 11 and above)
2. Web Browsers: The app can be accessed using the following web browsers:
 Google Chrome (version 85 and above)
 Mozilla Firefox (version 80 and above)
 Apple Safari (version 13 and above)
3. Internet Connectivity: The app requires a stable internet connection for performing
transactions. The following types of internet connectivity are supported:
 Wi-Fi
 3G/4G/5G mobile data network
4. Hardware Requirements: The app requires a device with the following hardware
specifications:
 At least 2GB RAM
 At least 16GB of internal storage
 At least a 1.5 GHz processor speed

2.5 Design and Implementation Constraints

Design Constraints:

1. Security: The app must be designed to ensure secure transactions and protect
user information from unauthorized access or malicious attacks.
2. Usability: The app must be user-friendly and easy to navigate, with a clear and
intuitive interface.
3. Compatibility: The app must be designed to work on a variety of devices and
platforms, including mobile devices and web browsers.
4. Performance: The app must be designed to perform transactions quickly and
efficiently, with minimal latency and downtime.
5. Scalability: The app must be designed to handle a large number of transactions
and users, with the ability to scale up or down as needed.

Implementation Constraints:
Software Requirements Specification for QuickPay Page 5

1. Technology Stack: The app must be developed using a specific technology

stack, including programming languages, frameworks, and tools, to ensure
compatibility and performance.
2. Third-Party Integrations: The app may require integration with third-party
services for transactions, such as payment gateways or banks, which may
require specific APIs or protocols.
3. Database Management: The app must be designed to manage user data and
transaction records in a secure and efficient manner, using appropriate
database management systems and technologies.

3. External Interface Requirements

3.1 User Interfaces

1. Login/Signup Screen:
 The first screen will ask the user to log in or sign up if they haven't registered
yet.
 It will ask for the user's email address and password or allow them to sign up
using their Google or Facebook account.
 It should also have a "Forgot Password" option for users who may have
forgotten their login details.

2. Home Screen:
 After logging in, the user is redirected to the home screen, where they can view
their account balance, transaction history, and available options.
 The home screen should have an easy-to-use navigation menu with options like
"Send Money," "Receive Money," "Withdraw Funds," "Add Funds," "Profile," and
"Settings."

3. Send/Receive Money Screen:

 When the user selects "Send Money" or "Receive Money" from the navigation
menu, they are taken to a screen where they can enter the recipient's email
address or phone number and the amount of money to be sent/received.
 They should also have the option to add a message to the transaction.

4. Withdraw Funds Screen:

 If the user wants to withdraw funds, they should be able to select the "Withdraw
Funds" option from the navigation menu.
 They will be asked to enter their bank account details, including the account
number, routing number, and the amount of money they want to withdraw.

5. Add Funds Screen:

 The "Add Funds" option in the navigation menu will take the user to a screen
where they can select their preferred payment method, such as a credit card,
PayPal, or bank transfer.
 They will be asked to enter their payment details and the amount of money they
want to add to their account.

6. Profile/Settings Screen:
Software Requirements Specification for QuickPay Page 6

 Users can access their profile and settings by selecting "Profile" or "Settings"
from the navigation menu.
 The profile screen will allow them to view and edit their personal information,
including their name, address, and contact details.

3.2 Hardware Interfaces

1. Mobile devices: The app must be compatible with various mobile devices,
including smartphones and tablets, running different operating systems such as
Android, iOS, or Windows.
2. Biometric Sensors: The app may require integration with biometric sensors such
as fingerprint readers or facial recognition sensors for secure user
authentication and verification.
3. Barcode Scanners: The app may require integration with barcode scanners for
scanning product barcodes or for generating barcodes for transactions.
4. Point-of-Sale (POS) Terminals: The app may require integration with POS
terminals for processing transactions in physical retail locations.

3.3 Software Interfaces

 Payment Gateway APIs: The app must integrate with payment gateway APIs to
enable users to make secure payments through credit/debit cards, net banking,
e-wallets, or other payment methods.

 SMS Gateways: The app may integrate with SMS gateways to send transaction-
related notifications and alerts to users.

 Email Gateways: The app may integrate with email gateways to send
transaction-related emails such as payment receipts, order confirmations, or
shipment details.
 Database Management Systems: The app must integrate with a database
management system to manage user accounts, transaction records, and other
data.
Software Requirements Specification for QuickPay Page 7

4. System Features

4.1 System Feature (Functional Requirements)

Functional Requirement 1 : Login in QuickPay( Check account exist or not)

● Input:

Entered the details like, mobile number and password

● Output:

Account doesn't exist. You have to sign in to create a QuickPay account.

Functional Requirement 2 : Add money in QuickPay Wallet

Software Requirements Specification for QuickPay Page 8

● Input:

Enter the amount and choose the method via which you want to add money
(like debit card, credit card.net banking)

● Output:
Display error message that the card number/Net banking id is invalid

Functional Requirement 3 : Error occur during the payment

● Input:
Software Requirements Specification for QuickPay Page 9

Enter the amount (n) you want to pay.

● Output:

If the wallet contains valid money then payment is successful, otherwise

payment unsuccessful.

Functional requirement 4 : Problems or errors come during transferring

money from wallet to bank.

● Input:
Software Requirements Specification for QuickPay Page 10

Enter amount, account holder's name, account number,,IFSC code

● Output:

Transferring is canceled, display account details is wrong

Functional requirement 5 : To pay money to shopkeeper

● Input:
Software Requirements Specification for QuickPay Page 11

Phone number/QR code of shopkeeper and the amount

● Output:

Payment Successful

Functional Requirement 6 : Create a link to accept QuickPay money from others

● Input:

Sender's phone number and amount

Software Requirements Specification for QuickPay Page 12

● Output:

Payment received

Functional requirement 7 : Mobile recharge/dish recharge

● Input:

Phone number and amount to recharge

Software Requirements Specification for QuickPay Page 13

● Output:

Recharge successful

Functional requirement 8 : Bill payment of electricity/gas/water bill

● Input:

Select type of bill, bill number and customer number

● Output:
Software Requirements Specification for QuickPay Page 14

Payment successful

Functional requirement 9 : Opens the portal of online shopping

● Input:

Select the item to be bought

● Output:

Transaction done and item will be delivered by estimated date

Software Requirements Specification for QuickPay Page 15

Functional requirement 10 : Online booking of movies/bus/trains/flights tickets

● Input:

Enter your date and place and then select your seat

● Output:

Ticket has been generated.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.1.1 Performance Requirement
Discription : Error message should be displayed at least 30 sec
Software Requirements Specification for QuickPay Page 16

5.1.2 Performance Requirement

Description : If there is no response from the QuickPay database after a
request within 2 minutes the payment is canceled with an error
message

5.2 Safety Requirements

 Authentication and Authorization: The app must have a robust authentication
and authorization mechanism to ensure that only authorized users can access
the app's features and perform transactions.

 Encryption: The app must use encryption techniques such as SSL/TLS to

secure the communication between the app and servers and to ensure that
sensitive user data such as passwords and payment information is protected.

 Fraud Detection and Prevention: The app must implement fraud detection and
prevention mechanisms to detect and prevent fraudulent activities such as
unauthorized access to user accounts or stolen credit card details.

5.3 Software Quality Attributes

5.4.1 Availability
Software Requirements Specification for QuickPay Page 17

The QuickPay servers should be in working condition 24*7 without any server
problems.

5.4.2 Security

QuickPay wallet should provide maximal security. User data like username, password,
account balance should be transferred over safely using high level encryption.
Software Requirements Specification for QuickPay Page 18

5.4.3 Maintainability

Only maintainers are allowed to check our QuickPay details. Maintainers are
basically the system administrators, so, no other user should be allowed to do so.

Analysis Models
The waterfall model which perfectly fit for our software will be Spiral Model.

Why is Spiral Model ?

The spiral model is a Risk-driven process model for software projects.

Four main Phase of Spiral model are:
 Planning Phase
Software Requirements Specification for QuickPay Page 19

Requirement Gathering
 Risk Analysis
Prototyping ( Incomplete versions of the software program
being developed)
 Engineering Phase
Coding And Testing
 Evaluation phase

When to use Spiral Model ?

 When costs and risk evaluation is important

 For medium to high-risk projects
 Users are unsure of their needs
 Requirements are complex
 New product line
 Significant changes are expected
(research and exploration)