Assosa University

College of Computing and Informatics

Department Of Computer Science
A Project Proposal for Web Based and Mobile Based
Agricultural Input Data and Notification Management
System for Benishangul Gumuz Region
A Project SRS Submitted to The Department of Computer Science oAssosa
University Partial Fulfillment of Requirement for The Degree of Bachelor of
Science in Computer Science

Prepared By:-
Beka faisa, Birtukan getu, Juhar hussen and Woinshet shewakena Advisors’ Name:
Main Advisor Mr. Eshetu and M.r Gebregziabher

January ,17, 2017

 APPROVAL SHEET
This is certified that the project entitled on < Web Based and Mobile Based Agricultural Input
Data and Notification Management System for Benishangul Gumuz Region> developed and
submitted by
1. Beka faisa
2. Birtukan getu
3. Juhar hussen
4. Woinshet shewakena
A Project Proposal Submitted to the Department of Computer Science of Assosa University in
Partial Fulfillment of Requirements for the Degree of Bachelor of Science in Computer Science

Advisors’ Name Signature Date

1, ____________________ _______________ ____________

APPROVED BY

Examining Board Signature Date

1, ______________________ _______________ ____________

2, ______________________ _______________ ____________

3, ______________________ _______________ ____________

II | P a g e
 Acknowledgment
First of all we will thanks to GOD who gave the time to complete this SRS document. Next to
GOD we will thanks to our advisor M.r .Eshetu, M.r Gebregziabher and our class mate students
who advise to do this SRS.

III | P a g e
Table of Contents
APPROVAL SHEET ....................................................................................................................... I
Acknowledgment .......................................................................................................................... III
List of tables ................................................................................................................................. VII
1. Introduction ................................................................................................................................. 1
1.1 Document Purpose ........................................................................................................... 1
1.2 Product Scope........................................................................................................................ 1
1.3 Definitions, Acronyms, and Abbreviations ........................................................................... 1
1.4.References ............................................................................................................................. 2
2. Overall description ...................................................................................................................... 3
2.1 Product perspective ............................................................................................................... 3
2.2 Product functions................................................................................................................... 3
2.3 User characteristics ............................................................................................................... 4
2.4. Operating Environment ........................................................................................................ 4
2.5. Design and Implementation Constraints .............................................................................. 4
2.6. User Documentation ............................................................................................................. 5
2.7 Assumptions and Dependencies ............................................................................................ 5
3. Specific Requirements ................................................................................................................ 5
3.1 External Interface Requirements ........................................................................................... 5
3.1.1 User Interfaces ................................................................................................................ 5
3.1.2 Hardware Interfaces ........................................................................................................ 6
3.1.3 Software Interfaces ......................................................................................................... 6
3.1.4 Communications Interfaces ............................................................................................ 6
3.2 Functional Requirements....................................................................................................... 6
3.3. System use case modelling................................................................................................... 7
Figure 3.1 use case model........................................................................................................ 7
3.3.1. Actors and use case........................................................................................................ 8
3.3.2. System use case documentation .................................................................................... 9
4 Non-Functional Requirement..................................................................................................... 30
4.1 Performance Requirement ................................................................................................... 30
4.2 Safety and Security requirement ......................................................................................... 30

IV | P a g e
 4.3.1 Reliability: The system shall be highly reliable by performing all the functionalities
expected by the end users. This is the most quality attribute needed by the end users. ............ 31
4.3.2 Robustness: the system can survive any invalid user input due to the system validation.31
4.3.3 Availability: The system available for 24 hours within 7 days; 24/7............................... 31
4.3.4 Maintainability: the system can be maintain easily without any complexity. ................. 31
4.3.5 Portability: our system can be easily portable to any device and software or operating
system. ....................................................................................................................................... 31

V|Page
VI | P a g e
 List of tables

Table 1. List of definition, acronyms and abbreviations ......................................................... 1

Table 2. Actors and use case ................................................................................................... 8
Table 3. Login use case documentation................................................................................... 9
Table 4.Create account use case documentation ................................................................... 10
Table 5. Send complain use case documentation .................................................................. 12
Table 6. View complain use case documentation.................................................................. 13
Table 7. Delete complain use case documentation ................................................................ 14
Table 8. Edit profile use case documentation ........................................................................ 15
Table 9. Submit data use case documentation ....................................................................... 17
Table 10. Edit submit data use case documentation .............................................................. 19
Table 11. Manage account use case documentation .............................................................. 20
Table 12. Prepare data form use case documentation ........................................................... 22
Table 13. View farmer data use case documentation ............................................................ 24
Table 14. Send SMS use case documentation ....................................................................... 25
Table 15. Generate report use case documentation ............................................................... 26
Table 16. Send news use case documentation ....................................................................... 27
Table 17. View news use case documentation ...................................................................... 28
Table 18. Assign privilege use case documentation .............................................................. 29

VII | P a g e
 1. Introduction
This section gives a scope description and overview of everything included in this SRS document.
Also, the purpose for this document is described and a list of abbreviations and definitions is
provided.
1.1 Document Purpose
The purpose of this document is to give a detailed description of the requirements for the
“Agricultural Input Data and Notification Management System” software. It will illustrate the
purpose and complete declaration for the development of system. It will also explain system
constraints, interface and interactions with other external applications. This document is primarily
intended to be proposed to a customer for its approval and a reference for developing the first
version of the system for the development team.

1.2 Product Scope

 The < Agricultural Input Data and Notification Management System > is a
software application aimed toward various users, such as customers, system
administrators and employees. These users will use/utilize the product to find
the data from farmers easily based on the user’s current position and other
specification like time, economic, transportation and more.
 The < Agricultural Input Data and Notification Management System > will
address the problem of the farmer to get the agricultural input like (fertilizers,
seed, insect site, etc.) with in short period of time.
 The product has features which will allow/enable users to access the system.
 The main purpose of the product is to facilitate/minimize cost and time
consuming during data gathering from farmer and input distribution.

1.3 Definitions, Acronyms, and Abbreviations

Table 1. List of definition, acronyms and abbreviations
Acronyms, Definition
abbreviations
AIDANM Agriculture Input Data and Notification Management

BGRS Benshangul Gumuz Regional State

1|Page
 FR Functional requirement

REQUIREMENT Any property of system that distinguishes it from the other.

SMS Simple Message Service

STAKEHOLDER Any direct or indirect user of the system.

USER Farmer, employee

USE CASE MODEL Is a model used to represent the stakeholder along with what he/she
does with or gains from it.

1.4.References

[1] R. S. Pressma, Software Engineering, nAPRACTITIONER’S APPROACH, 2005.

[2] B. Alli, "Object Orented System Development," McGraw, 1999.

[3] A. S. W., "the Elements of UML Style," ,T Cambridge University Press,, New York, 2003/5.

[4] I. Sommerville, Software Engineering, 8th Ed Pearson Edu Ltd, 2007.

[5] B. Ali, Object Oriented Systems Development, McGraw-Hil, 1999.

2|Page
 2. Overall description
This section will give an overview of the whole system. The system will be explained in its context
to show how the system interacts with other systems and introduce the basic functionality of it. It
will also describe what type of stakeholders that will use the system and what functionality is
available for each type. At last, the constraints and assumptions for the system will be presented.
2.1 Product perspective
 The product is a new, self-contained product intended for use on both web-based
and android platform.
 This project is not follow on member of other project family rather it is a new web-
based and mobile-based product that is intended to BGRSB.
 The product has three major components which take part in the system. The client-
side component handles the employee who interact the system as client. The
mobile-based device will let users to the farmer to access the system to give data
for the employee. The server side component will handle the administrator who
control the overall activity in the system.
 The product’s web part is developed to run on Windows, Mac OS X and Linux and
the mobile-app on Android OS.
 As this product is new, there are no any products that perform the functionalities of
this system planning to build. [1]

2.2 Product functions

With the web and mobile based system, the users will be able to communicate with the system
easily. The result will be based on the criteria the user inputs. There are several search criteria and
it will be possible for the administrator of the system to manage the overall activities in the system.
The system will let the Farmers to create account, Send complain, View news, Submit data and
Edit profile. And agricultural sector employees to Generate report, Send SMS Send news, View
complain and Edit profile.
The system will also allow Agricultural beurue to manage account, assign privilege and generate
report.

3|Page
2.3 User characteristics
The knowledge, technical skills or expertise, capabilities and experience of each potential class
user class to operate the system is given below.
Administrator: Well experienced IT Professional responsible for handling the system to access
the overall activities. Interact with the mobile and web based. They are managing the overall
system so there is no incorrect information within it. The administrator can manage the information
for each sector as well as the options for both the farmers and the employee
Farmer: End user who access the system as a client with mobile based. Use the system to submit
data to the employee, to give complained and to communicate with the employees. This means
that the farmer have to be able to know any things that are done in the agricultural sector.
Employee: who must be an IT professional use the mobile application and the web portal. There
they will manage the information about their sector, for example a description of the agricultural
input, to view farmer data, to view complain and view farmer paper data form. [2]
2.4. Operating Environment
OE1: The system’s web-app shall operate on any Operating System that support browsers Google
chrome version >= 20, Internet explorer version >=6 and Mozilla Firefox version >=14 etc.
OE2: The system shall operate on the server running Microsoft Windows Server 2012/Linux and
Glassfish Server 4 etc.
OE3: The system’s mobile-app shall operate on device which runs Android Operating System
greater than Android 7.1.1 (Nougat)

2.5. Design and Implementation Constraints

DI1: The system shall use MySQL Database Engine 5.6 as a back end.
DI2: The system shall use android programming for mobile development and PHP for web based
development.
DI3: The front-end programming shall be done with PHP/Java.
DI4: Android app shall be developed using Android SDK API level 25 (Nougat).
DI5: The system shall employ UML modeling language for specifying requirements, designing
subsystems and implementing the system.
DI6: Hardware Limitations Dependency on connectivity bandwidth constraints in different places
across the region for Web/Mobile based interface.

4|Page
DI7: Software limitation Screen readers, local language fonts .The portal needs to interact with
different set of applications and portals. Higher-Order Language requirements the applications
under Benshangul Gumuz Regional Agricultural Sector Bureau will be in vernacular languages
and language is not constrain.
DI8: Parallel Operation Unexpected increase in the number of concurrent user requests during
peak transaction period. [3]

2.6. User Documentation

UD1: The system shall have user manual which dictates users the step by step operation of certain
functionality of system to be performed.
UD2: The system shall have tutorials which detect users the step by step operation of certain
functionality of system to be performed.

2.7 Assumptions and Dependencies

AD1: The system assume that Windows OS 10, Mac OS and Linux OS is available.
AD2: The system makes an assumption of SQL Server Database 7 is available.
AD3: The system assume that a machine with processor speed of 6.7 GHz and RAM size of 16
GB is available for the development of the Mobile-based Android App.

3. Specific Requirements
This section contains all of the functional and quality requirements of the system. It gives a detailed
description of the system and all its features.

3.1 External Interface Requirements

This section provides a detailed description of all inputs into and outputs from the system. It also
gives a description of the hardware, software and communication interfaces and provides basic
prototypes of the user interface.

3.1.1 User Interfaces

UI1: The system shall permit complete navigation based on privilege of the user.
UI2: The system shall have headers consisting of organizations name, logo and product name.
UI3: The system shall make maximum use of selector dropdown menus, list boxes, and links to
minimize incorrect inputs/entries in to the database.
UI3: The system shall provide language preference (English, Amharic)

UI4: The system shall have keyboard shortcuts as an alternative and/or in the case when mouse is
not functioning well.

5|Page
3.1.2 Hardware Interfaces
HI1: Since neither the mobile application nor the web portal have any designated hardware, the
system does not have any direct hardware interfaces.

3.1.3 Software Interfaces

SE1: The system shall use MySQL Database Engine Version 5.6/SQL Server 7 as its database
component. Communication with the DB is through ODBC connections. The system must provide
SQL Data Table Definitions to be provided to the company DBA for setup.
SE2: The system shall use Android SDK API level 25 (Nougat)

3.1.4 Communications Interfaces

CI1: The system shall use default communication protocol, TCP/IP, for data transmission between
server and client. At upper level HTTP, default port 8080 shall be used for communication between
web server and client.
CI2: The system shall send a verification code through user’s email using port 53, http protocol
during account recovery.

3.2 Functional Requirements

This section includes the requirements that specify all the fundamental actions of the software
system.
Functionalities:
FR1. The system shall allow the farmer to create account
FR2. The system shall allow the farmer to view news
FR3. The system shall allow the farmer to submit data
FR4. The system shall allow the farmer to send complain
FR5. The system shall allow the farmer to edit profile
FR6. The system shall allow the employee to send news
FR7. The system shall allow the employee to view complain
FR8. The system shall allow the employee to send SMS
FR9. The system shall allow the employee to view farmer data
FR10. The system shall allow the employee to edit profile
FR11. The system shall allow the employee to generate report
FR12. The system shall allow the employee to paper data form
FR13. The system shall allow the administrator to manage account

6|Page
FR14. The system shall allow the administrator to assign privilege
FR15. The system shall allow the employee to generate report [4]

3.3. System use case modelling

Figure 3.1 use case model

7|Page
3.3.1. Actors and use case
Table 2. Actors and use case
Actors Use case

Farmer Log in

Create account

Send complain

Edit profile

Submit data

Edit submit data

View news

Employee Login

View complain

Delete complain

Edit profile

Prepare data form

View farmer data form

Send SMS

Generate report

Send news

Administrator Login

Manage account

8|Page
 Generate report

Assign privilege

3.3.2. System use case documentation

Login use case documentation
Table 3. Login use case documentation
Use case name Login

Use case id UC1

Author Woinshet

purpose The user to get in to the system

description Used to authenticate the user.

Requirement The user should be authorized.

traceability

priority High

precondition 1. The application is launched.

2. The user has user name and password.

Post condition 1. The system notifies as” username and password granted”.

2. The application main menu is displayed.

actors Farmer, employee, administrator

extends

Flow of events

9|Page
 Basic flow 1. he/she fills her/his own username and password on the space
provided.

2. He/she click”login” button.

Alternative flow 1.The system informs that he/she must fill the space provided if left
null and login button clicked

2.The system provides a chance of resetting username and password

if he/she forgets username and/or password

3. The system shows administrator some user account privacy rules

and guidelines.

Exceptional flow 1. The username and password validity exception.

2. User account privacy exception.

Create account use case documentation

Table 4.Create account use case documentation

Use case name Create account

Use case id UC2

author Birtukan

purpose To create account

description Allows new user to create user name and password.

Requirement The user should be authorized.

traceability

priority High

10 | P a g e
 precondition 1.the system must run

2.the URL must on BGRS AIDANMS website

Post condition 1. The system notifies that user account is created successfully

2. The system requests the farmer to insert account picture and fill
email as optional.

actors Farmer

extends

Flow of events

Basic flow 1. Press the creating account button.

2. Fill all the information including phone number.

3. Press the submit button.

4. Confirmation dialogs displayed and SMS confirmation code is sent to

user’s phone.

5. User enters the confirmation code.

6. Get user name and account.

Alternative flow A.2. It the user doesn’t fill all the information.

A.3. The system asks to fill all the information.

B.2. If the user enters inconsistent information for example if user

enters number on the name area.

B.3. The system asks to enter the correct data.

11 | P a g e
 Exceptional flow 1.The username and password validity exception

Send complain use case documentation

Table 5. Send complain use case documentation

Use case name Send complain

Use case id UC3

Author Juhar

Purpose To send farmers their idea

description Allows the farmer to send complain.

Requirement The farmer must be an authorized person

traceability

priority High

precondition 1.The user launches the application

2. The Farmer first login to the system

Post condition The Complaint sent to the Employer.

actors Farmer

extends

Flow of event

Basic flow 1 . The user presses send complain button.

12 | P a g e
 2 . The user selects complain from the sample or user can write its own
complains.

3 . Presses submit complain button.

4. The system notifies as the complaint is successfully submitted.

View complain use case documentation

Table 6. View complain use case documentation

Use case name View complain

Use case id UC4

Author Beka

purpose To view the farmers complain

description Allows the employee to view complains that is send from the farmers.

Requirement The agricultural sector employee can see the complain

traceability

priority High

precondition 1. The system must run

2. The employee login to the system.

Post condition System displays list of complains.

Actors Employee

extends

Flow of event

13 | P a g e
 Basic flow 1. The user presses send complain button.

2. The user selects complain from the sample or user can write its own
complains.

3. Presses submit complain button.

4. The system notifies as the complaint is successfully submitted.

Delete complain use case documentation

Table 7. Delete complain use case documentation

Use case name Delete complain

Use case id UC5

Author Woinshet

Purpose To delete the send/anccesary complain from the list

description 1. The user presses send complain button.

2. The user selects complain from the sample or user can write its own
complains.

3. Presses submit complain button.

4. The system notifies as the complaint is successfully submitted.

Requirement The information that should be deleted should be identified.

traceability

Priority Low

precondition 1. The Employee login to the system.

2. The Employee view complains.

14 | P a g e
 Post condition Complain delete from list of complains.

Actors Employee

Extends

Flow of event

Basic flow 1. The Employee press delete complain button.

2. The system displays confirmation dialog to enter password.

3. Employee confirms by entering correct password.

4. System delete complains and displays notification that tells the

operation is succeeded.

Alternative flow A.1. If user enters Incorrect password

A.2. System displays error message and ask to enter correct

password.

Edit profile use case documentation

Table 8. Edit profile use case documentation

Use case name Edit profile

Use case id UC6

Author Birtukan

Purpose To edit their profile picture

description Allow the user to edit his /her profile.

Requirement The user must be an authorized person.

traceability

15 | P a g e
 Priority Medium

precondition 1 The user launches the application.

2. The application main menu is loaded.

Post condition 1. The user views his/her profile.

2. Changes made on the user profile.

Actors Farmer, employee

Extends

Flow of event

Basic flow 1. The user press the edit profile button.

2. The user profile information displayed.

3. Select the item to edit.

4. Enter new value.

5. Press save button.

6. The system displays confirmation dialog.

7. The user confirms by entering password.

8. Changes will be saved.

Alternative flow A.4. If the user makes invalid edition.

A.5. The system display error message and ask to enter correct
information.

B.7. If the user enters incorrect user name and password.

16 | P a g e
 1. B.8. The system displays error message and ask to enter correct user
name and password.

Submit data use case documentation

Table 9. Submit data use case documentation

Use case name Submit data

Use case id UC7

Author Juhar

Purpose To submit the farmers data to the sector

description Allows the user to submit the data to database.

Requirement The user must be authorized person

traceability

Priority High

precondition 1. The user launches the application

2. The Farmer first login to the system

3. The farmer to cheek deadline.

4. Press the submit data menu Item.

17 | P a g e
 Post condition The data submitted to database.

Actors Farmer

Extends

Flow of event

Basic flow 1. The user Press the submit data menu item.

2. The user fills all information.

3. The user Press submit button system displays notification for the
successful submission and the data is saved in the database.

Alternative flow A.2. If the user inserts invalid information

A.3. the system displays error message and asks to reenter the correct
information.

B.2: If the user does not fill form

B.3. the system displays error message and ask to fill the form.

C.2: if the user have already submit the data.

C.3. system displays error message and notify he/she has already
submit the data.

D.2: if the dead line is passed.

D.3. the system displays error message and notify the user that dead
line is passed.

Edit submit data use case documentation

18 | P a g e
Table 10. Edit submit data use case documentation
Use case name Edit submit data

Use case id UC8

Author Beka

Purpose To edit the submitted data

description Allows editing the data he/she submitted.

Requirement The user must be authorized

traceability

Priority medium

precondition 1. The user launches the application.

2. The Farmer first login to the system

3. The user submits the data.

4. The user views the data.

Post condition 1. User view the data he/she submitted

2. Changes made to the data he/she submitted

Actors Farmer

Extends

Flow of event

Basic flow 1. the user hits the edit submitted button

2. The user selects a particular item to change its value.

3. User make changes and press save button

19 | P a g e
 4. The system notifies the user as his /her operations are
successful.

Alternative flow A.2. If the user enters invalid data.

A.3. the system displays error message and ask to enter valid data.

B.2. If the deadline is passed.

B.3. the system displays message that tells the dead line is passed.

Manage account use case documentation

Table 11. Manage account use case documentation
Use case name Manage account

Use case id UC9

Author Woinshet

Purpose To manage the overall activity

description Allows the admin to create account for other employees.

Allows the admin to delete account for employee.

Allows the admin to change his password.

Requirement The user must authorized person.

traceability

Priority high

precondition 1. The system must launch.

2. Administrator must login to the system.

Post condition The admin create new user account.

20 | P a g e
 The admin delete employee Account.

The admin change his password.

Actors administrator

Extends

Flow of event

Basic flow 1.1 The administrator press create account button.

1.2 The system displays signup form.

1.3 The administrator fills the form and press create button.

1.4 The system creates account and notifies the operation is success.

2.1The administrator press change password button.

2.2 The system display change password form.

2.3 The administrator fills old password and new password.

2.4 The system change password and notifies the operation is success.

3.1The administrator press delete account button.

2.2 The system displays confirmation dialog which asks to enter

password.

2.3 Admin confirms by entering correct password.

2.4 System deletes the account and display message which notify the
operation is succeeded.

Alternative flow A.1.3. If the admin enters invalid data.

A.1.3.4. The system displays error message and ask to enter valid data.

21 | P a g e
 B.2.1 If the admin enter invalid old password.

B.2.3.The system display error message and ask to enter correct

password.

C.3.1.1. If the user enters incorrect password

C.3.1.2. System display error message and ask to enter correct

password.

Prepare data form use case documentation

Table 12. Prepare data form use case documentation
Use case name Prepare data form

Use case id UC10

Author Birtukan

Purpose To prepare data form

description Allows the Employee to prepare the form that will be used to collect
the data from farmers.

Allows the employee make change on the form that is prepared.

Allows the Employee send data form to the user.

Requirement The user must be an authorized person.

traceability

Priority high

precondition 1. the system must be launch

2. The user login to the system.

22 | P a g e
 Post condition 1. Form is prepared and available to farmers.

2. Changes are made on the form.

3. The user sends data form to farmer.

Actors employee

Extends

Flow of event

Basic flow 1. The user press the prepare form button.

2. The system displays form to be filling.

3. User fills the form properly and save it.

4. The system displays notification that tells operations is succeeded.

5. The user press the Edit Form button

6. The system displays an interface that contains old values.

7. The user enters new values.

8. The system displays notification that tells operation is succeeded.

9. The user press send data form button.

10. The system display notification that tells operation is succeeded.

Alternative flow A.3. If user enters invalid data.

A.4. System displays error message and ask to enter valid data.

A.7.if the user enter invalid value.

A.8.the system display error message and ask to enter valid value.

23 | P a g e
View farmer data use case documentation

Table 13. View farmer data use case documentation

Use case name View farmer data

Use case id UC11

author Juhar

purpose To view the farmers data

description Allows the employee to view the data submitted from the farmers.

Requirement The user must be an authorized person.

traceability

priority high

precondition 1. The user login to the system.

Post condition The employee view the data submitted from farmers.

actors employee

extends

24 | P a g e
 Flow of event

Basic flow 1. The user press the view farmer data button.

2. System displays list of received data if any.

Send SMS use case documentation

Table 14. Send SMS use case documentation

Use case name Send SMS

Use case id UC12

author Beka

purpose To send SMS

description Allows the employee to send SMS message to farmer mobile phone.

Requirement The user must be an authorized person

traceability

priority high

precondition 1. The Employee first login to the system.

2. The farmer creates account.

Post condition The message is sent to the Farmers.

actors employee

25 | P a g e
 extends

Flow of event

Generate report use case documentation

Table 15. Generate report use case documentation

Use case name Generate report

Use case id UC13

author Woinshet

purpose To generate report

description Allows the Administrator and Employee to generate analysis report.

Requirement The user must be an authorized

traceability

priority high

precondition 1. The User login to the system.

Post condition The user generate analysis report.

actors Administrator, employee

extends

26 | P a g e
 Flow of event

Basic flow 1. The User press generate report button.

2. The system displays report.

Send news use case documentation

Table 16. Send news use case documentation

Use case name Send news

Use case id UC14

Author Birtukan

Purpose To send news

Description Allows the Employee to Send news

Requirement traceability The user must an authorized

Priority high

Precondition The Employee is login to the system.

Post condition The Employee sends news to farmer.

Actors employee

extends

27 | P a g e
 Flow of event

Basic flow 1. The Employee press send news button.

2. The employee writes full content of the news.

3. The employer upload the news.

View news use case documentation

Table 17. View news use case documentation

Use case name View news

Use case id UC15

author Juhar

purpose To view the news

description Allows the Farmer to view news

Requirement traceability The user must be an authorized person

priority high

precondition The Farmer first login to the system.

Post condition The Farmer Views news.

actors farmer

28 | P a g e
 extends

Flow of event

Basic flow 1. The Farmer presses view news button.

2. The Farmer views full content of the news.

Assign privilege use case Documentation

Table 18. Assign privilege use case documentation

Use case name Assign privilege

Use case id UC16

author Beka

purpose To assign the privilege

description Allows the Administrator to Assign privilege for employer

Requirement traceability The user must be an authorized person

priority high

precondition The Administrator first login to the system.

Post condition The Administrator assigns privilege for employer.

actors administrator

29 | P a g e
 extends

Flow of event

Basic flow 1. The Administrator presses Assign privilege button.

2. The Administrator assigns privilege to the correct user

successful.

4 Non-Functional Requirement
In this section we will explain how our system should operate.

4.1 Performance Requirement

Availability: Since the system is web based and mobile based, it should be available at any time
unless it is under maintenance.
Clarity: The system should be very clear for both the end users/for farmer, agricultural sector
employee and schedule manager. Training also made the system so clear. The system’s interface
has no intermingled unnecessary contents which diminishes the clarity of the system.
Consistency: The system should be consistent throughout the overall action of the system. Similar
elements and similar actions in the system have again similar use, similar notation, and similar
appearance. There is no need of worrying that similar looking elements may function differently.
Integrity: The system should be accurate in order to give good agricultural input data and
notification, so that the user can trust the system.
Accessibility: The agricultural input data and notification related information or any action can be
accessible easily for the user of the system.

4.2 Safety and Security requirement

In our project there is no sensitive data that needs to be secured. All data can be accessed easily
without any damage either human or the system.

30 | P a g e
 PE1: 95% of the transactions shall be processed in less than 1 second.
PE2: The system shall support 100,000 number of users at a time; concurrently.
PE3: The web-server shall have 4 GB of RAM for running the web-part app and 500 GB of HDD
to store persistent data properly.
PE4: The data shall not be damaged or harmed that could result from the use of the product.
PE5: The system shall use encryption technique such as MD5 to store the passwords and other
sensitive data in the form of cipher text in database. [5]

4.3 Software Quality Attributes

4.3.1 Reliability: The system shall be highly reliable by performing all the functionalities expected
by the end users. This is the most quality attribute needed by the end users.
4.3.2 Robustness: the system can survive any invalid user input due to the system validation.
4.3.3 Availability: The system available for 24 hours within 7 days; 24/7
4.3.4 Maintainability: the system can be maintain easily without any complexity.
4.3.5 Portability: our system can be easily portable to any device and software or operating
system.

31 | P a g e
32 | P a g e