Software Requirements

Specification
For

INCOME PREDICTOR

Version 1.0

Prepared by:

M.Dhiliprajan

N.J.Anishkumar

S.Arun

B.Ajay Sharithra

1
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................3
1.1 Purpose.................................................................................................................................3
1.2 Document Conventions........................................................................................................3
1.3 Intended Audience and Reading Suggestions......................................................................3
1.4 Product Scope......................................................................................................................3
1.5 References............................................................................................................................3
2. Overall Description..................................................................................................................4
2.1 Product Perspective.........................................................................................................................4
2.2 Product Functions................................................................................................................4
2.3 User Classes and Characteristics.........................................................................................4
2.4 Operating Environment........................................................................................................4
2.5 Design and Implementation Constraints..............................................................................4
2.6 User Documentation............................................................................................................4
2.7 Assumptions and Dependencies..........................................................................................4
3. External Interface Requirements...........................................................................................5
3.1 User Interfaces.....................................................................................................................5
3.2 Hardware Interfaces.............................................................................................................5
3.3 Software Interfaces..............................................................................................................5
3.4 Communications Interfaces.................................................................................................5
4. System Features.......................................................................................................................5
4.1 System Feature 1..................................................................................................................5
5. Nonfunctional Requirements..................................................................................................6
5.1 Performance Requirements..................................................................................................6
5.2 Safety Requirements............................................................................................................6
5.3 Security Requirements.........................................................................................................6
5.4 Software Quality Attributes.................................................................................................6
6. Other Requirements................................................................................................................6
Appendix A: Glossary....................................................................................................................6
Appendix B: Analysis Models.......................................................................................................7
Appendix C: To Be Determined List............................................................................................7

Revision History

Name Date Reason for Changes Version

2
1.Introduction
1.1 Purpose 

The purpose of software requirement specification(SRS) document in Business Predictor

application is to provide a detailed description of how to develop a application which is used
to provide the future income of a company. The user can analyze previous month sale and
can predict next month sale.

1.2 Document Conventions

The document conventions include:

Font TimesNew Roman

Heading size 18
Sub-heading 14
size
Content size 12

1.3 Intended Audience and Reading Suggestions

This document is intended for small scale business holders and medium scale business
holders. This project is an income predicting prototype and is intended to be used by business
holders.

1.4 Product Scope

The purpose of the Business Predictor application is used to predict the future income by
analyzing the old data. By storing the analyzed data in a remote database. Its an online web
application. 

1.5 References

IEEE Software Requirement Specifications.

Wikipedia and quora.
https://en.wikipedia.org/wiki/Income_Pretictor
2.Overall Description

3
2.Overall Description
2.1 Product Perspective

The origin of the product being specified in the SRS is a new product. The product is not a
component of any system. The system is open source and web based and it provides an
interface between a business holder and database.

2.2 Product Functions

The business holder gives the sales data of the previous month and by using regression
function and also suggest how to increase the sales for next month and it also provides how
much profit the business holder has earned this month rather than the last month

2.3 User Classes and Characteristics

Login and register:Business holder registers or logs in the application.

Invoice :The business holder can enter the data that he/she has obtained last month.

Purchase :He/She enter the amount of raw material they have purchased last month.

Analysis :By using the predictive function he/she can predict the next month income.

2.4 Operating Environment.

Internet explorer 11, Chrome 79, Firebox 72.

Tensorflow is used as developing environment.
React JS is used for front end.
Django is used for back end.

2.5 Design and Implementation Constraints

Security features and login fail shall be of the highest concern when developing this
project.The Business holder must have prior knowledge about the application.The application
can only operated only if the data connection is switched on.

2.6 User Documentation

The web application will come with an “About” tab, which will allow business holder to
access the help manual. This manual will be updated with each new versions.

2.7 Assumptions and Dependencies 

Let us assume that this is a government authorized for small and medium scale business
growth .The system needs user to have some knowledge of Income predicting web
application.The software is dependent on internet access as it is a remote web application. It
is assumed that the business holder is familiar in handling the software. 

4
3.External Interface Requirements
3.1 User Interfaces

 The user interface of the software will use standard web API and GUIs using React
js.The user interfaces include any kind of operating system platform
 The application contains single user interface for all the business holders which
enables you to Register/login. and use this application.

3.2 Hardware Interfaces

The hardware interface comprises of personal computer and a remote server.

3.3 Software Interfaces

 Front End - React JS

 Back End - Django
 Developing Environment - Tensorflow.

3.4 Communications interfaces

Communication interfaces will use TCP/IP for data transmission. All online access will be
monitored, for transparency purposes, and in order to reduce time for data updating and
reduce data error.

4.System Features
4.1System Features 1
       Description and priority:
 Accept the sales and purchase bill of the user in a company with valid authentication
 Data are highly secured so it is not easy to stole data by any anonymous user
 The application runs on online in which it uses a cloud based database
 The accounting app is included with tax calculation
 From the security point of view, authentication is done by password checking and if
the password is correct, the user will get further access to the system otherwise the
user will have to re-enter the password.
 The software is able to provide service for at most3 people per minute.
 The software is made with user limit and if it exceeds an warning message is sent to
the user.
      Functional requirements:
 User may view about the transactions and expenditure.
 After checking the products stats we can analyze the product on individual.
 If the user enters a wrong data he is able to cancel the item.
 The system is in such a way that it stands up to user expectations.
 The system is able to avoid disastrous actions. The system safeguards against
undesired events without human intervention.
 The response of all the operations are good.

5
5.Other Nonfunctional Requirements
5.1 Performance Requirements

The software should have high performance and low failure rates. Machines must have
firewalls installed and active virus scanning software in usage. Machines should solely be
used for operation of the software, in order to maximize performance and security. 

5.2 Safety Requirements

The user should feel secured because he/she is giving his/her business data for income
prediction. All online operations should be monitored and stored.

5.3 Security Requirements 

 The security should be tight so that it makes it difficult for the hackers to hack the database.
All the operations should be one to one encrypted and security should be ensured. 

5.4Software Quality Attributes

Flexibility, availability, correctness, reusability, robustness, and maintainability of the system

should be maximized for the business holders and it should be secure and updatable when
new updates are made.  

6.Other Requirements
Name of the user who enters the data in the application. SQL database is required to keep the
details about the user, product and other details. The product should be with unique product
id and should be able to analyze the product with the help of id. The report should contain
only valid details of the product which reached lot in the month end . The project should be
able to be reused with the inclusion of further updates.

Appendix A: Glossary
1.Baud rate: Rate of transfer of data over the internet/network.

2. Bit: Binary Digit, zero(0) or one (1).

3. TLS: Transport Layer Security, A high-encryption security protocol for internet

connection.

4. Tx/Rx: Transfer/Receive

5. Windows API: Windows Application Programming Interface,The API used to program

Windows applications and elemen

6. SQL: Structured Query Language.

6
7. SRS: Software Requirements Statement.

8. GUI: Graphical User Interface.

Appendix B: Analysis Models

Use case model, Object model, Functional model- Dataflow model and SADT model,
Dynamic model.

Appendix C: To Be Determined List