DAV Institute of Engineering and Technology

Jalandhar, Punjab– 144008

Software Requirements Specification

For Blockchain Management

Submitted by:
Kunal Thakur (126/20)
University Roll No: 2003656

Blockchain Management (SRS)

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

Blockchain Management (SRS)

 1

1. Introduction

1.1 Purpose
The main objective of this project is build a website which help farmers from Indian villages
too sell their product to different cities. Here if suppose some village farmers want to use this
facility and want to learn how is it possible and how they can use block chain farm data
management system to sell and buy the products,

E-farming system will help the farmers to builds a platform for farmers ,seller and buyer to
ensure greater profitability through direct farmer to buyer and seller to farmer
communication and vice-versa.
Ecommerce website development is a best and popular option for business, as they give them
massive scope in facilitating sells and online transaction secure and conveniently.
Ecommerce website enable customer to purchase or buy the goods.
⦿ Most prominent problem which the farmer face today is the interference of the
intermediaries .
⦿ The farmers cannot directly deal with the customers or the government for selling
their products. They don’t know what the real price in the market is. This lack of
transparency in the system is the cause of all the problems.
⦿ E-FARMING SYSTEM solves this problem using Block chain Technology.

1.2 Document Conventions

Heading: Font Size: 18
Font Style: Bold
Font : Cambria
Sub Heading: Cambria: 14
Font Style: Bold

1.3 Intended Audience and Reading Suggestions

This document is intended for any individual user, developer, tester, project supervisor that
needs to understand the basic system architecture and its specification. Here are the potential
users for each one of the reader types:

Developer: The developer who wants to read, change, modify or add new requirements into
the existing program, must firstly consult this document and update the requirements with
appropriate manner so as to not destroy the actual meaning of them and pass the information
correctly to the next phases of the development process.

Blockchain Management (SRS)

 2

User: The user of this program reviews the diagrams and specification presented in this
document and determines if the software has all the suitable requirements and if the software
developer has implemented all of them.

Tester: The tester needs this document to validate that the initial requirements of this
program actually corresponds to the executable program correctly

1.4 Product Scope

 There are three basic users as

a. Director(admin)
b. Users-farmers , buyers , seller
c. Computer professionals

 All users have their own profiles in e farming system.

 Farmers can create new account, log-in to their existing accounts which will give them the
authority to use the services provided by the system.
 If user select as farmer then there is option to select whether he wants to buy or sell then
he can directly go to that page.
 Buyer can search for all products which are currently available for sell. he can buy also as
per his requirements.
 Seller can also place their product for sell with all required information like product,
price, quantity

 Authenticated farmers can sell their product, claim the compensation from government
and can view his fund.
 The Farmer can check their account on fund transfer history.
 The data of all transaction is stored in the format of block chain that is immutable due to
which no one can make fraud with government regarding there the fund.
 If data is lost by farmer or seller the copy of data is stored to other person while
transaction by which he can retrieve back the transaction information.
 Admin has authority to add/delete users, he arranges overall management of website .but
he has no authority to change the transaction happens during purchasing or selling
because the data is form of hash code which is immutable and the transaction details
store in block chain.

1.5 References

 IBM RED BOOKS

 IBM TGMC sample synopsis

Blockchain Management (SRS)

 3

 Wikipedia: www.wikipedia.com
 www.efarmingdia.com
 Agricultural Marketing S.S. Acharya ISBN - 81-7188-387-7 Pages-259
 Agricultural marketing information and research network. (agmarket.nic.in)

1.6 Product Perspective

Block Chain Based Farm Data Management System has been developed on Java, Angular,
MySQL. The main purpose of the project Block Chain Based Farm Data Management System is
to provide the details of product based on which a user can sell or purchase a product on their
requirement. It will provide all the information about product and transaction details. The
purpose of the project is to build a web application which to reduce the manual work for
finding product and finding a cheap tenant of better product.
Block Chain Based Farm Data Management System will overcome the following drawbacks of
the existing system.
• Manual search for product.
• Manual search for tenant product.
• Need for middlemen or brokers.
• Less choices.
• Time wastage.
• Difficulty in payment.

1.7 Product Functions

This web application will allow the user to do various things such as

• Users can search product online and buy it according to his choice.
• Users can also see the reviews of product which he intends to buy on this web
application by seeing the he will go for right product choice.
• This web application will ease the process of payment through online payment.
• All the transaction details should be store in block chain in such a manner in future
if user want to see all the transaction he will see it.

1.8 User Classes and Characteristics

1.8.1 User-

Blockchain Management (SRS)

 4

The user of the system can be anyone. He can use the system as for selling or buying a product
to on there requirement.

1.8.2 Owner-

This user is the one who registers as a owner in the application. He can post his requirement
for product which he wishes to sell or buy. He may ask for a certain amount for the product
which he is providing or purchasing and a small amount of security deposit by he is ensure
the user will purchase the that product.

1.8.2 Admin-

Admin is a user which will have a specific controls to the application which will allow them to
control certain modules in the application. The admin can change the forum settings to make
the users happy. Admin will administer the overall control of the website and can override
any setting, constraints in any module as he/she wants but he is not able to change the
transaction details which is stored in block chain.

1.8.3 Computer professionals-

The computer professionals provides a guidance to user who may be farmer, seller or buyer to
give them a knowledge about how to use the website and solving the issues generated while
login or signup or purchasing of product.

1.9 Operating Environment

This web application can be deployed on Linux or Window machine with Apache Server and
MySQL server
• Minimum RAM 2 GB
• 320 GB Storage Space.
• Intel i3 Processor.
• Internet Connectivity with Ports configured.

• This application can be accessed by user through a machine having any web browser
with bootstrap. Angular support and flash to get video content. The client devices must
preferably have browsers like IE9 or above, Mozilla Firefox (version 60.02 quantum) or Opera
54.0 or chrome (version 68.0.3) or safari installed in their OS and must have enabled flash
content to get videos output. Specified versions are preferred to get Bootstrap 3.0 output.

Blockchain Management (SRS)

 5

Structure Chart:

Blockchain Management (SRS)

 6

Use Case diagram:

Blockchain Management (SRS)

 7

Sate diagram:

State diagram

Blockchain Management (SRS)

 8

Sequence Diagram:

Sequence Diagram:

Blockchain Management (SRS)

 9

Object diagram:

Blockchain Management (SRS)

 10

Component diagram:

Component diagram:

Blockchain Management (SRS)

 11

Deployment diagram:

Blockchain Management (SRS)

 12

Class diagram:

Class Diagram:

Blockchain Management (SRS)