FUND MANAGEMENT SYSTEM FOR MEKEDONIA

ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

A Senior Project documentation Submitted to Debre Berhan University in Partial Fulfilment

of the Requirement for the Degree of Bachelor of Science in Information System
By: Group-4
GROUP MEMBERS IDNO

1. YOSEF GORFU……………………….....098/06

2. GETNET ATILAW ……………………...070/06

3. DAGNE TSEGAW……………………….066/06

4. AMANUEL GELALCHA………………..056/06

5. MINTIWAB GIRMA…………………….082/06

Supervised by: instructor Chali Abraham

Department: Information system

College of Computing, Department of Information System

Debre Berhan University, Debre Berhan, Ethiopia

June 2017

i
Approval Letter
The Project is our own and has not been presented for a degree in any other university.
Name Signature
1, Yosef Gorfu ___________

2, Getnet Atilaw ___________

3, Dagne Tsegaw ___________

4, Amanuel Gelalcha ___________

5, Mintwab Girma ___________

Name of program coordinator: ____________________________

Signature: ___________________________
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope and quality,
as a project for the degree of Bachelor of Science in information system.
Name of Advisor: ___________________________
Signature: ___________________________
Examining committee members name and signature
1. Chairman _____________________ _______________

2. Examiner 1 ____________________ _______________

3. Examiner 2 ____________________ _______________

It is approved that this project has been written in compliance with the formatting rules laid down by the
Computing College of Debre Berhan University.

ii
Acknowledgement
First of all, we would like to thank our God, who gives us love, patience, healthy, wisdom and ability to walk
through all the problems and obstacles during the period of our study. Then we would like to thank our advisor,
instructor Chali Abraham for his constructive opinion and willingness to participate in each part of our project
and her effective direction, assistance and guidance for the accomplishing of this project.

iii
Contents
1.1 Introduction ............................................................................................................................................................... 1
1.2 Background Information of the Organization ................................................................................................... 1
1.2.1 Vision of Mekedonia .......................................................................................................................................... 2
1.2.2 Mission of Mekedonia ........................................................................................................................................ 2
1.3 Background of the Project ....................................................................................................................................... 2
1.4 Problem Statement.................................................................................................................................................... 2
1.5 Team Composition .................................................................................................................................................... 3
1.6 Objectives of the Project........................................................................................................................................... 3
1.6.1 General Objective .............................................................................................................................................. 3
1.6.2 Specific Objectives ............................................................................................................................................. 3
1.7 Scope and Limitation of the Project .......................................................................................................................... 3
1.8 Significance of the Project ........................................................................................................................................ 4
1.9 Target Beneficiaries of The project ......................................................................................................................... 4
1.10 Methodology of the Project .................................................................................................................................... 5
1.10.1 Data Collection Methods ................................................................................................................................. 5
1.10.2 System Analysis and Design Methodology..................................................................................................... 5
1.10.3 System Development Environment ................................................................................................................ 6
1.10.4 Testing Procedures........................................................................................................................................... 6
2.1 Introduction of the Existing System ........................................................................................................................ 7
2.2 Players in the Existing System ................................................................................................................................. 7
2.3 Major Function in the Existing System ................................................................................................................... 8
2.4 Business Rules ........................................................................................................................................................... 8
2.5 Report Generated in the Existing System ............................................................................................................... 9
2.6 Forms and Other Documents of the Existing System ............................................................................................ 9
2.7 Bottlenecks of the Existing System ........................................................................................................................ 12
2.8 Practices to be preserved ........................................................................................................................................ 12
2.9 Proposed Solution for the new System .................................................................................................................. 12
2.10 Requirements of the Proposed System ................................................................................................................ 13
2.10.1 Functional Requirement ................................................................................................................................ 13
2.10.2 Non-Functional Requirement ....................................................................................................................... 14
3.1 System Models ......................................................................................................................................................... 15
3.1.1 Scenarios ........................................................................................................................................................... 15
3.1.2 Use case Model ................................................................................................................................................. 15
3.1.3 Use Case Description ....................................................................................................................................... 17
3.1.4 Object Model .................................................................................................................................................... 27
3.1.4.1 Data Dictionary ......................................................................................................................................... 28
3.1.4.2 Analysis Level Class Diagram (Conceptual Modeling) ......................................................................... 30
3.2 Dynamic Model ....................................................................................................................................................... 31

iv
 3.2.1 Sequence Diagram............................................................................................................................................ 31
3.2.2 Activity Diagram .............................................................................................................................................. 36
3.2.3 State Chart Diagram ........................................................................................................................................ 41
3.2.4 User Interface Prototype ................................................................................................................................. 42
3.2.5 Supplementary Specifications ......................................................................................................................... 46
4.1 Introduction ............................................................................................................................................................. 47
4.1.1 Purpose of the System ...................................................................................................................................... 47
4.1.2 Design Goals ..................................................................................................................................................... 47
4.2 Current Software Architecture .............................................................................................................................. 48
4.3 Proposed Software Architecture............................................................................................................................ 48
4.3.1 Overview ........................................................................................................................................................... 48
4.3.2 Subsystem decomposition ................................................................................................................................ 48
4.3.3 Hardware/software mapping .......................................................................................................................... 49
4.3.4 Persistent data management ........................................................................................................................... 49
4.3.4.1 Mapping ..................................................................................................................................................... 50
4.3.4.2 Database Design ........................................................................................................................................ 50
4.3.5 Access control and security ............................................................................................................................. 51
4.3.6 Global software control ................................................................................................................................... 52
4.3.7 Boundary conditions ........................................................................................................................................ 52
4.4 Subsystem services .................................................................................................................................................. 53
4.5 Component Diagram............................................................................................................................................... 54
4.6 Deployment Diagram .............................................................................................................................................. 55
5.1 Introduction ............................................................................................................................................................. 56
5.2 Object design trade-offs.......................................................................................................................................... 56
5.3 Interface documentation guidelines ...................................................................................................................... 57
5.4 packages ................................................................................................................................................................... 57
5.5 class interfaces ......................................................................................................................................................... 58
6.1 Introduction ............................................................................................................................................................. 59
6.2 Final Testing of the system ..................................................................................................................................... 59
6.3 Hardware software acquisitions ............................................................................................................................ 59
6.4 User manual preparation ....................................................................................................................................... 60
6.5 Training ................................................................................................................................................................... 60
6.6 Installation process ................................................................................................................................................. 61
6.7 Start-up strategies ................................................................................................................................................... 76
7.1 Conclusions .............................................................................................................................................................. 77
7.2 Recommendations ................................................................................................................................................... 78
Appendix ........................................................................................................................................................................ 79
References ...................................................................................................................................................................... 80

v
List of figures

Figure 2.1 form to make donation via dashen bank………………………………………...……9

Figure 2.2 form to make donation via CBE……….……………………………………….……10

Figure 2.3 way of advertising money and material fund collecting………………………..……10

Figure 2.4 sample way of item donation………………………………………………………...11

Figure 2.5 sample way for collecting money…………………………………………………....11

Figure 2.6 way of advertising to collect items………………………………………………..…11

Figure 3.1 Use case description for the proposed system……………………………………….16

Figure 3.2 Conceptual class diagram………………………………………………………........31

Figure 3.3 Sequence diagram for login………………………………………………………….32

Figure 3.4 Sequence diagram for registration…………………………………………………...32

Figure 3.5 Sequence diagram for add advertisement………….………………………...………33

Figure 3.6 Sequence diagram for send notification..............................................................…....33

Figure 3.7 Sequence diagram for donate money………………………………………………..34

Figure 3.8 Sequence diagram for donate material……………………………………...………34

Figure 3.9 Sequence diagram for manage user………………………………………...………35

Figure 3.10 Sequence diagram for change profile. ……………………………………...…….35

Figure 3.11 Sequence diagram for apply for help. ………………………………….……...…36

Figure 3.12 Sequence diagram for membership entry. ………………………………….....…36

Figure 3.13 Activity diagram for login……………………………………………………….37

Figure 3.14 Activity diagram for advertisement……………………………………………...37

Figure 3.15 Activity diagram for donate material……………………………………………38

Figure 3.16 Activity diagram for donate money. ……………………………………………38

Figure 3.17 Activity diagram for send notification………………………………………….39

Figure 3.18 Activity diagram for registration………………………………………… ……39

Figure 3.19 Activity diagram for membership entry……..…………………………………40

vi
Figure 3.20 Activity diagram for apply help………………………………………..……. 40

Figure 3.21 State chart diagram for login. ………………………………………..……….41

Figure 3.22 State chart diagram for registration…………………………………...………41

Figure 3.23 User interface Flow Design…………………………………………...………42

Figure 3.24 Login interface prototype..........................................................................…....43

Figure 3.25 Register/sign up interface prototype…………………………………………..43

Figure 3.26 Membership form interface prototype…………………………………...……44

Figure 3.27 Money donation form (for Members) interface prototype……………...…….44

Figure 3.28 Material donation form interface prototype………………………………......45

Figure 3.29 Message sending form interface prototype………………………………...…45

Figure 3.30 Apply for Help (for needy people) form interface prototype……………...…46

Figure 4.1 Software design architecture …………………………………………….....…48

Figure 4.2 Subsystem decompositions…………………………………………………....49

Figure 4.3 Mapping of design of class and database…………………….…………….…50

Figure 4.4 Database design…………………………….…………………………….…..51

Figure 4.5 Access control table………………………………………………………….52

Figure 4.6 Component diagram for new system………………………………………...54

Figure 4.7 Deployment diagram for the new system……………………………………55

Figure 6.1 homepage user interface design……………………………………………...61

Figure 6.2 User interface design for sign up/registering users…………………………..61

Figure 6.3 User interface design for login into the system………………………………62

Figure 6.4 User interface design for donor page………………………………….…..….62

Figure 6.5 User interface design for view notifications…………….…………………….62

Figure 6.6 User interface design for human membership………………………………...63

Figure 6.7 User interface design for organizational membership………………………...63

Figure 6.8 User interface design for material donation…………………………………...64

Figure 6.9 User interface design for member donors (through bank) ……………...…….64

vii
Figure 6.10 User interface design for non-member donor (through bank) ……………….65

Figure 6.11 User interface design for direct notification generates from the system……..65

Figure 6.12 User interface design for controlling users by the manager………………….66

Figure 6.13 User interface design for sending SMS for needy people approval………….66

Figure 6.14 User interface design for donated material delivery check-up……………….67

Figure 6.15 User interface design for showing Mekedonia balance……………………....67

Figure 6.16 User interface design for list of donated material……………………….…....68

Figure 6.17 User interface design for generated receipt for donors after donation….…….68

Figure 6.18 User interface design for generating report by option selection….……….….69

Figure 6.19 User interface design for filling help form for needy people………………....69

Figure 6.20 User interface design for money donation (through pay pal)...……………….70

Figure 6.21 an error message for pay pal money transaction……………..…………….….70

viii
List of Tables

Table 1.1 team composition………………………………………….……………..……3

Table 1.2 hardware tools…………………………………………………………………6

Table 3.1 Use case description about Login………………………….……………....…18

Table 3.2 Use case description about Logout………………………….……………..…18

Table 3.3 Use case description about Sign up.………………………….………………19

Table 3.4 Use case description about view notification………………….……………..20

Table 3.5 Use case description about membership…….….……………….……………20

Table 3.6 Use case description about donate money……………………………….…...21

Table 3.7 Use case description about donate material……………………………….…22

Table 3.8 Use case description about Change profile…………………………….…….23

Table 3.9 Use case description about Add advertisement……………………….……..24

Table 3.10 Use case description about Manage user……………………………..…….25

Table 3.11 Use case description about Send notification………………………….…...26

Table 3.12 Use case description about apply for help…………………………….....…27

Table 3.13 Data Dictionary for apply for help (for needy people) table…………….....28

Table 3.14 Data Dictionary for member human table……………………………….…29

Table 3.15 Data Dictionary for member organization table……………………….…...29

Table 3.16 Data Dictionary for donated material table………………………….……..30

ix
Abbreviations

Pcs: Personnel Computers

HTML: Hypertext Mark-up Language

SMS: Short Messaging Service

HTTP: Hypertext Transfer Protocol

PHP: Hypertext pre-processor

MySQL: My Structured Query Language

UC: Use Case

DVD/CD: Digital Video Disc/Compact Disk

USB: Universal Serial Bus

UML: Unified Modelling Language

OOP: Object Oriented Programming

URL: Uniform Resource Locator

ODD: Object Design Diagram

UI: User Interface

x
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER ONE: INTRODUCTION OF WHOLE PROJECT

PROCESS

1.1 Introduction
Funds management is the management of the cash flow of a governmental or non-governmental financial
institution for the purpose of generating profit for itself or providing profit for others. In our country there are
many profit and non-profit organizations are found for different purpose, from one of those non-profit
organizations, Mekedonia is the most well-known. Mekedonia is a non-profit organization that are found for
the purpose of helping elderly and mentally disabled peoples in Ethiopia. Mekedonia works on providing a
mechanisms to get money and material from donors in order to support the needy peoples. Right now
Mekedonia works on registering needy peoples, providing an agreement with members and creating a
promotional advertisement related with collecting money. All of those functions are done without dynamic
website. Because of this our project team select the title “fund management system for Mekedonia elderly and
mentally disabled people help organization”, the funding process of money takes place through pay pal sand
box, which means the donor must create an account on the pay pal developer under sandbox option.

1.2 Background Information of the Organization

Mekedonia is a non-profit organization which is a safe and loving home for the Elderly and mentally disabled
compatriots in Ethiopia’s capital city; Addis Ababa. It was started by Benyam Belete in September, 2011 with
30 elderly and mentally ill people. The center is based at Benyam’s childhood home. Mekedonia has only
been serving its residents for the past four years but in this time it has grown to house and care for 850
residents. Mekedonia has become hope for the poor, the friendless and the sick in Ethiopia. By now Mekedonia
is home to 375 mentally disabled people, 260 elders and 215 bed ridden who use diapers and need constant
care 24/7. The residents of Mekedonia Home for the Elderly and Mentally Disabled include people who suffer
from severe mental illness, HIV patients, cancer patients, those who are terminally and chronically ill people
and bed ridden people who need constant care and attention in toileting, moving, eating, and bathing in other
activities of daily living. These people were once homeless but now they live in a decent house; they were
once hungry; but now they are fed; they were once naked; but now they are clothed; they were once hopeless
and desperate but now they live rich lives; they were once physically and sexually abused; but now they live
in a safe environment; they were once sick but now they receive proper medical care and compassionate
personal care. In short those who lived under the shadow of death have now seen light.

1
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

1.2.1 Vision of Mekedonia

Mekedonia Home for the Elderly and Mentally Disabled envisions Ethiopia where all the elderly and
mentally disabled have equal access and opportunity to basic needs of life.

1.2.2 Mission of Mekedonia

Mekedonia Home for the Elderly and Mentally Disabled is a non-profit organization dedicated to provide
food, clothing, housing, medical care and companionship to the most helpless, neglected and mentally ill
people.

1.3 Background of the Project

Ethiopia is one of the developing country in Africa through this process there are different obstacles that our
community face among those lack of funds like economical financial and others are included, in the context
of this problem funding organizations may not got the chance to raise the needed funds for elder and disable
peoples .Mekedonia is one of the funding organization that is established to help elder and mental disabled
people in Ethiopia, especially in Addis Ababa. But the organization face different problems sins it is lack in
having a dynamic funding website, advertisements, recording donors and needy people our project focused on
providing an efficient way funding mechanism to Mekedonia organization by using pay pal method of money
transfer, material donation.

1.4 Problem Statement

 Funding process is difficult due to lack of central management and control.
 Difficult to find people who want to donate, at the right time and place.
 Registering the needy peoples are done through manually.
 Most of the time funding method is made at different organizations, hotels schools universities and
telethon programs. This methods make the funding process difficult and hard to manipulate.
 There is no way of registering peoples who donate as a membership.
 Funding method of advertisement is also made through banners, postures, flayer advertisement,
broadcasting via radios and televisions. Those methods can also need much more financially be strong
and more time consuming.
 There is no secured way of keeping information about the donors and the needy peoples in that
organization, this may lead to lose of information.
 When someone want to help equipment’s or items to the organization, the way to help is so tedious
and too much time consume, Because no time based logistics management ( date of destination, what
type of is the item? and more information about that item).

2
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

1.5 Team Composition

The project team consist of 5 members, one team leader, one vice Leader, one secretary, and 2 members.
Decision on problem and approach are made by group agreement, which is much better than individual
decision.

No. Name Role Responsibility

1. Yosef Gorfu Leader Requirement analysis, System Design, Implementation &
Testing
2. Getnet Atilaw Vice Leader Data gathering, Requirement analysis & Testing
3. Amanuel Gelalcha Secretory System Design ,Implementation & Testing
4. Dagne Tsegaw Member Data gathering, Requirement analysis & Testing
5. Mntiwab Girma Member Data gathering & Testing
Table 1.1 team composition

1.6 Objectives of the Project

1.6.1 General Objective
 The general objective of this project is to develop a web based funding management system for
Mekedonia elderly and mentally disabled people help organization.

1.6.2 Specific Objectives

 Identify the problem in the current system.
 Suggest alternative solutions in order to address the current problem.
 Understand functional and non-functional requirements of the system.
 Provide an efficient way of funding management via financially or equipment.
 To develop effective and efficient funding management system.

1.7 Scope and Limitation of the Project

Scope of the Project

The scope of this project is providing fund for Mekedonia elderly and mentally disabled people, in terms of
financially and materials, including the following activities.
 Registering donors who want to fund for the organization and needy people who need help.
 Providing an advertisement about fund collections.
 Providing logistic information about those materials, which means full information about the items.
 Generating general User information related to fund.
 Providing a membership form for donors after sign up into the system.

3
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

But the system did not include the following tasks because time and cost: -

 Not concerned with controlling the day to day activities of the needy peoples in the organization.
Which means it does not interacting with health status check-up of each needy people.
 Not concerned with to setup a schedule for employees and volunteers, in order to help the elders and
mentally disabled peoples in that organization either physically or mentally.

Limitation of the study

 We now that Banks have not an interest to share their databases, because of this our financial funding
system is not about sharing real World Bank databases, rather it concerned with pay pal simulator of
creation an account and transfer of money and creating a bank database inside the computer server.
 The pay pal way of funding process is an optional, because most of the time it is not worked specially
for Ethiopia.

1.8 Significance of the Project

 For the donor’s
 Easily perform the funding process without any obstacles (no more time consume).
 The donors can gets more information about the organization, which includes the location and
contact information.
 Those donors can get more conscience satisfaction, when they donate to the organization.
 For the needy people
 When more funds are donated, the needy people gets a better life style and health conditions.
 For the rest of the society
 The society will have a better understanding and think positively about the elderly and mentally
disabled peoples.
 Be motivated to donate money and useful materials.

1.9 Target Beneficiaries of The project

The main target beneficiaries of this fund management system for Mekedonia are:-
 Needy peoples who live in the organization
 The organization itself, which means they gets more fund donors after the software developed.

4
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

1.10 Methodology of the Project

1.10.1 Data Collection Methods

The methods that facilitate us to capture information about requested system is called Methodology Starting
from proposed system we gathered information and data through different mechanisms.

Interview

This is one of the methods used for the collection of data in which the project developers have the chance
of asking different questions. By using different asking question mechanisms like via by email and calling.

Document analysis

This method of data collecting is analysing the document prepared in the existing system. We analysed
different documents like forms and report samples in the existing system.

Observation

We use direct and to look the manual working mechanisms and also we use indirect observation, cause of
short period of time that we have and maximum transportation cost, however by searching and finding
something about Mekedonia on the internet we observe some information.

1.10.2 System Analysis and Design Methodology

 For our system analysis and design steps, we use Object oriented software development methodology,
which uses Unified modelling language. Because of the following features.

Faster Development: OOD has long been touted as leading to faster development. Many of the claims of
potentially reduced development time are correct in principle, if a bit overstated.

Reuse of Previous work: This is the benefit cited most commonly in literature, particularly in business
periodicals. OOD produces software modules that can be plugged into one another, which allows creation
of new programs. However, such reuse does not come easily. It takes planning and investment.

Increased Quality: Increases in quality are largely a by-product of this program reuse. If 90% of a new
application consists of proven, existing components, then only the remaining 10% of the code has to be
tested from scratch. That observation implies an order-of-magnitude reduction in defects.

Client/Server Applications: By their very nature, client/server applications involve transmission of

messages back and forth over a network, and the object-message paradigm of OOD meshes well with the
physical and conceptual architecture of client/server applications.

5
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Better Mapping to the Problem Domain: This is a clear winner for OOD, particularly when the project
maps to the real world. Whether objects represent customers, machinery, banks, sensors or pieces of paper,
they can provide a clean, self-contained implication which fits naturally into human thought processes.

1.10.3 System Development Environment

Hardware tools

Tools Quantity Purpose

Pcs 3(1PCs,2HP desktop) Used for Designing the website, data entering, manipulating data.

Printer 1 To convert softcopy into hardcopy.

CD/DVD 3 To store temporary and necessary data.

USB flash 2 (8GB and 16GB) To transfer data from pc to pc.

Table 1.2 hardware tools

Software tools

 Microsoft word 2013:-for documenting the corresponding deliverables associated with the project.
 Microsoft power point 2013:- used to present our documentation project.
 PHP:- for the software developing
 Notepad++:- for writing the code.
 Java script:-associated with PHP.
 Edraw max: - For designing UML diagrams associated with the project.
 Xampp server: - for designing the database.

1.10.4 Testing Procedures

Testing is a trial experience in which the deliverables of the project are checked with
acceptable Standards in the project. We used unit testing, and system testing to test the
correctness of each Module and the compiled program.
 Unit Testing
We use unit testing to test the individual functional component of our system before testing
the whole system once.
 System Testing
For verifying as the whole system is functioning in integrated manner with respect to the goal
of our system.

6
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER TWO: DESCRIPTION OF THE EXISTING SYSTEM

2.1 Introduction of the Existing System

Existing system means a system which defines the current working method of one organization. The current
way of Mekedonia organization funding mechanism is using bank account number from Dashen bank and
Commercial Bank of Ethiopia, and cash mechanisms (by physical contact). Also to record the needy people
information currently they use manual or paper based registration.

2.2 Players in the Existing System

The current system of Mekedonia organization have two characteristics or ways of doing work.

 On the website and

 The manual funding methods (which includes money and material donation).
 The website: - The current website of Mekedonia have the following players.
1. Publisher: -this player posts and publishes different news and information’s related with Mekedonia
organization activities.
2. End user: - donors or any other user can gives suggestion or comment, read news, read volunteer and
needy people comments, show other sensitive information about Mekedonia,: -such as to know the
Mekedonia bank account number with branch location in order to make aid or fund and contact
information.
 Manual funding methods: -currently Mekedonia have the following players that are involved in the
manual funding mechanisms.
1. Donor: - anyone who are an interest to donate money by using Commercial bank of Ethiopia (account
number: -1000067118948 swift code: -CBETETAA) and Dashen bank (account number: -
0025658566001 swift code: - DASHETA), also donor can also fund materials by using filling paper
form and signature.
2. Casher: - an employee who are worked in the bank for transferring money from donor to Mekedonia
bank account. Or a volunteer who are worked in the Mekedonia organization, for receiving the money
in terms of cash from the donors.
3. Manager: -who control the casher’s activity and check the funded money or material to the
organization, the manager of the organization also agree with other parties either freely or financially
to advertise via radio, television, flying papers or banners and to make telethon programs.

7
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

2.3 Major Function in the Existing System

The following are the major functionalities of the existing Mekedonia website.

1. The current system of the Mekedonia website publish news, when new things are done in the
organization such as: - when famous peoples are donate money to the organization, when materials or
items are supported to Mekedonia from different organizations and from other parties.
2. The current system of the Mekedonia website display an information about the organization mission,
values and contact information’s and their bank account information.
3. The current system of the Mekedonia website have a photo gallery about the needy peoples.
4. The current system of the Mekedonia website have a mechanism for anyone a way of giving comments
about the Mekedonia organization services.
5. Currently Mekedonia uses different methods of money and material collecting ways of advertisement,
such as radio and TV advertisements, banners and flying papers advertisement and telethon programs.
6. Anyone who want to donate, it uses two mechanisms these are either by cash (physically) or going to
those banks and filling money transfer form (Commercial bank of Ethiopia or Dashen bank). Also for
material funding mechanism, the donors can fill their own form for about the material they want to
donate.

2.4 Business Rules

Business rule of the existing system
The current system of Mekedonia organization have the following business rules.
Business rule 1: Anyone can get the chance to help needy people privately outside the organization.

Business rule 2: When donor want to donate money via bank, donor must have either a dashen bank or
commercial bank of Ethiopia bank account in the current system.

Business rule 3: to get a help needy peoples must be who lives in a street and nothing to do. Additionally to
get a help needy people must be either a disabled people or mentally disabled people. The way of verifying
needy people is applying physical and mental check-up, including age consideration.

Business rule of the proposed system

Business rule 1: the proposed system is developed using English language, so user needs an English
language skill to interact with the system.
Business rule 2: to make money donations donors should have a bank account in bank database.
Business rule 3: to get SMS service, users should submit correct phone number during donation process.

8
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Business rule 4: The new developed system supports one way of funding process at a time, which means
donors cannot fund money and material at the same time, but they can donate one by one.
Business rule 5: The system is connection oriented, which means to operate the new developed system it needs
an internet connection.

2.5 Report Generated in the Existing System

Currently Mekedonia organization have a report generated mechanism about the registered needy people
information, which includes how money elders and mentally disabled peoples are there? And for those how
much amount of money per day is needed?

2.6 Forms and Other Documents of the Existing System

Figure 2.1 form to make donation via dashen bank

9
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 2.2 form to make donation via commercial bank of Ethiopia

Figure 2.3 way of advertising money and material fund collecting.

10
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 2.4 sample way of item donation

Figure 2.5 sample way for collecting money

Figure 2.6 way of advertising to collect items

11
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

2.7 Bottlenecks of the Existing System

 The donating process is via bank, which means usually donors they donate money by going to banks
physically in order by full filling money transfer form, otherwise by cash or check physically.
 Additionally the current system haven’t any mechanisms or ways to fund materials online.
 The current system of the Mekedonia website does not support any mechanism to advertise different
ways of money and materials collecting methods from donors and organization via online.
 The process of recording or registering the needy people’s information from different areas are done
through manually or paper based.
 The current system of the Mekedonia website does not have an online registration of peoples who want
to fund money or material to the organization.

2.8 Practices to be preserved

From the current system of Mekedonia donating via dashen bank and commercial bank of Ethiopia are
preserved and continued inside our pay pal method donation process because our fund management system is
another method of funding mechanism.

2.9 Proposed Solution for the new System

 The new proposed system register new donors and manage the existing one: - peoples who are willing
to donate must be registered and the existing ones are manage the activities, which means anyone who
want to fund to Mekedonia, must be registered for the security purpose and then he or she can manage
their page after registering process by login to their pages.
 The new proposed system register peoples who need help: -this functionality of the system deal with
recording or registering people who need support, either elderly peoples or mentally disabled peoples.
Which means those peoples who need help can tell us about their problems, in order to get services
from different parts of the country.
 The new proposed system allow users to fill membership forms: - this functionalities deal with
recording peoples who want to donate as a member for Mekedonia
 The new proposed system allows to provide an advertisement: - this functionalities deals with creating
and announcing advertisements, this advertisement are basically connected with providing a way to
attract donors in order to fund for our organization in terms of money or material.
 The new proposed system generate general information about donors and needy peoples: - this
functionalities deals with allows to the system manger/administrator to show the all over information,
related with who register into the system? Who donate money or material to the organization in which
day, year, month and other related information?

12
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

 The new proposed system allows to provide logistic management: -describes or includes all
information about the material, which means detail description about each and every materials which
are prepared to be donated.

2.10 Requirements of the Proposed System

In this chapter we studied the existing system deeply, when we studied the existing system we gave emphasis
for here under listed questions:

 How the existing system is working?

 What kind of method they have for donors in order to fund?

After studying the existing system, we also determined the requirement or the feature that must be included
in the proposed system. Furthermore by analysing the current system, we could also estimate how the propose
system solve the setbacks of the existing system.

2.10.1 Functional Requirement

Functional requirement is a description of activities and services that a system must provide. It is clear that
the new system have to perform the funding management tasks. The following are the functional requirements
that must be fulfilled by our system.

1. Registering of donor and people

The system allows people and organization who want to donate, to be registered for the security purpose, in
order to make a fund money or material after login into the system. And the system allows peoples who need
help in terms of food, clothes and medical treatment are given their full information after login into the system,
for getting those services after qualifying, either the registered needy people are a needy one or not.

2. donate money

The system allows donors to make a fund in terms of money based on their financial capacity, after login into
the system. Those donors can aid or fund as a member or without membership. The funding process of money
takes place at pay pal sandbox.

3. donate material

The system allows donor to fund materials or item that are essential for the needy people such as: - food,
clothes and other material. All this material donation process is also done after the donor login into the system.
During the funding material process logistic related information of each items are included before donating.

4. Generate user information

13
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

The system allows for the manager of the system to manage the user in order view the overall information
about the whole processes, delete user information.

5. Sending a notification

The system allows for the manager of the system to send a notification for donors that are registered as a
member, in order to remember when the donating month or year are too close.

6. Provide membership form

The system allows for anyone who want to donate as a member for the Mekedonia organization, after login
into the system.

2.10.2 Non-Functional Requirement

Non-functional requirement describes invisible aspects of the system that are not directly related to the system.
Unlike functional requirement the non-functional requirement deals with additional quality of the system such
as:

 User interface: The system provides user interfaces that are compatible with windows platform.
 Reliability: The system consistently performs its intended function .e.g. the important functions are
validated. So the system is reliable.
 Efficiency: The system is efficient based on the concept of resource consumption. E.g. it only needs a
computer that has a browser to access the system.
 Error handling: Our system handles error by showing the message” invalid input” when the user enter
invalid input.
 Integrity/security: only manger has a privilege to access the database but every user cannot perform
any change on the database. Only authorized users can access the system based on their privilege.
 Easy to use: our system is user friendly and also compatible with modern browser.
 Service: The website is easily understandable by customers who know how to use the internet. And
customers can be located anywhere having internet access. The system lets the users give a feedback.
 Availability: The system is available 24/7 to everyone.

14
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER THREE: SYSTEM ANALYSIS

3.1 System Models

System modelling is a technique to express, visualize, analyse and transform the architecture of a system.
Here, our proposed system may consist of software components, hardware components, or both and the
connections between these components. A system model is then a skeletal model of the system that help as to
model our function of the system and it is used to ensure that a developing piece of software evolves in a
consistent manner and that the task of integrating software components is simplified.

In our project we used unified modelling language to model our system. The Unified Modelling Language
(UML) is a general-purpose modelling language in the field of software engineering, which is designed to
provide a standard way to visualize the design of a system. There are different model diagram in UML that
we used to model the system.

3.1.1 Scenarios
Scenario is a detailed description of each and every use case elements that are designed for the new proposed
system. Scenario includes use case id, use case name, use case description, flow action, pre-condition, post-
condition and actors that involve in the use case function.

3.1.2 Use case Model

Our Use case describes the behaviour of the proposed system as seen from an actor’s point view. A use case
describes a function provided by the system as a set of events that yield a visible result for the actors. In the
analysis phase they represent the functionality of the system. In our use case modelling we included collection
of all actors and all use cases.

15
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.1 Use case description for the proposed system

Use case identification

Identifying the activities that are mainly performed on the proposed system is the basic thing in analysing a
new system. The following use cases have been identified from the system specification.
 Login
 Logout
 Sign up
 View notification
 Fill membership
 donate money
 donate material
 change profile
 Add advertisement
 Manage user
 Send notification

16
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

 Apply for help

Actor identification

The purpose of actor analysis is to identify all of the actors that interact with the system. An actor has a role
in that interacting with the system. The actors that interact with the system are:-

 Donor: - anyone who want to fund money or material to the organization. Before login to the system
he or she must be a registered one (sign up), after then he/she can perform the following activities such
as: - filling membership form, donate money, donate material, change profile, view notification and
finally logout from the system.
 Manager: - is who interact in the proposed system that has full control over the system. After login to
the system whose responsibility is: - add advertisement, view user information, delete user
information, send notification to users, change profile and finally logout from the system.
 Needy people Benefactor: - perform an activity like helping needy people to fill apply for help or
registration to get help and view notification.

3.1.3 Use Case Description

It is a sequence event that describes what the proposed system will develop and how it interacts with the
environment mainly. This section describes the most important activates that the actors of Fund management
system for Mekedonia Elderly and mentally disabled people help organization do experience to make use of
the system.

Use case name: Login

UC_ID: UC_01
Actor: Manager, Donor and Needy people benefactor.
Description: This use case is used to ensure security in system usage.
Precondition: Manager, Donor and Needy people benefactor must have at
least username and password
Main course of action: Step 1: user has to activate the system and click it on login
button.
Step 2: The system responses by displaying the login interface
and allow the user to inter the user name and password.
Step 3: user fill his or her username and password.
Step 4: he/she clicks login/sign in button.
Step 5: The system verifies username and Password.

17
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Step 6: the system displays “access granted welcome to your

page”.
Step 7: user can get authentication and access the system.
Step 8: Use case ends.
Post condition: Manager, Donor and Needy people benefactor can get access to
the system according to their predefined system privilege and
finally he/she logout or turn off the page.
Table 3.1 Use case description about Login
Alternative course of action for Login
A5: If users enters wrong username and / or password, the system displays “Login Failed please check your
user name and password / or required field must be filled”.

Use case name: Logout

UC_ID: UC_02

Actor: Manager, Donor and Needy people benefactor.

Description: this use case allows to logout and back to the login/main page
Precondition: the Manager, Donor and Needy people benefactor should be
login to the system and wants to log out
Main course of action: Step 1: The user click logout button.
Step 2: The system returns to login/ main page.
Step 3: use case ends.
Post condition: The Manager, Donor and Needy people benefactor log out from
their privileges and go back to home page.
Table 3.2 Use case description about Logout

Use case name: Sign up

UC_ID: UC_03
Actor: Donor and needy people benefactor.
Description: This use case is used to ensure security in system usage
before/in order login into the system.
Precondition: 1. Launch the system.
2. Anyone who have an interest to fund money or material

18
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

3. People who have a problem that does not have the ability
to get specific needs.
Main course of action: Step 1: Donor and needy people benefactor has to activate the
system and clicks on Sign up.
Step 2: The system responses by displaying the registration
options.
Step 3: Donor and needy people benefactor can choose the
option and fill the form.
Step 4: he/she clicks submit button.
Step 5: The system verifies all the fields of the form and check
the values.
Step 6: the system displays “registration success, welcome to
our site”.
Step 7: Use case ends.
Post condition: 1.Can login into the system
2.Can donate money or material and manage their pages
based on their privilege after login.
Table 3.3 Use case description about Sign up
Alternative course of action for sign up
A5: If Donor or Needy people not fill all the fields or missed some textboxes the system act as “a required
field must be filled”.

Use case name: View notification

UC_ID: UC_04
Actor: Donor and needy people benefactor.
Description: This use case is used to ensure that the donor or needy people have
the right to show new notification.
Precondition: Donor and needy people benefactor must be login into the system.

Main course of action: Step 1: user has to activate the system and click it on login button.
Step 2: The system responses by displaying the login interface/form
Step 3: user fill his/her username and password.
Step 4: The system verifies the username and password
Step 5: system displays “access granted welcome to your page”.

19
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Step 6: the system displays the user main window/page.

Step 7: user clicks on view notification button.
Step 8: The system displays available notification.
Step 9: use case ends.
Post condition: Donor and needy people benefactor can get new notification related
with their function from the admin.
Table 3.4 Use case description about view notification
Alternative course of action for view notification
A3: users enters wrong username and / or password, the system displays “Login Failed please check your user
name and password / or required field must be filled”.

Use case name: Fill membership

UC_ID: UC_05
Actor: Donor
Description: This use case is used to ensure that the donor can also fill
membership form in order to donate as a member.
Precondition: Donor must be a registered (to use the system by getting username
and password) after then Donor login into the system to fill the
membership form.
Main course of action: Step 1: donor has to activate the system and click it on login button.
Step 2: The system responses by displaying the login interface/form
Step 3: donor fill his/her username and password.
Step 4: The system verifies the username and password
Step 5: system displays “access granted welcome to your page”.
Step 6: the system displays the user main window/page.
Step 7: donor clicks on membership entry button.
Step 8: The system displays a form for membership.
Step 9: donor fill the form.
Step 10: use case ends.
Post condition: Donor can donate money either per month or year.
Table 3.5 Use case description about Fill membership
Alternative course of action for Fill membership
A3: user enters wrong username and / or password, the system displays “Login Failed please check your user
name and password / or required field must be filled”.

20
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: Donate money

UC_ID: UC_06
Actor: Donor.
Description: This use case is used to ensure that anyone who want to fund, can
donate money.
Precondition: 1.Donor should have willingness to donate money.
2.Donors must be a registered one.
3. Donors must be login into the system.
Main course of action: Step 1: donors has to activate the system and clicks on login.
Step 2: The system responses by displaying the login interface/form
and allow the donors to login.
Step 3: donor fill his or her username and password.
Step 4: The system verifies the username and password and it
displays “access granted welcome to your page”.
Step 5: the system displays the donor’s main window/page.
Step 6: donor clicks donate money option.
Step 7: The system displays options or methods to donate money.
Step 8: the donor select method of the options.
Step 9: the system displays form for the selected options.
Step 10: the donor fill the pay pal form and click it.
Step 11: the system displays an appropriate information for pay pal.
Step 12: Use case ends.
Post condition: The Donor can donate money either as a membership or at any time
they want.

Table 3.6 Use case description about donate money

Alternative course of action for donate money
A3: If donor enters wrong username and / or password, the system displays “Login Failed please check your
user name and password / or required field must be filled”.
A10: If donors cannot not have a pay pal account it must be create the new one at pay pal developer.

21
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: Donate material

UC_ID: UC_07
Actor: Donor.
Description: This use case is used to ensure that anyone can donate
items/material such as food, clothes and so on.
Precondition: 1.Donor should have willingness to donate material.
2.Donors must be a registered one.
3. Donors must be login into the system.
Main course of action: Step 1: donors has to activate the system and click it on login.
Step 2: The system responses by displaying the login interface/form
and allow the donors to login.
Step 3: donor fill his or her username and password.
Step 4: The system verifies the username and password and it
displays “access granted welcome to your page”.
Step 5: the system displays the donor’s main window/page.
Step 6: donor clicks donate material option.
Step 7: The system displays material or item list type.
Step 8: the donor select what he want to donate from the list of
option and click it on.
Step 9: the system displays a form for the selective one.
Step 10: the donor fill all the form fields and click it on “donate this
material” button.
Step 11: the system displays “you are successfully donate the item”.
Step 12: Use case ends.
Post condition: The Donor can donate material at any time they want.

Table 3.7 Use case description about donate material

Alternative course of action for donate material
A3: If donor enters wrong username and / or password, the system displays “Login Failed please check your
user name and password / or required field must be filled”.
A10: If donors cannot fill all fields of the form, the system act as “the required field must be filled”.

22
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: Change profile

UC_ID: UC_08
Actor: Donor and Manager
Description: This use case is used to ensure that donors and manager can manage
their personnel page, which includes changing password and profile.
Precondition: Donor and Manager must be login into the system.

Main course of action: Step 1: user has to activate the system and click it on login button.
Step 2: The system responses by displaying the login interface/form
Step 3: user fill his/her username and password.
Step 4: The system verifies the username and password and it
displays “access granted welcome to your page”.
Step 5: the system displays the manager or donor main window/page.
Step 6: user clicks on mange account and change profile.
Step 7: The system displays a form for change profile.
Step 8: user fill the form for profile change.
Step 9: the system displays “change successfully”.
Extend: Change profile, view notification.
Post condition: Manager or donor can manage their page effectively and efficiently
for security purpose at any time, after then they can logout from the
system.

Table 3.8 Use case description about Change profile

Alternative course of action for change profile
A3: During login if manager or donor enters wrong username and / or password, the system displays “Login
Failed please check your user name and password / or required field must be filled”.
A8: During change password process, if the new password and re-type password are not match or old password
not correct the system displays “password change failed, password does not match with your new password”.

23
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: Add advertisement

UC_ID: UC_09
Actor: Manager
Description: This use case is used to ensure that, the Manager have a privilege to
add advertisement associated with fund collection methods.
Precondition: To add advertisement, Manager must be login into the system.

Main course of action: Step 1: Manager has to activate the system and click it on login
button.
Step 2: The system responses by displaying the login interface/form
Step 3: Manager fill his/her username and password.
Step 4: The system verifies the username and password and it
displays “access granted welcome to your page”.
Step 5: the system displays the manager main window/page.
Step 6: Manager clicks on add advertise button.
Step 7: The system displays a form for adding advertisement.
Step 8: Manager fill the form and click on add advertisement button.
Step 9: the system displays “the advertisement added successfully”.
Post condition: The added advertisement of news officially posted on the site and
any one can see it.

Table 3.9 Use case description about Add advertisement

Alternative course of action for add advertisement
A3: During login if Manager enters wrong username and / or password, the system displays “Login Failed
please check your user name and password / or required field must be filled”.
A8: if the form is empty or some textbox is missed the system act as “the required field must be filled”.

Use case name: Manage user

UC_ID: UC_10
Actor: Manager
Description: This use case is used to ensure that, the Manager have a privilege to
view information, delete information.
Precondition: Manager must be login into the system.

24
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Main course of action: Step 1: Manager has to activate the system and click it on login
button.
Step 2: The system responses by displaying the login interface/form
Step 3: Manager fill his/her username and password.
Step 4: The system verifies the username and password and it
displays “access granted welcome to your page”.
Step 5: the system displays the manager main window/page.

Step 6: Manager clicks on manage user.

Step 7: The system displays view user information, delete user
information options.
Step 8: Manager clicks on view user information option.
Step 8.1: The system displays registered donor button,
registered needy people button, donated material button, and
donated money button.
Step 8.2: Manager clicks on registered donor button or
registered needy people button or donated material button or
donated money button.
Step 8.3: the system displays registered donor information or
registered needy people information or donated material
information or donated money information.
Step 9: Manager clicks on delete user information.
Step 9.1: the system displays list of user information.
Step 9.2: Manager choose the deleted one and click on delete
button.
Step 10: use case ends.
Extend : View user information, delete user information
Post condition: The Manager of the system maintain the all over information’s
related to fund management of Mekedonia.

Table 3.10 Use case description about Manage user

Alternative course of action for Manage user
A3: During login if Manager enters wrong username and / or password, the system displays “Login Failed
please check your user name and password / or required field must be filled”.

25
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: Send notification

UC_ID: UC_11
Actor: Manager
Description: This use case is used to ensure that, the Manager have a privilege to
send messages for donor (who are only member), and in order to
tell them the funding period is too close (either monthly or yearly).
Precondition: Manager must be login into the system.

Main course of action: Step 1: Manager has to activate the system and click it on login
button.
Step 2: The system responses by displaying the login interface/form
Step 3: Manager fill his/her username and password.
Step 4: The system verifies the username and password
Step 5: system displays “access granted welcome to your page”.
Step 6: the system displays the manager main window/page.
Step 7: Manager clicks on send notification button.
Step 8: The system displays form for send notification.
Step 9: Manager fill the appropriate information including the
message on the form, then click on send button.
Step 10: The system displays “message sent, message successfully
send”.
Step 11: use case ends.
Post condition: The Manager of the system sending a successful notification for
member donors and needy people.
Table 3.11 Use case description about Send notification

Alternative course of action for Send notification

A3: During login if Manager enters wrong username and / or password, the system displays “Login Failed
please check your user name and password / or required field must be filled”.
A8: if the message form is empty the system act as “the required field must be filled”.

26
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Use case name: apply for help

UC_ID: UC_12
Actor: Needy people Benefactor
Description: Needy people can describe their problem and send it to the organization
in order to get help, by using needy people benefactor volunteers.
Precondition: Needy people benefactor must be login into the system.

Main course of action: Step 1: user has to activate the system and click it on login button.
Step 2: The system responses by displaying the login interface/form
Step 3: user fill his/her username and password.
Step 4: The system verifies the username and password
Step 5: system displays “access granted welcome to your page”.
Step 6: the system displays the user main window/page.
Step 7: user clicks on help form button.
Step 8: The system displays a form for help.
Step 9: user fill the appropriate information on the form.
Step 10: The system displays the form successfully filled.
Step 11: use case ends.
Post condition: The needy people from any place can describe and fill their problem in
to our site before they come through by using needy people benefactor
volunteers.

Table 3.12 Use case description about apply for help

Alternative course of action for apply help
A3: During login if manager enters wrong username and / or password, the system displays “Login Failed
please check your user name and password / or required field must be filled”.
A8: if the help form is empty the system act as “the required field must be filled”.

3.1.4 Object Model

A collection of objects or classes through which a program can examine and manipulate some specific parts
of its world. In other words, the object-oriented interface to some service or system. Such an interface is said
to be the object model of the represented service or system.

27
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

3.1.4.1 Data Dictionary

A data dictionary is a collection of descriptions of the data objects or items in a data model for the benefit of
programmers and others who need to refer to them. A first step in analysing a system of objects with which
users interact is to identify each object and its relationship to other objects. After each data object or item is
given a descriptive name, data type and its relationship is described.

Descriptive Name Data type Description

AP_ID Int Contains the id number of needy people

First name String Holds the First name of people who need help.

Middle name String Holds the Middle name of people who need help.

Last name String Holds the Last name of people who need help.

Gender String Holds the Gender of the people who need help.

Age Int Holds the age of the people who need help.

Region String Holds the region where he or she lives.

City String Holds the city where he or she lives.

Wereda String Holds the wereda where he or she lives.

Kebele Int Holds the Kebele where he or she lives.

Problem String Holds the descriptive problem of the people who need help.

Date datetime Holds the date where the needy people recorded.

Table 3.13 Data Dictionary for apply for help (for needy people) table

Field Name Data type Description

MH_ID Int Contains the id number of member donor human.

First name String Holds the First name of donor.

Middle name String Holds the Middle name of donor

28
 FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Last name String Holds the Last name of donor

Gender String Holds the Gender of donor.

Country String Holds the country where donor lives.

State String Holds the region where donor lives.

City String Holds the city where donor lives.

Phone number Int Holds the phone number of donor.

Email address String Hold the email of donor.

Donation time String Hold the donation time of the member.

Amount of money Float Hold the amount of money, that donor gives as a member.

Date Datetime Hold the date where the member humans fill the membership

Table 3.14 Data Dictionary for member human table

Field Name Data type Description

MO_ID Int Contain the id number of member organization

Name of the organization String Holds the name of the organization.

Country String Holds the country where the organization is found.

State String Holds the region where the organization found.

City String Holds the city where the organization found

Phone number Int Holds the phone number of the organization.

Donation time String Hold the membership donation time. Example: - per month or
year...

Amount of money Float Hold the amount of money that the member donate per month
or year or any other period.

Date datetime Hold the date where the organization fill the membership

Table 3.15 Data Dictionary for membership organization table

29
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Field Name Data type Description

MA_ID Int Contain the id number of the material

Item type String Holds the type of the item.

Item name Int Holds the name of the item.

Item quantity String Hold the total amount of item.

Image of item String Hold the sample image of item

From String Hold the sender of the item

To String Hold the receptor of item

Detailed information of item String Hold the detailed information about the item.

Cost of transportation Float Hold the transportation cost of the material.

Date Datetime Hold the date where the material donated.

Table 3.16 Data Dictionary for donated material table

3.1.4.2 Analysis Level Class Diagram (Conceptual Modeling)

A type of diagram which shows of a set of relationships between factors that are believed to impact or lead to
a target condition; a diagram that defines theoretical entities, objects, or conditions of a system and the
relationships between them.

Characteristics of Models

The main characteristics or goals of a conceptual model are as follows:

 It improves a person's understanding of the subject being modelled.

 It communicates details between people who need to know them.
 It gives a point of reference for people like designers to come up with specific plans.
 It provides a document that can be referred to in the future and used when people work together.

30
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.2 Conceptual class diagram

3.2 Dynamic Model

Models are the things we build to help us understand things better. When dealing with concepts of reality we
have as the only alternative those abstractions we develop as models, or in situations where it is simply too
costly to build the real thing, we build models to help us understand. In short models are simplifications, or
abstractions, of reality intended to promote understanding. Whether the models we create are good models or
poor models depends on the extent to which they aid us in developing the understanding we seek. As to
whether a model is correct or incorrect is probably something which will only become evident in time.

3.2.1 Sequence Diagram

The Sequence Diagram models the collaboration of objects based on a time sequence. It shows how the objects
interact with others in a particular scenario of a use case. With the advanced visual modeling capability, you
can create complex sequence diagram in few clicks. Besides, Visual Paradigm can generate sequence diagram
from the flow of events which you have defined in the use case description.

31
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.3 Sequence diagram for login

Figure 3.4 Sequence diagram for registration

32
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.5 Sequence diagram for add advertisement

Figure 3.6 Sequence diagram for send notification

33
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.7 Sequence diagram for donate money

Figure 3.8 Sequence diagram for donate material.

34
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.9 Sequence diagram for manage user

Figure 3.10 Sequence diagram for change profile.

35
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.11 Sequence diagram for apply for help.

Figure 3.12 Sequence diagram for membership entry.

3.2.2 Activity Diagram

Activity diagrams, which are related to program flow plans (flowcharts), are used to illustrate activities. In the
external view, we use activity diagrams for the description of those business processes that describe the
functionality of the business system. Contrary to use case diagrams, in activity diagrams it is obvious whether
actors can perform business use cases together or independently from one another. Activity diagrams can be

36
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

developed in various degrees of detail. They can be refined step by step. In the external view, activity
diagrams, just like use case diagrams, exclusively represent business processes and activities from the outside
perspective.

Figure 3.13 Activity diagram for login

Figure 3.14 Activity diagram for advertisement

37
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.15 Activity diagram for donate material

Figure 3.16 Activity diagram for donate money.

38
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.17 Activity diagram for send notification

Figure 3.18 Activity diagram for registration

39
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.19 Activity diagram for membership entry.

Figure 3.20 Activity diagram for apply help.

40
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

3.2.3 State Chart Diagram

A state diagram shows the behaviour of classes in response to external stimuli. Specifically a state diagram
describes the behaviour of a single object in response to a series of events in a system. A state diagram, also
called a state machine diagram or state chart diagram, is an illustration of the states an object can attain as well
as the transitions between those states in the Unified Modelling Language (UML). In this context, a state
defines a stage in the evolution or behaviour of an object, which is a specific entity in a program or the unit of
code representing that entity. State diagrams are useful in all forms of object-oriented programming (OOP).
The concept is more than a decade old but has been refined as OOP modelling paradigms have evolved. This
UML diagram models the dynamic flow of control from state to state of a particular object within a system.

Figure 3.21 State chart diagram for login.

Figure 3.22 State chart diagram for registration.

41
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

3.2.4 User Interface Prototype

User interface (UI) prototyping is an iterative analysis technique in which users are actively involved in the mocking-
up of the UI for a system. UI prototypes have several purposes:

As an analysis artifact that enables you to explore the problem space with your stakeholders.

As a requirements artifact to initially envision the system.

As a design artifact that enables you to explore the solution space of your system.

A vehicle for you to communicate the possible UI design(s) of your system.

A potential foundation from which to continue developing the system (if you intend to throw the prototype away and
start over from scratch then you don't need to invest the time writing quality code for your prototype).

Figure 3.23 User interface Flow Design

42
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.24 Login interface prototype

Figure 3.25 Register/sign up interface prototype

43
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.26 Membership form interface prototype

Figure 3.27 Money donation form (for Members) interface prototype

44
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.28 Material donation form interface prototype

Figure 3.29 Message sending form interface prototype

45
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 3.30 Apply For Help (for needy people) form interface prototype

3.2.5 Supplementary Specifications

The supplementary specification document is composed of different section including Functionality, Security,
Reliability, Performance, Supportability, Design Constraints, Online User Documentation and Help System
Requirements, Purchased Components, Licensing Requirements, Legal, Copyright, and Other Notices,
Applicable Standards.

46
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER FOUR: SYSTEM DESIGN

4.1 Introduction
System design is the process of defining the components, modules, interfaces, and data for a system to satisfy
specified requirements. System development is the process of creating or altering systems, along with the
processes, practices, models, and methodologies used to develop them. In this chapter, we define the design
goals of our project and decompose the system into smaller subsystems that it can be understandable. We also
select strategies for building the system, such as the hardware/software platform on which the system will run,
the persistent data management strategy and the access control policy. The result of this chapter is a model
that includes a clear description of each of these strategies, a subsystem decomposition, and a UML
deployment diagram representing the hardware/software mapping of the system.

4.1.1 Purpose of the System

In our system development process system design part is very important so as to make the implementation of
the proposed system very easy. The different types of the system modelling techniques that are used to make
easy the implementation of the system such as deployment and component modelling are show in detail.

4.1.2 Design Goals

The design goals are to describe the structure of the system, including any subprograms to be used along with
the packaging of the system. Design goals describe the qualities of the system that developers should achieve.
Such goals are normally derived from the non-functional requirements of the system described earlier.

The design goals are:-

1. End User Criteria: The proposed system should have simple and understandable graphical user Interface
such as forms and buttons, which have descriptive names.
2. Performance: The web application matters in performing tasks in fraction of minutes, so a fast response
time with maximum throughput is a serious issue.
3. Dependability: The system needs not to be highly dependable as it is expected to be used by unprofessional
users. The system should be robust and fault tolerant.
4. Security: The system should control who can get the services through authentication and verification.
5. Maintenance: The web application should be easily extensible to add new features at a later stage. It should
also be easily modifiable to make changes to the features and functionalities.
6. Easy: The system should be easy to learn, use, understand or deal with. The system provides interfaces that
are capable of being understood by every user so any interaction with the system has no complexity to access
all of its services.

47
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

4.2 Current Software Architecture

For funding management system the current Mekedonia organization does not have a software architecture, because
currently Mekedonia organizations uses banking mechanism. So right now Mekedonia does not have a software
architecture for the funding process.

4.3 Proposed Software Architecture

4.3.1 Overview
Software architecture is the interaction between the system components. We use client/server architecture.
The user will use computers to interact with the web application using interface provided. The system uses
browser to interact with web server using http. The client side server provides user interface and the database
server is where all information is stored and can be accessed by authorized parties.

Figure 4.1 Software design architecture

4.3.2 Subsystem decomposition

Decomposition refers to the process by which a complex problem or system is broken down into parts that are
easier to conceive, understand, program, and maintain. It results large systems in to a set of loosely dependent
parts which make up the system. To reduce the complexity of the solution domain, we decompose a system
into simpler parts called subsystems, which are made of a number of solution domain classes. From the
functional requirements the proposed system could consists of the following subsystems:

48
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 4.2 Subsystem decompositions

4.3.3 Hardware/software mapping

Hardware/software mapping means mapping the hardware and software components of the system, which
means it is described on deployment diagram.

4.3.4 Persistent data management

Persistence models in our system are used to communicate the design of database. This is basically the entity
relation in database application. The system that we design overall persistent modelling is described at class
modelling part. To design the database we will use the table to indicates what our database looks like and we
define appropriate field name, data type, length of the input, primary key and remarks.

49
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

4.3.4.1 Mapping

Figure 4.3 Mapping of design of class and database

4.3.4.2 Database Design

Database design is the process of producing a detailed data model of a database. This logical data model
contains all the needed logical and physical design choices and physical storage parameters needed to generate
a design in a data definition language, which can then be used to create a database. A fully attributed data
model contains detailed attributes for each entity. It can be thought of as the logical design of the base data
structures used to store the data.

50
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 4.4 Database design

4.3.5 Access control and security

Access control is a security technique that can be used to regulate who or what can view or use resources in a computing
environment. There are two main types of access control: physical and logical. Physical access control limits access to
campuses, buildings, rooms and physical IT assets. Logical access limits connections to computer networks, system
files and data. Access control systems perform authorization identification, authentication, access approval, and
accountability of entities through login credentials including passwords, personal identification numbers (PINs)

51
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 4.5 Access control table

4.3.6 Global software control

The fund management system for Mekedonia architecture is to have an explicit, decentralized software
control. Also the system dynamic control of distributed among different controllers such that each object
delegate some responsibility to other objects.

4.3.7 Boundary conditions

 Start-up: go to system URL and login
 Shut Down: click log out and close browser
 Error Conditions:

1. Logging in:
o Username and password field cannot be empty.
o The welcome screen does not appear after logging in.
2. Data entry:
o Password did not match.
o User name already reserved
o If there is an incorrect filling, not jumped to the next field
o The email address is already reserved

52
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

4.4 Subsystem services

1. The Manager Subsystem
- Responsible for managing user which includes view user information, sending SMS through phone
number, generate report, and delete user information after login into the system
- Responsible for sending notification (message) for member donors, member organizations and for
needy people who fill apply for help form
2. The change profile Subsystem
- Responsible for providing a mechanism to change profile, such as user name, password or any other
profile for donors and managers.
3. The donate money subsystem
- Responsible for providing member donation option and non-member donation option for donors.
4. The member subsystem
- Responsible for providing member donation form for both human and organization in terms of money
but not for material. For example: - Donor choice what they are either human or organization. after
then they fill it the form by remembering their membership data entry and click on donate now button
then the link direct to pay pal sandbox site, if the donor have a pay pal sandbox account they fill the
user name and password, next click on the donate button. If they don’t have a pay pal account click it
on register/create account link on the pay pal.
5. The non-member subsystem
- Responsible for providing non- member donation form for both human and organization in terms of
money but not for material. For example: -Donor can select either of two from human and organization,
after then they fill it the form and click on donate now button then the link direct to pay pal sandbox
site, if the donor have a pay pal sandbox account they fill the user name and password, next click on
the donate button. If they don’t have a pay pal account click it on register/create account link on the
pay pal.
6. The donate material subsystem
- Responsible for providing an options or choices for donors to make a fund in terms of material. Such
as food, clothes and others.
7. The membership Subsystem
- Responsible for providing human membership and organization membership registration form to
donors
8. The needy people Benefactor Subsystem
- Responsible for viewing or showing notification, which are send from the manager
- Responsible for providing apply for help registration form to elderly and mentally disabled people.

53
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

4.5 Component Diagram

Component diagrams are often used to model high-level software components and how they interact. The
interfaces between these components become clearer as the model grows, which provides a much clearer
delineation of duties of each component. So from that point component diagrams are used to visualize the
physical components in a system. These components are libraries, packages, files etc.
Component diagrams can also be described as a static implementation view of a system. Static implementation
represents the organization of the components at a particular moment. It does not describe the functionality of
the system but it describes the components used to make those functionalities. A single component diagram
cannot represent the entire system but a collection of diagrams are used to represent the whole.

Figure 4.6 Component diagram for new system

54
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

4.6 Deployment Diagram

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. Deployment diagrams consist of nodes and their relationships. The name Deployment itself
describes the purpose of the diagram. Deployment diagrams are used for describing the hardware components
where software components are deployed. 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,) and how the software components are
distributed across the units.

The purpose of deployment diagrams can be described as:

 Visualize hardware topology of a system.

 Describe the hardware components used to deploy software components.
 Describe runtime processing nodes.

Figure 4.7 Deployment diagram for the new system

55
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER FIVE: OBJECT DESIGN

5.1 Introduction
Object design defines object design trade-offs made by designers, that guidelines they followed for subsystem
interfaces, the decomposition of subsystems into packages and classes, and the class interfaces. The ODD is
used to exchange interface information among teams and as a reference during testing. Web based fund
management system of Mekedonia elderly and mentally disabled people help organization consists of
subsystems which work separately but simultaneously. Subsystems interact with each other and each
subsystem works when it is named by another subsystem. During the object design, characteristic of each
system must be considered its own and the whole system must be considered.

5.2 Object design trade-offs

The following are the trade-offs found in our web based fund management system.

Understand ability versus Cost

Understand ability of the code is too important especially during the testing phase. Each function and
operations must be readable, so number of operations increase in the system and functions must be
implemented in a clear way. Writing comments into the source code increases the understand ability of the
code. This causes an additional cost in the developing phase.

Guidelines and Convention

Web based fund management system of Mekedonia is to change manually to automated system including
registering needy peoples and members. From the backup server so called XAMPP control panel or
localhost/phpmyadmin the database can be created and also inside the database there is some tables which
includes some attributes have data type and maximum length it contains and also primary keys and foreign
keys. From the UI, any text entry.
Boundary Cases
From the UI, any text entry field should have a maximum length which indicates a boundary Also from the
UI, depending on the language we use, the numeric fields could also contain alpha characters which could
cause all kinds of internal issues. Depending on the type of database we use, the fields might have a maximum
width value. We need to make sure there is enough space in each of the fields.
Exception Handling Mechanisms
The web based fund management system is dealing with this programming language construct to ensure the
fact that normal flow of execution takes place constantly. Not only just to synchronize the integrity of the

56
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

system what are the constraints and raising these exceptions in a useful way to deal with any sort of problem
or semi-predicate problem such as “Invalid User Name Password” and “Please fill out this field” Exception
Security versus Cost

In web based fund management system of Mekedonia, users must be authorized to connect system, and
unauthorized people should not be able to access the system. Each user will be able to login to the system by
using the username and password that is assigned by super user. This brings an additional cost to the system.

5.3 Interface documentation guidelines

Interface documentation guidelines and naming conventions are the most important factors that can
improve communications between developers during object design. Naming conventions make
programs more understandable by making them easier to read. They can also give information about the
function of the identifier-for example, whether it's a constant, package, or class-which can be helpful in
understanding the code.

5.4 packages
Package diagram is a graphical representation of the logical structure of the system as a set of packages
combined with dependencies and decomposed. These diagrams are used for grouping and organizing
complex project documentation. Our system has the following packages.
 Database Package: This package contains databases used for making connections and executing
queries on the database, this package have two different databases those are bank and Mekedonia
user databases. Each of them contains different table classes.
 Donor user interface package: This package represents the user interface for donors.
 Manager user interface package: this package represents the user interface for managers. Contains
classes which perform user management related functions.
 Needy people benefactor user interface package: this package represents the user interface for needy
people benefactors.
 Script Package: The package name is Script package, and is responsible to show dynamic web pages
to users.
 Comment Package: The package name is user comment package, and it contain class that accept
comment about system from user and transmit to Admin.
 Authentication Package: The package name is user Authentication package, and it contain class that
perform user Authentication functions.

57
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

5.5 class interfaces

Class interfaces can be described by the class diagram. It shows the interactions between different
classes of the system or the way how classes are interacted each other to accomplish their task.

1. Main Package: localhost/Mekedonia/index.php

Index class

• Index class is part of the main package, and it display the main interface to manager, donor and
needy people benefactor.
• This class represents the sign up and login window. And it allows the manager, donor and needy
people benefactor to login into system.
2. Donor package:
Material donation class
• This class represents material donation window. Any donor who have an account on the site can
donate material for the organization after login into the system.
Membership registration class
• This class represents for human and organizational membership window. Any donor who want to
help as a member can fill either human membership or organizational membership or both of them.
Money donation class
• This class represents money donation window for both member and non-member donors. Donors
who want to help Mekedonia can donate money based either as a member (based on their
membership, organizational or human) or as a non-member.
3. Manager Package:
Notifying class
• This class represents sending notification for donors and needy people window. The manager can
send message based notification for donors when their donation time is too close or when material
donated by donor is delivered, it sends normal message from manager account to donor account or
SMS message for donors through their phone number using internet connection.
4. Needy people benefactor package

Filing help form class

• This class represents help applying form window. Needy peoples who need help can send their
biographies through needy people benefactor peoples in order to get help from the organization
after approval of their biography.

58
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER SIX: IMPLEMENTATION AND TESTING

6.1 Introduction
During this phase physical design specification must be turned into working computer code, and provide help
for current and future users and take care of the system. And then the code is tested until most of the errors
have been detected and corrected. The purpose of this activity is to convert the final physical system
specification into working model with reliable software and hardware.

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

6.2 Final Testing of the system

Testing is a procedure to show the correctness of the program and designed to analyse the logic used in the
implementation of the System. In the case of our project we use unit, function and system testing method.

 Unit Testing
In unit testing, each module (roughly a section of code that performs a single function) is tested alone in an
attempt to discover any errors that may exist in the module’s code. We use unit testing to test the individual
functional component of our system before testing the whole system once.

 functional Testing
Functional testing is the testing to ensure that the identified functionality required in the system requirements
works.it deals with the functional requirements that are listed in the previous chapter two.

 System Testing
System testing is also intended to demonstrate whether a system meets its objectives. For
verifying as the whole system is functioning in integrated manner with respect to the goal of
our system.

6.3 Hardware software acquisitions

Hardware software acquisitions define the system resource requirements, its ability with other systems and
linkages, its interface requirements to existing systems if any, its security competence, lacks and weakness
and to make sure there are not previously existing system that provide corresponding functionality.

59
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Hardware acquisitions
 Desktop computer with modern browser.
 Personal computer with modern browser.

Software acquisitions

 Notepad++ V6.6.8
 MySQL Server
 Apache local server

6.4 User manual preparation

US we that every services and functions that are important for the user will be clarified and executed. Since
the server side system is web application everything important for the user will be explained and implemented
while preparation of short training document when the system is deployed. And also notify the user whether
the teams prepare to give training.

6.5 Training
When Mekedonia organization want to use the software system, we try to train the users of the system
effectively. Giving an important training for the user generates the following advantages for the organization
 Reduces cost and saves time: deals with cost and time minimization, when the users get an efficient
training from the system developers, the organizations can minimize the costs that are paid for other
training consultants.
 Made successful system operations: after a successful training time, any user of the system can easily
adapt with software and simply they can make successful system operations or functions based on their
privilege.

During the deployment of the system, the project group members will give short time training for the system
users (donors, manager and needy people benefactors) and explaining how the system works and in what way
they can manage their system. Help activity are set for donors, they can show after login into system.

60
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

6.6 Installation process

To make the installation process there are some requirements that are needed:

1. First, users need a desktop or personal computer.

2. Second, those devices needs to install modern browsers.
3. Third, Xampp controller must be installed on the user computer (which includes apache server
and MySQL database server)
4. Fourth, the user computer must be connected to internet, for some functionalities such as SMS.

The following are the newly implemented software system user interfaces:

Figure 6.1 homepage user interface design

Figure 6.2 User interface design for sign up/registering users

61
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.3 User interface design for login into the system

Figure 6.4 User interface design for donor page

Figure 6.5 User interface design for view notifications

62
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.6 User interface design for human membership

Figure 6.7 User interface design for organizational membership

63
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.8 User interface design for material donation

Figure 6.9 User interface design for member donors (through bank)

64
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.10 User interface design for non-member donor (through bank)

Figure 6.11 User interface design for direct notification generates from the system

65
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.12 User interface design for controlling users by the manager

Figure 6.13 User interface design for sending SMS for needy people approval

66
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.14 User interface design for donated material delivery check up

Figure 6.15 User interface design for showing Mekedonia balance (donated through bank)

67
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.16 User interface design for list of donated material

Figure 6.17 User interface design for generated receipt for donors after donation

68
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.18 User interface design for generating report by option selection

Figure 6.19 User interface design for filling help form for needy people

69
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Figure 6.20 User interface design for money donation (through pay pal)

Figure 6.21 an error message for pay pal money transaction

70
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Sample codes for index page

71
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Sample code for sign up

72
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Sample code for login

Sample code for money donation

Sample code for pay pal

73
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Sample code for membership registration

74
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Sample code for SMS

75
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

6.7 Start-up strategies

The start-up strategy will be:
 Buying a domain name from a company with its corresponding IpAddress for the server.
 Hosting the database the server
 Finally available internet connection for users.

76
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

CHAPTER SEVEN: CONCLUSIONS AND

RECOMMENDATIONS
7.1 Conclusions
Implementing the analyzed and designed online fund management system for Mekedonia mentally and
disabled people help organization might be the best solution to the current major problem of money and
material funding process. Our proposed web based fund management system of Mekedonia will also provide
quick and reliable registration process, membership and needy people recording process, money donation
through bank and material donations, sending of fast SMS notification through Phone and account.
Therefore, in the first chapter of this project document we were trying to assess the problem of statement,
scope of the project and limitation, setting the objective and in the second chapter we were trying to assess the
existing system and studying each and every activity of the existing system by conducting different data
gathering methodology. Then after examination of the current existing we choose the web based system, as it
will be able to address problems encountered by users (donors and Needy people benefactor) within the current
donation process and needy people registration.
And in order to accomplish the objective of the proposed system implementation tool such as programming
languages (PHP, JavaScript, CSS, MYSQL, HTML) and Edraw max software for design model of (use case
modeling, sequence diagram, activity diagram, class diagram, state chart diagram, component and deployment
diagram) in chapter three and four. The sequence diagram shows the steps and processes how to done functions
in the new developed system. The activity diagram shows different type of user interacts with the system.
Furthermore, the use cases showed what the user will do with the system. And finally each class and attribute
was explained in detail. Furthermore the class diagram demonstrates the relationship between classes in the
system. From a proper analysis of positive points and constraints on the existing system we conclude that the
proposed system that we designed to implement will be efficient and effective one to solve current problem,
if we implement it in carefully planned manner.

77
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

7.2 Recommendations
The proposed system that we are trying to develop involves only automating fund management in terms money
and material donation that are done for Mekedonia. But there are still areas that may be considered as a further
and important area to improve on, and our suggestion go thus.

 Add the management of day to day activities of needy peoples.

 Provide a mechanism for volunteers to set a time schedule in order to help the organization.
 Make it the SMS service automatic, to send message for donors when the donation date is passed or
forgotten.
 Try to integrate the pay pal service, when the service is available for Ethiopia.
 We also recommend the donation time auto remembering for donors, when the donation time is too
close.
 Additionally we recommend developing this software system in multiple local and international
languages, such as Amharic, Oromiafa, Tigrigna, French and Spanish.
 We also recommend applying auto completing country, city and country code phone number
selections.
Therefore, others who are interested to develop a new system on fund management system for Mekedonia
elderly and mentally disabled help organization or other related systems can get some initial idea about the
system. By focusing on the limitation and functional areas of the system they can also develop a better fund
management system that automates all function that are managed in fund management system.

78
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

Appendix

Symbol Description
Actor

System boundary

Decision

Use case

Class

Object life line

Node for Deployment diagram

Component for component diagram and

deployment diagram

Message line extends from the lifeline of one

object to the lifeline of another object.
Include, relates to the include use case to
indicate inserted behaviour
Create Return Message

79
FUND MANAGEMENT SYSTEM FOR MEKEDONIA ELDERLY AND MENTALLY DISABLED PEOPLE HELP ORGANIZATION

The state of the activity

Starting point of activity/state diagram

Ending point of activity/state diagram

End of the object

References
1. Ministry of Foreign Affairs, (2010). A Manual Prepared by the Ministry of Foreign Affairs Regarding
the Service it Renders to Charities Established Abroad and Applying for Registration to Operate in
Ethiopia Pdf Retrieve on April 08,2014 fromhttp://www.mfa.gov.et/docs/NGO_Rule_English.pdf
2. Allen, B., &Reser, D. (1990). Content analysis in library and information science research. Library &
Information Science Research, 12(3), 251-260.
3. J. Fisher (1998, Nongovernment. NGOs and the Political Development of the Third World, West
Hartford: Kumarian Press).
4. Inger Ulleberg, (2009). The role and impact of NGOs in Capacity Development from Replacing the
State to Reinvigorating Education. UNESC
5. System analysis and design 8thedtionkennethekendall and julee.kendall
6. Sherine Jayawickrama & Neil McCullagh, (2009). What Makes International NGOs Distinctive?
Contributions, Characteristics and Challenges. Hauser Centre for Non-profit Organizations. Harvard
University.
7. System analysis and design 8thedtionkennethekendall and julee.kendall.

80