You are on page 1of 4

Software Requirement Specification(SRS)

2.1) Introduction:
Software requirement specification is a starting point of the software development activity.
Software requirement specification is focused specifically on functioning of the system. the basic
purpose of SRS is to build the communication between parties involved in the development of
the project.It allows developer to understand the system, functions to be carried out .

2.2) Purpose:
The purpose of this document is to specify the requirement and give guidelines for the
development of the application online GSM. it will explain the purpose and features of the
system, the interfaces and what the system will do and the constraints under which must operate
and how the system will react to external stimuli. it provides the visibility in design and provides
information needed for the software support.

2.3)Scope
The scope of this document is to provide sufficient detailed functional and non-functional
requirements of a project to see all the functionalities are properly implemented. Any changes
made to the requirement in the future will have to go through a formal approval process.

2.4)Definition, acronyms, abbreviations:

Acronyms Definitions
DFD Data Flow Diagram
GUI Graphical User Interface
FIREBASE Database Server
XML Extended Markup Language
GRADLE Build System for indexing source files
into APK
APK Android Package Kit

2.5)Overall description:
The overall description of our project can be treated as creating and managing the data produced
by the users and user friendly interface to manipulate their data to their benefits.
A authentication provided to accomplish safety to all task and all users.This section of SRS
describe all general factors of the product and its requirements.
2.5.1) Product perspective:
Shopkeepers need an application which would provide keep their day-to-day transaction data
and suppliers can you store information and about the product status of the items and the
proposal can be made to supplier about product supply.Local customers can view the store
information and they can pre-oder the product.It is way to maintain all information online and
make paperless and quick transaction.The main perspective of product is to keep and process
the data of many shop owners to keep their accounts and to manage it easily.The supplier
and customer are the addd-ons to improve the buisness of shopkeeper

2.5.2) Product functions:


This application runs on Android platform and can remotely control. This application
1) Maintain shopkeepers data and give reports notification of low stock.
2) Shopkeepers can generate bill.
3) Notification of the product buying proposal from the suppliers.
4) Notification from the customers.
This application stores the data on the server side. So that data should be able to access
anywhere as per users need securly.

2.5.3)User classes and characteristics interface:

Shopkeepers or store owners: Shopkeeper is a user he can create his account and update his
daily transaction to maintain transaction data properly.

Supplier
He can login and view the stock information of various stores stocks.And he can make a
request-notification to shopkeeper about sale his product.
Customer
customers can view the products available in the store at any time and they can check the
product status before going to the store.

2.5.4)General constraints:
 Application is based on Android platform environment.
 All the values should be defined by default values supplied by the application.
 System should detect errors If in case any errors occurs.
 The application should support almost all Android devices above 5.0.
 No error condition shall cause the application to exit prematurely.

2.5.5) Assumptions and dependencies:


 Internet connection required.
 The user should know the basic functioning of Android application.
 One assumption about the product is that it will always be used on mobile phones that
have enough performance
.
2.6) External interface requirements:
This section provides a detailed description of all inputs into to and output from the system. It
also gives a description of the hardware software and communication interfaces and provides a
basic prototypes of the user interface.

2.6.1) User Interface:


User interface is a graphical user interface consisting of Tab forms and bottom-navigation
menus. The user interface must be simple and easy to use. All interaction of the software with
the people must be easy and clearly specified.This is a software provides UI and command
buttons,text boxes, labels, and data grids are used.

2.6.2) Hardware and Software interfaces:


operating system: Android 5.0 to 8.0
RAM: At least 512 MB of RAM
Memory: At least 300 MB of internal storage

2.7) Functional requirements:

The functions of the form used in the application are as follows it specifies which output should
be produced from the given input and they describe the relation between inputs and outputs of
the system. All the operation performed on the input data to obtain the specified output should
be specified. The application has three characteristics supplier, shopkeeper and customer.

shop owner has following privileges


 Create or Delete his account.
 Edit his profile.
 Add or remove the product.
 Search and view the product information.
 Generating bill and Full control over the product details.

Supplier has following privileges


 Create or delete account.
 edit profile.
 only view of stock info.
 privilege to make a product buying proposal to the shop owners about their supply.

Customer has following privileges

 View product information.


 Edit or create or delete their account information.
 Order the product.
2.8)Non functional requirements:

 Performance requirements

This section describes the performance requirements expected from this project:
 Add any records within the fraction of seconds.
 Users can be there any records within 5 seconds.
 Quick navigation between pages.
 Various validations of a user inputs.
 For every user password and email authenticity.

 Security requirements
 The every user should login to the system to manipulate with their data
 The system shall permit only shopkeeper who have full authorisation of product
information to edit the product details and billing and reporting.
 Email verification is given to validate every account.

You might also like