1.

Introduction

The introduction of the Software Requirements Specification (SRS) provides an overview of the
entire SRS with purpose, scope, definitions, acronyms, abbreviations, references, and overview
of the SRS. The aim of this document is to gather and analyze and give an in-depth insight of the
complete Airtel App system by defining the problem statement in detail. Nevertheless, it also
concentrates on the capabilities required by stakeholders and their needs while defining high-
level product features. The detailed requirements of the Airtel App are provided in this
document.

1.1 Purpose

The purpose of the document is to collect and analyze all assorted ideas that have come up to
define the system, its requirements with respect to consumers. Also, we shall predict and sort out
how we hope this product will be used to gain a better understanding of the project, outline
concepts that may be developed later, and document ideas that are being considered, but may be
discarded as the product develops.

In short, the purpose of this SRS document is to provide a detailed overview of our software
product, its parameters, and goals. This document describes the project's target audience and its
user interface, hardware, and software requirements. It defines how our client, team and audience
see the product and its functionality. Nonetheless, it helps any designer and developer to assist in
software delivery lifecycle (SDLC) processes.

1.2 Scope

Primarily, the scope pertains to Different functions and features. It focuses on the company, the
users, and applications, which allow the users to do perform different functions to enrich the
lives of the users.

This SRS is also aimed at specifying requirements of software to be developed but it can also be
applied to assist in the selection of in-house and commercial software products. The standard can
be used to create software requirements specifications directly or can be used as a model for
defining an organization or project specific standard. It does not identify any specific method,
nomenclature, or tool for preparing an SRS.
1.3 Overview

The remaining sections of this document provide a general description, including characteristics
of the users of this project, the product's hardware, and the functional and data requirements of
the product.  General description of the project is discussed in section 2 of this document. 
Section 3 gives the functional requirements, data requirements and constraints and assumptions
made while designing the Airtel App.  It also gives the user viewpoint of product.  Section 3 also
gives the specific requirements of the product.  Section 3 also discusses the external interface
requirements and gives detailed description of functional requirements. Section 4 is for the non-
functional requirements of the software. Section 5 is for Constraints of the Software. Section 6
contains the User case diagram of the software. Section 7 contains the Test case of the software.

2. Overall Description

This document contains the problem statement that the current system is facing which is
hampering the growth opportunities of the company. It further contains a list of the stakeholders
and users of the proposed solution. It also illustrates the needs and wants of the stakeholders that
were identified in the brainstorming exercise as part of the requirements workshop. It further lists
and briefly describes the major features and a brief description of each of the proposed system.

The following SRS contains the detail product perspective from different stakeholders. It
provides the detail product functions Airtel App with user characteristics permitted constraints,
assumptions and dependencies and requirements subsets.

3. Functional Requirements
This section of the document contains the different kind of features used in making Airtel App
It includes the features like login, Pay Bills, Shop etc. These requirements are organized by the
features discussed in the vision document. Features from vision documents are then refined into
use case diagrams and to sequence diagram to best capture the functional requirements of the
system. All these functional requirements can be traced using tractability matrix.

Functional Requirement 1
Description
Ask the user to enter details to become a registered user or for login.
Input
User Must enter a valid mobile number
Processing
Storing the number entered in the database and check if a person with same mobile no available
or not. If not, then store in database and OTP as SMS.
Output
App Shall automatically detect the OTP and display “Account Created Successfully” Or account
already existed then it will login in the account

Functional requirement 2
Description: Transfer money from wallet to bank or from your account to another account.
Input: Enter amount, account holder's name, account number, IFSC code
Processing: Check if
1. Account details are right or not
2. amount of transferring money is valid or not
3. Pin is correct or not
 Output: Transferred Successfully and Bill will be generated

Functional requirement 3.
Description: Bill payment of electricity/gas/water bill
 Input: Select type of bill, bill number and customer number
 Processing: Checks the amount to be paid and transfers the money to the specified
company
 Output: Payment successful

Functional requirement 4
 Description:
Mobile recharge/dish recharge/ Fastag recharge
Input: enter the Phone number or id and amount to recharge
 Processing: Contact the service provider and recharges the device and deducts money from
your wallet.
 Output: Recharge successful and it will generate the bill for it.
Functional requirement 5
Description: Opens the portal of shop
Input: Select the item to be bought (i.e., sim card, broadband, credit card)
Processing: Generates the bill of the item and sends the prompt to the seller and ask the
customer to payment
Output: Transaction done, and item will be delivered by estimate date

Non-Functional Requirements:

Scalability:
Security:
 The system should provide a secure login to the users by using advanced secure login
algorithms and provide access only to the authorized users as security is the key
requirement of this system
 The login OTP should not be shared with anyone.

Reliability:
 The main pillar of reliability of the system is the backup of the database which is
continuously maintained and updated to reflect the most recent changes.

Robustness:
 In case user’s device crashes, or a failure is there, a backup of their payment, recharge,
profile history must be stored on remote database servers to enable recoverability.

Performance:
The application should be able to operate on all conditions. with all of its fundamental functions.
It should not slow-down the system even at peak hours without affecting the quality of service of
the system.

Portability:
The application is java, C++ and flutter language based. So, the end-user part is fully portable,
and any device should be able to use the features of the app, including any hardware platform
that is available or will be available in the future. An end-user is use this system on any OS,
either it is Windows or Linux or iOS. The system shall run on PC, Laptops, Mobile phones and
Tablets etc.
Maintainability:

Constraints

Sender's phone number

Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kM3R2ZDF1OTFycjc5LmNsb3VkZnJvbnQubm
V0L2JkZWM4NDA0MWQ1Nzk5ZjU3NWU2MGY1MTgyYWQ4ZGQ1L2h0bWwvKiIsIkNvbmRpdGlvbiI6eyJE
YXRlTGVzc1RoYW4iOnsiQVdTOkVwb2NoVGltZSI6MTY2NTMzNzczMn19fV19&Signature=GRY0~aCPJQv
Umm0xS2TIh75xDipK4l73AeZfNXqsBfzto0gbZ-
YJacoZ2k17hiW1Meu~yiJHLMxZCLvxI3Y9h3vSd7GEv5JFdVho~tAvvT8G1rDdXik9eNegp7zP92Zine9R54Zgm
TaRFDCeiSnOPA9v9SsigyqYA43W7sKXgBYaM5HquD0izhePYZ04F3842ZZU8nFG-
jkZdnA3X~FXRLxGBhdYOcvd2fQKN~etz4C3tV2TNPZtZNU6YEkNw4N9LLj6kT7k95m5tjHZROQ7AsWnAoC
mnwE0Te3GjpKcJopGAwWvDeDE92Qr2L8Xhcf8qJvbArO6ldenbjTNSzBGQA__&Key-Pair-
Id=APKAJ535ZH3ZAIIOADHQ