You are on page 1of 9

FUNCTIONAL REQUIREMENTS

FOR OFERS
Fertilizer Solution Optimizer
Version Description of Change Anuthor Date

1.0 Initial Draft Nikhil Nehete 11/27/2017


1.1 Edits in the initial draft Nikhil Nehete 11/28/2017

1
CONTENTS

1 INTRODUCTION ...................................................................................................... 3
1.1 Purpose.................................................................................................................... 3
1.2 Scope ....................................................................................................................... 3
1.3 Background ............................................................Error! Bookmark not defined.
1.4 References ............................................................................................................... 3
1.5 Assumptions and Constraints .................................................................................. 4
1.6 Document Overview ............................................................................................... 4
2 FUNCTIONAL REQUIREMENTS ........................................................................... 4
2.1 Context .................................................................................................................... 4
2.2 User Requirements .................................................................................................. 4
2.3 Data Flow Diagrams ............................................................................................... 5
2.4 Functional Requirements .......................................Error! Bookmark not defined.
3 OTHER REQUIREMENTS ....................................................................................... 6
3.1 Interface Requirements ........................................................................................... 6
3.2 Data Conversion Requirements .............................................................................. 6
3.3 Hardware/Software Requirements .......................................................................... 6
3.4 Operational Requirements ...................................................................................... 7
APPENDIX A - GLOSSARY ............................................................................................ 8

2
1 INTRODUCTION
OFERS is an application which calculates an optimal mixture of fertilizer needed for a
crop. The application is focused towards Lab Technicians or reasearchers and farmers to
come up with a fertilizer solution specific to their needs. Ideally the farmer nned a fertilizer
solution specific to variety of crop and also taking consideration of existing soild condition.
For example if the soil contains nitrogen, the application shall provide the percentage of
nitrogen required to fulfill left over nitrogen. This can be achived by providing existing
soil condition parameters generated by third party experts after the farmer submits a
sample. Furthermore 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. This report generated consists of ideal and optimum ferilizer mix solution
required for the soil condition provided by the soil report. Suppose a Lab researcher
experiments and comes up with a new formulation which is proven in lab, he/she has the
provision to add this new solution through the application for future use. The application
also has a feature to save a new solution that a Lab Technician formulates.

1.1 Purpose
The purpose of this document/artifact is to document Functional requirements for OFERS
the system in proposal.

1.2 Scope

After discussion with Famers and Lab researchers/technician the need to develop an
application which would overcome the shortcomings of the legacy system was proposed.
The project team evaluated the requirements and the legacy system to come up with
functional requirements documented in this artifact.
The end users need features and enhancements which are not present in the legacy system.
The scope of the application is limited to providing administrator rights, an intuitive user
interface, ability to add a new solution and the ability to add soil condition.

1.3 References

 Business Requirement Document Version 2.0


 FerData data document.
 Formula Sheets for calculating solutions
 Agricultural Data
o Nutrient Management 2016
o Optimal Fertilizer Formulations for Improved Grain Yields
o Nutrient Uptake in plants
o Interpreting soil test results-The Extraction Method
o Guide to How To Choose a Limiting Material
o Complete guide to Pre-Plant Fertilizer Application
o Hydroponics Nutrient Solutions
o How to Successfully choose Growing Media

3
1.5 Assumptions and Constraints

1.5.1 Assumptions
It is assumed that the system will be only used on Windows OS. The UI will be intuitive
with images and follow select-enter-click operation.

1.5.2 Constraints
There are no legal constraints except for Data privacy, the data and the business logic is
very critical to the client’s business and shall not be shared with unauthorized personnel
without permissions from the client.
The end user must follow state regulations regarding use and application of fertilizer. The
application does not provide this, and user should check with respective governing body.
The application is meant to run for Windows 8 and above. Management at OFERS does
not promise support for lower versions of windows operating system. However, the
management will provide a 7-day induction/training program.

1.6 Document Overview


The document will go through versioning when there any changes or additions are made
to it.

2 FUNCTIONAL REQUIREMENTS

2.1 Context
The users of OFERS shall input crop details and soil conditions in the application. The
application will generate a report of optimal fertilizer solution respectively in the form of
a detailed report suggesting percentage required for each constituent.

2.2 User Requirements

Types of Users:

There are 5 types of users who shall interact with the system.
 Admin
 Lab technician
 Lab researcher
 Farmer with admin rights
 Farmer without admin rights

4
High level Functionality:

The Admin module shall have CRUD (Create Read Update Delete) Functionality:
1. Ability to create a new record.
2. Ability to read existing fertilizer records.
3. Ability to update existing fertilizer records.
4. Ability to delete Fertilizer solution.
5. Ability to save a new solution.

The regular User module will have only Read functionality:


1. Ability to read existing fertilizer records.

2.3 Data Flow Diagrams:

The data flows from User to to OFERS, OFERS uses business logic to calculate the
fertilizer solution. Also, in another scenario User creates a new solution by entering the
formulation details and saves in the application. This new record is updated in FerData
database.

2.3.1 Functional Requirements Admin Module

Section/
Requirement ID Requirement Definition
FR_1.0 The system shall let user login as an Admin
FR_2.0 The system shall let user create new fertilizer solution.
FR_2.1 The system shall let user read existing fertilizer solution.
FR_2.2 The system shall let user create a new crop.
FR_2.3 The system shall let user save a new crop.
FR_2.4 The system will let user enter fertilizer application method.
FR_2.5 The application will let user select growth stage
FR_3.0 The system shall let user enter a crop type for the new crop.
FR_3.1 The system shall let user enter a fertilizer solution for new crop+crop type
FR_3.2 The system shall let user save a fertilizer solution for new crop+crop type
FR_4.0 The system shall let user select crop.
FR_4.1 The system shall let user select crop type.
FR_5.0 The system shall let user enter soil report.
FR_6.0 The system shall let user generate report.

5
2.3.2 Functional Requirements User Module with no admin rights

Section/
Requirement ID Requirement Definition
FR_1.0 The system shall let user enter as a regular user.
FR_1.1 The system shall let user enter crop.
FR_1.2 The system shall let user enter crop type.
FR_1.3 The system shall let user enter application method.
FR_1.4 The system shall let user enter growth stage.
FR_4.1 The system shall let user enter soil details.
FR_4.2 The system shall let user read generated fertilizer solution.

3 OTHER REQUIREMENTS
Section/
Requirement ID Requirement Definition
FR_7 The system shall be available whenever user opens it.
FR_8 The system shall take backups of the data.
FR_9 The system shall function on all Windows computers with OS Win 8 or above.
FR_10 The system shall not take more than 10 minutes to install.
FR_111 The system shall not loose critical data.

3.1 Interface Requirements


The user interface will be designed using Axure.
The database FerData will be converted to (CSV) format.

3.1.1 Hardware Interfaces


The system shall work on Computers with at least Win 8.

3.1.2 Software Interfaces


OFERS built in axure will be interfaced with FerData.

3.2 Data Conversion Requirements


The organization which controls FerData will provide with data in excel sheets or CSV
format.
The organization will also provide calculations for fertilizer solutions.

3.3 Hardware/Software Requirements

6
Hardware Software
OS Windows 8 MS Excel
RAM 4GB, Processor i3 and up Axure

3.4 Operational Requirements


The system shall be:
 Executable by .exe application.
 Downloadable from OFERS website.
 Able to save new solution and update in database.

3.4.1 Security and Privacy


A. State the consequences of the following breaches of security in the subject application:
1. Loss or corruption of data:
OFERS relies on FerData, there is no system without data. Hence FerData
corruption is not acceptable.
2. Disclosure of new fertilizer solutions:
System shall abide by data sharing laws. New solutions can be revolutionary and
OFERS will not publish findings by researchers to any third party.
3. Software malfunction or corruption:
Software not functioning according to proposed flow will have provisions to secure
data.
B. State the type(s) of security required. Include the need for the following as appropriate:
1. Physical security: shall be shared with users with admin rights.
2. Access by user role or types: Users with no admin rights will be able to use the
system at the same level.
3. The client shall provide user log in provision for Admin login.
4. The admin login enables user to alter data.

3.4.2 Audit Trail


When Admin alters the record, or add new records it will create a metadata which will
capture the user and timestamp. This will help create a trail and the user making changes
can be traced back.

7
3.4.3 Recoverability
The DB shall be restored and backed-up manually in excel sheets as per the User suggests.
OFERS will create backup every week.

3.4.4 General Performance


The fertilizer mix is critical information. Therefore, the calculations should be precise.
OFERS will calculate solutions efficiently based on formulations provided.

3.4.5 Capacity
OFERS does not limit number of users. However, it limits the number of Admin login
authentication to three users.

3.4.6 Validation Rules


 New user registering will follow the following format: Initial of first name, Initial
of last name, Lab assigned employee ID.
o Ex: NN1005
 Incase of farmer as the user: Initial of First name, Initial of last name and a four-
digit number.
o Ex: GK2013
 While creating a new record for fertilizer solution: The name of the solution will
have first three letters of crop name, three letters of crop type.
o Ex: COFC
For Corn, flint corn.
 Decimals wherever applicable in the calculations or in the display shall be rounded
to 3 digits.

APPENDIX A – GLOSSARY
1. Link to Nutrient Management 2016
2. Link to Optimal Fertilizer Formulations for Improved Grain Yields
3. Link to Nutrient Uptake in plants
4. Link to Interpreting soil test results-The Extraction Method
5. Link to Guide to How To Choose a Limiting Material
6. Link to Complete guide to Pre-Plant Fertilizer Application
7. Link to Hydroponics Nutrient Solutions
8. Link to How to Successfully choose Growing Media

You might also like