Sei sulla pagina 1di 37

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 and our class mate students who advise to do this
SRS.
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.1Document Purpose

The purpose of this document is to give a detailed description of the requirements for the
“Agricultural input data and notification management system” (ALL) 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 web based and mobile
based system which helps to the employee to find the data from farmers easily based on the user’s
current position and other specification like time, economic , transportation and more. And also
the system helps to the farmer to get the agricultural input like (fertilizers, seed, insect site, etc.)
with in short period of time. The system should be free to use either by a mobile phone application
or web services.
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

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.5 Reference
Template of SRS given by advisors.
Handout of software requirements engineering
www.tutorial.com.

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
This system will consist of two parts: one web based and one mobile based. The mobile application
will be used to collect the data from the farmers while the web based will be used for managing
the information about the agricultural sector and the system as a whole.
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.
Manage account
Create account
Generate report
Send SMS
Send news
Send complain
View news
View complain
Submit data
Edit profile
2.3 User characteristics
There are three types of users that interact with the system: the farmers, the agricultural sector
employee and administrators. Each of these three types of users has different use of the system so
each of them has their own requirements.
The farmers can 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.
The employee will 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.
The administrators also 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
2.4. Operating Environment

The AIDANM system interact with the software, operating system windows 7,8,10 and also it is
plat form independent that interact with any hardware components. And it can operate /run on any
browser such as Internet explorer, Mozila , firefox, ,Baidu spark browser, chrome etc.

2.5. Design and Implementation Constraints


The Internet connection is also a constraint for the system. Since the system fetches data from the
database over the Internet, it is crucial that there is an Internet connection for the system to
function.

Both the web based and the mobile based system will be constrained by the capacity of the
database. Since the database is shared between both system it may be forced to queue incoming
requests and there for increase the time it takes to fetch data.

Hardware Limitations

Dependency on connectivity: bandwidth constraints in different places across the region for
Web/Mobile based interface

Hardware interfaces: for accessibility like speaker, touch screens, Braille interfaces

Software limitation

Screen readers, local language fonts .The portal needs to interact with different set of applications
and portals.

Parallel Operation: Unexpected increase in the number of concurrent user requests during peak
transaction period

Higher-Order Language requirements: The applications under Benshangul Gumuz Regional


Agricultural Sector Bureau will be in vernacular languages and language is not constrain.

2.6. User documentation

The user documentation includes the project deliverable those are the whole project system
requirement specification document, system Design description, test plan document, the main
product of the project which is Agricultural Input Data and Notification Management System for
Benishangul Gumuz Region user manual and a programmer manual.

2.7 Assumptions and dependencies

One assumption about the product is that it will always be used on mobile phones that have enough
performance. If the phone does not have enough hardware resources available for the system, for
example the users might not use the system properly, there may be scenarios where the system
does not work as intended or even at all.

Data is an asset. It is valuable resource, as it has real and measurable value.


Accurate and timely data is critical to quality and efficiency of service.
Data input and its accuracy will depend on the user.
Accountability of data will be defined.
Content generation and updating will be done timely by the user
Portal Management Framework will be devised and user will play active role in it User will
provide content in Amharic/English languages.

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

The user interface of AIDANM system is very simple and highly flexible for the end users to use
the system in a short period of time. It is supported by easily remember able shortcuts as an
alternative and/or in the case when mouse is not functioning well. Moreover, the system has an
interface with a good usability such as visibility of the system, flexibility, error prevention, user
control and freedom for the employee and administrator.

3.1.2 Hardware interfaces

The system works on any computer to access the agricultural input data and notification with no
device type selection and functional on both computers and mobile phones for displaying related
information.
3.1.3 Software interfaces

The mobile application communicates with the SMS application in order to get information about
the user and the visual representation of it, and with the database in order to get the information
about the agricultural sectors. The communication between the database and the web based
consists of operation concerning both reading and modifying the data, while the communication
between the database and the mobile application consists of only reading operations.

3.1.4 Communications interfaces

The communication between the different parts of the system is important since they depend on
each other. However, in what way the communication is achieved is not important for the system
and is therefore handled by the underlying operating systems for both the mobile based and the
web based.

To access the portal internet connectivity will be needed at both server side as well as client side.
Along with this, the portal will interact with the SMS Gateway server to push SMS to different
stakeholders and emails servers to send the automated emails generated from the system to various
stakeholders of the system.

3.2 Functional requirements

This section includes the requirements that specify all the fundamental actions of the software
system.

3.2.1 User Case 1-farmer

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

3.2.2 User Case 2-employee

Functionalities:

FR1. The system shall allow the employee to send news

FR2. The system shall allow the employee to view complain

FR3. The system shall allow the employee to send SMS

FR4. The system shall allow the employee to view farmer data

FR5. The system shall allow the employee to edit profile

FR6. The system shall allow the employee to generate report

FR7. The system shall allow the employee to paper data form

3.2.3 User Case 3-administrator

Functionalities:

FR1. The system shall allow the administrator to manage account

FR2. The system shall allow the administrator to assign privilege

FR3. The system shall allow the employee to generate report


3.3. System use case modelling

Figure 3.1 use case model


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

Generate report

Assign privilege

3.3.2. Use case diagram

Figure 3.2 use case diagram for farmer


Figure 3.3 use case diagram for employee
Figure 3.4 use case diagram for administrator
3.3.3. 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

Basic flow 1. he/she fills her/his own username and password on the space
provided.
2. He/she clicks ”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
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.


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.


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
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.

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

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.

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.

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

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

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.

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.

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.

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.

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

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

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

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

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

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

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 ether human or the system. The user can use the system freely.

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

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.

Potrebbero piacerti anche