Professional Documents
Culture Documents
Software Requirements Specifications: Synopsis Report On
Software Requirements Specifications: Synopsis Report On
Synopsis Report on
‘Bankbazaar.com’
Roll: - RK17PGB38
Table of contents
1. Introduction………………………………………………………………………………………………3
2. System features………………………………………………………………………………………..5
1. Introduction
Thousands of software are manufactured on the basis of the user requirements and among
them very few are coming out to be outstanding. The quality of software depends upon various
factors; user-friendly, compact, portable, attractive and bug free. These all factors ensure the
favorable environment of software usage. For attaining this, a proper practical approach should
be followed which must include a step by step implementation of parts of a software. Thus a
documentation of all the requirements of software is called as Software Requirement
Specification, SRS. An SRS acts as a path through which a software is developed through
different phases. SRS includes the functional requirements, non-functional requirements,
external features, and proper implementation steps.
1.1 Purpose
Software requirement specifications(SRS) is the documentation of the software before the
software actually takes place its real form. This document helps to specifies the different
elements, functional and non- functional requirements of the software. This documentation
describes the SRS of how the bankbaazar.com works in the real world.
2. System Requirements :
It consists of the functional requirements of the software. The main tasks and services
which the software offers to the layman users and the admins. Functional requirements
of BankBazaar include following operations;
2.1.1 Loan
Description: Using this function we can show different types of loans provided to the user.
Output: A new window will open redirecting to the process related to the specific loans.
Input: fill up the requirements related to the loan you asking for loan and submit it
Output: A new window will appear showing the required loan types with information.
Processing: In this section, a loan will be sanctioned to a user on the basis of the user’s
requirements.
2.1.2 Card
Description: Using this function a user can be availed with different types of cards.
Processing: when user click on the card icon, he will be taken to a new card homepage. In
this homepage types of cards will be shown along with further functions related to card
issuing.
2.1.3 Insurance
Description: Using this function different types of insurances will be shown to the user.
Processing: when user click on the insurance, different types of insurance will be shown to
the users. User can choose the type of insurance using this function.
2.1.4 Investment
Description: Using this function a user can get to know about different types of investments.
Processing: when the user clicks on the investment, a new window is opened showing types
of investments for the user.
Description: using this function a user can calculate the loan EMI
Output: A new homepage of Insurance tool will display with three types of calculators;
home, car, and personal loan calculator respectively.
Processing: when the user clicks on the financial tool, he will be taken to a new window
having types of loan calculator. A user can do choose the type of loan and calculate it in one
to two steps in the same homepage.
2.1.6 Track application
Processing: when user click track application, he will be taken to a homepage of track
application asking tracking application ID or phone number. If the id matches, the progress
of user work will be showing to him.
Non-functional requirements:
Non- functional requirements of software basically include the security, responsive views, user-
friendly interfaces. BankBazaar offers the portability mode, linked interfaces and hardware
implementations, working environments.
User interface shall not take more than 2 seconds for transitions.
2.3 security
2.4 Usability
The interface should have user defined orientation, languages, and understandable. It should
contain responsive contents relevant to the topic and easiness of the end user.
2.5 Portability
The software must be accessible 24/7 and 365 days with easy transportable in different user
environment. It should be portable to adopt in different working environment.
2.6 Efficiency
The software should be efficient in connecting end user with the related departments and
services. Even, if the stops malfunction sometime, it should be able to retrieve back to normal
condition within short period of time.
2.7 Reliability
System should be reliable in providing services and information to the end user. It should be
free of malicious digital piracy, should provide all time services to the people at specific time.
3. Methodology:
The synopsis has been prepared by using different modern approaches to meet the SRS
requirements. Different methodologies that are being used are categorized into different sets
as follow;
a. Data collection and analysis: the feasibility of the software in the global market is
the utmost thing to be taken care of. In order to meet the problems of people with
quicker solutions public interactions, surveys and data mining are being carried out.
4. References:
Different resources are being used as a reference source to meet with the requirements,
including functional and non- functional parts of software. The previously built software and
their analysis has been helping to create more prolific modules.
a. www.businessindiatoday.in
b. www.slidesharer.com
c. www.google.com
d. www.wikipedia.org