ARBA MINCH UNIVERSITY
ARBA MINCH INSTITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE & INFORMATION TECHNOLOGY
Web Based Information Management System For Gamo Gofa zone
Agriculture sector
1
Topics discussed in this section:
Problem statement
Objectives of the project
Scope of the project
Functional requirements
Nonfunctional requirements
Implementation statement
Conclusion
2
Problem statement
The existing system has the following problems.
Since processes are being manually implemented, they need much man
power.
The communication from Zone to Woreda office by letters so it consumes
time.
Persistent data storage and management is difficult.
Not accurate.
Response rates are systematically low in some cases (e.g. machinery and
pesticides).
3
Objectives of the Project
General objectives.
To introduce web based information system for Gamo Gofa zone
agricultural sector.
Change the manual system into web based system.
Specific objective
Identify the problems of the existing system,
Perform requirement analysis,
Design the architecture for the proposed system,
Develop user friendly and interactive system,
Scope of the project
The scope of this project is to design and implement web based
information system
The main scope of our system is concerned on transferring
information about crop production between zone office and
Woreda office.
The system uses Amharic language
5
Functional requirements
The functional requirement is the functionality that the system can
be done.
zone office:- generate report, land use management, post news
and events, response in emergency, target annual plan, give
information about production and productivity, distribution seed
and fertilizer, view type of crop production.
Woreda office:- can be view solution, view different type of
information, see news and events, see emergency response, send
feedback, send report.
1.6
6
Non Functional requirements
A non-functional requirement is a requirement that specifies criteria
that can be used to judge the operation of a system, rather than
specific behaviors.
It defines how a system is supposed to be.
Non-functional requirements are often called qualities of a
system
Performance
Focus should be kept managing the performance and service
availability of software.
7
Implementation and Testing
The implementation phase is the critical phase in which it transform
the design and analysis of the system in to tangible system by writing
the code to the system to be developed and make is operational and
applicable by testing debugging the functionalities that are done
This phase involves the construction of the actual result.
The main objective of this phase is generally is to deploy and
enable operation of the new information system in the production
environment.
8
Final testing of the system
It is the final step of testing in which the entire system as a whole
with all forms, code, and modules are tested.
System testing ensures that the entire integrated software system
meets the desired requirements.
Unit testing
Every module of the System is separately tested. I.e. the team tests
every module by applying some selection mechanism.
Through this mechanism every modules gets tested.
If an error occurs correction will be taken without affecting another
module.
9
Cont’d…..
Integrated Testing
All the modules will be combined together and tested it for its fitness
with each other and with the systems functionality.
If error occurs in combining them, the module with problem will be
identified and recombined.
If an error occurs correction will be taken without affecting another
module.
Black Box Testing
The team has conducted this testing procedure to evaluate only the
outputs generated in response to selected inputs and execution
conditions.
Hardware software acquisitions
Hardware
Computers: for writing code &document, design the system.
Printer: To printing the documents
Server: To create connection to the client computer(to host the system
Software
Notepad++
HTML 5 AND CSS
PHP XAMPP
EDraw Max 7
Expression web
Microsoft office 2007
11
User Manual Preparation
A user manual entitled as a help in our system home page
navigation bar that can guide users when they get any confusion
during their usage.
How to use the system?
In order to access the system, first of all every user must have an
account or permission from system administrator.
So, system administrator should have to create an account for
every user like employee of zone and Woreda.
Users should enter to the system parts by using their individual
Username and password and also with the role given to them.
These Username and password is created by the system
administrator, then the user can access the system.
12
Training
During the deployment of the system, the team will give short time
training for the system administrators and Agricultural Expert
explaining how the system works and in what way they can manage
their system.
Installation Process
Since the project is a web based System, there is no need to install it
on a particular machine rather it will be hosted on a web server.
Database server will also be configured.
13
Conclusions
In this project, we develop a web based system that facilitates Agro
office information provider activities.
The web based system enables the user to know activities like
view information about the fertilizer,
about crop production,
view information about seeds,
view the solution,
view complains,
upload news,
response solution and sends complains.
14
Thank you !!!
Not The End…
14