Final Project

AMBO UNIVERSITY
AMBO INSTITUTE OF TECHNOLOGY
DEPARTMENT OF COMPUTER SCIENCE
TITLE: WEB BASED AGRICULTURAL DATA COLLECTION SYSTEM

FOR WEST SHEWA ZONES
A Project Submitted to Computer Science Department for the Partial Fulfillment of

the Requirement for the Degree of Bachelor in Computer science
Student Name id
1.Deribew Beko…………………………………………………….. BRT/2280/08
2. Getu Fituma………………………………………………………..BRT/2290/08
3. Fikre Tadesse………………………………………………….......BRT/2135/08
4. Fikadu Dule………………………………………………………..BRT/2286/08
5. Firehiwot Turineh………………………………………………......BRT/2287/08
6. Latera Kumburi………………………………………………........BRT/2155/08
7. Talile Desalegn..... .......................................................................BRT/2241/08
Advisors Name: MSc.Tadele Degefa Submission Date June 17/2019 GC

Web Based Agricultural Data Collection System for West Shewa Zones
Ambo University Academic Education Evaluation System

Approval for the examining board:
_____________________________ _________________
Chairman, Examining Committee signature
______________________________ _________________
Advisor signature
_______________________________ _________________
Examiner signature
Declaration
This is to declare that this project which is produced under the supervision of
MSc. Tadele Degefa title “Web based agricultural data collection system for west shewa zones”
is the sole contribution of the authors and no part here of has been produced illegally which can
be considered as plagiarism. We will be responsible and liable for any consequences if violation
of this declaration is proven.
Date: ________________
Project members:
Name: Deribew Beko signature_______________________
Name: Getu Fituma signature_______________________
Name: Fikre Tadesse signature_______________________
Name: Fikadu Dule signature_______________________
Name: Firehiwo tTurineh signature______________________
Name: Latera Kumburi signature______________________
Name: Talile Desalegn signature______________________
The project has been submitted for examination with my approval as university advisor.
Advisor name: ____________________signature______________date_____________________
i
Acknowledgement
First of all we would like thanks to GOD for helping and enable us to reach this time and finish
our first part of our project on the documentation part. After that we would like thanks to our
advisor MSc.Tadele Degefa for his continual advice and support us as much as possible by
taking more time to help us and his guidance. Then we would like unlimited thanks to MSc.
Naol Bekele computer science department for his supporting in any conditions to support us to
work our project. Finally we would like thanks to all other peoples that are not mentioned for
their help and supporting.

ii
Abstract
The system is Web based agricultural data collection system for west shewa zones. The main
idea of this project is to change manual collection system of agricultural data specifically
concern on crop production registration to web based crop production registrations. We design
and implement the proposed system through going stages of life cycle or by applying software
development model (water fall model). For requirement gathering and requirement analyzing we
use interview, document analysis and observation. For system design we use UML modeling.
And for implementation phase we will use php development methodology. The proposed system
provides many benefits for researchers, ADCOWs, extension workers and manager.
The user of the system must have an account to access the system. And there will be
authentication mechanism to confirm and/or restrict unauthorized users.
iii
Keys Words
ADCOWs Agricultural Data Collectors Offices Workers

CSA Central Statistical Agency
CSS Cascading style sheet
CPU Central Processing Unit
GB Giga Byte
GHZ Giga Hertz
HTML Hyper Text Markup Language
MS word Micro soft word
MYSQL Structured Query Language
OOP Object Oriented Paradigms
PHP Hyper Text Preprocessor
RAM Random Access Memory
SSN Social Security number
Ul User Interface
UML Unified Modeling Language
WLAN Wireless Local Area Network
WBADCs Web Based Agricultural Data Collections
Contents
CHAPTER ONE..............................................................................................................................1
1.1 Background of Organization.................................................................................................1
1.2 Statement of the Problem...........................................................................................................1
1.3 Objective....................................................................................................................................2
1.3.1 General objective................................................................................................................2
1.3.2 Specific objective................................................................................................................2
1.4 Scope of the Project...................................................................................................................3
1.5 Significance of the Project.........................................................................................................3

iv
1.5.1 Target beneficiaries of the system......................................................................................4
1.6 Methodology of the Project.......................................................................................................4
1.6.1 Data sources........................................................................................................................4
1.6.2 Fact Finding Techniques.....................................................................................................4
1.6.3 Systems Analysis and Design (approach)...........................................................................5
1.6.4 Development Tools.............................................................................................................7
1.6.5 Testing procedure...............................................................................................................8
1.6.5 Proposed Implementation Method......................................................................................8
1.7 Limitation of the Project............................................................................................................9
1.8 Risk and Contingencies.............................................................................................................9
1.9 Assumptions and Constraint....................................................................................................10
CHAPTER TWO...........................................................................................................................12
2.1 Description of the current system........................................................................................12
2.1.1 Players in the Existing System.....................................................................................12
2.1.2 Functions/activities in the existing system...................................................................14
2.1.3 Business rules...............................................................................................................14
2.1.4 Report generated in the existing system.......................................................................14
2.1.5 Bottlenecks of the existing system...............................................................................14
2.2 Practices to be preserved.....................................................................................................15
2.2 proposed system...................................................................................................................16
2.3.1 Team composition........................................................................................................17
2.3.2 Feasibility study............................................................................................................18
2.3.3 Requirements of the Proposed System.........................................................................20
v
CHAPTER THREE.......................................................................................................................24
3.1 Introduction..........................................................................................................................24
3.2 System Requirement Specifications....................................................................................24
3.2.1 Use case diagram..........................................................................................................25
3.2.2 Object Model................................................................................................................39
3.2.3 Dynamic Model............................................................................................................41
3.2.4 User interface modeling................................................................................................62
CHAPTER FOUR.........................................................................................................................64
Proposed System Design...........................................................................................................64
4.1 Introduction..........................................................................................................................64
4.1.1 Purpose of the System..................................................................................................64
4.1.2 Design Goals.................................................................................................................65
4.2 Current Software Architecture.............................................................................................66
4.3 System Architecture............................................................................................................66
4.3.1 Overview.......................................................................................................................67
4.3.2 Sub system decomposition...........................................................................................67
4.3.3 Hardware/Software Mapping.......................................................................................68
4.3.4 Persistent Data Management.......................................................................................71
4.3.5 Access control...............................................................................................................71
4.3.6 Global Software control................................................................................................72
4.3.7 Boundary condition......................................................................................................72
Chapter Five...................................................................................................................................74
Implementation and Testing......................................................................................................74
vi
5.1 Introduction......................................................................................................................74
5.1.1 Final Testing Of the System.........................................................................................84
5.1.2 Hardware Software Acquisitions..................................................................................84
5.1.3 User Manual Preparation.............................................................................................84
5.2 Training................................................................................................................................91
5.3 Installation Process..............................................................................................................91
5.4 Start-Up Strategy.................................................................................................................91
Chapter 6........................................................................................................................................92
Conclusion and Recommendation.............................................................................................92
6.1 Conclusion...........................................................................................................................92
6.2 Recommendation.................................................................................................................92
6.3 Reference.........................................................................................................................93
List of Tables
Table 1:software tools......................................................................................................................7
Table 2: hardware tools...................................................................................................................8
Table 3: project budget plan..........................................................................................................19
Table 4: use case description for login..........................................................................................27
Table 5: use case description for create account...........................................................................28
Table 6:use case description for search item.................................................................................29
Table 7: use case description for delete account...........................................................................30
Table 8: use case description for register......................................................................................31
Table 9: generate report use case description................................................................................32
vii
Table 10: use case description for change password.....................................................................33
Table 11: use case description for submit data..............................................................................34
Table 12: use case description for view data.................................................................................35
Table 13: use case description for view current information........................................................36
Table 14: use case description for manage users...........................................................................37
Table 15: use case description post current information...............................................................38
Table 16 Acceess Control and Securtiy.........................................................................................72
List of Figures
Figure 1shows waterfall development life cycle.............................................................................6
Figure 2 Team Member Communications.....................................................................................18
Figure 3 UML Use case Diagram..................................................................................................26
Figure 4Class Diagram..................................................................................................................40
Figure 5sequence diagram for create account...............................................................................42
Figure 6sequence diagram for delete account...............................................................................43
Figure 7sequence diagram for change password...........................................................................44
Figure 8 sequence diagram for view crop data..............................................................................45
viii
Figure 9 sequence diagram for generate report.............................................................................46
Figure 10 sequence diagram for send feedback.............................................................................47
Figure 11 sequence diagram for register page...............................................................................48
Figure 12 sequence diagram for post current information.............................................................49
Figure 13sequence diagram for submit crop data..........................................................................50
Figure 14 sequence diagram for view current information...........................................................51
Figure 15 activity diagram for login account................................................................................52
Figure 16 activity diagram for change password...........................................................................53
Figure 17 activity diagram for generate report..............................................................................54
Figure 18activity diagram for post current information................................................................55
Figure 19 activity diagram for register crops................................................................................56
Figure 20activity diagram for submit crop data............................................................................57
Figure 21 activity diagram for create account...............................................................................58
Figure 22 activity diagram for delete account...............................................................................59
Figure 23 state chart diagrams for login account...........................................................................60
Figure 24 state chart diagrams for register crops...........................................................................61
Figure 25 state chart diagram for generate report..........................................................................61
Figure 26 state chart diagram for submit crop...............................................................................62
Figure 27 graphical user interface diagram...................................................................................63
Figure 28 Sub system decomposition............................................................................................68
Figure 29: Hardware/Software Mapping Deployment Diagram...................................................69
Figure 30 : Deployment Diagram..................................................................................................70
Figure 31 : User Interface for Homepage......................................................................................85
ix
Figure 32 User Interface for Login Page.......................................................................................86
Figure 33 : Use Interface for Admin page.....................................................................................87
Figure 34 : Use Interface for ADCOWS Page...............................................................................88
Figure 35 : Use Interface for Manager Page..................................................................................89
Figure 36 : Use Interface for Extension Worker Page...................................................................90
x
CHAPTER ONE
1 Introduction
1.1 Background of Organization
West shewa Zone Agricultural Offices is found in oromia region which far 114km from central
city Finifine establish in 1920 E.C. It has 529 rural kebeles and 46 urban kebeles, according to
1999 E.C census conduct by the CSA West Shewa Zone has 1,070,898 male and 10,690,016
women, and generally the total population of the west shewa zone is 2,139,914. This agricultural
office gives services to 22 woreda through different cultivation activities. Those activities are
gives advices on irrigation, on variety of crop production, on animal production and Animal
husbandry etc.
1.2 Statement of the Problem

In many cases web based system has brought new opportunities to the government, non-
government organization, and even to individual person. Indeed to this, starting from mid of
1990’s a number of organizations began to publish their own web site on the network to offers
their services and to announce their products online to the customers. Moreover use it to
facilitate their activities that enhance to achieve mission and vision and become more competent
and profitable.
So, West shewa Zone Agricultural Offices is far from these realities because of most of their
activities are enrolling manual through manpower. As a result some of the prominent problems
that the team focuses on to identifying and proposing solution are:
 Agricultural data about crop production report is not accurate.

 Manual collection of crop data is time consuming and tedious.
 Searching of data is very difficult.
 File mixed each other (misplaced file). .
 Persistent data storage and management is difficult.
 Decrease in data completeness.
1
 Allocate high budget for data organizer.

 Low security.
 Data loss.
 Wastages of resource like pen, paper, etc.
 Data redundancy and inconsistency happens.
1.3 Objective
1.3.1 General objective

The general objective of our project is to change the manual system collection of agricultural
data to automated web based agricultural data collection system.
1.3.2 Specific objective

The aim of this project is to develop a secured Web based system with the following specific
objectives:
 To avoid data redundancy and inconsistency.

 Develop user friendly and interactive system.
 Show the potential of the system for further application and scalability.
 Improve and facilitate the communication between the zones and woreda
agricultural offices.
 To make the system more effective and efficient of the system
 To give reliable data about crops production report.
 To record new crops production report.
 To exchange new information between offices.
 To update crops production report.
 To check filled form easily.
 To give reliable search facility.
 To make the system more secured.
 Easy to generate reports.
2
1.4 Scope of the Project

There are different kinds of agricultural data collection activities in the organization. But the
scope of our proposed system is web based agricultural data collection system for west shewa
zone concern specifically on crop production report only.
The scopes of the proposed system are:
 Display all the collected information about crop production report.

 Generate and view report.
 Submit the data that is collect from ambo woreda to zones.
 Give privilege for register ADCOWs.
 Accurate way of Storing and retrieving crop production data into and from
database.
 Usable only between ambo woreda and west shewa zone.
 Modify data.
 Easy ways of backup and recovery data.
1.5 Significance of the Project

The web based agricultural data collection system provides many advantages for the organization
and society. It can improve the efficiency of the system and overcome the drawbacks of the
existing system concern on crop production registration. So our project can reduce the time and
resource required in the current system by using the newly proposed system. Because the
proposed system is an automated way of collecting crop production data report through online.
In general the system has the following benefits:
 Easy to search the recorded data.

 The system can be accessed everywhere in the organization in the given time
frame.
 Provide timely information.
 Reduce resource wastage.
 Easy Data storage and management.
3
 Reducing the probability of errors.

 Potentially increasing data security.
 Easy to generate report.
 Reduce wastage of time.
 Easy to manipulate and maintain the system.
 Increase means of communication between offices workers.
 Reduce data loss.
 Easy to backup and restores if the document has to be damaged.
1.5.1 Target beneficiaries of the system

Any project to be design to gives service for the user to simplify statement of problem. So the
main target beneficiaries of the system in this section described:
 Researchers: get information about crop production and types crops found in west shewa
zones from the system easily and it is also base lines for researchers for modification the
system by adding additional activities occurred in the organization.
 Woreda Extension workers: by using the system extension workers can save their time
and effort to register crop product information, to search item they want easily and easy
ways to record data in data base without loss of information.
 West shewa zone agricultural offices: get report within a time and small resource for
the offices and generate report easily by searching information stored in data base. It also
knows types of crops found in ambo woreda.
1.6 Methodology of the Project
1.6.1 Data sources

In order to develop the system, we will use different data sources like software engineering
books, the project and internet.
1.6.2 Fact Finding Techniques

Interview
4
We would gather information by interviewing both Ambo Woreda agricultural offices and west
shewa zones worker about the existing system.
Document analysis
We also collected certain relevant information from written documents from west shewa zones
agricultural office.
1.6.3 Systems Analysis and Design (approach)

The proposed system will be develop using object oriented analysis and design approach because
the idea behind the approach is to build software systems by modeling them based on the real
world objects that they were trying to represent. OOP is a collection of objects, each with its own
data and its own set of responsibilities. The objects interact by sending messages to each other.
So OOP is:
 Easier to understand.
 Easier to write.
 Contain fewer errors.
 Reduction of development time.
 Reduction of time and resources required to maintain existing systems.
 Increase code reuse.
So to develop or design our system we use system development methodology that is used to
structure, plan and control the process of developing the system. There are different types of
software system development methodologies to develop a system; among these we select
waterfall system development method [4]. Because, waterfall model is simple to implement and
also the amount of resources required for it are minimal when compared to the others. In this
model, output is generated after each stage, hence it has high visibility. The pure waterfall
lifecycle consists of several non-overlapping stages, as shown in the following figure. The model
begins with establishing system requirements and software requirements and continues with
architectural design, detailed design, coding, testing and Maintenance. The waterfall model
serves as a baseline for many other life-cycle models.
5
Figure 1shows waterfall development life cycle.

Planning: during the planning process, we required coming out with as many ideas as possible
on what we going to do, how us going to implement it, what are the software objectives, who are
going to use it and so on. We also construct the work plan at some stage in this phase to make
sure all the datelines can be reached in exact time.
Analysis: the second stage is analysis stage where we are requisite to study and evaluate all the
existing the entire existing problem faced during collecting data. What we are achieved at the
end of this phase is that all the information needed including what the problem that the current
software encounter, how to fix and enhance it and choose the best alternative solution for all
these problems.
Design: the stage followed by the analysis stage is designing stage. We are used a logical
design. Logical design refers functional features of our system described independently. It is
more of a rough sketch on a paper on how the flow of the software and all the diagrams are
generated in this phase. The physical design refers transforming logical specifications details. All
the diagrams constructed are then transformed to more specific details.
Implementation: this phase contains Coding, documentation, training procedures, installation

and testing of our system. This is the most time consuming phases. It needs a lot of courage and
commitment. Diagrams and all information gathered earlier are now be used to build the
software.
6
1.6.4 Development Tools

To develop the system we can use both software and hardware component.
Software tools
TOOLS ACTIVITIES
Html Client side coding run on web browser.
JavaScript Client side script runs on web browser.
CSS Client side CSS run on web browser, used for
font, color and border and pagination.
MySQL Database server
PHP[1] Server side scripting run on web server.
Chrome, uc Browser Browser
Notepad++[2],Sublime_Text_2.0.2 It is one of the writing editors which help us
to write code using PHP programming
language.
MS _word For write documentation part.
Edraw Max To draw different diagram.
Table 1:software tools
Hardware tools
TOOLS ACTIVITIES
Flash disk with 8 GB To transfer data from one computer to the other computer.
Used for recovery purpose.
Both desktop and laptop To input data, to display the output, to do the main programs and to insert
computer with >2 GB input and to store information.
RAM and 10 GB (this
specifications are a
minimum requirement)
Printer For print the documentation.
Ethernet cable Used for connection to access different information that helps our
projects.
Table 2: hardware tools
7
1.6.5 Testing procedure

Testing procedure is the way to know the system functionality weather it is working
according to the specification, behavioral and performance requirements. After completing
the development of system, the testing process will take place. This part recognizes that the
system works it is function correctly or not. Testing will be carried out after all coding process
completed. So we are testing our system using those testing procedures.
Component testing: used for testing of individual program components. We will use this type of
testing to test functions in a class and to test a single class and how they behave.
Integration testing: in this section we will test the dependency between two or more
components and see how components work with each other.
System testing: to test the complete project.
Throughout this testing process it may possible to find the following error:
 Incorrect or missing function error.

 Initialization and termination error.
 Performance error.
1.6.5 Proposed Implementation Method

This section discusses how the proposed system replaces the existing system. The proposed
system will functions parallel with the existing system with features like as modify, generate,
submit and record crop production report and search data item using online. Because the
proposed system needs every office of west shewa zones and ambo woreda will have desktop
computer that is support by connection either wireless or Ethernet cable (WLAN).
1.7 Limitation of the Project

The system we proposed only registered through online and it can be used only for crop
production collection information specifically. It is not give permission for users who have no
account number to submit or send data.
8
1.8 Risk and Contingencies
Risk and contingencies mean the challenge that we will phase during the system development.
Among the challenge that may happen during this system development are:
 Shortage of enough time to develop the system.

 Learning obstacles due to political mission of few people.
 Power failure, at the time of system developments.
 Files may damage by virus or deleted accidentally.
 Un voluntariness of zone agricultural offices to give all information, but they
allow to give some of information like types of crops, how they receive report
from ambo woreda, background of the organizations.
To overcome the above challenges team members will be decide to do these activities:
 Try to use the time given wisely by managing and decomposing our free time
properly.
 We will try to use a laptop computer when there is a power failure is occur.
 Create a backup by using flash disk and by uploading on cloud services like
Google drive.
 Install antivirus software in order to prevent file attacked by virus.
 Use nearby internet cafes and ask expertise related to this project.
 To cooperate with the organization to explain surely the aim our project.
1.9 Assumptions and Constraint

Project assumptions are expected to occur during the project life-cycle for successful
implementation and completion. Although assumptions are the driving force that determines to
project success, typically they’re outside the total control of the project team. So we are
assuming to do our system through members plan from introduction part to implementation part
through exchange idea from team members (each member must participate while doing the
project).Any project is managed under a set of clear-cut constraints, and we need to be defined
9
from the very beginning of the project. If the senior stakeholders clearly understand limitations
of the project environment (such as due dates, resource availability etc.) under which the
activities are to be performed, we will do a better job for ensuring project success and developing
a well-grounded implementation plan.
Generally assumption and constraints are described below. Some of them are:
Assumption
 All the team members have positive thinking to develop or work cooperatively
for success.
 We will have also some resource that we are using in the systems; we will have
back up flash disk to overcome loss of data.
 The system must have an interface which is simple enough to understand.
 The code should be free from errors.
 All necessary hardware and software are available for implementing and use of
the tools.
 End users should have basic little knowledge of computer.
Constraints
When developing and implementing the system the constraint that we set is:
 Unauthorized person cannot use the system

 If users are outside the organization (system) they can view information and
resource but they cannot access the other functions of the system like generate,
registration, modification and record of crop production data without account.
10
CHAPTER TWO
Existing and proposed system
2.1 Description of the current system

In the existing system the organization collect crop product report in manually operations. Those
operation are collecting, recording and documenting about crop production based on the form
prepared on excel. The form has many attributes, such as woreda name, type of crops, types of
crops to be harvest, scatter of crops and the amount crops collected in quintal. Based on the form
firstly, attributes to be filling by extension worker assigned on woreda. Before transfers to zones
from woreda sector the attributes again checked by ADCOWs that works in the staff of zone, if
11
error has to been occurred on the form the ADCOWs to be modify it and transfer to zone
manager. Based on submitting data the zone makes re-organize the data on the form and report
it. In addition to this the zone give advice how to prepared plan to submit the collected data
within time frame.
In generally the existing system has the following function:
 Collect crop production types.

 View reported data.
 Modify submitted crop production report data.
 Record crop production in document.
 Submit the record crop production report.
 View comment based on the reported data.
2.1.1 Players in the Existing System

The existing system is collect crop production data in manual way. During collecting these data
the organization needs certain number of employees to manage the overall function of the
system. That means a number of different actors can be incorporated in the existing
system. The actor involved in the existing system:
 Manager
 extension worker
 ADCOWs
Extension worker: The main players in the existing system are the extension worker. The
function of this actor is:
 Collect types of crops.

 Send crop production reports to ADCOWs.
 View feedback from ADCOWs if the report has a problem.
 Report feedback to ADCOWs.
Agricultural data collection office worker (ADCOW): one who is working in the staff of
agricultural data collection office that is services as secretary. The activity of this actor is:
12
 Give advice to extension workers.

 Edit data about crop production report if all information is fulfill come from
extension worker.
 Send the editable crop production report to manager of the zone.
 View feedback.
 Send feedback to extension worker.
 Submit crop production report.
Manager: is an actor that is working agricultural office as a manager. He/she has the power to
control other staffs in that office. The activity of this actor is:
 Manage user (extension worker, ADCOWs).

 View the reported data.
 Modify reported data.
 Generate report.
 Prepare plan how they submit crop production.
 Give comment.
 Assign location of work place for the collector.
2.1.2 Functions/activities in the existing system

Activities of the existing system are giving and getting supports, transfer crop production report,
view the reported data, modify the submitted data and generate overall report based on the
attributes prepared on the form.
2.1.3 Business rules
The organization have it is own business rule and regulation which are followed to perform work
in easier and best manner. Using the rules organization share information about crop production
reports mostly three times a years (during plough, scatters and collecting).Whenever the
Organization purchases any item, the businesses rule control the bought material like selected
crops and necessary instrument they used during transportation, electronic equipment like
computer, printer. Based on the material to buy for organization the needed material must be
13
request to finance in paper form. When an item is purchased, the organization should have to fill
all necessary information required from them on the form after that the original form will be
given to the finance and the copy of the original form is left for the organization and this form
helps both the finance and the organization for the privacy purposes. Based on the form finance
decide to buy all material they need.
2.1.4 Report generated in the existing system

In order to control and manage over all activities of the crop production report must be generated
in file form. These reports are generates within specific time but are generated in a very routine
and boring manner.
2.1.5 Bottlenecks of the existing system

The bottlenecks of the current system can be categorized as follows.
 Time consuming: In the existing system there are different levels that are
connected manually, for this particular reason sharing of information is time
consuming.
 Economic problems: The budget invested to the data organizer is a huge
amount.
 Data redundancy.
 Searching of type’s crop production is very difficult.
 Misplaced of data item about crop production during transfer of files.
 Files mixed to each other’s.
2.1.5.1 Performance (Response time)

The existing system does not provide fast response time because it is difficult to access and
search data from the record document within second.
2.1.5.2 Input and Output

The existing system collect crop production based on the attributives form prepared on excels.
The form have it is own attributes. Based on the form the collector may insert duplicate value
within their respective attributes which could be inaccurate, redundant and inflexible and
14
these inputs may leads to inaccurate output. So generally the existing system does not provide
fast input and output processing for provides information to users.
2.1.5.3 Security and Controls

Since every file about crop production report is recorded and documented in the manual way, it
is difficult to control and secure these crop production data. That means it is less secured in case
of transition of data, and also there is no authentication mechanism for documenting crop
production information. The way to control the record files is difficult, if the stored document
and files may damage due to fire, natural disaster and man-made disaster.
2.1.5.4 Efficiency
The effectiveness of the existing system is also somewhat not the same as the new
proposed system. Existing system is inefficient in terms of searching, speed and
competency than new proposed system.
2.2 Practices to be preserved

The existing system use file and forms used to perform operation about crop production item,
describe the operations that apply in the agricultural data collection. There are a number of
activities that need to be preserved to be used in the proposed system from the existing system.
We preserve the following practices.
 Submit crop production report based on attributes on the form.

 Edit crop production report.
 Add new crop production data item based on the form.
 Explain mission, vision and objectives of the organization.
 Report is shared between three actors.
2.2 proposed system

The proposed system is a new system that we are implementing to reduce the problem of existing
system of the organization in terms of speed, times, cost and redundancy of data. After we are
carefully observing the problem of current manual system and identifying all the problems
occurred during over all activities of the existing system, we are deciding to design web based
agricultural data collection system for west shewa zones concern on crop production. Since the
15
system web based, so it is fully flagged online at any time during register, modify, submitting
and view report of crop production data. The proposed system will perform functionality of the
existing system and able to advance in high speed, performance and efficiency than current
system. It also reduces the cost of assigned for buying paper again and again, it is easy to backup
and recovery the data.
The proposed system aims to alter the task of the collecting of crop production in different
directions by removing the bulky process of manual collection of data about crop production
report system preparation by a computerized system. This involves creating a centralized
information system that generates and post crop production report automatically on the Ethernet.
The proposed system follows client server architecture model. Client/server architecture is a
computing model in which the server hosts, delivers and manages most of the resources and
services to be consumed by the client. This type of architecture has one or more client computers
connected to a central server over a network or internet connection. When a client user accesses
online the system services through online with a web browser (the client), the client initiates a
request to the system web server. The client login credentials may be stored in a database, and
the webserver accesses the database server as a client. An application server interprets the
returned data by applying the system business logic, and provides the output to the web server.
Finally, the web server returns the result to the client web browser for display.
In each step of this sequence of client–server message exchanges, a computer processes a request
and returns data. This is the request-response messaging pattern. When all the requests are met,
the sequence is complete and the web browser presents the data to the users.
In general the proposed system has the following importance.
 It minimizes the time required to do the task.

 Minimizes the capital that will be invested.
 Fast rate of operation and excellent response time.
 The system is flexible i.e. it can be accessed at any time if there is connection is available.
16
 Easy way of back up or duplicating data in diskettes in case of data is damaged naturally or
man-made disasters.
 Better storage and faster retrieval system.
 Minimizes the labor used.
 Makes the task easy and interactive.
 Ensures accuracy of data.
 Prevent data redundancy.
 Increase searching item.
This will give almost all of the functionalities that the existing system gives. And minimize the
hierarchical structure.
2.3.1 Team composition

In developing any project, there should be team organization to achieve the goal of the project.
We are cooperating each other while doing our projects. So team composition is important for:
 Suitable for less understood, more complicated problem.

 Our member is on the same level and we can review each other
 Higher moral among team member.
 Nobody leads as a boss from the group (all of us are equally participated).
 Encourage to share and review others work.
17
Figure 2 Team Member Communications

2.3.2 Feasibility study
This section helps our proposed project to objectively decide whether to proceed or not. It helps
us to consider things such as technological limitations, staffing requirements, schedule and
economic projections. Feasibility study is made to see if the project on completion will serve the
purpose of the organization for the amount of work, effort and the time that spend on it. It lets us
(project team) predict the future of the project and the usefulness.
2.3.2.1 Operational feasibility

Measure how much the proposed system solves the existing system problems. The project is
operational feasible because the system will reduce the need of time and man power to give
service. The system can be easily operated and accessed by the users anywhere who interact to
the system.
2.3.2.2 Technical feasibility

The system doesn’t require new professional computer skill training person that process the
implemented Web based. Because the system easily understandable and accessible for the users.
18
So, each and every user of the system who has authenticated user name and password of the
organization can access without any confusion by using any web browser.
2.3.2.3 Economic feasibility

Economic feasibility involves comparing the costs of proposed development project with the
benefits the proposed system is going to have for the intended users once it has been developed.
One of the major influences to the new system is to minimize resources that are needed in the
existing system. This project is economically feasible.
Intangible benefits: are benefits that cannot be quantified or not measured in Birr. Those are as
follow:
 It minimizes the work load of the employee.

 Work flow will be efficient.
 Improve accuracy in critical operations.
 Increase speed of activities and competence.
 Error reduction.
The followings are costs related to development of the proposed system. These specifications are
a minimum requirement.
1 Desktop and 2 laptop computer with 8 GB 26,000 birr

RAM 40 GB hard disk and 6.0 GHz CPU speed
in total.
4 GB or higher flash disk to transfer files and to 80 birr
keep backups.
Costs to print the documentation. 350 birr
Cost of transportation to get information from 50 birr
existing system actors.
Total 26,480 birr
Table 3: project budget plan
Tangible benefits: are benefits that can be measured or quantified. They are generally in money
or time saved. The time saved can be converted into birr by applying hourly rate or daily rate.
Some of tangible benefits are:
19
 There is no time wasted by filling cost sharing.

 There is no wastage of papers (it reduce manual work).
 Uses less work load than the existing system.
2.3.2.4 Political Feasibility

This section concerns if the proposed project would have any legal implications for the
organization due to government regulation or software license agreements and ensuring that
there are no people that are going to be affected by the system to be developed. Our system will
not be a conflict for legal requirement. And it doesn’t affect any individual or group of people.
The system we proposed is a lot valuable in our country’s agricultural development.
2.3.2.5 Schedule Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means
estimating how long the system will take to develop, and if it can be completed in a given time
period using some methods like payback period. In time feasibility our project will be finished in
a proper time given to us.
2.3.3 Requirements of the Proposed System

In this section we stated the requirements that are needed in the proposed system which address
the problems of the existing system. We have identified the two types of requirements those are
functional and non-functional.
2.3.3.1 Functional requirements

Functional requirement defines a function of a system or its component. The system perform
register, update, save about crop production report, technical details (how they are used the
system), data manipulation, processing and other specific functionality that define what a system
is supposed to accomplish. .Generally, functional requirements are expressed in the form system
must do (requirement).
Extension workers
 Register crop report.

 Send feedback.
20
 View feedback.
 View current crop information.
 Search item.
ADCOWS
 Submit crop data.

 Edit crop data.
 View crop data.
 Generate crop report.
 Send feedback.
 View feedback.
 Search item.
Manager
 View crop data.

 Post current crop information.
 View feedback.
 Generate report yearly.
 Search item.
Administrator
 Create account to user.

 Delete account to user.
 Change password of user.
 Manage user.
So in generally the system have the following functional requirements:
21
 The system should allow staff (ADCOWs) to login to the system using their username
and password.
 The system should display full information for the agricultural data collection worker’s
from the database to the interface of the web page based on the interest of users.
2.3.3.2 Non Functional requirement

Non Functional requirement concern with user visible aspects of the system not directly related
to functional behavior. 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. In
order to give satisfaction to the client is should do all the operations of existing system in
interactive and easy way with fast response time and maximum through put.
Non Functional requirement expressed in the form:
Performance: the performance of the system is highly measured by the device performance that
the end users are used. If they have a good hardware then the system will be run in an efficient
manner and gives the best response time.
Response time: the System will reacts to the user input or requests with in a second intervals as
the system will be developed for any computer platforms GUI(graphical user interface) to enable
the communication between user and the proposed system.
Throughput: the system can accomplish a requested output within seconds.
Availability: the system will be available 24/7(24 hrs. and 7 days). Because the system is
integrated on an online server it is available at any desired time if the user has an internet
connection.
User interface: the system should have a user interface which is simple to use and negotiable
through each page. It is user friendly to interact with the system. The system provides database
application user interfaces that are compatible with windows platform.
22
Error handling: The Error-handlers are represented explicitly and passed into the program (via
argument). When the error occurs, call the appropriate error-handler with the necessary
arguments. The system handles error if enter integer in place of user name, by displays ”the
name must be string ”.and also if password contains only string or integer the system handles
error, by displays “password must contains special characters, integer and letters” .
Security and Access permissions: security requirements are important factors in this system as
classified data will be stored in the database. The authorization mechanism of the system will
block the unwanted attempts to the server. If unauthorized users try to enter username and
password for more than three times, the system check un-authorization and lock the system or
access denied. User should have an account to enter the system, if user does not have an account
he/she cannot access the system.
Backup and Recovery: since the system is supported by connection so it can be accessed
anytime from the recorded database.
Usability: because the system is integrated on an online server it is available at any desired time
if the user has an internet connection. Every operation of the system must be as simple as
possible for the users to control or use simply
CHAPTER THREE
System Analysis and Modeling
23
3.1 Introduction
System analysis is the basic thing in our system development which helps us system designer to
find the purpose of the system in order to providing partial computerized information handling
system. System modeling is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. It is intermediate language
between requirements and code and also it is the first step in moving from problem domain to
solution domain proceeding from abstract to more concrete representations. It is a creative
activity that determines the major characteristics of a system and represented in three different
models.
Functional model: represented in use case diagrams, describes the functionality of the system
from the user’s point of view.
Object model: Objects are instances of classes that are created, modified, and destroyed during
the execution of the system. It have state that includes the values of its attributes and its
relationships with other objects represented in class diagrams, describes the structure of a system
in terms of objects, attributes, associations, and operations.
Dynamic model: represented in sequence diagrams, state chart diagrams, and activity diagrams,
describes the internal behavior of the system.
3.2 System Requirement Specifications

It is a set of documentation that describes the features and behavior of a system .This section
describes the proposed system in terms of:
 Sequence diagram
 Use case diagram
 Activity diagram:
 Class diagram:
3.2.1 Use case diagram

A system use case model describes the potential usage of the proposed system. It is part of the
analysis document which consists of use case describes sequence of action that provide
24
measurable value to an actor. The rectangle around the use cases is called the system boundary
box and the name suggests it indicates the scope of the system. The use cases inside the rectangle
represent the functionally that the system intend to implement.
Below this there is the use case diagram for Web Based agricultural data collection system for
West Shewa Zone.
25
Figure 3 UML Use case Diagram
3.2.1.1 Use case description (scenario)
26
Use case Name Login

Use case id UC01
Actor ADCOW, Administrator, Extension workers, Manager
Description Used to authenticate the user. I.e. the actor should enter user
name and password.
Precondition Must have valid user name and password.
The user must launch the system.
Basic course of action ADCOW, Administrator, Extension Worker, Manager
1. Open home page
2. Click sign in from the page
3. Enter Username and password.
4. If the system validates of the address.
5. User login to the system.
6. User view help.
Post condition The ADCOW, Administrator, Extension Worker, Manager

enters to the System.
Alternative flow of action 3.a) If the user enter incorrect password and user name
the system gives message “please enter the correct
password and user name”
b) user ”reenter the username and password again correctly ”
Table 4: use case description for login
Use case Name Create Account

Use case id UC02
Actor Administrator
Description Allows the administrator to create account for other staff

member (ADCOWs).
27
Precondition The administrators launch the system.

The administrator login to the system.
Basic course of action The Administrator
1. Administrator Enter to the home page.
2. Administrator login as admin.
3. Click on create account tab.
4. Fill the account information.
5. Click create menu.
6. User view for help.
Post condition New account created.
Alternative flow of If valid account not created

action 4. a The system allows the user asks to fill all the information.
4. bIf the user enters inconsistent information for example
if user enters number on the name area. The system
asks to enter the correct data.
If the user enter incorrect password and username “the system
display please enter correct password and username”.
Table 5: use case description for create account
Use case Name Search item

Use case id UC03
Actor ADCOWs, Manager, Extension worker
Description Allows the ADCOWs, Manager and Extension worker to search item
crops by specify id.
Precondition The actors launch the system.

The actors login to the system.
28
Basic course of action Those actors

1. Enter to the home page.
2. Click on search item.
3. User view help.
Post condition Item to be search successfully.
Alternative flow of 3 a) If the actors don’t enter specify id. The system
action asks to reenter the valid id.
If the user enters incorrect password and username “the system display
please enters correct password and username”.
Table 6:use case description for search item
Use case Name Delete account

Use case id UC04
Actor Administrator
Description Allows the administrator to delete account from staff

members (ADCOWs) by specify id.
Precondition The administrators launch the system.

The administrator login to the system.
1. Administrator opens the home page.
2. Administrator login as admin.
3. Click on delete account tab.
4. Fill the form information.
5. Click delete menu.
6. View for help.
Post condition Account is deleted successfully from database.
Alternative flow of 4. If the user doesn’t enter any id

action The system asks the user to” reenter valid id”.
If the user enter incorrect password “the system display
29
please enter correct password”.
Table 7: use case description for delete account
Use case Name Register crop
Use case id UC05
Actor Extension Workers
Description Allows the extension workers register crops to

ADCOWs by fill form.
30
Precondition The users launch the system.

The extension workers login to the system.
Basic course of action 1. The user display home page.

2. The users press the register form menu.
3. The system displays form to be filling.
4. User fills the form properly and save it.
5. The system displays notification that tells
operations is succeeded.
Post condition Extension worker is already registered product item
include new crops.
Alternatives flow of If all form not filled

action The system asks the users to fill all forms correctly.
If the user enters incorrect password and username
“the system display please enters correct password
and username”.
Table 8: use case description for register
Use case Name Generate Report
Use case id UC06
Actor Manager
Description Allows Manager to generate analysis report.
Precondition The manager login to the system.

The managers launch the system.
31
Basic course of Manager

action 1. Display the home page.
2. The users press the generate report form menu.
3. The user fill form and click generate report link.
5. View for help.
Post condition The system generates analysis report is success.
Alternatives flow of If all form not filled

actions The system asks the users to fill all forms correctly.
If the user enters incorrect password and username “the system
display please enters correct password and username”.
Table 9: generate report use case description
Use case Name Change password
Use case id UC07
Actor Administrator
Description Allows changing the password of the account.
Precondition The administrator login to the system.

The Administrator launch to the system.
32

1. Press Change Password menu.
2. The system asks to enter old password.
3. The actor enters old password.
5. If old password correct “the system asks to enter
new password”.
6. The actor enter new password and click change
password.
7. The system display notification that tells the
operation is succeeded.
Post condition Password changed.
Alternative flow of action 3 a) If you are enter incorrect old password the system
give information “please enter correct old
password”.
Table 10: use case description for change password
Use case Name Submit crop data
Use case id UC08
Actor ADCOWs, Manager
Description Allows the user to submit the crop data to database.
Precondition The manager, ADCOWs login to the system.

The manager, ADCOWs Launch the system.
33
Basic course of action The ADCOWs

1. Open home page.
2. Click the submit crop data menu Item.
4User fills the form properly and save it.
5. The system displays notification that tells
Operations are succeeded.
Post condition The ADCOW enter to the System and Submit the crop
data.
Alternative flow of action 5. If deadline not passed

System allowsthe userto fill form correctly to submit
data.
.
Table 11: use case description for submit data
Use case Name View crop production data.
Use case id UC09

Actor ADCOW, Manager
Description View crop production data that was submitted yearly and
monthly.
Precondition The manager, ADCOWs login to the system.

The manager, ADCOWs Launch the system.
34
Basic course of action The ADCOW

1. Open home page.
2. The users press the view crop data form menu.
3. The system displays crop data.
4. View for help.
Post condition Display the crop production data.
Alternative flow of action If the user enters incorrect password and username “the system
asks the user to reenter correct password and username to view
data”.
Table 12: use case description for view data
Use case Name View current information.
Use case id UC10

Actor Extension workers
Description View current information.
Precondition The extension workers login to the system.

The extension workers Launch the system.
35
Basic course of action The Extension workers

1. Open home page.
2. The users press the view current info menu.
3. The system displays current info.
57. View for help.
Post condition Display current information.
Alternative flow of action If the user enters incorrect password and username “the system
asks the user to reenter correct password and username to view
data”.
Table 13: use case description for view current information
Use case Name Manage users
Use case id UC11
Actor Administrator
Description Allows the Administrator to delete the staff members who have
already changed their job place.
Precondition User must be login in to System.
36
Basic course of 1.Display home page.

action 2. System displays employee detail information.
3. User specifies the employee to be deleted.
4. User clicks on delete employee Button.
5. System displays the confirmation message.
6. System deletes the employee from database.
7. Use case ends.
Post condition The employee deletes from the list.
Alternative’s 3. If the manager doesn’t specify any employees

flow of action The system allows the manager to specify the employee.
Table 14: use case description for manage users
Use case Name Post Current Information
Use case id UC12
Actor Manager
Description The manager posts Current information.
Precondition Manager logged into the system

The managers launch the system.
37
Basic course of 1. displays home page.

action 2. Manager selects the post current information
option.
3. System display post current information option.
4. The system posts the information.
5. Use case ends.
Alternative flow 1. System check the data entered.
action 2. System inform to the manager you enter incorrect data
3. The system returns to step 2.
4. Use case ends.
Post condition The information is posted into extension worker interface.
Table 15: use case description post current information
3.2.2 Object Model
3.2.2.1 Class Diagram

It describes the structure of the system by showing the systems class attributes; operations and
the relationships among object their associations. Classes are abstractions that specify the
attributes and behavior of a set of objects.
38
Figure 4Class Diagram
39
3.2.3 Dynamic Model
3.2.3.1 Sequence diagram

Sequence diagrams describe patterns of communication among a set of interacting objects that
shows how processes operate with one another and in what order. An object interacts with
another object by sending messages. The reception of a message by an object triggers the
execution of an operation, which in turn may send messages to other objects. Arguments may be
passed along with a message and are bound to the parameters of the executing operation in the
receiving object.
40
Figure 5sequence diagram for create account
41
Figure 6sequence diagram for delete account
42
Figure 7sequence diagram for change password
43
Figure 8 sequence diagram for view crop data
44
Figure 9 sequence diagram for generate report
45
Figure 10 sequence diagram for send feedback
46
Figure 11 sequence diagram for register page
47
Figure 12 sequence diagram for post current information
48
Figure 13sequence diagram for submit crop data
49
Figure 14 sequence diagram for view current information
3.2.3.2 Activity diagram

An activity diagram is essentially a flowchart describes a system in terms of activities. Activities
are states that represent the execution of a set of operations.
50
Figure 15 activity diagram for login account
51
Figure 16 activity diagram for change password
52
Figure 17 activity diagram for generate report
53
Figure 18activity diagram for post current information
54
Figure 19 activity diagram for register crops
55
Figure 20activity diagram for submit crop data
56
Figure 21 activity diagram for create account
57
Figure 22 activity diagram for delete account
58
3.2.3.3 State chart diagram

State chart diagrams depict the various states that an object may be in the transition between
those states. State is condition of an object when particular event occurs. In other word, it has
initial and final states in addition to transition that is a progression from one state to another.
These represent the events that cause the object to change from one state to another. A state
chart diagram models the behavior of a single object, specifying the sequence of events that an
object goes through during its lifetime in response to events.
Figure 23 state chart diagrams for login account
59
Figure 24 state chart diagrams for register crops
Figure 25 state chart diagram for generate report
60
Figure 26 state chart diagram for submit crop
3.2.4 User interface modeling

The user interface (UI) is the space where interactions between actors and system machines
occur. The goal of this interaction is to allow effective operation and control of the system from
the actor’s end, whilst the system simultaneously feeds back information that aids the operators'
decision-making process. Generally, the goal of user interface design is to produce a user
interface which makes it easy, efficient, and enjoyable (user-friendly) to operate a system in the
way which produces the desired result. This generally means that the operator needs to provide
minimal input to achieve the desired output, and also that the machine minimizes undesired
outputs to the human.
61
Figure 27 graphical user interface diagram
62
CHAPTER FOUR
Proposed System Design
4.1 Introduction
System design is the transformation of the analysis model into a system design model. Up to now
we were in the problem domain. System design is the first part to get into the solution domain in
a software development. This chapter focuses on transforming the analysis model into the design
Model that takes into account the non-functional requirements and constraints described in the
Problem statement and requirement analysis sections discussed earlier.
The purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based
on understanding of the model the software built on. The objectives of design are to model the
System with high quality.
Implementing of high quality system depend on the nature of design created by the designer. If
one wants to change to the system after it has been put in to operation depends on the quality of
the system design. So if the system is design effetely, it will be easy to make changes to it.
4.1.1 Purpose of the System

The system is designed to implement a solution to an application domain which consists
of a Web Based Agricultural Data Collection System. This will be achieved by delivering a
software system that will interact with the corresponding actors, such as Administrator, Manager,
ADCOWS and Extension Workers that handles the request for manage System, control other
staffs in the office, Works as a secretory of the Office and Submit Crop Data, browse and
generate report by using website. The system will be an online based software system that can
be accessed from any computer with a connection to the internet. The solution implemented will
allow better manage Crop Product report.
The main purpose of the proposed system is to improve some activities through computerized
way that simplifies the workload of the existing system and speedup the operation of the system.
63
We all know the importance of automation. The application areas for the computerization have
been selected on the basis of following factors:
 It minimizes the time required to do the task.

 Minimizes the capital that will be invested.
 Fast rate of operation and excellent response time.
 The system is flexible i.e. it can be accessed at any time if there is connection is available.
 Easy way of back up or duplicating data in diskettes in case of data is damaged naturally or
man-made disasters.
 Better storage and faster retrieval system.
 Minimizes the labor used.
 Makes the task easy and interactive.
 Ensures accuracy of data.
 Prevent data redundancy.
 Increase searching item.
4.1.2 Design Goals

The objectives of designing are to model a system with high quality. Implementing of
high quality system depends on the nature of the design created by the designer if one wants to
make changes to the system after it has been put in to operation depends on the quality of the
system design. So if the system is designed perfectly, it will be easy to make changes to it.
The goal of the system design is to manage complexity by dividing the system in to manageable
pieces. Some of the goals are listed below.
 Security: The system should be secured from unauthorized user.

 Modifiability: The system should be modifiability to modify different services
depending on the need of the institute.
 Flexibility: The system able to change to suit new condition or situation.
 Efficiency: The system must do what it is supposed to do efficiently without the
problem..
 Performance: The system should respond fast with high throughput
64
 Reliability: System should be reliable to increase user’s confidence.

 Usability: Usability is the extent to which a product can be used by specified users to
achieve specified goals with effectiveness, efficiency and satisfaction in a specified

context of use. From the end users’ perspective, the system should be designed in such a way
that it is easy to learn and use and efficient.
4.2 Current Software Architecture

Currently there is no software architecture for Web based Agricultural Data collection. The
current system is a paper based system that is outdated and unorganized. There is no full
computerized system for handling the data to delivers the information as well as manages report.
In order to handle or process the report data there is the manual system that is deployed within
the Excel.
4.3 System Architecture

The system will be built on a layered architecture. A layered architecture makes it easier to
maintain or modify one part of the system without affecting the others. For example if the
developer need a modification on the User interface, they could get it without affecting the rest
of the system.
User Interface Layer: - The interface between the system and user perspective. This layer
wraps access to the post report layer of our system. For instance in our system the User interface
(UI) provide the user to access the system easily.
Post report layer: - post report layer implements all the functional requirements which
implements the concepts relevant to our post report.
Persistence Layer: - Persistence layers encapsulate the capability to store, retrieve, and delete
objects/data permanently without revealing details of the underlying storage technology in the
system. Our system uses MYSQL database.
Database: - The system will be using a relational database for its persistent data storage. The
layer at the bottom of architecture will be database system.
65
4.3.1 Overview
In our system we have preferred tier system architecture because of the following main
advantages: -
 Scalability – Each tier can scale horizontally

 High Performance – the Presentation tier can cache requests, network utilization is
minimized, and the load is reduced on the Application and Data tiers.
 High degree of flexibility in deployment platform and configuration
 Better Re-use
 Improve Data Integrity
 Improved Security
 Easy to maintain and modification is bit easy, won’t affect other modules
 In three tier architecture application performance is good.
The website is the main part of the WBADCs for West Shewa zone that controls the crop
product report activities The Manager, Extension worker, and ADCOWs can communicate using
this website. They can do their task using their own account in this website.
4.3.2 Sub system decomposition

Subsystem decomposition is the process of separating out a module into a standalone module. It
makes the system easy to understand, design, develop and maintain in system analysis section we
have identified, the functional requirements of the system under development. By reviewing
these functional requirements, we decomposed the system into subsystems. A subsystem is a
collection of classes, operations, events and constraints that are interrelated to provide a set of
services to a system. These are a grouping of model elements that represent a behavioral unit in
a physical system. We used subsystem decomposition diagrams to express how our system is
decomposed to smaller parts or set of related operations that share a common purpose. Web
based agricultural data collection system can be decomposed to four subsystems. The major
subsystems are account management, report generating, Import system management, and Data
submission management.
66
 Account management: allow the Administrator to make change on password, Manage

user, Delete account and allows creating account for ADCOWs.
 Generate Report: allow the ADCOWs to generate reports based on the collected data.
 Import system management: Allows the ADCOW to Import submitted.
 Data submission management: Allow the ADCOW to submit data, insert data and make
changes to the submitted data.
Figure 28 Sub system decomposition
4.3.3 Hardware/Software Mapping.

One of the major tasks in system design deals with hardware/software mapping which deals with
which components would be part in which hardware and so on. The system is a broad that
performs many functions. The system assists the officer to generate report. So the web based part
is expected to run on a networked environment on different Operating System platforms. The
client/server architecture of the system enables different clients to connect to the server remotely
through Internet connection. The applications of the system will run on the web server connected
to the database server by MYSQL. Users merely need to start their browsers and enter the URL
67
of the application Web site. The server hosting the Web site is responsible for allocating all the
resources the Web application requires
Figure 29: Hardware/Software Mapping Deployment Diagram
The software going to be developed is allowed by UML model. UML deployment diagram
show physical view of system, taking software into real world by showing how software gets
assigned to hardware and how communicates.
The deployment diagram shows how the software components, processes, and objects are
deployed into the physical architecture of the system.
It shows the configuration of the hardware units (e.g. Computers, communication devices, etc)
and how the software components are distributed across the units. Deployment diagrams are used
to visualize the topology of the physical components of a system where the software components
are deployed.
So, Deployment diagrams are used to describe the static deployment view of a system and
consist of nodes and their relationships. It used for describing the hardware components where
68
software components are deployed and mainly used by system engineers. These diagrams are
used to describe the physical components (hardware), their distribution and association. To
clarify it in details we can visualize it as the hardware components/nodes on which software
components reside.
So the usage of this diagrams can be described as follows:
 To model the hardware topology of a system.

 To model embedded system.
 To model hardware details for a client/server system.
 To model hardware details of a distributed application.
 To design the hardware components efficiently
Figure 30 : Deployment Diagram
69
4.3.4 Persistent Data Management

Persistence modeling needs to use to communicate each other the design of the database in our
system, it is usually the data base to both the users of WBADCs and for the developers. It is
also used to describe the persistence data aspect of WBADCs system.
4.3.5 Access control

Here we will describe the privileges or authorities of actors over the functionalities. In this
system there are four actors Manager, Agricultural data collection office worker (ADCOW)
,Extension worker and Administrator. Each has their own privileges to gain access of the system.
Manager ADCOWS Extension Administra

workers tor
Login    
Change password 
Insert Data   
View Crop Data  
Edit Submitted Data  
Register crop data 
Create Account 
Delete Account 
View feedback   
View 
current information
Send feedback 
Post current data 
information
Send comment  
Generate crop report 
Search   
Submit crop data 
Generate report 
yearly
Table 16 Acceess Control and Securtiy
70
4.3.6 Global Software control

The WBADCS architecture is to have an explicit, centralized software control. The system's
dynamic control is distributed among different controllers such that each object delegates some
responsibility to other objects. The request initiations are event-driven:
 The Manager initiates the UI Subsystem by logging into the system.

 The Main Subsystem initiates the account subsystem by gathering information from
ADCOWs and Manager.
 The Main Subsystem initiates the employee subsystem by checking the availability and
notifying of the Response.
 The Database Subsystem can be initiated at any point by all Subsystems except the UI
Subsystem. Any request (add/update/retrieve) to the repository initiates the Database
Subsystem. The system stores its contents in the database between executions. When the
application is run again, it retrieves the contents from the previous execution. Any change
in the contents during this execution updates the database
4.3.7 Boundary condition

Startup: go to system URL and login
Shut Down: click log out and close browser
Error Conditions:
 Logging in:
o Username or password field can be blank
o Password is not take if length less than four characters long.
o Password and username don’t match.
o Username is wrong or does not exist.
 Data Entry
The system fails if the admin deactivate when the manager, ADCOWs, Extension workers are
entering information.
 Product availability
 There are no available products in any.
71
 Monitor display
 The system crashes or the backup also crashes.
 The system hangs up.
 The desktop application may fail up.
 Relative searching for customer or product.
 Search criteria do not return any results who has not valid account
numbers
 Logging out
 Manager unable to logout.
 ADCOWs unable to logout.
 Administrator unable to logout.
 Extension workers unable to logout.
Chapter Five
Implementation and Testing
5.1 Introduction
Implementation refers to the coding of the all documents gathered starting from
requirement analysis to design phase. So now the team is in a position of converting all
documents gathered and designed into the code so that the system will be implemented for the
user to be used for the purpose it developed. The Implementation phase in the software life-cycle
is where the actual software is implemented. The result of this phase consists of source
code, together with documentation to make the code more readable. This is what we call
software implementation.
72
The purpose of these activities is to convert the final physical system specification into working
model with reliable software and hardware, document the work that has been done, and provide
help for current and future users and take care of the system. After implementing the system it
must be tested. Testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the software
process that could be viewed as destructive rather than constructive. A strategy for software
testing integrates software test case design methods into a well-planned series of steps that result
in the successful construction of software. Testing is the set of activities that can be planned
in advance and conducted systematically. The underlying motivation of program testing is to
affirm software quality with methods that can economically and effectively apply to both
strategic to large and small-scale systems. In this, coding, testing, installation and training etc.
Coding
Simple Coding for Login Page
<?php
include("connection.php");
session_start();
?>
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/style.css">
<link rel="stylesheet" href="css/responsive.css">
<link href="aa.css" rel="stylesheet" type="text/css" media="screen"/>
73
<script src="aa.js" type="text/javascript"></script>
<script src="js/modernizr.js">
</script>
</head>
<body>
<div class="wrapper">
<header class="cf">
<a href="#"><img src="img/log.png" alt="" width="350" height="185" align="left"></a>
<a href="#"><img src="img/spla.jpg" alt="" width="300" height="185" align="center"></a>
<a href="#"><img src="img/log.png" alt="" width="350" height="185" align="right"></a>
</header>
<nav class="cf">
<ul id="nav" class="sf-menu">
<li class="current-menu-item"><a href="Home.php">Home</a></li>
<li><a href="#">About Us</a>
<ul>
<li><a href="background.php">Background</a></li>
<li><a href="objective.php">Objective</a></li>
</ul>
74
</li>
<li><a href="help.php">Help</a></li>
<li><a href="contact.php">Contact Us</a></li>
<li><a href="#">login</a>
<ul>
<li><a href="admin_page.php">administrator</a></li>
<li><a href="login.php">ADCOWS</a></li>
<li><a href="login.php">Manager</a></li>
<li><a href="login.php">Extension workers</a></li>
</ul>
</nav>
<div id="main" class="cf">
<div class="page-content">
<div class="entry-content cf">
<ul class="tabs"></ul>
<div class="panes">
<div><div id="map">
<body>
<table align="center" id="insides" width="850px">
<tr>
75

<td width="25%" height="500px" valign="top" id="insides">
</td>


<td valign="top">
<div style="width:420px; height:350px; margin:0 auto; position:relative; border:2px solid

rgba(0,0,0,0);
-webkit-border-radius:10px; -moz-border-radius:5px; border-radius:25px; -webkit-box-shadow:0

0 18px rgba(0,0,0,0.4);
-moz-box-shadow:0 0 18px rgba(0,0,0,0.4); box-shadow:0 0 18px rgba(0,0,0,0.4); margin-

top:20px; color:#000000;">
<form id="form1" name="login" method="POST" action="login.php" onsubmit="return

validateForm()">
<div style="background-color: green;border-radius:5px;font-family:Arial, Helvetica, sans-serif;

color:#000000; padding:5px; height:22px;">
<div style="float:left;" ><strong><font color="red" size="5px">please Login

</font></strong></div>
<div style="float:right; margin-right:20px; background-color:#cccccc; width:25px; text-

align:center; border-radius:10px; height:12px;"><a href="Home.php" title="Close">
<img src="imgs/close_icon.gif"></a></div>
</div>
<?php
76
if (isset($_POST['submitlogin'])){
$username=$_POST['username'];
$password=$_POST['password'];
//$pass=md5('$password');
$sql = "SELECT * FROM users WHERE username='$username' AND

password='$password'";
$result = mysql_query($sql);
// TO check that at least one row was returned
$rowCheck = mysql_num_rows($result);
$row=mysql_fetch_array($result);
$status=$row['status'];
if($row['level']==1){
if($status==1)
$_SESSION['user_id']=$row['user_id'];
echo "<script>window.location='admin_page.php';</script>";
else
echo'<p class="wrong"> Your Account is not active Please contact the system
Admin</p>';
77
echo' <meta content="4;login.php" http-equiv="refresh" />';
else if($row['level']==2){
if($status==1)
$_SESSION['level']=$row['level'];
echo' <meta content="1;manager.php" http-equiv="refresh" />';
else
echo' <p class="wrong"> Your Account is not active Please contact the system
Admin</p>';
else if($row['level']==3)
if($status==1)
78
echo' <meta content="1;datacollector.php" http-equiv="refresh" />';
else
Admin</p>';
}}
else if($row['level']==4)
if($status==1)
echo' <meta content="1;adcows.php" http-equiv="refresh" />';
else
79
Admin</p>';
else {
echo'<br>';
echo' <p class="wrong">Please Enter The Correct User Name and Password!!</p>';
mysql_close($conn);
?>
<p align="center"><img src="img/k.gif" title="Please Login" width="80"> <p

align="center"></p>
</p>
<table width="386" valign="right" align="center" border="0">
<tr>
80
<td class='para1_text' width="320px"><font color="red">*</font>

User_name:</td><td>
<input type="text" name="username" placeholder="username" title="Enter

Username"></td>
</tr> <tr>
<td class='para1_text'><font color="red">*</font> Password:</td><td><input

type="password" name="password" placeholder="password"title="Enter password" ></td>
</tr>
<tr>
<td><div align="right"></div></td>
<td class='para1_text' width="380px"><a href="forget.php">Forget Your Password? <img

src="imgs/help.png"> </a></td>
</tr>
<tr>
<td> </td>
<br>
<td><input type="submit" name="submitlogin" class="button_example"

value="Login"/></td> </tr>
</table>
</form> </div> </td> </tr>
</table> </body>
</div> </div> </div> </br></br>
<div class="footer-divider"></div>
81
<footer class="cf">Copyright © 2019/2011 AMBO UNIVERSITY | DESIGN BY

GROUP 2 STUDENT'S FOR FINAL PROJECT 1<sup>rst</sup> BSC</footer>
</div>
<script src="js/jquery.js"></script>
<script src="js/custom.js"></script>
<script src="js/superfish-1.4.8/js/hoverIntent.js"></script>
<script src="js/superfish-1.4.8/js/superfish.js"></script>
<script src="js/superfish-1.4.8/js/supersubs.js"></script>
<script src="js/nivoslider.js"></script>
<script src="js/tabs.js"></script>
</body> </html>
5.1.1 Final Testing Of the System

The tests will allow us to ensure correct program flow, and to determine the error-
handling capability of the system Once code has begun, the testing process can begin and
proceed in parallel. As each program module is produced, it can be tested individually, as part of
the larger program, and then as part of larger system. The tests will allow us to ensure correct
program flow, and to determine the error-handling capability of the system. The following are
different testing strategies.
5.1.2 Hardware Software Acquisitions

In order to implement and use the entire ADCO system, different hardware and software are
required as it was described in ‘Hardware and Software requirement’ in chapter one. Any user
who is intended to use this system must have the following hardware and software to
implement and use the complete system.
 Software
 XAMPP (X-os, Apache, MySQL, PHP server and Perl).
82
 Internet Browser (i.e. Google chrome, Opera).

 OS (i.e. windows).
 Hardware
 Server Computer
 Hard disk with enough storage and flash disk.
 Switch and internet cable or wireless network.
5.1.3 User Manual Preparation

User manual is used to show each procedures of the system for the simplicity of performing the
operation of the system easily. As the system is hosted on the single machine that is server, there
is need of preparing user manual. Some useful information’s are given to the user when
deploying the system and also little guiding information on the site of the system which guides
the user how to use the system. The user manual describes as the followings
User Interface for Homepage
83
Figure 31 : User Interface for Homepage
User Interface for Login Page
84
Figure 32 User Interface for Login Page
Use Interface for Admin page
85
Figure 33 : Use Interface for Admin page
Use Interface for ADCOWS Page
86
Figure 34 : Use Interface for ADCOWS Page
Use Interface for Manager Page
87
Figure 35 : Use Interface for Manager Page
Use Interface for Extension Worker Page
88
Figure 36 : Use Interface for Extension Worker Page
89
5.2 Training
Training is the process of teaching or learning a skill or job. During the development of
the system, the project group members will give short time training for the system administrator
and employee explaining how the system works and in what way they can manage their
system. Training is needed for two reasons: If users are not adequately trained they will not
operate with the system correctly or efficiently.
If users fill the task they are being asked to perform are outside their capabilities, they may
become demoralized and separated. User training must be provided to user of the system in order
to help make them to equate with the system. Users are vital part of any system
5.3 Installation Process

Installation of our proposed system at minimum requires a computer to serve as a computer to
run the web based program. In addition XAMP software needs to be installed and configured so
that the database and other web based interrelated functions can be process. After all hardware
and software requirements have been fulfilled, you can install simply by following steps:
Step1: Install XAMPP (X-os, Apache Sever, MySQL, PHP and Perl) on computer.
Step2: Get the folder “ADCO “which contains files and source code of the system from the
Developers Team.
Step 3: Past the folder in the C:\Xampp\htdocs.
Step4: Run XAMPP control panel and start all services.
Step5: Installation is finished
5.4 Start-Up Strategy

After our web page is configuring, the page start up in three ways.
One which needs password and username that is for all employees and system
administrator. To access his/her own authorized pages one should have password and
90
Chapter 6
Conclusion and Recommendation
6.1 Conclusion
In this System we develop a web based application that facilitates agricultural data collection
activities. The system is web application. The web application enables to create user accounts,
view the data, view comment, and generate report. Our model contains analysis model which
contains the functional and non- functional requirements, use case, sequence, activity diagram,
class diagram and user interface. And also contains design model which consists subsystem
decomposition, deployment diagram, persistence modeling of classes, and access control.
6.2 Recommendation
While doing this system the team has faced different types of challenges. But by the
cooperation of all the group members and the advisor, the team is now able to reach to the
final result. All the group members strongly fought these challenge and take the turn to the front.
Especially the internet connection becomes the challenge face in this second semester project.
The challenge of our system is deeply understand how the organization activities performed its
task and changing these to our system and due to complexity of their work understanding their
process was so difficult. And we recommend that select non-complex and easily understudied
process to the system. Our documentation will help to the next developers greatly. Moreover,
there are some minor features that we cannot implement on top of this web-application. For
example, full compatibility of the system. So we recommend the next developers to perform their
action from this angle.
91
6.3 Reference
[1].Url for XAMPP (Apache, MySql and php) https://www.apachefriends.org/download.html
Last accessed on January 10, 2019
[2].Url for Notepad++ http://www.notepad plus plus.org.
[3].Grady Brooch, James Rumbaugh, Ivar Jacobson,” The Unified Modeling Language User
guide”.
[4].Books Chapter: Stephen R.Schach. “Software Life-Cycle Models” in Object-Oriented and

Classical Software Engineering, 8th edition, Lora Neyens, Ed.NewYork:McGraw-HillInc, 1221
Avenue of the Americas, 2011, pp.53-55.
[5].books:StephenR.Schach.Object-Oriented and Classical Software Engineering. New York:

The McGraw-Hill, 2011.
92

Final Project

Uploaded by

Copyright:

Available Formats

You might also like

Final Project

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Project

Uploaded by

Copyright:

Available Formats

AMBO UNIVERSITY

AMBO INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE

TITLE: WEB BASED AGRICULTURAL DATA COLLECTION SYSTEM

A Project Submitted to Computer Science Department for the Partial Fulfillment of

1.Deribew Beko…………………………………………………….. BRT/2280/08

7. Talile Desalegn..... .......................................................................BRT/2241/08

Advisors Name: MSc.Tadele Degefa Submission Date June 17/2019 GC

Ambo University Academic Education Evaluation System

Advisor name: ____________________signature______________date_____________________

ADCOWs Agricultural Data Collectors Offices Workers

1.1 Background of Organization.................................................................................................1

1.2 Statement of the Problem...........................................................................................................1

1.3.1 General objective................................................................................................................2

1.3.2 Specific objective................................................................................................................2

1.4 Scope of the Project...................................................................................................................3

1.5 Significance of the Project.........................................................................................................3

1.5.1 Target beneficiaries of the system......................................................................................4

1.6 Methodology of the Project.......................................................................................................4

1.6.1 Data sources........................................................................................................................4

1.6.2 Fact Finding Techniques.....................................................................................................4

1.6.3 Systems Analysis and Design (approach)...........................................................................5

1.6.4 Development Tools.............................................................................................................7

1.6.5 Testing procedure...............................................................................................................8

1.6.5 Proposed Implementation Method......................................................................................8

1.7 Limitation of the Project............................................................................................................9

1.8 Risk and Contingencies.............................................................................................................9

1.9 Assumptions and Constraint....................................................................................................10

2.1 Description of the current system........................................................................................12

2.1.1 Players in the Existing System.....................................................................................12

2.1.2 Functions/activities in the existing system...................................................................14

2.1.3 Business rules...............................................................................................................14

2.1.4 Report generated in the existing system.......................................................................14

2.1.5 Bottlenecks of the existing system...............................................................................14

2.2 Practices to be preserved.....................................................................................................15

2.2 proposed system...................................................................................................................16

2.3.1 Team composition........................................................................................................17

2.3.2 Feasibility study............................................................................................................18

2.3.3 Requirements of the Proposed System.........................................................................20

3.2 System Requirement Specifications....................................................................................24

3.2.1 Use case diagram..........................................................................................................25

3.2.2 Object Model................................................................................................................39

3.2.3 Dynamic Model............................................................................................................41

3.2.4 User interface modeling................................................................................................62

Proposed System Design...........................................................................................................64

4.1.1 Purpose of the System..................................................................................................64

4.1.2 Design Goals.................................................................................................................65

4.2 Current Software Architecture.............................................................................................66

4.3 System Architecture............................................................................................................66

4.3.2 Sub system decomposition...........................................................................................67

4.3.3 Hardware/Software Mapping.......................................................................................68

4.3.4 Persistent Data Management.......................................................................................71

4.3.5 Access control...............................................................................................................71

4.3.6 Global Software control................................................................................................72

4.3.7 Boundary condition......................................................................................................72

Implementation and Testing......................................................................................................74

5.1.1 Final Testing Of the System.........................................................................................84

5.1.2 Hardware Software Acquisitions..................................................................................84

5.1.3 User Manual Preparation.............................................................................................84

Advisor name: signaturedate___