Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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.
FR Functional requirement
REQUIREMENT Any property of system that distinguishes it from the other.
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.
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
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.
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.
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.
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.
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.
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.
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.
This section includes the requirements that specify all the fundamental actions of the software
system.
Functionalities:
Functionalities:
FR4. The system shall allow the employee to view farmer data
FR7. The system shall allow the employee to paper data form
Functionalities:
Farmer Log in
Create account
Send complain
Edit profile
Submit data
View news
Employee Login
View complain
Delete complain
Edit profile
Send SMS
Generate report
Send news
Administrator Login
Manage account
Generate report
Assign privilege
Author Woinshet
priority High
Post condition 1. The system notifies as” username and password granted”.
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
author Birtukan
priority High
precondition 1.the system must run
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
Alternative flow A.2. It the user doesn’t fill all the information.
Author Juhar
priority High
actors Farmer
extends
Flow of event
Author Beka
description Allows the employee to view complains that is send from the farmers.
priority High
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.
Author Woinshet
2. The user selects complain from the sample or user can write its own
complains.
Priority Low
Actors Employee
Extends
Flow of event
Author Birtukan
Priority Medium
Extends
Flow of event
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.
Author Juhar
Priority High
Actors Farmer
Extends
Flow of event
Basic flow 1. The user Press the submit data menu item.
3. The user Press submit button system displays notification for the
successful submission and the data is saved in the database.
A.3. the system displays error message and asks to reenter the correct
information.
B.3. the system displays error message and ask to fill the form.
C.3. system displays error message and notify he/she has already
submit the data.
D.3. the system displays error message and notify the user that dead
line is passed.
Priority medium
Actors Farmer
Extends
Flow of event
B.3. the system displays message that tells the dead line is passed.
Author Woinshet
Priority high
Actors administrator
Extends
Flow of event
1.3 The administrator fills the form and press create button.
1.4 The system creates account and notifies the operation is success.
2.4 The system change password and notifies the operation is success.
2.4 System deletes the account and display message which notify the
operation is succeeded.
Author Birtukan
description Allows the Employee to prepare the form that will be used to collect
the data from farmers.
Priority high
Actors employee
Extends
Flow of event
A.4. System displays error message and ask to enter valid data.
author Juhar
description Allows the employee to view the data submitted from the farmers.
priority high
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.
author Beka
description Allows the employee to send SMS message to farmer mobile phone.
priority high
actors employee
extends
Flow of event
author Woinshet
priority high
extends
Flow of event
Author Birtukan
Priority high
Actors employee
extends
Flow of event
author Juhar
priority high
precondition The Farmer first login to the system.
actors farmer
extends
Flow of event
author Beka
priority high
actors administrator
extends
Flow of event
4. Non-functional 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.
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.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.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.