AGRICULTURE INFORMATION

REPORTING SYSTEM
TABLE OF CONTENTS

• Overview

• Statement of problem

• Objective

• Scope

• Methodologies

• Current system
TABLE OF CONTENTS…

• Proposed system

• System model

• Design goals

• Proposed software architecture

• Packages
OVERVIEW

• Agriculture in Ethiopia is foundation of country’s economy.

• The governing body that controls Agriculture Information reporting is MOA.

• MOA has 10 regions, 89 zones, 935 woredas and around 14,000 to 16,000 kebeles
under its system.

• MOA consists of mainly four sectors

• MOA gathers reports from the four sectors starting from every kebele, woreda, zone
and region every quarter of the year.
STATEMENT OF PROBLEM

• Most of Agricultural sectors in Ethiopia are burdened by cumbersome paper work

and manual processes.

• MOA tries to gather the reports mainly using Microsoft Excel and for sending the
reports they use emails.

• Data Analysis process is tedious.

• All sectors has no way of gathering the data from kebele to federal using
centralized database.
Objective

General Objective

The main objective of the system is to design and develop web-based

application that will help:
• to change the agricultural sector reporting system from the current semi
computerized system to a simplified reporting system using website and
centralized database.
Objective…

Specific Objectives

To accomplish the general objective, this project has the following specific objectives:
• Analyze the existing system to specify the requirements
• To design a database system for storing the data collected from kebele to federal level.
• Organize the specified requirements in the form of functional and non-functional
requirements.
• Design the system according to the identified requirements.
• To develop web app using suitable programming languages.
Scope

• This project undergoes a detailed study and requirement gathering on the problem
from MOA.
• Design and implementation of web-based Agriculture Information Reporting
System for Ethiopian agricultural sectors will be done.
• To provide a mechanism for the reporting to be fully computerized.
• It is not going to support local languages.
• Gives agricultural information to the users.
• Doesn’t have instant mobile app.
Methodologies

System Development Methodology

• An object-oriented system analysis and design methodology is applied

• Waterfall Model software development methodology is the software model of

this project.
Investigation (Fact-Finding) Methods

• Discussion

• Interview

• Document Analysis
Current system

• All agricultural sectors of MOA does not have an online system.

• Microsoft excel, email and other manual based routines to collect the information
and reports.

• At kebele level, kebele extension worker (KEW) collects the data manually on the
paper.

• From woreda to region the workers prepare the report using Microsoft Excel and
send it to the higher administrator using email.
Proposed system


Functional Requirements

•The system shall provide user account management.

•The system shall allow System Administrator to manage sector.

•The system shall provide a mechanism for approval of change request of report for the

user.

•The system shall allow users to generate report based on their access level.
Proposed System..
Functional Requirements..

• The system shall record and hold information about things and elements of the
four sectors of MOA.

• The system shall provide agricultural information for public users

• The system shall provide kebele extension worker management.

• The system shall allow registering of plan for current season.

• The system shall provide analysis of report.

• The system shall allow the user to download the report in pdf format.
Proposed System…

Non-Functional Requirements
• User interface and Human Factors
• Documentation
• Hardware Consideration
• Performance Characteristics
• Error Handling and Extreme Conditions
• Quality Issues
Proposed System …

Non-Functional Requirements…
• System Modification
• Physical Environment
• Security Issues
• Resource Management
System model

Use case Model

• Use cases work by describing the typical interaction between the users of a system
and the system itself.

 Use case Diagram

• It’s representation of user’s interaction with the system

The use case model for our proposed system is described as follow
Use Case Description
Use Case ID 008
Use Case Name Generate Report
Use Case Description Allow the user to generate report and send to its upper level administration.

Participating Actor  User (Federal User, Regional User, Zone User and Woreda User)
   Kebele Extension Worker
Pre-condition Actor must be logged in
Flow of Events 1. An actor clicks on “Generate Report” link.
2. The system provides registered sector report as an option.
3. An actor selects one of the report types.
4. The system displays generate report button.
5. An actors clicks on generate report button.
6. The system generates report needed and displays Submit Report button.
7. An actor clicks on the Submit Report button.
8. The system saves the report.

Alternative Flow 1. [If there is no available report from the lower level administration]
1. The system displays message.
Post Condition System acknowledges report successfully generated and submitted.

Exit Condition When a report generated and submitted successfully

Dynamic Modelling

Sequence Diagram

• A sequence diagram is an interaction diagram that shows object interactions

arranged in time sequence.

• It depicts the objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of
the scenario.
Sequence Diagram
Design Goals

Performance
• Response time
• Throughput

Dependability
• Reliability
• Robustness
• Availability
• Fault tolerance
Design Goals…

Maintainability
• Extensibility
• Modifiability
End User Criteria
• Usability
Proposed software architecture

Overview
• As the application is a web-based application, it will be accessed through a
web browser.
• The system design proposed to implement Three-Tier client/server
architecture.
• The system will be of the Model View Controller (MVC) architecture.
• Web page or website as View

• Services and Logic as Controller

• Data as Model
Proposed software architecture

Subsystem Decomposition

The “Agriculture Information Reporting System” has the following

subsystems.
• User interface subsystem

• User management subsystem

• Report management subsystem

• Data management subsystem

Persistent Data Management
Packages

Packages of the system are presented as follows:

• User Interface Package

• User Management Package

• Report Management Package

• Data Management Package