NAME OF COMPANY

Business Requirements Document (BRD)

Template
Project/Initiative
Month 20YY
Version X.XX

Company Information
 BRD
1 Document Revisions

Date Version Number Document Changes

26/11/17 1.0 Initial Draft

27/11/17 1.1 Reviewed initial draft and added missing information and requirements.
28/11/17 1.2 Reviewed and diagrams, appendix updated.
29/11/17 2.0 Baselined

2 Approvals
Role Name Title Signature Date
Project Sponsor Gaurav Kulkarni

Business Owner Shrey Khosla

Project Manager Vijay S.

System Architect Ramkrishna A

Development Lead Nikhil Nehete

User Experience Lead Ritu S

Quality Lead M. Sinha

Content Lead Bharadwaj C.

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 1
copyright INKtopia Limited | All Rights Reserved
 BRD
3 Introduction
3.1 Project Summary
Optimal Fertilizer Solution is an application which calculates an optimal mixture of fertilizer needed for
a crop. The solution is calculated on predefined and documented agricultural data available. The
application takes input from user/ lab technician/farmer and returns a calculated report. The
application also has a feature to save a new solution that a Lab Technician formulates.

3.1.1 Objectives
 Deliver an application which calculates a fertilizer solution based on fix rules.
 User should be able to login as an existing user or as an admin.
 Allow user to select crop and its variety.
 User should be able to enter the soil condition report result.
 User should be able to enter other decision variables.
 User should be able to generate usable reports consisting of Fertilizer solution.
 User should be able to enter his own customized solution.
 User should be able to apply his customized solution to crops.

3.1.2 Dependencies
Proposed application will be based on data which is already documented by labs and knowledge from
farmers over 25 years. Access to database FerData is provided. The data contains crop,variety and
conditions required for the crop. Depending on these conditions formulas exist to create a fertilizer
solution.

3.1.3 Current System

The current system is hard coded for fertilizer solutions. If you click on a crop it will generate a report
which contains a solution which works generally. This always is not what the user is looking for.
Considering various parameters, the requirement for the same crop may vary depending on growth stage,
soil conditions and fertilizer application method.

3.1.4 Proposed System

The proposed system overcomes the above limitations and truly gives an appropriate solution based on
current conditions. This solution is more appealing to the end user since if reflects directly on the
produce, quality and eventually profits. The application will incorporate calculations provided by
agricultural proven and tested methods tested and implemented in research labs. The user needs to
enter values of variables, soil conditions and the system will generate a report containing a solution. The
application will be user friendly and overcome users limitation to use a software by having images and
intuitive interface.

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed
 BRD
3.2 Project Scope
The project should limit its boundary to developing an application and connecting to existing
database FerData.

3.2.1 In Scope Functionality

 Login as a User or Admin
 Develop an interface.
 The first page should accept details about crop.
o Select crop.
o Select crop variety.
o Select Application Method
o Select growing method
o Set yield goal.
o Select growth stage.
o Choose list of fertilizers.

 The first page should redirect to another page.

 The second page contains soil conditions
o Enter soil conditions values.
o Generate fertilizer solution functionality.

 If the user logins as an administrator, he has the authority to enter new fertilizer solution in
the first page by selecting ‘choose list of fertilizers’
 The admin can save the new customized solution n FerData for future use.

3.2.2 Out of Scope Functionality

 Email reports from the application.
 Change existing fertilizer solution formulations.

3.3 System Perspective

[Provide a complete description of the factors that could prevent successful implementation or
accelerate the projects, particularly factors related to legal and regulatory compliance, existing
technical or operational limitations in the environment, and budget/resource constraints.]

3.3.1 Assumptions
 The existing data in FerData is correct.
 The end user has some knowledge of handling a software application.
 The end user has the capacity to use basic CRUD functions.

3.3.2 Constraints
 Impending changes to privacy regulations may impact data dictionary design.
 Timeline for enterprise platform updates will impact execution of testing plan.

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 1
copyright INKtopia Limited | All Rights Reserved
 BRD
3.3.3 Risks
 Not developing the software before 31st March will set back the farmer by one year since the sowing
season starts by mid-March.
 If the software is used without prior knowledge of fertilizers, the solution may prove harmful to
crops and life.

3.3.4 Issues
 If the software fails to save the fertilizer solution after clicking save, valuable research of the new
solution will be lost.
 If the user manual and or training is not detailed enough the adaptability towards the application
will be low.

4 Business Process Overview

4.1 Current Business Process (As-Is)

4.2 Proposed Business Process (To-Be)

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 2
copyright INKtopia Limited | All Rights Reserved
 BRD
5 Business Requirements
The business requirements describe the needs of the business. The following types of requirements must be defined fully here:
 Security Requirements — The application will adhere to IT Security and Quality guidelines based on ISO 27001 and ISO 9001: 2013. The system will
comply to the privacy of all the complex calculations and the flow/chain that connects them. Documents related to the system will be stored on a
secured shared location provided by client and accessible only by authorized personnel’s.
 Performance Requirements — The system will be error free in providing the end results and should combine the data in Master Database
efficiently,also it should be readily available on technician/farmers machines as and when required.
 Availability Requirements — The first module of the product after requirements gathering must be available for user acceptance test in 1 month.
 User Requirements – The finished product will have a UI which will let the users access different modules
 Forms should be available in different modules to
 Enter crop data
 Add a new fertilizer solution
 Generate customized reports

The requirements in this document are prioritized as follows:

Value Rating Description

1 Critical
2 High
3 Medium
4 Low
5 Future
This requirement is critical to the success of the project. The project will not be possible without this requirement.
This requirement is high priority, but the project can be implemented at a bare minimum without this requirement.
This requirement is somewhat important, as it provides some value but the project can proceed without it.
This is a low priority requirement, or a “nice to have” feature, if time and cost allow it.
This requirement is out of scope for this project, and has been included here for a possible future release.

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 0
 BRD
6 Budget and Resource Estimates
Projected estimates:

OFERS-I.T Solution for Fertilizer

Expenditure $ Capital $

Software and Hardware 5000.00 20000.00

Personnel Resources 20000.00 15000.00

Maintenance 5000.00 10000.00
Miscellaneous 10000.00 —
Total $40000.00 $45000.00

Template provided at no charge by TechWhirl.com

You are free to use and customize as needed 1