OMO PRJT Whole Document

Wolaita OMO Micro Finance Online System
Acknowledgment
First of all we like to glorify our almighty God for help us in all our life movement.
Our indebted and gratitude adviser Amarekebede for his advice, suggestion, eroticism,
guidance encouragement and overall assistance cannot adequately be courted in few
sentences. Successful accomplishment of this research would have been very difficult
without his generous time devotion and tireless effort.
Lastly but not least, We would like thank AtoTilahun and his secretary who works in OMO
micro finance, for his support in all your project movement he give us all necessary
information’s at any time when he need. He never refuses us to give information. And also
AtoTamene he gave the whole information about how to calculate payroll.
0|Page
Abstract
The main objective of our project is to develop automated saving and loan system in order to
secret the evidence, prevent destroying of data and increase the productivity of an
organization.
Major functions of the departments in Arba Minch OMFI are analyzed to understand clearly
how activities are undertaken in the existing system of the company. Identifying documents,
forms, reports, that are related with the project scope, and employees in the existing system
followed by discussions on each subject from the existing system point of view.
Furthermore, identifying the problems in the existing system using various analysis
techniques and analyzing options to address the identified problems, and proposing a new
system.
In general, we want to do this computerized system in order to solve the existing problem,
develop loan and saving work and effectiveness of the client.
1|Page
Table of Contents
Titlepage
CHAPTER ONE
1 INTRODUCTION----------------------------------------------------------------------------------------------------------------1
1.1 Vision--------------------------------------------------------------------------------------------------1
1.2 Mission------------------------------------------------------------------------------------------------1
1.3 Values--------------------------------------------------------------------------------------------------1
2. BACKGROUND --------------------------------------------------------------------------------------2
3 .STATEMENT OF THE PROBLEM--------------------------------------------------------------3
4. PROPOSED SOLUTION----------------------------------------------------------------------------3
4.1 Requirements of the proposed system------------------------------------------------------------4
4.1.1Functional requirement---------------------------------------------------------------------------4
4.1.2 Nonfunctional requirement----------------------------------------------------------------------4
5. PROJECT OBJECTIVE-----------------------------------------------------------------------------5
5.1. General Objective ------------------------------------------------------------------------------5
5.2 Specific Objectives-----------------------------------------------------------------------------5
6. SCOPE OF THE PROJECT------------------------------------------------------------------------5
6.1. Limitation --------------------------------------------------------------------------------------6
7. FEASIBILTY STUDY------------------------------------------------------------------------------6
7.1 Technical feasibility-----------------------------------------------------------------------------6
7.2 Operational feasibility---------------------------------------------------------------------------7
7.3 Economic feasibility-----------------------------------------------------------------------------7
7.3.1. Tangible benefits---------------------------------------------------------------------------------7
7.3.2. Intangible benefits-------------------------------------------------------------------------------7
8. METHODLOGY-----------------------------------------------------------------------------------8
i|Page
8.1. Data collection mechanisms--------------------------------------------------------------------8

8.1.1 Document analysis--------------------------------------------------------------------------8
8.1.2 Interview------------------------------------------------------------------------------------------8
8.1.3 Observation---------------------------------------------------------------------------------8
8.2. Development environment and programming tools---------------------------------------8
9. SECURITY AND ACCESS PERMISSION----------------------------------------------------9
9.1. Description of the existing system ---------------------------------------------------------9
9.2 Description of the new system----------------------------------------------------------------9

9. TEAM COMPOSITION---------------------------------------------------------------------------10
10. TIME SCHEDULE--------------------------------------------------------------------------------11
11. COST BREAKDOWN----------------------------------------------------------------------------12
CHAPTER TWO--------------------------------------------------------------------------------------12
2 DESCRIPTION OF EXISTING SYSTEM----------------------------------------------------12
2.1. Introduction of existing system--------------------------------------------------------------12
2.2. Players in the Existing System---------------------------------------------------------------12
2.3. Major Functions in the Existing System like to inputs, processes &outputs-----------13
2.4. Business rule-------------------------------------------------------------------------------------15
2.5. Report Generated in the Existing System----------------------------------------------------18
2.6. Forms and other documents-------------------------------------------------------------------18
2.6.1. Saving Account opening form-------------------------------------------------------18
2.6.2. Loan form------------------------------------------------------------------------------18
2.6.3. Subsidiary ledger card---------------------------------------------------------------19
2.6.4. General Ledger card------------------------------------------------------------------20
2.7. Bottlenecks of the existing system Using PIECE framework-----------------------------20
2.7.1. Performance Related problem------------------------------------------------------20
2.7.2. Information related problem--------------------------------------------------------20
2.7.3. Control related problem-------------------------------------------------------------21
2.7.4. Control related problem-------------------------------------------------------------21
2.7.5. Efficiency related problem----------------------------------------------------------22
ii | P a g e
2.7.6. Economic related problem----------------------------------------------------------22

2.7.7. Service related problem-------------------------------------------------------------22
2.8. proposed solution for the new system that address problem of the existing system---23
2.9. Requirements of the proposed system--------------------------------------------------------23
2.9.1. Functional Requirements------------------------------------------------------------23
2.9.2. Non Functional Requirements------------------------------------------------------23
CHAPTER THREE----------------------------------------------------------------------25
3. SYSTEM ANALYSIS--------------------------------------------------------------25
3.1. Introduction--------------------------------------------------------------------------------------25
3.2. System requirement specification (SRS)-----------------------------------------------------25
3.2.1. Actor Identification-------------------------------------------------------------------25
3.2.2. Use Case Diagram-------------------------------------------------------------------26
3.3. Documentation of new System in Use Case Diagram--------------------------------------26
3.3.1. Login------------------------------------------------------------------------------------27
3.3.2. Open Saving Account ----------------------------------------------------------------28
3.3.3. Opening Loan account----------------------------------------------------------------28
3.3.4. Withdrawal money--------------------------------------------------------------------29
3.3.5. Return lone money--------------------------------------------------------------------29
3.3.6. Registering Employee----------------------------------------------------------------30
3.3.7. Change employee Password---------------------------------------------------------31
3.3.8. Update customer information--------------------------------------------------------31
3.3.9. Generate Saving Report----------------------------------------------------------------------32
3.3.10. Generate Loan Report-----------------------------------------------------------------33
3.4. Sequence diagram--------------------------------------------------------------------------------34
3.4.1. Sequence Diagram for login---------------------------------------------------------34
3.4.2. Sequence diagram for open saving account---------------------------------------35
3.4.3. Sequence diagram for opening loan account--------------------------------------36
3.4.4. Sequence diagram for Withdrawal money----------------------------------------37
3.4.5. Sequence diagram for return money------------------------------------------------38
3.4.6. Sequence diagram for employee registration---------------------------------------39
3.4.7. Sequence diagram for change password--------------------------------------------40
3.4.8. Sequence diagram for saving report-------------------------------------------------41
3.4.9. Sequence diagram for loan report----------------------------------------------------42
3.5. Activity diagram------------------------------------------------------------------------------------43
iii | P a g e
3.5.1. Activity diagram for login--------------------------------------------------------------43

3.5.2. Activity diagram for open saving account--------------------------------------------44
3.5.3. Activity diagram for opening loan account-------------------------------------------45
3.5.4. Activity diagram for lone credit/ withdrawal money--------------------------------46
3.5.5. Activity diagram for lone debt/return money-----------------------------------------47
3.5.6. Activity diagram for employee registration------------------------------------------48
3.5.7. Activity diagram for changing password --------------------------------------------49
3.5.8. Activity diagram for generating saving report----------------------------------------50
3.5.9. Activity diagram for loan report--------------------------------------------------------51
3.6. Class diagram----------------------------------------------------------------------------------------

52
3.7. User interface prototyping--------------------------------------------------------------------------

53
3.8. Supplementary specifications----------------------------------------------------------------------
53
CHAPTER FOUR----------------------------------------------------------------------------53
4. SYSTEM DESIGN-------------------------------------------------------------------------- 53
4.1. Introduction--------------------------------------------------------------------------53
4.2. Class Type Architecture------------------------------------------------------------53
4.2.1. Layered class type architecture-------------------------------------------------------53
4.2.2. User interface layer--------------------------------------------------------------------54
4.2.3. Controller/process Layer--------------------------------------------------------------54
4.2.4. Business/Domain class----------------------------------------------------------------54
4.2.5. System layer----------------------------------------------------------------------------55
4.2.6. Persistence------------------------------------------------------------------------------55
4.3. Class Modeling-------------------------------------------------------------------------55
4.4. State chart---------------------------------------------------------------------------56
4.4.1. State chart for saving account form-------------------------------------------------56
4.4.2. State chart for loan account form---------------------------------------------------56
4.5. Collaboration modeling------------------------------------------------------------57
4.5.1. Collaboration modeling for login----------------------------------------------------57
4.5.2. Collaboration diagram for opening saving account-------------------------------58
4.5.3. Collaboration modeling for open loan account------------------------------------59
4.5.4. Collaboration modeling for return money------------------------------------------60
4.5.5. Collaboration modeling for registration---------------------------------------------61
4.5.6. Collaboration modeling for change password--------------------------------------62
4.5.7. Collaboration modeling generating saving report----------------------------------63
4.5.8. Collaboration modeling for generating loan report--------------------------------64
iv | P a g e
4.6. Component Modeling--------------------------------------------------------------65

4.7. Deployment modeling------------------------------------------------------------66
4.8. Persistence modeling--------------------------------------------------------------67
4.9. User interface-----------------------------------------------------------------------------68
4.9.1. Home page----------------------------------------------------------------------------------68
4.9.2. Admin login page--------------------------------------------------------------------------69
4.9.3. Operator login page------------------------------------------------------------------------69
4.9.4. Clerk login page----------------------------------------------------------------------------69
4.9.5. Saving Card form for Personal Tax-----------------------------------------------------70
4.9.6. Credit Card form for Personal Tax------------------------------------------------------71
CHATER 5-------------------------------------------------------------------------------------------72
5. CODING-----------------------------------------------------------------------------------------72
5.1. Home page code ------------------------------------------------------------------------72
5.2. Home page code-------------------------------------------------------------------------72
5.3. Admin login page code-----------------------------------------------------------------74
5.4. Operator login page---------------------------------------------------------------------77
5.5. Saving card form code------------------------------------------------------------------80
5.6. Loan card form--------------------------------------------------------------------------88
Chapter Six----------------------------------------------------------------------------------------91
6. CONCLUISION---------------------------------------------------------------------------------91
7. REFERENCES----------------------------------------------------------------------------------------92
v|Page
Acronyms
Acronyms Definition
OMFI OMO micro finance Institution
SNNPRS Southern Nations and Nationalities

Peoples Regional Sate
MFIs microfinance institutions
PHP hypertext preprocessor
MYSQl structured query language

HTML Hyper Text Markup Language
Ms. Word Microsoft word
DB Data Base
ER Entity relationship
DFD Data Flow Diagram
Table1; - List of Acronyms
1|Page
1. Introduction
Microfinance refers to a variety of financial services that target low-income clients,
particularly women. Since the clients of microfinance institutions (MFIs) have lower
incomes and often have limited access to other financial services, microfinance products tend
to be for smaller monetary amounts than traditional financial services. These services include
loans, savings, insurance, and allowances.
A bank is a financial institution and a financial intermediary that accepts deposits and
channels those deposits into lending activities, either directly by loaning or indirectly through
capital markets.
1.1. Vision
The Vision of OMFI is in the year 2018 G.C to see a society in which people are free from
the grips of abject poverty, with all the power determining their future in their own hands,
and its own capacity as an institution well developed to provide best services for all in need
in a sustainable manner.
1.2. Mission
The mission of OMFI is to improve the economic situation of low income, productive poor
people in the Southern Nations and Nationalities Peoples Regional Sate region through
increased access to lending and saving services. It will maintain cost effectiveness in service
delivery, and integrates its activities with government and NGO's working towards achieving
food security and poverty alleviation in the region.
1.3. Values
 Treating customers with utmost respect, dignity and impartiality.
 Delivering quality services with skilled motivated inspired, ethical and presentable
staff supported by modern ITC.
 Fair treatment of staff.
 Committed to the welfare of the community.
 Committed to team spirit and team work
2|Page
2. Background
Arba Minch OMO micro finance was established in October 1997E.C, aiming to
feel the gap of formal institutions to meet the need of small-scale borrowers in
income generation schemes and it was legally registered by the National Bank of
Ethiopia, according to ProclamationNo.40/1996.Currently it operates in the
following towns of the Southern Nations and Nationalities Peoples Regional State
(SNNPRS):
• Arbaminch (Gamogofa Zone);
• Hossana (Hadiya Zone);
• Durame (Kembata, AlabaTembaro Zone);
• Wolkite (Guraghae Zone);
• Bonga (Kafa and Sheka Zone);
• Awassa (Sidama Zone);
• Dilla (Gedio Zone);
• Mizan (Bench Maji Zone);
• Sodo (Wolaita Zone).
The Institution will continue operating in the SNNPRS now it Covered 60
Woredas, 11 Branches, 80286 Clients Served so far.
3|Page
3.Statement of the problem

Currentlythere are plenty of problems in Arab MinchOMOmicro finance institution.Among
these the main problems are:-
1. Security
2. File management
3. Work efficiency etc.
4. Project Objective
4.1 General objective
The general objectives of this project are:-
 To developArab Minch OMO micro finance online system
4.2 Specific Objectives
 To develop data base for registration of customers
 To develop application to saving, debit and credit activities.
 To develop application that can calculate interest for customer account
 To create accessibility of customer information
 To generate the report
 To develop security mechanism
 To design interactive user interface
5. Scope of the project

The following are the major components of the system will be address through the project:
 Customer relation management (that means the range from handling each
information’s about the customers involved in saving and loan
 account.)
Our project will focuses on the following activities:
 Saving Account
 Loan
 Customer registration
4|Page
 Interest calculation
 Withdrawing money
 Report generation
5.1. Limitations
Our project will have the following limitations
 Language constraints
 Database connection with commercial bank of Ethiopia
6. Feasibility Analysis
To bring the successful completion of this project goals and objectives the feasibilities issues
listed below has determined the project viability or the discipline of planning, organizing,
and managing resources analysis.That includes:-
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
6.1 Technical Feasibility

The entire group members are expected the system to be technically feasible. The system is
going to be developed by technological development technique such as PHP, java script,
CSS. And the team has the ability to develop this system without any difficulty since the
team has studied the required methodologies and tools. So the system will be technically
feasible.
6.2 Operational Feasibility

The entire team member, expect that the system which is in development is to be operational.
That is once the system is deployed, it can operate on any of the operating systems. Our
project also has security to gives access privilege providing account for an authorized person.
The system also have user manual to easily use the system. This project is surly operational
feasible because the proposed solution maker of the problem.
6.3 Economic Feasibility
Economically the proposed project does not cost much more and also the material to be
implemented the system do not cost a much amount of money
5|Page
Since this project is going to be computerized there will be reduction of material costs used
by institution for manual operation like paper [pencil pen human power space needed to store
documents and the time that the employee consumed during the manual system.
Cost reduction for materials
Cost of existing system
Material cost for existing system

Item Quantity per year/cost Unit price/birr
Price/salary
Pencil 20 1.25 25
Paper 70 90 6300
Pen 60 4 240
Labor cost 8 1500(average cost) 12000
Table 14 180 2520
Chair 6 300 1800
Shelf 6 800 4800
Ticket and receipt 60 packet 56 3360
Total 31045 birr
material cost
Table Material cost for existing system
Cost of new system
Material cost for newly developed system

Item Quantity per year/cost Unit price/birr
Price/salary
Cable 5 56 672
Divider 7 65 455
CD-ROM 2 8 16
Labor cost 4 2000(per average) 8000
Sockets 4 80 320
Chair 3 300 900
Paper 4 90 360
Printer 1 4500 4500
Dell computer 4 10000 40000
Total material cost 54413
Table Material cost for new system
Cost variation between existing system and after deployed money required for payment.
6|Page
54413birr-31045birr=23368 birr
The total profit of the new system is equal to 23368 birr
Tangible benefits
 Reduction of paper and pen.

 Reduction of man power /number employee.
 Customer records are organized in a proper manner.
 Making errors are reduced

Intangible benefit:
 Give better and effective service

 Error reduction
 Increase security
 Increase speed
7. Methodology
7.1 Data Collection mechanisms
7.1.1. Document analysis

Studying the documents that are used in the past; it enables us to get more information in
order to understand about problems with the existing system, organizational directions, rules
for processing data, etc.
7.1.2. Interview
Interview the employee and customers to have reliable and clarified information from users,
managers, workers of the institution. It will be used to assure the information which is
observed from documents, forms and reports, etc.
7.1.3. Observation
This will be used in order to analyze the conditions to which the existing system is acting. It
is useful to observe how jobs are done, how information flows directly observe user.
7|Page
8. Soft ware and Programming Tools
After having all the required data and information, we will use different software programming tools in
order to design and to represent the new system.
Activities Tools/ Programs
Client side coding HTML/DHTML
Client side scripting JavaScript
Database server MySQL
Web server XAMP SERVER
Server-side scripting PHP
Browsers Google chrome, Mozilla Firefox 3.0
Design tools E-draw, DFD
Documentation MS office
Table 1 Development Environment and Programming Tool
9. Security and access permission
9.1. Description of the existing system
 It is less secure because of paper based operation

 Inappropriate timing of the loan disbursal and repayment
 Unauthorized access to the system because weak security system was provided.
8|Page
9.2 Description of the new system
 Only users holding the role manager can manage contents of the web site and
maintain system user’s profile.
 Our system secured means un authorized body cannot damage the system and system
resources.
 The system permits the administrator to edit customer and clerk’s information.
 Login is must
 An employee (Accountant, Casher, Manager) to be able to use this system, he/she
has to enter
 The user must have a valid username and password. Everything is done in the
database created by the system
 Username and password which he/she has assigned when create an account. To use
this functionality.
9|Page
10. Team Composition
Project
Title
ARBA MINCH OMO on line micro finance Institution
NO Prepared By: Phone number Responsibility
1 TEKLU HAILU RET/ICT/118/03 All activities

0912247300
2 EMUNESH TAMIRE RET/ICT/049/03 All activities

0913226383
3 MITIKU YOHANNES RET/ICT/088/03 0921005816 All activities
4 GEREMEW GESHARTO RET/ICT/061/03 All activities

0910964757
5 KUMA CHUFA RET/ICT/074/03 0934818057 All activities
Table 2 Team Composition
10 | P a g e
11. Time schedule

Nov Dec Jan Feb March Apr Apr May May
(1-30) (1-30) (1-30) (1-30) (1-30) (1-15) (15-30) (1-15) (15-30)
Data collection
Requirement
Analysis
Design
Coding
Testing
Verification
Documentation
Table Time schedule
11 | P a g e
12. Cost breakdown
Item name Quantity Unit price Total price
Paper 2 packet 800 birr 1600birr
Pen 20 5 birr 100 birr
Print 400 pages 2 birr 800 birr
CD-RW 6 15 birr 90 birr
Mobile card 20 50 1000
Transport - 2.50 400
Total price 3990birr
Table 4:- Cost breakdown
12 | P a g e
Chapter Two
Descriptions of the existing system
2.1 Introduction of existing system

The current system of ArbaminchOmo Micro finance is manual. Let see how the finance
department work manually, in this department there are two basic things Opening Saving
Account and Giving loan services.
We have tried to study the detailed nature and procedure of the tasks and operations
performed by the OMFI regarding the saving account, loan and the relationship maintained
between them in the system.
Generally, the main issues of this chapter concern’s on describing the major functions of the
existing system (with Inputs, Processes and Outputs), players in the existing system, business
rules, the report generated by the existing system, the forms and documented used in the
existing system, the problems of the existing system, practices to be preserved from the
existing system, the option analysis and essential modeling and system requirements of the
system (both functional and non functional).
2.2 Players in the Existing System
Player or actor refers to a person, organization, or external system that plays a role in one or
more interactions with the existing system. The major actors or players that are involved in
the existing system are the following:
Customer: A person/ an organization that needs services from the OMFI. The main player
that interact with the system in order to open account, make deposit, to get loan.
13 | P a g e
Signature Verifier: An employee who check the validity of customer’s signature by

comparing the signature on the voucher with the signature on the specimen signature card.
Casher: Interact with the system in processing the demand of the customer during deposit..
Supervisor: Supervises the overall activities of employees.
Auditor: An Employee who checks the whole day-to-day activities.
Loan Officer: An Employee who determines the borrowing capacity of the borrower (customer).
Manager: An employee who manages and controls the activities of the OMFI.
2.3Major Functions in the Existing System like to inputs, processes &outputs

At first the customer to get services, he/she is expected to make visit to the OMFI to get the
service of his/her choice. Since the OMFI deals agreements with the legal person and
organization. If the customer deals the agreement, then there exists a relationship with the
OMFI. Once the relation exists the customer is expected to contact the manager. The
manager has to interview the new customer what type of service he/she want. If the service is
loan the customer is expected to contact the loan officer. If the service is saving the customer
is expected to contact the manager.
We will describe the major functions performed in the OMFI with Input, Process and Output
as follows: -
2.3.1 Opening Saving Account
Input:
o Customers need to have Renewed ID card for individuals.

o Two passport size photographs
o Deposit voucher form with the minimum of 20 birr as initial deposit.
o Appropriately filled Saving Account Opening Form
o Four (4) signatures each on two specimen signature card
Process:
14 | P a g e
o The customer fills opening saving account

o Signature Verifier check the filled information on Saving Account Opening Form, the
ID Card/ the license and verifier appropriateness of signature on the specimen
signature card
o The Supervisor checks the validity of the overall process
o The Casher receives the initial deposit.
o At the last, Supervisor registers the Customer in the Register Book.
Output:
o Customer gets Passbook.

o Customer has an Account.
o Become official Customer of the OMFI.
Loan
A process by which an individual or an organization is borrowed certain amount of money

from the OMFI.
Loan has different forms/types:
Short Term: a loan type by which an individual or an organization is going to borrow for a short period
of time that ranges from one year to five year.
Medium Term: ranges from seven to ten years. You can borrow in order to purchase
something like means of transportations and machines.
Long Term: is allowed for ten years. This loan is for huge business like real estate.
the current loan interest is:
Short Term 8.5 %
Medium Term 9.0 %
Long Term 9.75 %
15 | P a g e
Input:-
o Salaried or business man borrower (Customer). This enables the OMFI to determine
the borrowing capacity of the borrower.
o The borrower (customer) with guarantee means a fixed asset to ensure the OMFI that
borrower will return the borrowed money).Which contains full information about the
Customer.
o Singed loan agreement format (the format implies the changes of the interest; the
change is made by OMFI based on the current country economy, business activity and
fluctuation money).
Process:-
o Customer requests for loan

o Loan officer receives all the required documents
o Loan Officer checks the appropriateness of the documents.
o The Loan Officer determines the borrowing capacity of the Customer by business rule
OMFI.
o The Manager confirms the document and sign (initiate) on the form.
o The customer registered
Output:
o The Customer gets the requested money from the teller.

o The Customer gets the Loan Coupon sheet.
2.4 Business rule

Business rule is a rule in which the organization uses it to perform any activities. Hence any
activities are expected to be valid with respect the rule. A rule often focus on access control
issue, may also business calculation, policy of the organization.
Identifier: OMFI001
16 | P a g e
Name: any applicant should have an ID and Valid license
Description: In order to get a service from OMFI, every applicant needs to have an ID and
valid license for organizations.
Saving Rule
Identifier: OMFI002
Name: Initial deposit should be at least 10 Birr
Description: For saving account the minimum amount of initial money to be deposited (To
open an account) is 10 birr.
Identifier: OMFI003
Name: The person should be at least age of 18
Description: for saving account the minimum age to depose (To open an account) is 18
Identifier: OMFI004
Name: The rate for saving=3.4% [not fixed]
Description: for saving account the rate is 3.4%.
Identifier: OMFI005
Name: the interest payment
Description: for the interest on the saving account can be calculated as
Principal * Rate * Time
Where principal= the minimum balance.
Rate=refer OMFI004 (to calculate the interest at a rate of 3.4 %)
Example:
17 | P a g e
Let us take the minimum balance picked is 4200, and then to calculate interest at a rate of
3.4% will be
4200 X 3.4/100 X 1/12=11.9
Loan Rules
Identifier: OMFI006
Name: Customer should have a collaborator
Description: Customer should have a fixed asset to loan
Identifier: OMFI007
Name: Customer has to pay a loan with in specified time and amount
Description: If customers are not going to pay the specified monthly amount and to pay his
or her loan for consecutive of three months the OMF I will bid the collaborator.
Identifier: OMFI008
Name: Marital status
Description: If the Customer is married then his wife/ her husband should know the case
Identifier: OMFI009
Name: short term loan
Description: short term loan to the customer is 10,000 birr.
Identifier: OMFI010
Name: Medium term loan.
Description: Medium term loan to the customer is 50,000 birr.
Identifier: OMFI011
18 | P a g e
Name: Long term loan
Description: Long term loan to the customer is 100,000 birr.
2.5 Report Generated in the Existing System

These are reports generated for the manager, this enables the manager to control and
supervise the daily, monthly and annual activities of the OMFI.
2.6 Forms and other documents

1. Saving Account opening form
o Saving Account opening form used to receive required information from new
customer and the form contain the following fields
o Date ,Full Name, Nationality, Address, Woreda, Kebele, House No, Town ,
o Initial deposit Birr, Applicant(s) Signature Opened By, Approved By, Remark
Fig saving form
2. Loan form
o Loan form is used to receive required
19 | P a g e
o Guarantee letter , amount of loan birr , information from new customer and the form
contain the following fields
o Date ,Full Name, Nationality, Address, Woreda, Kebele, House No, Town ,
o Applicant(s) Signature,Approved By, Remark
Fig loan form
3. Subsidiary ledger card
20 | P a g e
Fig Subsidiary ledger card
4. General Ledger card
Fig General Ledger card
21 | P a g e
2.7 Bottlenecks of the existing system Using PIECE framework

2.7.1 Performance Related problem
o When the number of customer increases the response time of the system serving the
customers will decrease because the system performs its tasks manually.
o The productivity of the organization is not effective.
o The work procedure is prone to error.
2.7.2 Information related problem

Information (and Data)
Output:-
o Generating report requires more skilled experience and greater attention.

o The report may encounter inaccuracy as needed.
o Inaccuracy in updating relevant information by knowing or without knowing and
calculating interest (balance) since manual processing is prone to error.
o Data is not flexible – not easy to meet new information needs from stored data.
Input:-
o Redundant information is captured. Customer information is registered in various

cards again and again for example on register book, spaceman signature card.
o The inputs are not validate( i.e. the system cannot check whether the customer has
account before )
o Mishandling of customer information may be occur
Storage:-
o Information that is not in a useful format.

o Information that is difficult to produce (manipulate).
o Data is difficult to correct and maintain.
o Data is stored redundantly in multiple files.
22 | P a g e
o Data is not secure from accident or vandalism (damage).

o Data is not well organized.
o Data is not easily accessible.
2.7.3 Control related problem

o Here the reliability is under big question [i.e. the problem encounters due to the
exhaustion of the employee’s maters the organization].
o Security is another big issue concerning manual based system.
2.7.4 Efficiency related problem

o Since the work is performed manually the efficiency of the working system is that
much not good.
o As the amount of the customer increase the waiting time of the customer will be
increase.
o The resource of the customer and department is being waste. [Time, Money,
stationary materials like Pen, Pencil, Papers etc...].
o Since the data is stored in redundant manner, the information generated also is
redundant.
2.7.5 Economic related problem

The departments need many employees and hence it forced to pay huge salary.
Manual handling of data is expansive as compared to automated system. Cost in terms of

time is high. In addition to that it needs more stationary materials due to data duplication,
errors, and storage as number of customer increase.
2.7.6 Service related problem

The customers do not get better service as they need, then they may shift to other good
service providers so that the profitability of the OMFI decreases.
2.8. proposed solution for the new system that address problem of the existing system
After we have analyzed the existing system we decide to computerize the existing system,
the main aim of this project is developing system wise working environment. We have
23 | P a g e
selected the option, which is to computerize the system as a solution for the system. This
emphasizes on making and handling the loan and saving activities by using computers and
making the system centralized:-
In general when it is applied the system will have:-
 better utilization of resources,

 performance
 security
 reliability and
 accuracy
Advantage
o Data can be shared.

o Improved accessibility of data.
o Redundancy can be reduced.
o Quality data can be maintained.
o Inconsistency can be avoided.
o Integrity can be maintained.
o Security measures can be enforced.
o Centralized information control.
o Speed, less labor, compactness.
Disadvantage
o needs skilled professional

o Introduction of new professional and specialized personnel.
o Complexity in designing and managing data.
2.9. Requirements of the proposed system

2.9.1. Functional Requirements
The functional requirements of our system includes:-
24 | P a g e
o Updating customer Account (balance)

o Calculate Interest and withdrawal money
o Change Information
o Change employee information
o Generate Account Number
o Generate saving and loan report
2.9.2 Non Functional Requirements
Performance: more effective when compared to the manual approach, resulting in fast
accomplishment of task with in some amount of time [Performance / Response time]. And
also the system should work properly with its storage capacity, accuracy, speed and the likes.
But its performance may be affected by connection lose, electric power problem (It has less
power consumption when it compare to its work.
User Interface: the user interface of the new system should be user sociable (easy to work
and interact), or user friendly for both technical and non technical work. Its application will
be accessed through a Browser Interface. The software would be fully compatible with all
type of browser like Microsoft Internet Explorer and Mozilla Firefox.
Security and Access permission: In order to make the system safe from unauthorized
access and modification:-
 The system uses a log in account to differentiate among the different users of the
system on the organization side. This enables the system to verify who has logged in
using the correct logging account provided and display the right form associated with
that user.
 Access is controlled through proper password verification facilities which the
database and the server require.
 The security service provided by the system will maintain the security, confidentiality
and integrity of the system. Security is addressed using proper authentication.
Generally this system introduces a proper authentication and accountability through
proper authentication requirement to that aspect.
25 | P a g e
Authorization is the mechanism by which a system determines what level of access

particular authenticated official should have to secure resources controlled by the system.
 The proposed system provides authorization facilities and finding the authorized
person to perform on it, i.e. for the actors of the system there is a password and user
name to do their task according to their privilege that is given.
Backup and Recovery: efficient every week. Our system will backup using external drives
like CD, DVD, and Flash. We use documents and forms of finance department, drawing
software and also employees who works in finance department.
Resource: consumes less resource like time, power needed to perform the task. For our SQL
and other code we use logical backups. Logical backup save information represented as
logical data base structure and also this back up done by querying the MYSQL server to
obtain data base structure and content information.
Chapter three
System analysis
(Modeling of the existing and proposed system using the chosen methodology)
3.1 Introduction
Before we begin the proposed system it is necessary to deal the system that will be
developed.
26 | P a g e
After that we established this system in order to solve the problem that found in the existing
system. Our system helps the customer easily to use the service.
The system will have better utilization of resources, performance, security, reliability,
accuracy and in general better service grant.
3.2.System requirement specification (SRS)
3.2.1. Actor Identification:-
o Administrator: -a person who manage the system access right for other users and
managing overall activities of the system.
o Clerk:–a person whose job is manage saving money
o Operator: - a person who control the loan activities
3.2.2. Use Case Diagram
27 | P a g e
28 | P a g e
3.2.3. Documentation of new System in Use Case Diagram
1. Name: Login
Description: Entering to the System
Identifier: L123
Precondition: Have to have User Name & Password
Post Condition: Access to the System
Basic Course of Action
1. The Employee log in to the system

2. The Employee opens the system
3. The System asks for username and password
4. The employee Enter username and password
5. employee click Login button
6. The System check the entered value
7. The system displays the main form of the software
8. The employee has granted to act on the system
Alternative course A: Invalid Username & Password
A.1: The System Displays “Sorry Enter correct Username or Password”
A.2: The System asks the employee to enter Username and password for three times
consequently after that the use case Ends else It continues at step5 in the basic course of
action
2. Name: Open Saving Account

Identifier: OS123
Description: Open saving account for new customer
Precondition: The clerk logs in to the system
The applicant has fulfilled all the requirements
Post condition: The applicant will become a customer with account
1. The clerk log-in to his/her page
29 | P a g e
2. The system display to enter his/her correct user and password

3. Click login button
4. The system displays the registration form
5. The counter clerk fill the required information
6. The clerk clicks on “save” button
11. The System checks that all the required information are entered
Alternative Course A: Invalid ID
A.1: The Applicant will be ask to renewed his/her ID or renewed License

A.2: The Use case ends
Alternative Course B: Not properly filled
B.1: The applicant asks to fill out the form again
B.2: If applicant’s initial deposit is less than expected then customer ask to change
B.3: The use case continues at step 4 in the basic course Action
Alternative Course C: Not properly filled in the system or initial deposit is <10
C.1: The system asks the clerk to fill all the requirements
C.2: If Initial Deposit is <10, then the system asks to Change it
C.3: The clerk fills all the requirements
C.4: Use case continues at step 11 in basic course action
3. Name: Opening Loan account

Description: Customer borrowing money from the OMFI
Identifier: L123
Pre-condition: Has to be approved by Loan Officer and
Post Condition: The applicant will be legal customer.
1. The Operator log-in to his/her page

3. Operator login button
4. The system display loan card form
5. The operator fills the required information
6. The System check the validity of the filled out information
30 | P a g e
7. The operator click Save button

8. The Operator gives coupon (which contains Account Number and the amount of
money) to the customer.
9. The Operator tells the customers to receive his/her loan from the Teller.
Alternative Course A: Not properly filled in the system
A.1: The system asks the operator to fill all the requirements
A.2: The operator fills all the requirements again
A.3: Use case continues at step 7 in basic course action
4. Name: Withdrawal money

Description: this process is initialized when the customer need to with draw money from his
account from the micro finance.
Identifier: Wd002
Actor: clerk
Precondition: customer should be registered and should have saved account
Postcondition: If the customer fulfills all the requirements then they can withdrawal money
from the OMO micro finance.
Basic course of action
1. The clerk selects his/her login page
2. The clerk successfully logged in
3. Clerk should fulfill the requirements
4. The clerk should search for the existence of his/her account
5. The clerk checks whether the customer fulfill the requirements entered the attributes
6. The system validate the given information
7. The system calculates and set the account balance of the client after the withdrawal
8. If the required information is provided and validated then clerk will withdrawal the money
for the customer
9. End process
31 | P a g e
AlternativecourseA6: If the customer did not fulfill the requirements (not registered and
have no saved account), then he/she cannot withdraw money.
A7: use case end
5. Name: Return lone money

Description: Customer pays the money that he loaned from the OMFI
Identifier: LP123
Pre-condition: Has to have coupon
Post Condition: System Updates customer loan
1. Clerk select debt

2. The clerk successfully login
3. The customer should come to return and with the interest (from the day he/she loaned
to the come to return.
4. The clerk enter the money with the calculate interest value to the system
5. The system validated whether the given information is true or not.
6. The system calculates the return balance and adds it to the micro finance balance and
subtract the return money from the balance other than the interest
7. End process
Alternative Course A: A6 the client will not be fulfill the required data for returning the
transaction cannot operate
A7. If the customer has not loaned money the process cannot take.
6. Name: Registering Employee

Description: Entering the Employee (admin, clerk or operator) to the System
Identifier: RE123
Pre Condition: Has to be employed in OMFI
Post Condition: Employee enter to the System
1. The Admin log-in to his/her page

32 | P a g e
4. Admin click Registor_admin,Registor_clerk and Registor_operator.

5. The System Open the Employee Registration Form
6. The system asks to enter the employee user name, password and to Re_enter
password.
7. Click Add button
8. The System Checks the Proper fulfillment
9. The system display successfully register
10. The Employee will have user name and password
Alternative Course A: If it is not properly filled
A.1: The System asks the Admin to fill the form again
A.2: Use case continue at step 7 in the basic course of action
7. Name:Change employee Password

Description: Changing Existed Employee (admin, clerk or operator) Password
Identifier: CP123
Precondition: Have to have Password
Post Condition: Changed Password
1. The Admin log-in to his/her page

4. Admin log into the system
5. The Admin clicks “Change Password for operator, clerk and admin
6. The system displays Change Password form
7. The System asks to enter user name ,current password, enter new password and its
Confirmation
8. Click Update password button
9. The System Displays Successfully Changed password
Alternative Course A: Invalid username and Password
A.1: The system asks the customer to enter his correct username and password
A.2: Use case continue at step 8 in basic course of action
Alternative Course B: If Password Mismatch
B.1: The System Displays new password mismatch
33 | P a g e
B.2: Enter the password Again
B.3: Use case Continue at step 8 in the Basic Course of Action
8. Name:Update customer information

Description: Changing customer information
Identifier: CP123
Precondition: Register customer
Post Condition: updated customer information
1. Click login clerk button from the home page

2. The Clerk log-in to his/her page
5. The System Validates entered information
6. The system displays saving card form
7. Click generate saver report form at the right side of clerk page
8. The system display generate report page of saving card
9. Click edit button at the right side of displayed table
10. The System Displays update saving card form
11. The clerk can edit the customer correct information
12. Click save button
13. The System validates the entered information
14. The System Displays Successfully updated
Alternative Course A: Invalid customer information
A.1: The system asks the clerk to enter his correct customer
A.2: Use case continue at step 11 in basic course of action
Alternative Course B: If Password Mismatch
B.1: The System Displays new password mismatch
B.2: Enter the password Again
B.3: Use case Continue at step 12 in the Basic Course of Action
9. Name: Generate Saving Report

Description: Generate Report of the transaction made
34 | P a g e
Precondition: the report generator should be Admin
Post Condition: Generate Saving Report
1. Admin wants to audit the transaction made

2. system display report generator report form
3. The Admin enter the required information
4. the system validate all the information
5. The System Generates Report
6. use case ends
10. Name: Generate Loan Report

Description: Generate Report of the transaction made
Actor: Admin
Precondition: the report generator should be Admin
Post Condition: Generate Loan Report
Main Flow
1. Admin wants to identify which customer performs its duty and which one is not.
2. The system display report generator form
3. The Admin enter the required information
4. the system validate all the information
5. The System Generates loan Report
6. use case ends
35 | P a g e
3.3. Sequence diagram
1. Sequence Diagram for login
36 | P a g e
1. Sequence diagram for open saving account
37 | P a g e
2. Sequence diagram withdrawal/debtmoney
3. Sequence Diagram for return ( withdrawal) money
38 | P a g e
4. Sequence diagram for employee registration
39 | P a g e
5. Sequence diagram for change password.
40 | P a g e
41 | P a g e
6. Sequence diagram for generate saving report
42 | P a g e
7. Squence diagram for generate loan report
3.4 Activity diagram

1. Activity diagram for login
43 | P a g e
Employees System
Provide Login
Click On Form
Login Button
Enter Id and
Password False
Is
Valid(ID,Password)
Click on O K
Button True
Select The Display Main

Required Activity Page
44 | P a g e
2. Activity diagram for open saving account
45 | P a g e
3. Activity diagram for opening loan account
46 | P a g e
4. Activity diagram for loan credit/withdrawal money
47 | P a g e
5. Activity Diagram for loan debit/payment
6. Activity diagram for employee registration
48 | P a g e
49 | P a g e
7. Activity diagram for changing password
8. Activity diagram for generating saving report
50 | P a g e
9. Activity diagram for generate loan report
51 | P a g e
3.2.5 Class diagram
52 | P a g e
53 | P a g e
3.6 User interface prototyping
3.7 Supplementary specifications

o Any customer have passbook.
o Any customer visit OMFI to contact the manager
o The customer provided all activities
54 | P a g e
CHAPTER FOUR
4. SYSTEM DESIGN
4.1. Introduction
This chapter mainly focuses on how the system is going to be built. The purpose of designing
is to show the direction how the system is built and to obtain clear and enough information
needed to drive the actual implementation of the system. Here Object Oriented Design
(OOD) methodology is used for transforming the analysis model into design model. This
serves as a blue print for the construction of the software.
The following topics are included in this chapter:-
1. Class type Architecture

2. Design Class Modeling
3. Class Documentation
4. State Chart Diagram
5. Collaboration Diagram
6. Component Diagram
7. Deployment Diagram
8. Relational Persistence model
9. User interface
4.2. Class Type Architecture
4.2.1. Layered class type architecture
55 | P a g e
4.2.2. User interface layer

The following are the User Interface (UI) Classes:-
A. Logged in Administrators
 Main Page(Window)
 Login
 Register employee
 Changing password
B. Logged in Operator
 Main Page (Window)
 Login
 Loan account form
 Enter user information
C. Logged in as Clerk
 Main window
 Login
 Saving account for saver
 Enter user information
4.2.3. Controller/process Layer
The OMFI has the following controllers:-
 Login
 Enter user information
 Changing password
 Check user information
 Register user
 Update user information
 Store user information
 Display the user information
 Business/Domain Layer
4.2.4. Business/Domain class
The following are the Business/Domain classes
 Clerk
 Operator
 Admin
 Saving and Loan account
 Generate report
 Calculate interest
 Withdrawal and return money
56 | P a g e
4.2.5. System layer:-provide operating-system-specific functionality for our

applications, isolating our software from the operating system (OS) by
packaging OS-specific features, increasing the portability of our application
4.2.6. Persistence: - provide layers encapsulate the capability to store, retrieve, and
delete objects/data permanently without revealing details of the underlying
storage technology in the system. . For instance, our system uses MySQL
database.
4.3. Class Modeling
57 | P a g e
4.4. State chart

4.4.1. State chart for saving account form
Account Login
Saving form
Save Fill information
4.4.2. State chart for loan account form
login to th
Account Loan form
Login
Loan Fill information
58 | P a g e
4.5. Collaboration modeling

4.5.1. Collaboration modeling for login
Admin Micro-finance Login Form

System
Enter Id and Password
Error message if user

Login
Omit either id or password
controller
If valid go to main page
Check Id and Password
Errormessage if
invalid id or password
Data base
59 | P a g e
4.5.2. Collaboration diagram for opening saving account
Microfinan Open saving

Operator ce System
Account form
Enter the requires information
Error message if the
Information unknown
Security-controller
If Valid display Successful message
Error message if Check the information
invalid information
Data base
60 | P a g e
4.5.3. Collaboration modeling for open loan account
Operator
Microfinan Open loan
ce System Account form
Enter the required information
If valid display loan number

Security
controller
Error message
if invalid information
Check the information
Data base
61 | P a g e
4.5.4. Collaboration modeling for return money
Operator
System Loan debit
form
Enter loan number and
amount
If valid display loan number and account

Security
controller
Error message if invalid
number and amount Check the loan number and
amount
Data base
62 | P a g e
4.5.5. Collaboration modeling for registration
Clerk Micro finance

Registration
System form
Enterinformation
If valid display successful message Security

controller
Error message Check the information
if invalid information
Data base
63 | P a g e
4.5.6. Collaboration modeling for change password
Admin Micro finance

Change
System password form
Enter user name and password
Security
If valid display successful message controller
Error message
if invalid user name check the user number and Password
and password
Data base
64 | P a g e
4.5.7. Collaboration modeling generating saving report
Micro finance
Admin Generate
System saving report
form
Enter query
If valid the report display the report

Security
controller
Error message check query
if invalid query
Data base
65 | P a g e
4.5.8. Collaboration modeling for generating loan report
Micro finance
Generate
Operator System loan report
Enter query
If valid display the loan report Security

controlle
Error message r
if invalid query check query
Data base
66 | P a g e
4.6. Component Modeling

Our component modeling describes components of our system such as operator,
administrator, and clerk and how can they interact with each other depending on their
functionality, and what is there common function that can share by all the components of
our system It can also describe the interaction of our system components with the security
control system.
4.7. Deployment modeling
67 | P a g e
We use deployment modeling diagram to show our systems static view of the run-time
configuration of processing nodes and the components that run on those nodes. The
following figure shows our deployment modeling diagram to our system.
68 | P a g e
4.8. Persistence modeling
69 | P a g e
4.9. User interface

4.9.1. Home page
70 | P a g e
4.9.2. Admin login page
4.9.3. Operator login page
4.9.4. Clerk login page
71 | P a g e
4.9.5. Saving Card form for Personal Tax
72 | P a g e
4.9.6. Credit Card form for Personal Tax
73 | P a g e
Chapter 5
5. Coding
5.1. Home page code
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!DOCTYPE html>



<html lang="en" class="no-js">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<script type="text/javascript" language="javascript">
functiondisableBackButton(){
window.history.forward()}
disableBackButton();
window.onload=disableBackButton();
window.onpageshow=function(evt) { if(evt.persisted) disableBackButton() }
window.onunload=function() { void(0) }
</script><meta charset="UTF-8" />

<title>Login and Registration Form with HTML5 and CSS3</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Login and Registration Form with HTML5and
CSS3" />
<meta name="keywords" content="html5, css3, form, switch, animation, :target,
pseudo-class" />
<meta name="author" content="Codrops" />
<link rel="shortcut icon" href="../favicon.ico">
<link rel="stylesheet" type="text/css" href="css/demo.css" />
<link rel="stylesheet" type="text/css" href="css/style.css" />
<link rel="stylesheet" type="text/css" href="css/animate-custom.css" />
<title>Omo Microfinance</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link href="style.css" rel="stylesheet" type="text/css" />
74 | P a g e

</head>
<body>
<div id="main">
<div id="header"><imgsrc="images/logo.jpg" width="610" height="130"
alt="Catchinfo" />
</div><div id="body">
<div id="left">
<ul><li><a href="index.html" class="home">Home</a></li>
<li class="li1"><a href="contact.html" class="contact">Contact</a></li>
</ul></div>
<div id="mid">
<br /><br /><br /><br /><br /><br /><br />
<h3 align="center">Arba Minch OMO Micro finance Online System</h3>
<p class="nibh"> Microfinance refers to a variety of financial services that target low-
income clients, particularly women. Since the clients of microfinance institutions
(MFIs) have lower incomes and often have limited access to other financial services,
microfinance products tend to be for smaller monetary amounts than traditional
financial services. These services include loans, savings, insurance, and allowances. A
bank is a financial institution and a financial intermediary that accepts deposits and
channels those deposits into lending activities, either directly by loaning or indirectly
through capital markets.</p>
<span><h3 align="middle">Vision</h3></span><p class="nibh">The Vision of OMFI
is in the year 2018 G.C to see a society in which people are free from the grips of abject
poverty, with all
the power determining their future in their own hands, and its own capacity as an
institution well developed to provide best services for all in need in a sustainable
manner.</p>
<span><h3 align="middle">Mission</h3></span><p class="nibh">The mission of
OMFI is to improve the economic situation of low income, productive poor people in
the Southern Nations and Nationalities Peoples Regional Sate region through increased
access to lending and saving services. It will maintain cost effectiveness in service
delivery, and integrates its activities with government and NGO's working towards
achieving food security and poverty alleviation in the region.</p>
<span><h3 align="middle">Values</h3></span>
75 | P a g e
<ul>
<li><p class="nibh">Treating customers with utmost respect, dignity and
impartiality. </li>
<li><p class="nibh">Delivering quality services with skilled motivated inspired,
ethical and presentable staff supported by modern ITC.</li>
<li><p class="nibh">Fair treatment of staff.</li>
<li><p class="nibh">Committed to the welfare of the community.</li>
<li><p class="nibh">Committed to team spirit and team work.</p></li>
</ul></div>
<div id="right_bg">
<ul><li><a href="aboutus.html">About us</a></li>
<li><a href="service.html">Services</a></li>
<li><a href="loginadmin.php">Login Admin</a></li>
<li><a href="loginoperator.php">Login Operator</a></li>
<li><a href="loginclerk.php">Login Clerk</a></li>
</ul></div><br class="blank" />
</div></div>
<div id="bottom_table">
<div align="center"><imgsrc="images/online.gif" alt="online supportchart"
width="610" height="140" border="0" title="online support" />
</div><div id="footer">
<div id="footer_div">
<h2 align="middle">Designed by: AMU CS&IT 2008 Graduates </h2>
<h3 align="middle">Copyright:&copyAll right reserved.</h3>
</div></div>
</body>
</html>
5.2. Admin login page code
<!DOCTYPE html>
76 | P a g e
<head>
<?phpsession_start();
include('connect.php');
include('login_processadmin.php');
?><meta charset="UTF-8" />
<meta name="description" content="Login and Registration Form with HTML5 and

CSS3" />
<meta name="keywords" content="html5, css3, form, switch, animation, :target, pseudo-

class" />
<script type="text/javascript" src="custom.js"></script>
<?php
include('login_processadmin.php');
?></head>
<body>
<div id="main"><div id="header"><imgsrc="images/logo.jpg" width="610" height="130"

alt="Catchinfo" />
<div id="left"><ul>
<li><a href="index.html" class="home">Home</a></li>
</ul></div>
<div id="mid">
<br /><br /><br /><br /><br /><br /><br /><br /><br />
<form method="POST" action="loginadmin.php">
<fieldset><legend><h4>Admin Login Page:</h4></legend>
<table><tr>
<td>UserName:</td>
<td><input type="text" size="30" name="username"></td>
</tr><tr><td>Password:</td>
<td><input type="password" size="30" name="password"></td>
</tr><tr><td>
<input type="submit" name="submit" value="Login"></td></tr>
78 | P a g e
</table></form><font face="arial, Times, serif" color="#CC0000"><?php echo $message; ?

></font>
</fieldset></div><div id="right_bg">
</ul></div><br class="blank" /></div></div>
<div align="middle"><imgsrc="images/online.gif" alt="online supportchart" width="500"

height="140" border="0" title="online support" />
<div id="footer_div"><h2 align="middle"> Designed by: AMU CS&IT 2008 Graduates

</h2><h3 align="middle">©All right reserved.</h3>
</div></div></body>
</html>
5.3. Operator login page

<!DOCTYPE html>
79 | P a g e
<head>
<?php
include('login_processoperator.php');?>
<meta charset="UTF-8" />

CSS3" /><meta name="keywords" content="html5, css3, form, switch, animation, :target,
pseudo-class" />

</head><body>
80 | P a g e

alt="Catchinfo" />
<div id="left">
</ul></div>
<div id="mid">
<form method="POST" action="loginoperator.php">
<fieldset><legend><h4>Operator Login Page:</h4></legend>
<table><tr><td>UserName:</td>
</tr><tr><td>
</table></form>
<font face="arial, Times, serif" color="#CC0000"><?php echo $message; ?></font>
</fieldset></div>
<div id="right_bg">
81 | P a g e
</ul></div>
<br class="blank" />
</div></div>

<h3 align="middle">©All right reserved.</h3>
</div></div>
</body>
</html>
5.4. Saving card form code

<!DOCTYPE html>
<head>
<script type="text/javascript">
82 | P a g e
functionvalidateform(){
var a=document.forms["myForm"]["fname"].value;
var b=document.forms["myForm"]["spbn"].value;
var c=document.forms["myForm"]["addressvillage"].value;
var d=document.forms["myForm"]["groupno"].value;
var e=document.forms["myForm"]["cname"].value;
var f=document.forms["myForm"]["date"].value;
var g=document.forms["myForm"]["refno"].value;
var h=document.forms["myForm"]["deposit"].value;
var i=document.forms["myForm"]["withdrawal"].value;
var j=document.forms["myForm"]["interest"].value;
var k=document.forms["myForm"]["balance"].value;
var l=document.forms["myForm"]["datevol"].value;
var m=document.forms["myForm"]["rn"].value;
var n=document.forms["myForm"]["depositvol"].value;
var o=document.forms["myForm"]["withd"].value;
var p=document.forms["myForm"]["inte"].value;
var q=document.forms["myForm"]["balancev"].value;
var r=document.forms["myForm"]["cb"].value;
if(a==null || a==""){
alert("Value of Firest Name is blank");
return false;}
if(b==null || b==""){
alert("Value of Saving Pass Book No is blank");
83 | P a g e
return false; }
if(c==null || c==""){
alert("Value of Adress Village is blank");
return false; }
if(d==null || d==""){
alert("Value of Group No. is blank");
return false; }
if(e==null || e=="") {
alert("Value of Center Name No is blank");
return false; }
if(f==null || f==""){
alert("Value of Date is blank");
return false; }
if(g==null || g==""){
alert("Value of Ref. No is blank");
return false; }
if(h==null || h=="") {
alert("Value of Deposited Compulsary Saving is blank");
return false; }
if(i==null || i==""){
alert("Value of Withdrawal Compulsary Saving is blank");
return false;}
if(j==null || j==""){
alert("Value of Interest Compulsary Saving blank");
84 | P a g e
return false; }
if(k==null || k=="") {
alert("Value of Balance Compulsary Saving is blank");
return false; }
if(l==null || l==""){
alert("Value of Date Volentory Saving is blank");
return false; }
if(m==null || m==""){
alert("Value Ref No. VolentorySaving is blank");
return false; }
if(n==null || n=="") {
alert("Value of Deposited Volentory Saving is blank");
return false;}
if(o==null || o=="") {
alert("Value of WithdrawallVolentory Saving is blank");
return false;}
if(p==null || p==""){
alert("Value of Date of Interest Volentory Saving is blank");
return false;}
if(q==null || q=="") {
alert("Value of Date of Balance Volentory Saving is blank");
return false; }
if(r==null || r=="") {
alert("Value of Date of Comulative Balance is blank");
85 | P a g e
return false;
}}
</script>
<?php
session_start();
if(isset($_POST['submit'])){
include 'connect.php';
// escape variables for security
$fname = $_POST['fname'];
$spbn = $_POST['spbn'];
$addressvillage = $_POST['addressvillage'];
$groupno = $_POST['groupno'];
$cname = $_POST['cname'];
$date = $_POST['date'];
$refno = $_POST['refno'];
$deposit = $_POST['deposit'];
$withdrawal = $_POST['withdrawal'];
$interest = $_POST['interest'];
$balance = $_POST['balance'];$datevol= $_POST['datevol'];
$rn = $_POST['rn'];
$depositvol = $_POST['depositvol'];
$withd = $_POST['withd'];
$inte = $_POST['inte'];
$balancev = $_POST['balancev'];
86 | P a g e
$cb=$balance+$balancev;
$sql=mysql_query("INSERT INTO saving_card_client

(fname,spbn,addressvillage,groupno,cname,date,refno,deposit,withdrawal,
interest,balance,datevol,rn,depositvol,withd,inte,balancev,cb)
VALUES('$fname','$spbn','$addressvillage','$groupno','$cname','$date','$refno','$deposit','$w
ithdrawal',
'$interest','$balance','$datevol','$rn','$depositvol','$withd','$inte','$balancev','$cb')");
if(!$sql){
$message="coud not inserted, cheak again"; }
$message='<p style="text-size:10;color:green">Congratulations! You have successfully

Registore Personal Tax<p>'; }
Else{
$message="";}
?><meta charset="UTF-8" />
<title>Saving Card for Personal Tax</title>

CSS3" />

class" />
87 | P a g e

</head><body>

alt="Catchinfo" />
</div><div id="body"><div id="left">
<ul></ul>
</div><div id="mid">
<br /><br /><br /><br /><br /><br /><br />
<form name="myForm" action="clerkpage.php" method="POST" onsubmit="return

validateform()">
<fieldset><legend><h4>Saving Card for Personal Tax Form:</h4></legend>
<table border="10" bgcolor="pink">
<tr><td>Full Name</td><td><input name="fname" type="text" size="15"

/></td><td>Saving Pass Book No.</td><td><input name="spbn" type="text"
size="15"></td></tr>
<tr><td>Adress Village</td><td><input name="addressvillage" type="text"

size="15"></td><td>Group No.</td><td><input name="groupno" type="text" size="15"
></td></tr>
<tr><td>Center Name No.</td><td><input name="cname" type="text"

<tr><td colspan="4" bgcolor="blew" align="center">Compulsary Saving</td></tr>
88 | P a g e
<td>Date</td><td><input name="date" type="date" size="15" ></td><td>Refer

No.</td><td><input name="refno" type="text" size="15"></td></tr>
<tr><td>Deposited</td><td><input name="deposit" type="text"

size="15"></td><td>Withdrawal</td><td><input name="withdrawal" type="text"
<tr><td>Interest</td><td><input name="interest" type="text"

size="15"></td><td>Balance</td><td><input name="balance" type="text"
<tr><td colspan="4" bgcolor="blew" align="center">Volentory Saving</td></tr>
<tr><td>Date</td><td><input name="datevol" type="date" size="15" ></td><td>Refer

No</td><td><input name="rn" type="text" size="15"></td></tr>
<tr><td>Deposited</td><td><input name="depositvol" type="text"size="15"

></td><td>Withdrawal</td><td><input name="withd" type="text" size="15"></td></tr>
<tr><td>Interest</td><td><input name="inte" type="text"

size="15"></td><td>Balance</td><td><input name="balancev" type="text"
<tr><td colspan="4" align="right"><input type="submit" name="submit" value="Save"

></td></tr>
</table>
</fieldset>
</form>
</div><div id="right_bg">
<ul><li><a href="logout.php">Logout</a></li>
<li><a href="clerkpage.php">Saving Card for Personal Tax</a></li>
<li><a href="clerkpagegrouptax.php">Saving Card for Group Tax</a></li>
<li><a href="clerkpagenoncredittax.php">Saving Card for Non Credit Client</a></li>
<li><a href="clerkpageintitution.php">Saving Card for Institutional/NGOs Tax</a></li>
89 | P a g e
<li><a href="clerkgeneratereport.php">Generate Savers Report</a></li>
</ul></div>
</div></div>

</div></div>
</body>
</html>
5.5. Loan card form

<!DOCTYPE html>
<head>
<?php
include('login_processclerk.php');?>
<meta charset="UTF-8" />
90 | P a g e

CSS3" />

class" />


<?php
session_start();
include('login_processclerk.php');
?>
</head>
<body>
<div id="main">
<div id="header"><imgsrc="images/logo.jpg" width="610" height="130"
alt="Catchinfo" />
</div>
<div id="body">
<div id="left">
91 | P a g e

</ul></div><div id="mid">
<form method="POST" action="loginclerk.php" align="center">
<fieldset><legend><h4>Clerk Login Page:</h4></legend>
<table><tr><td>UserName:</td>
</tr><tr><td>
</table></form>
</fieldset>
</div><div id="right_bg">
</ul> </div>
</div></div>
<div align="middle"><imgsrc="images/online.gif" alt="online supportchart"
width="500" height="140" border="0" title="online support" />
</div></div>
</body>
</html>
92 | P a g e
Chapter Six
Conclusion
So far we were intended in analyzing the existing system of the OMFI up to proposing our
new system that solves the difficulties related to the existing system. To say something on
the existing system: it is running almost manually, hence it is highly exposed to the manual
related problems, like the productivity of the organization is not effective , the work
procedure is susceptible to error, Data is not flexible, Data is not secure as well as it is not
well organized. Since the work is performed manually the efficiency of the working system
is that much not good generally it degrades the effectiveness and efficiency of the system.
By having this over the existing system our aim was to build a new system that have greater
functionality that enhance effectiveness and efficiency related parameters on the system. By
keeping this in mind that the new system will “have greater usage on” or bring the existing
system fully functional.
To achieve our goal (to design new system) the project team has spent all of its time on the
project on performing the tasks individually and in group based on the schedule available.
The team has faced many challenges starting from the lab due to electric power loss, lack of
resources like time, and in the organization some of the employees were not interested to
cooperate or to provide as relevant information as we need i.e. they have threats on us to
provide the information we need with respect to security.
93 | P a g e
13 References
 http://www.mixmarket.org/mfi/omo/report
 OMO microfinance institution demote branch browser.
 Wisdom microfinance institution browser.
 Ethiopian proclamation No 40/1996
94 | P a g e

OMO PRJT Whole Document

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMO PRJT Whole Document

Uploaded by

Copyright:

Available Formats

Wolaita OMO Micro Finance Online System

8.1. Data collection mechanisms--------------------------------------------------------------------8

9.1. Description of the existing system ---------------------------------------------------------9

9.2 Description of the new system----------------------------------------------------------------9

2.7.6. Economic related problem----------------------------------------------------------22

3.5. Activity diagram------------------------------------------------------------------------------------43

3.5.1. Activity diagram for login--------------------------------------------------------------43

3.6. Class diagram----------------------------------------------------------------------------------------

3.7. User interface prototyping--------------------------------------------------------------------------

4.6. Component Modeling--------------------------------------------------------------65

SNNPRS Southern Nations and Nationalities

MYSQl structured query language

Table1; - List of Acronyms

3.Statement of the problem

5. Scope of the project

6.1 Technical Feasibility

6.2 Operational Feasibility

Cost reduction for materials

Cost of existing system

Material cost for existing system

Cost of new system

Material cost for newly developed system

The total profit of the new system is equal to 23368 birr

 Reduction of paper and pen.

 Customer records are organized in a proper manner.

 Making errors are reduced

 Give better and effective service

7.1.1. Document analysis

8. Soft ware and Programming Tools

Activities Tools/ Programs

Client side coding HTML/DHTML

Client side scripting JavaScript

Database server MySQL

Web server XAMP SERVER

Server-side scripting PHP

Browsers Google chrome, Mozilla Firefox 3.0

Design tools E-draw, DFD

Table 1 Development Environment and Programming Tool

9. Security and access permission

9.1. Description of the existing system

 It is less secure because of paper based operation

9.2 Description of the new system

10. Team Composition

NO Prepared By: Phone number Responsibility

1 TEKLU HAILU RET/ICT/118/03 All activities

2 EMUNESH TAMIRE RET/ICT/049/03 All activities

3 MITIKU YOHANNES RET/ICT/088/03 0921005816 All activities

4 GEREMEW GESHARTO RET/ICT/061/03 All activities

5 KUMA CHUFA RET/ICT/074/03 0934818057 All activities

Table 2 Team Composition

11. Time schedule

Table Time schedule

12. Cost breakdown

Item name Quantity Unit price Total price

Paper 2 packet 800 birr 1600birr

Pen 20 5 birr 100 birr

Print 400 pages 2 birr 800 birr

CD-RW 6 15 birr 90 birr

Mobile card 20 50 1000

Transport - 2.50 400

Total price 3990birr

Table 4:- Cost breakdown

2.1 Introduction of existing system