Moges

Web Based System for ACSINGA
Application of web based system for Amhara Credit and Saving Institution
(ACSI)
North Gondar Area

Approval sheet
This project paper en-titled Web Based System for ACSI, North Gondar Area has been read and
approved as the requirement of the department of Information science in the partial fulfillment
for the award of degree of bachelor in Information science, University of Gondar, Gondar
Ethiopia.
Research and Scholarly Communication Management Team Leader
Principal Adviser
Signature
Date
GetachewGedamu
MelsewBelachew..

Acknowledgement
First of all we would like to thank our GOD that helped us in all up and down and who made us
to successfully complete this projecteffectively beyond what we had anticipated. Next we would
like to express our deepest gratitude to our advisors GetachewGedamuand MelsewBelachew
who contributed all their idea in order to make this projectthe best as much as they can. Thus we
are very grateful for all these; the project team thanks the ACSI North Gondar Area
administration members who helped us by providing all important information needed for the
fulfillment and successful completion of the work.

Page
List of Tables
Table: 1 Accounts table .... 59

Table 2: complaint Table......... 59
TABLE 3: customer Table ...... 60
TABLE 4: interest Table .... 61
TABLE 5: loan Table ....
62
Table 6: loan accept Table .... 62

Table 7:loan paid Table......63
Table 8:loan type Table...63
Table 9:login Table.64
Table 10:rejected information Table...64
Table 11:transactions Table....65
Table 12:hardware specification.....66
Table 13:software specification..67
Table 14:Input data and expected results of the system after testing ..86
Table 15:Input data and expected results of the systemnot yet tested.87
Table 16:Test Case 1.Register Customer.89
Table 17:Test Case2.Login..89
Table 18:Test Case 3.Add Loan Type..90
Table 19:Test Case4.Create Password...90
Table 20:Budget for Stationary...95
Table 21:Service expenses..95
Table 22:Budget Summary..95
Table 23:Project schedule.96

Page
List of Figures
Fig. 1: Architecture of the system...,,,. 17

Fig. 2:Functional decomposition diagram...,,,.18
Fig. 3:Use case diagram for Amhara Credit and Saving System,,.,,..23
Fig. 4:Association of Customer Class,,39
Fig. 5:Association of Loan Class,,...40
Fig. 6: Class diagram of the ACSINGA web based System....41
Fig. 7:Manager Deposit Money to customers...48
Fig. 8:Customers view loan..48
Fig. 9:Employee withdraw Money to customer.49
Fig. 10:Manager login to the System50
Fig. 11:EMI...50
Fig. 12:Employee registers customer.51
Fig. 13:Activity diagram for New Customer Registration....52
Fig. 14:Activity diagram for Withdraw Money.....53
Fig. 15:state chart diagram of the system.54
Fig. 16:Subsystem decomposition diagram..56
Fig.17: Hardware or software mapping57
Fig. 18:Deployment diagram of the system.58
Fig. 19:Homepage of ACSINGAWBS71
Fig. 20:Login page of ACSINGAWBS...72
Fig. 21:Forgotten your Password.73
5

Fig. 22:Manager Homepage of ACSINGAWBS..74
Fig. 23:Employee Homepage of ACSINGAWBS75
Fig. 24:Employee Perform Transaction Page of ACSINGAWBS...76
Fig. 25:Customer Homepage of ACSINGAWBS77
Fig. 26:Customers View Financial Statement page of ACSINGAWBS..78
Fig. 27:Deposit slip, using flat rate calculation manually..114

Acronyms and Abbreviations
ACSI- Amhara Credit and Saving Institution
ACSINGA- Amhara Credit and Saving Institution North Gondar Area
CSI- Credit and Saving Institution
EMI-Equated monthly installment
HTML-Hypertext markup language
IT-Information Technology
MIS-Management Information System
UML-Unified Modeling Language

Abstract
The purpose of this project which is entitled Web Based System for Amhara Credit and Saving
Institution, Gondar Branch is to Reduce the time and labor required to provide services, Reduce
the error that made by the employees, change the manual storage mechanisms into computerized
system (database), provide fast, efficient, flexible, reliable and secure services for better
satisfaction of customers and improvement of motivation of the employee. To do this project the
project team used different data collection methods such as Interview, Document analysis and
Practical observation.Since the current system was manual, to change this system to web based,
we need different software and hardware tools like PHP, adobe Dreamweavercs6, MYSQL,
RAM,CD-RAW and others.
Contents
Approval sheet............................................................................................................ II
8

Acknowledgement..................................................................................................... III
List of Tables.............................................................................................................. IV
List of Figures............................................................................................................. V
Acronyms and Abbreviations.................................................................................... VII
Abstract................................................................................................................... VIII
SECTION ONE............................................................................................................. 1
1.
Introduction.......................................................................................................... 1
1.1.
Background.................................................................................................... 1
1.2.
Statement of the Problem..............................................................................3
1.3. Objective of the project.................................................................................... 4

1.3.1. General objective....................................................................................... 4
1.3.2. Specific objective....................................................................................... 4
1.4
Scope of the project....................................................................................... 4
1.5. Limitation and Delimitation of the project........................................................5

1.5.1 Limitations.................................................................................................. 5
1.5.2 Delimitations............................................................................................... 5
1.6. Significance of the project................................................................................5
SECTION TWO............................................................................................................. 6
2.
Literature Review................................................................................................. 6
2.1.
Background CSI in Ethiopia............................................................................ 6
2.2.
The Review of CSI system in Ethiopia............................................................8
SECTION THREE........................................................................................................ 11
3. Project methodology............................................................................................. 11
3.1 Introduction..................................................................................................... 11
3.2. Data collection method..................................................................................11
3.2.1 Interview................................................................................................... 11
3.2.2 Observation............................................................................................... 12
3.2.3 Document Review..................................................................................... 12
3.3. System Analysis............................................................................................. 12
3.3.1 Proposed System....................................................................................... 14
3.3.2 Feasibility study........................................................................................ 17
3.4. Design............................................................................................................ 20
3.4.1 Design goals.............................................................................................. 21
9

3.4.2 Analysis of activities................................................................................22
3.4.3 ACSI system architecture..........................................................................54
3.4.4 Deployment Diagram................................................................................57
3.4.5 Database Tables........................................................................................ 59
3.5 Specification.................................................................................................... 65
3.5.1 Hardware specification.............................................................................. 65
3.5.2 Software specification............................................................................... 66
3.6 Requirements Specifications...........................................................................67
3.6.1 Functional requirements............................................................................67
3.6.2 Non-functional requirements.....................................................................68
3.7 Implementation............................................................................................... 68
3.7.1 Techniques of implementation.............................................................................. 69
3.7.2 Sample Input or output Screens................................................................71
3.7.3 Sample codes............................................................................................ 79
3.8 Testing............................................................................................................. 83
3.8.1. Test Plan Overview................................................................................... 83
3.8.2. Features to be tested............................................................................... 84
3.8.3 Testing Approach....................................................................................... 84
3.8.4 Testing materials....................................................................................... 85
3.8.5 Test Case Specification..............................................................................85
3.9 Documentation................................................................................................ 92
3.10 Evaluation..................................................................................................... 92
Section 4: RESULT and DISSIMINATION.....................................................................93
4.1 Results achieved............................................................................................. 93
4.2 Dissemination.................................................................................................. 94
4.2.1. Dissemination method.............................................................................94
SECTION FIVE........................................................................................................... 95
5. Budgeting............................................................................................................. 95
5.1. Budget of the project...................................................................................... 95
SECTION SIX............................................................................................................. 96
6.
Action Plan......................................................................................................... 96
Section 7 conclusion and Recommendation.............................................................97

7.1 conclusions...................................................................................................... 97
10

7.2 Recommendation............................................................................................ 99
References.............................................................................................................. 100
Appendixes............................................................................................................. 101
11
SECTION ONE
1. Introduction
Credit and Savings institution refers to an array of financial services, including loans,
savings and insurance, available to poor entrepreneurs and small business owners who have no
collateral and wouldn't otherwise qualify for a standard bank loan. Most often, microloans are
given to those living in still-developing countries who are working in a variety of different
trades, including carpentry, fishing and transportation. [3]
Web based systems are the ultimate way to take advantage of today's technology to enhance your
organizations productivity and efficiency. Web based application gives you an opportunity to
access your business information from anywhere in the world at any time. Some of the core
benefits of web based system are, Cross platform compatibility, more manageable, highly
deployable, secure live data, and Reduced costs.
Supporting the credit and saving sector with the Information Communication Technology (ICT)
is a major strategy to provide quality service to the clients. Automated systems offer real time
information flow. One way in which automated systems reduce human error and repetition is by
automatically populating some fields with information.
1.1. Background
Amhara Credit and Savings Institution (ACSI) was initially established on October 1995 as a
department with the former Ethiopian Relief Organization (ERO), the current Organization for
Rehabilitation and Development in Amhara /ORDA/. It was licensed by the National Bank of
Ethiopia as a micro finance intermediary share company in April 1997. [1]
Amhara Credit and Saving Institution North Gondar area was established on November 9, 1997,
it is one of the branches of the organization several branches which officially began the work of
micro finance before 18 years ago at Gondar. However, when the organization first commence
1

the work have only 6 employees, but now they have increased their number into 16 due to day to
day increase number of clients that demand the companys services.
The main vision of the organization is to see a reduced level of poverty through efficient,
sustainable and well developed institution that provide demand driven financial service for all in
sustainable way.
The mission of the organization is to take part and play an important role in the struggle against
poverty alleviation and food security by facilitating to bring about a sustainable economic
development throughout the country by providing financial service that will stimulate individual
initiative for self-reliance and food security.[4]
The objective of the organization is to ensure that all poor house hold have access to financial
service, to encourage self-employment in particular ladies youth school dropout and youth
completed their school and trained in technical and vocational and to improve agriculture and
productivity and agricultural marketing by improving access to financial service. The types of
services provided to clients include: credit delivery, saving service, advisory service etc.
This project has various important roles for the ACSI, among this some of them
are:Strengthening the relationship with the client: The client is the heart of credit and saving
institution, allowing a unique and complete vision of all the activities. In this way the system aids
in the building of more solid relationships, Increase in productivity: credit and saving institution
increases the companys productivity by means of automating all the areas of the business, while
avoiding manual procedures and possible human error risk, Maximum Management speed: credit
and saving institutions agility and speed of the system allows for rapid customer service,
avoiding unnecessary delays and therefore, increasing customer satisfaction, Essential Reports at
the right time: credit and saving institution provides instantaneous management reports allowing
for increased control of the business, management information for decision taking and the
mandatory reports to fulfill financial authorities control requirements, On-line Institution: With
credit and saving your institution have a system that is available on-line and real time, allowing
you to obtain instant information.

1.2. Statement of the Problem
According to the interview made with the manager, even if most of activities are done manually,
there is only one semi automates activity that is recording customers information simply in
Microsoft office excel.
As an evidence for the existence of the problem in current system, one can observe the
increasing number of comments about the lack of automating system made by unsatisfied
customers and stockholders on suggestion boxes.
Obviously the organization has got lots of business related problems that can be solved by
applying the computer system methodologies even the project team are concerned in developing
a web based system making a big IT infrastructure through which the organization may later
explore for solutions of other problems. However the very problems that the project team
members are about to solve are:
Employees are overloaded by the paper work
Client dissatisfaction due to service delay
It has a disadvantage on the competitive advantage on other related institution
It is redundant, not economical and not flexible
Hindrance of smooth information flow among stake holder
It needs large space for storage of document
Imposes work load on employees and dissatisfaction
Difficulty to trace information easily
Difficulty of identifying the background of the customer
Absence of simple and comfortable working system.
Absence of methods to specify deep need of the customer.
Absence of reliable record keeping due to manual working system.
So, this project will fill the gap through developing web based system to the institution.

1.3. Objective of the project
1.3.1. General objective
The general objective of the project is to develop web based credit and saving system for Amhara
Credit and Saving Institution (ACSI) North Gondar area.
1.3.2. Specific objective
The specific objectives of the project are the following:

To design a user friendly system.
To develop a database to keep the overall records associated with the management
process to store all transactions and uses to make some desire decision.
Model and designing the solution to meet requirements of the system.
To guarantee security of the system by bases on the user and clients privilege.
To recommend additional projects if any.
1.4 Scope of the project

The project focuses only developing a web based system for ACSI, North Gondar area because
of making the organization to have well organized credit and saving system, which gives fast
service for the customers and for the user it will give confidence and comfort on their working
environment. Also time and power will be saved and efficient and timely reports will be
generated by this system.
And the web based system is limited to perform the following tasks:
Handle client information

Handling loan Service
Handling saving deposit
Handling withdraw money information
Handle employee information database.
Provide customer information delivery service
The study covers ACSI North Gondar area only, because the investigatorsare near to this
institution so it was easy to gather information and to observe the activities by presenting
physically.

1.5. Limitation and Delimitation of the project
1.5.1 Limitations
Lack of adequate and accurate data when the team gather it.
Complexity of the business rules of the institution.
1.5.2 Delimitations
When the project team starts this project the team has proposed a number of functionalities to be
included in this project. The team put list of this functionalities in the scope part of this project
document. But due to limitations some of these functionalities are excluded from
implementation. Such as:
Online registration of customers. Because of the business rule of the
institution, it requires customers must register by presenting physically.
Transfer of money from one institution to another, due to lack of
capability of the team members.
1.6. Significance of the project

The significance of a project can be categorized into different areas.
For the organization: For ACSI the system helps in reducing the broad manual work, to
reduce the number of employees, to make its service delivery process fast, to make its data
accurate and secure. It also gains Competitive Advantages with other financial institutions
due to the above improvements.
For employees of the organization: the system is important to access their organizational
data easily anywhere, reduce their work load and labor, reduce redundancy of work, to
generate reports for managers and higher officials and it makes them to be motivated for their
job.
For customers:
Reduce the time and labor required to get services from the institution.
Reduce the error that made by the employees.
It changes the manual storage mechanisms into computerized system.
5
It enhances accuracy, speed, efficiency, flexibility, reliability, and
services.
For their better satisfaction with fast services provided by the employees.
security of
For the project developers: For the project developers help for the fulfillments
Bachelors degree in Information science and team member can get experience.
SECTION TWO
2. Literature Review
Introduction
Credit and saving institution is a source of financial services for entrepreneurs, self-employees
and small and micro enterprise lacking access to banking and related services.
The purpose of this chapter is to introduce the finance academic community to the discipline of
microfinance and microfinance institutions, to understand functionalities of credit and saving
institutions and financial operational procedures. The project team perform a comprehensive
review of a number of related articles and address the issues of CSIs sustainability, products and
services, management practices, clientele targeting, regulation and policy, and impact assessment
in particularly in Ethiopia and also in other world. [5]
2.1. Background CSI in Ethiopia

Currently CSI is one of the most powerful tools for combating poverty primarily by
providing loan to the poor section of the society. The number of CSIs serving the poor in
Ethiopia has grown to over 30 with in short period of time. There is growth and expansion
of credit and saving programs and increasing attention to microfinance as a poverty
reduction strategy throughout the country.
Until 1996, the provision of credit and saving services in Ethiopia has been carried out
mostly by donor funded programs through NGOs and government institutions. Most of the
time a poverty lending approach was followed with subsidized interest rates. This practice

has undermined loan collection performance leading to huge default and hence weakened the
development of self-sustaining CSIs. [2]
The regulatory framework in Ethiopia has created an enabling environment for establishment of
specialized formal financial institutions that provide financial service to those who were
considered as unbendable, enabled CSIs to offer a wide range of products (for example
credit, savings and money transfer etc.) and promoted standardization and transparency in
the sector. In general, the regulatory and supervisory framework, in addition to other
factors,
has
benefited
the credit and saving institutions in Ethiopia to show impressive
performance in terms providing wide range of finical services including: extending credit,
saving mobilization, money transfer and providing other related services to lower income
section of the population.
The formal banking system in the country presents many restrictions to the lower income
section of the population to access economic resources to finance their productive activities.
This has led to give more attention to credit and saving as financial intermediary through which
the poor section of the population gets access to financial services.
Amhara Credit and Saving Institution (ACSI)
Amhara Credit and Savings Institution (ACSI) was initially established in October 1995 as a
department with the former Ethiopian Relief Organization (ERO), the current Organization for
Rehabilitation and Development in Amhara /ORDA/. It was licensed by the National Bank of
Ethiopia as a micro finance intermediary share company in April 1997.
Amhara Credit and Saving Institution North Gondar branch was established on November 9,
1997, it is one of the branches of the organization several branches which officially began the
work of micro finance before 18 years ago at Gondar. However, when the organization first
commence the work have only 6 employees, but now they have increased their number into 16
due to day to day increase number of clients that demand the companys services.
The main vision of the organization is to see a reduced level of poverty through efficient,
sustainable and well developed institution that provide demand driven financial service for all in
sustainable way.
7

The mission of the organization is to take part and play an important role in the struggle against
poverty alleviation and food security by facilitating to bring about a sustainable economic
development throughout the country by providing financial service that will stimulate individual
initiative for self-reliance and food security.
The objective of the organization is to ensure that all poor house hold have access to financial
service, to encourage self-employment in particular ladies youth school dropout and youth
completed their school and trained in technical and vocational and to improve agriculture and
productivity and agricultural marketing by improving access to financial service.[6]
2.2. The Review of CSI system in Ethiopia

Ethiopia is found in the horn of Africa having a large population of 76.8 million (in the
year 2008/2009).
76.8% of the population is living in rural area where there main
activity is subsistence agriculture. Sectored breakdown of goods and services produced

during fiscal year 2008/2009 showed that agriculture, industry and services contributed
43.2, 13, and 45 percent share to GDP respectively. [5]
The main problems of the country include poverty and unemployment. The government of
Ethiopia has been providing attention to reduce poverty in the country. Microfinance is
considered as one of the tools for fighting poverty. Until 1996, loans for the low income
population section of the population or micro-entrepreneurs in Ethiopia were provided
through government programs, cooperatives and Non-government Organizations. These
programs were charging subsidized interest, based on the view that the poor do not have the
capacity to pay their debt at market interest rates (Dr. WoldayAmaha, 2000).
The Ethiopian Financial system, generally speaking falls into three categories. These include:
Formal, semi-formal and informal financial system. The formal financial system is a regulated
sector, which is well organized and provides financial services mainly to urban areas.
This formal Financial system in Ethiopia is mainly compared of financial institutions such as
banks, insurance companies and microfinance institutions. At the end of 2008/2009, there
are Commercial Banks (two government owned), 1 government owned development bank,
insurance companies (one of which is government owned,) and 30 microfinance
institutions (owned by regional governments, NGOs, individuals, associations etc.)
8

The saving and credit cooperative are considered as semi-formal financial institutions,
which are not regulated and supervised by NBE. The informal financial system includes Equib,
Eddir and others, which are not regulated. [7]
The Historical Development of the CSI Sector in Ethiopia
CSI in Ethiopia has its origin in traditional informal method used to accumulate saving and
access credit by people who lacked access to formal financial institutions.
The history of formal establishment of Ethiopia CSI is limited to about twelve years. The
first group of few CSIs was established in early 1997 following the issuance of Proclamation No.
40/1996 in July 1996.
The objective of the CSIs is basically poverty alleviation through the provision of
sustainable financial services to the poor who actually do not have access to the financial support
services of other formal financial institutions.
Since then these CSIs have been playing the role of promoting and accessing financial services
to mainly the rural area. The CSI sector is growing in terms of number and size. The sector is
currently serving more than 2.3 million clients. [8]
CSIs in Ethiopia have been able to serve the productive poor people mainly with
savings, credit, money transfer, micro-insurance and other related services. Governmental
and other developmental organizations have played a vital role for impressive performance
of the microfinance sectors in the country.
Conclusion
CSIs are decisive way outs from the vicious circle of poverty particularly for the rural and
urban poor segment of the society especially in a country like Ethiopia where many people
live barely below the absolute poverty line. The Credit and Saving industry of Ethiopia is
escalating in the face of the growing deep concerns for inflation and low interest rate in the
microfinance industry affecting the financial health and viability of CSIs.

From all the above review we can understand that the presence of credit and saving institutions
is necessary for our country to balance the survival of the people economically. Currently credit
and saving institutions are available in almost all the urban and rural areas. The objective of the
credit and saving organization in Ethiopia is to ensure that all poor house hold have access to
financial service, to encourage self-employment in particular ladies youth school dropout and
youth completed their school and trained in technical and vocational and to improve agriculture
and productivity and agricultural marketing by improving access to financial service.
The presence of these institutions makes a wide change through the survival of the people
especially for the poor, farmers, self-employers in particular ladies youth school dropout and
youth completed their school and trained in technical and vocational colleges.
This growth and expansion of CSIs programs and increasing attention to CSIs as a
poverty reduction
strategy throughout the country leads to use information technology to
address services easily and to enhance the satisfaction of the customers.

ACSI is one of the government financial institutions at North Gondar. Its service that it provides
for the people becomes wide. But still it uses manual system. This system cant make its service
efficient and effective. So, to make its service better and to compete with other CSIs it needs to
use computerized and internet based system.
SECTION THREE
3. Project methodology
3.1 Introduction
Methodology is the process used to collect information and data for the purpose of making
business decisions. The methodology includes publication research, interviews, surveys and
other research techniques, and could include both present and historical information.
3.2. Data collection method

In order to obtain data requirement for the project, the project team used different methods. From
the different methods used includes interviews, observation, and document analysis are among the
different methodologies of collecting the data and information required for the proposed system.
10

3.2.1 Interview
This is one of the method used for the collection of data, and the reason why the researcher select
this method is that it gives informants the chance to challenge the agenda set by the researcher,
raising new issues, asking questions back,Collecting qualitative data, i.e. allowing the researcher
to probe the meanings interviewees give to their behavior, ascertaining their motives and
intentions, Giving informants the opportunity to check what is meant by a question; allowing for
long and complex responses,Flexibility - making possible changes in the order of questioning,
the questions asked and the topics discussed, Probing - follow-up questioning seeking
clarification or further explanation.
The researchers have the chance of asking different questions to the organization employee for
obtaining the required information and data. The project designers used this kind of collecting
data most of the time. We had the chance of talking to the manager of ACSI North Gondar
AreaAtoShiferawMekonen many times and we have collected enough information and we could
make another appointment if the team want additional information concerning the existing
system. Generally by using this method the team have gathered informations like, the date of the
institution was established, how they currently perform activities like saving and depositing of
money and business rule of the institution.
3.2.2 Observation
This is another type of method for collecting data and information in which could witness
the actual events which happen in the organization.It is very direct method for collecting data or
information, data collected is very accurate in nature and also very reliable, improves precision
of the research results, problem of depending on respondents is decreased, helps in
understanding the verbal response more efficiently, by using good and modern gadgets
observations can be made continuously and also for a larger duration of time period, observation
is less demanding in nature, which makes it less bias in working abilities, by observation, one
can identify a problem by making an in depth analysis of the problems.
In this method all team members have to do is observation and note down the events what the
team observed, so here the team members have seen some events like, employees are keeping
clients file manually, clients dissatisfaction by the service, calculation errors, takes time to search
clients file, takes large place for storing the files, and lack of data security are some of them.
11

3.2.3
Document Review
The project team uses this method as one means of data collection because it is relatively
inexpensive good source of background information, unobtrusive, provides a behind-the-scenes
look at a program that may not be directly observable, and may bring up issues not noted by
other means.
This method of collecting a data is analyzing the document prepared in the existing system. The
team analyzed different documents like forms and report samples in the existing system. In form
samples the researcher used information that the customers used to get services from the
institution like loan request forms, money deposit forms, withdraw forms and so on. And from
the report samples the team gathered information about the day to day activities of the institution.
The researchers used to identify the problems of the existing system and develop the new system.
3.3. System Analysis

The project team should have to follow system development life cycle (SDLC) as conceptual
model because it is used us in project management to describe the stages involved in the system
that the team propose to develop from an initial feasibility study through maintenance of the
completed application.
System development life cycle is a framework through which the team describes the activities
performed at each stage of the system development.
The team has to follow sequential SDLC Phases to develop the system efficiently.
Systems Investigation: This is the first stage of the development of the system. In this stage the
analyst makes a survey by gathering all the available information needed for the system elements
and allocation of the requirements to the software. The team has identified problems to be
solved or operational functionalities that should be included in the system that the team proposes
to develop.
Planning: The designers have prepared detail development plan. During this first phase of the
development life cycle, security considerations are key to diligent and early integration, thereby
12

ensuring that threats, requirements, and potential constraints in functionality and integration are
considered.
Systems Analysis: The team should have to analyze the ways how can the team solve the
problems.
The analysts understand the nature of the information and the functions of the software which is
required for the system. The analysts make a brief survey of the requirements and try to analyze
the performance of the system which is to be developed and makes sure that they gets enough
information and resources for building the appropriate system.
The team has listed functionalities or activities performed in the ACSI and identify by whom
each operations performed. Then the team has analyzed the relation between each operation, the
flow of operations and the relation between each operation and the actors in the system by using
different diagrams such as use case, class diagram, data flow, activity and sequence diagrams.
Systems Design: The system development team actually makes number of designs of the system
on paper or on the computer and sees to it that the rough image made of the system comprises of
all the requirements or not. Once this is done, the analysts have selected and finalized a best
suited design for the development of the system.
System Coding: The programmer translates the design into code. The coding step was very time
consuming and involves number of rooms for errors.
System testing: Once the programmers is through with the coding stage we tests the systems and
sees to it that it is working as per the expectations or not. The team corrects the flaws in the
system if any.
Systems Implementation: in this phase the team has to implement the system and receive
feedback from the users of the ACSI system.
Systems Maintenance and test: This is the last stage of the SDLC, in this stage the team has
understand the problems or errors phased when the team implement the system and feedbacks
received from users. Then the team has to maintain the system and see to it that it working within
13

the standards set. The team has to maintain the system by removing the defects of flaws
occurred. Finally the team has to evaluate or test the results of the solution again and it will
continue in this way.
3.3.1 Proposed System
To avoid all these limitations and make the working more accurately the system needs to
be computerized.
The aim of proposed system is to develop a system of improved facilities. The
proposed system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work.
3.3.1.1 Purpose of the Proposed System
The
system
is
simple
to
design
and
to
implement.
It
requires
very
low
system resources and the system will work in almost all configurations. It has got the
following features
Security of data.
Ensure data accuracy.
Minimize manual work.
Minimum time needed for the various processing.
Greater efficiency.
Better service.
User friendliness and interactive.
Minimum time required.
3.3.1.2 Description of the proposed system
This project segregated into two sections and a number of modules or activities to be
accomplished. This will be described as follows:
14

Client side
Depositing money: This module covers how customers save their money in ACSI
whenever they want. Major function of ACSI is to mobilize savings by encouraging
people to save some portion of their income from consumption. Some of the
mechanism of persuading people to save is by paying interest for the saved and
deposited amount in the ACSI, by making them aware of the use of ACSI. This task
will be accomplished by using this web based system.
Withdraw: In saving account, the owner of the money who once becomes a customer
of the institution can withdraw his money from the institution performed either by the
Manager or by Employee.
Calculate EMI: the system calculates customers equated monthly installment by
entering the amount of the money he/she lent, the duration he/she returns the money
and interest rate in percentage.
Loan Request: Customers of the institution can apply for loan request to the Manager
of the system online based on the certain criteria set by the institution. Currently deposit
received by the institution is not kept idle. After keeping certain cash reserves above the
minimum balance, the loan is given by the ACSI to the needy borrowers. He/ she takes
the loan physically from the Manager.
Information database: The system handles both customer and Employee information
database. The customers can login to the system by using their account to view his/her
status. Employees have also their own login to the system to manage customers. They
can also access their financial information anywhere through their address.
Customer information delivery: The system provides online information delivery
service for the customers of the organization. Any customer can access information
from the website of the organization through his/her address anywhere.
Financial Statement: Timely financial report which is available for customers is
generated during transaction of money performed by the Manager and the Employee of
the system.
15

Server Side
Approver: This activity/module is utilized by Manager to approve the loans applied by
the users. If the customers fulfilled all the required information, then the loan will be
accepted, otherwise it will be rejected.
Information & Report: Allow the Manager to monitoring the existing information,
appending information to its existing information, verifying new customers and
acknowledging them.
System Architecture
16

The
system
is
built
on
the
three
tier
architecture
of
web
applications.
Fig.1 architecture of the system

When a request is made on a web page through the browser, PHP that is residing on the web
server processes the request. It connects to the database to retrieve the requested information and
sends its response back to the browser which displays the output on another web page. The
advantage of this architecture is that the database is more secured as it is only accessible by the
application logic that resides on the web server.
3.3.2 Feasibility study
This part of the document is used to express the feasibility of the project in the organization as a
problem solver system.
Undergoing feasibility study to this project is used to understand and describe economic, legal
and political environment, the financial system, the area of the market segment and the
level of competition and unsatisfied demand of the products, the type of financial products to
be offered, the economic impact of the financial service to be offered and related issues. All
17

these information
help to serve the project segment with specific risk profile before
commencing its operation.

3.3.2.1 Operational Feasibility
The project have user-friendly interface to be operated by both employees and customers easily.
It is used to improve the current operations and to solve the major operational problems of the
organization. It will make the service delivery process efficient and effective.
Fig.2 Functional decomposition diagram
3.3.2.2 Technical Feasibility
The project is important for practicality of the specific technical solution and the availability of
technical resources and expertise. It is used to enhance the speed and accuracy of technical works
and to reduce technical errors in the Amhara Credit and Saving Institution North Gondar Area.
And it is easy to be utilized by any users of the organization.
Relevance of the technologies
18

The project team used different technologies to develop this project. Software development and
technology gives us access to cutting edge knowledge in software design, programming
languages, databases, distributed systems, artificial intelligence, algorithms, software
development processes, requirements, organization and management. The program gives us
opportunity to work with all phases of the development process analysis, design, development,
test and launch, and we are learning and applying how to design and program software systems
of all scales, from manual system to web based business solutions.
3.3.2.3 Schedule Feasibility
The fulfillment of all the necessary requirements and budget makes our project to be completed
on time. If this so it will be completed on time without any delay as scheduled.
3.3.2.4 Economic Feasibility
As depicted in the problem statement, currently the Amhara Credit and Saving Institution North
Gondar Area is exposed for unnecessary economical wastes in different ways such as man power
and time to calculate manually, documentation materials, calculation tools etc.
But after the project implementation these unnecessary wastes will be reduced. It will have the
required number of computers and infrastructure. But there will no more manual work and
unnecessary waste with manual materials. .
3.3.2.4.1 Cost and Benefit Analysis
Cost includes development costs, which are specifically shown in a table format, and ongoing
costs through the entire lifetime of the project, such as:
Operating staff salaries and overheads
Stationary and other consumable items
Maintenance of hardware, software and other equipment
Cost of backup arrangement.
Benefits
Benefits are shown as tangible and intangible benefits for the system.
19

Tangible Benefits:
Producing financial reports with no error.
Completing jobs in fewer hours,
Decreasing response time,
Easy to control the database.
Makes the database secure.
Intangible Benefits:
Customer satisfaction
Improve employee morale and job satisfaction,
Better decision-making.
Work effectiveness
Competitiveness of the institution
3.4. Design
The project team have used Object Oriented method (approach) to develop our system, that is to
carefully represent complex relationship, as well as to represent data and process with consistent
notation throughout the system and to make our system efficient.
It is also used us for analyzing, designing and implementing the system by applying the objectoriented prototype and visual modeling throughout the development life cycles to foster better
stakeholder communication and product quality. Its additional advantages that make us to choose
it for our project are:
The ability to tackle more achieving problem domains.
Increased consistency among analysis, design and programming activities.
Common design and coding methodologies, including Object-Oriented Design (OOD),
Design Patterns, and the Unified Modeling Language (UML)
Explicit representation of unity among system components.
20

Reusability of analysis, design and programming results.
Increased consistency among all the models developed during Object Oriented Analysis,
design and implementation
3.4.1 Design goals
The design of our system considers or incorporates the following major goals.
Easy to implement: the design of the system is easy to change it in to implementation or
code for the project group. It is also easy to design and implement the database of the
system.
Flexibility: The team may have to change the way in which certain things work. The
design accommodates these changes with minimum effort.
Extensibility: The system design is be able to accommodate new functionality easily
when it is needed. Ideally when the institutional operations become enhanced, the team
must be able to add new stuff by adding code and not by modifying existing code,
because modifying existing code may break stuff that was already working.
Maintainability: The system is easy to maintain and improve at any time when the
organization needs.
Maintainability = Flexibility + Extensibility + Bug fixes + Refactoring.
Reliability: The system consists of all the major functionalities of ACSI.
Fault Tolerance: The system is fault tolerant to loss of connectivity with the routing
service or other faults.
Usability: the system is easy and user friendly users. It doesn`t require a high level of
expertise in computers. Any user can access it simply using user guide.
Response time:
The system responds as quickly as possible for authorized or
unauthorized access requests.

Memory space: The system considers the memory space in which run.
Security: The system security is taken in to consideration to make institutional
information and financial cases secure and confidential.
21

And others such as Good documentation, Well-defined interfaces, User-friendliness, Reuse
of components, Rapid development, Readability, Ease of learning, Ease of remembering,
Ease of use and robustness.
3.4.2 Analysis of activities
The system is built from different operational activities accomplished in ACSI. These different
activities are performed by assigned actors that each activity concerned.
This part covers the detail analysis of activities included in the system by using different
diagrams (i.e. the relation between operational activities and actors, the relation between each
operational activity, the flow of operational activities, and the relation between states of the
system).
3.4.2.1 Use Case Diagram
The project team used Use case diagram to typically define interactions between a role (known
in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. The actor
can be a human or an external system. The team used it as a blueprint for the system especially
for the interface design.
It is also used to describe what a system does and to reflect the view of the system from the Perspective of
a user outside of the system.
We used UML to design the use case model and derive systems object and their
interaction with each other with the users of the system.
Actors identification
The following actors are used in our system
Manager
Employee
Customer
Use Case Identification
The following use cases were identified
Manage customer
22

Manage Loan
Manage Transaction
Manage Account type
Manage Deposit
Manage Employee
Messaging
View financial Statement
Fig.3 Use case for Amhara Credit and Saving System
23

Use Case Description
Description of the Manager use cases
Name of use case: Register Customer
Participating actor:Manager
Entry condition: The Manager logs in to the system using his account.
Flow of events:
1. The Manager logs to his account from the homepage of Web based system for Amhara
Credit and Saving Institution North Gondar Area
2. The Manager clicks on the Manage Customers button
3. The system displays user registration page
4. The Manager clicks on the Register customer link and the user registration form
displayed.
5. The Manager fills user registration data and click Add Button
6. The system displays Added to the Database message
Name of use case: Update Customer
Flow of events:
2.
3.
4.
5.

The Manager clicks on the Manage Customers button
The system displays update user page
The Manager clicks on the Update customer link and the user Update page displayed.
The Manager selects the desired Customer ID from the combo box and click the Fetch
Details Button
6. The Manager can make changes on the desired data and clicks Update Button
7. The system displays Data Updated Successfully Database message
Name of use case: Delete Customer
24

Flow of events:
Credit and Saving institution North Gondar Area
2. The Manager clicks on the Manage Customers button
3. The system displays Delete user page
4. The Manager Selects from the lists of Customer IDfrom the combo boxand clicks on the
Delete Button
5. The system displays Customer Deleted Successfullymessage
Name of use case: Add Loan Type
Entry condition: Manager logs in to the system using his account.
Flow of events:
2.
3.
4.
5.

The Manager clicks on the Manage Loan button
The system displays manage loan page and
The Manager clicks on the Loan Type link and the Add New Loan Type page displayed.
The Manager click Add New Loan Typebutton and the system display Add New loan type
form.
6. The Manager enters the Loan details in the form and click Add button.
Name of use case: Update Loan Type
Flow of events:
2. The Manager clicks on the Manage Loan button
3. The system displays manage loan page and
4. The Manager clicks on the Loan Type link and the Update Loan Type page displayed.
25

5. The Manager click Update New Loan Typebutton and the system display the combo box
to select from loan types and select and click Fetch Details Button.
6. The system displayed the loan type details
7. The Manager makes changes to the desired record and click Update button.
8. The system displaysData Updated Successfully message
Name of use case: Delete Loan Type
Flow of events:
2.
3.
4.
5.

The system displays manage loan page
The Manager clicks on the Loan Type link and the Delete Loan Type page displayed.
The Manager click Delete Loan Typebutton and the system display the combo box to
select from loan types and select and click Fetch Details Button.
6. The system displayed the loan type details
7. The Manager selects the desired record from the loan types to Delete and click Delete
Loan Button.
8. The system displays Loan Type Deleted Successfullymessage
Name of use case: Check Loan Request
Flow of events:
2. The Manager clicks on the Manage Loan button
3. The system displays manage loan page
4. The Manager clicks on the Check Loan Request link and checks whether or not there are
loan requests from customers.
5. If there are loan requests from customers, the manager click either accept or reject the
loan requests based on the fulfillment of requirements.
6. If the Manager click the accept link, the system display the loan detail page.
26

7. The system manager clicks the submit button and display the loan can be performed
message.
Name of use case: Loan detail
Flow of events:
2.
3.
4.
5.

The system displays manage loan page and
The Manager clicks on the Loan Detail link
The system display Loan Detail information.
Name of use case: Loan Paid

Flow of events:
2. The Manager clicks on the Manage Loan button and then Loan Paid Link
3. The System displays customers loan payment detail.
Name of use case: View Financial Statement
Entry condition: The Manager and the Employee logs in to the system using their respective
accounts.
Flow of events:
1. The Manager and the Employee logs to their account from the homepage of Web based
system for Amhara Credit and Saving institution North Gondar Area
2. The Manager and the Employee clicks on the View Financial Statement button
3. The system displays View Financial Statement page
27

4. The Manager Selects from the lists of the desired Account Numberfrom the combo
boxand clicks on the Financial Detail Button
5. The system displays Financial Statement report of the customer.
Name of use case: Add New Account Type
Flow of events:
2. The Manager clicks on the Manage Account Type button
3. The system displays manage Account Type page
4. The Manager clicks on the Add New Account Type link and the account type detail form
page displayed.
5. The Manager fills the form and clicks the Add Button
6. The system displayed the Added to the database message.
Name of use case: Update Account detail

Flow of events:
2. The Manager clicks on the Manage Account Type button
4. The Manager clicks on the Update Account Detaillink and the system display the combo
box to select from account types and click Fetch Details button.
5. The Manager make changes to the data in the form and clicks the UpdateButton
6. The system displayed the Data Updated Successfully message.
Name of use case: Delete Account details
28

Flow of events:
2. The Manager clicks on the Manage Account Type link
4. The Manager clicks on the Delete Account Details link and the account type detail form
page displayed.
5. The system displays the combo box to select from account types and click Delete
Account button.
6. The system displayed theAccount Deleted Successfully message.
Name of use case: Create User Password
Flow of events:
2. The Manager clicks on the Set Password button
3. The system displays Manage Password page
4. The Manager clicks on the Create User Password link and the Create users password
Page displayed.
5. The Manager fills the Password and the Confirm password field and clicks the
CreateButton.
6. The system displayed the Added to the database message.
Name of use case: Update User Password
Flow of events:
2. The Manager clicks on the Set Password link
3. The system displays Manage Password page
29

4. The Manager clicks on the Update User Password link and the Update users password
Page displayed.
5. The Manager fills the Old Password, New Password, the Confirm password, and and
clicks the UpdateButton.
6. The system displayed the Data Updated Successfully message.
Name of use case: Search Customer
Flow of events:
2.
3.
4.
5.

The Manager clicks on the Search Customer link
The system displays search customer page
The Manager selects from the list of Customer Id and clicks on the Fetch Detailbutton
The system displays the detail of the desired customer.
Name of use case: Send Message

Flow of events:
2. The Manager clicks on the Send Messages Button
3. The system displays send message page
4. The Manager selects the receiver customer Id and fills in the subject and Message field
and clicks on the Send button.
5. The system Message sent message
Name of use case:Deposit Money
Flow of events:
30

2. The Manager clicks on the Manage Transaction Button and click on Perform transaction.
3. The system displays the Transaction manager Page.
4. The Manager selects from Transaction Type(i.e Deposit) anddesiredAccountNumberfrom the
list and fill in the Amount field and finally click on Transact button
5. The System displays Transaction completed successfully message

Name of use case:Withdraw Money
Flow of events:
2. The Manager clicks on the Manage Transaction Button and click on Perform transaction.
4. The Manager selects from Transaction Type (i.e Withdrawal)anddesiredAccount
Numberfrom the list and fill in the Amount field and finally click on Transact button
5. The System displays Transaction completed successfully message
Description of the Employee use cases
Name of use case: Register Customer
Participating actor:Employee
Entry condition: The Employee logs in to the system using his account.
Flow of events:
1. The Employee logs to his account from the homepage of Web based system for Amhara
2. The Employee clicks on the Manage Customers Button
3. The system displays user registration page
4. The Employee clicks on the Register customer link and the user registration form
displayed.
5. The Employee fills user registration data and click Add Button
Name of use case: Update Customer
31

Flow of events:
2.
3.
4.
5.

The Employee clicks on the Manage Customers Button
The system displays update user page.
The Employee clicks on the Update customer link and the user Update page displayed.
The Employee selects the desired Customer ID from the combo box and click the Fetch
Details Button
6. The Employee can make changes on the desired data and clicks Update Button
7. The system displays Data Updated Successfully Database message
Name of use case: Delete Customer
Flow of events:
2. The Employee clicks on the Manage Customers Button
3. The system displays Delete user page
4. The Employee Selects from the lists of Customer ID from the combo boxand clicks on
the Delete Button
5. The system displays Customer Deleted Successfully message
Name of use case: View Financial Statement
Entry condition: The Manager and the Employee logs in to the system using their respective
accounts.
Flow of events:
1. The Manager and the Employee logs to their account from the homepage of Web based
system for Amhara Credit and Saving institution North Gondar Area
2. The Employee clicks on the View Financial Statement Button
3. The system displays View Financial Statement page
32

4. The Employee Selects from the lists of the desired Account Numberfrom the combo
boxand clicks on the Financial Detail Button
5. The system displays Financial Statement report of the customer.
Name of use case: Search Customer
Flow of events:
2.
3.
4.
5.

The Employee clicks on the Search Customer Button
The system displays search customer page
The Employee selects from the list of Customer Id and clicks on the Fetch Detail button.
The system displays the detail of the desired customer.

Flow of events:
Credit and Saving institution North Gondar Area The Employee clicks on the Send
Messages Button
2. The system displays send message page
3. The Employee selects the receiver customer Id and clicks on the Send button.
Name of use case:Deposit Money
Flow of events:
Credit and saving institution North Gondar Area
33

2. The Employee clicks on the Manage Transaction Button and click on Perform
transaction.
4. The Employee selects from Transaction Type (i.e. Deposit) and desired Account Number from
the list and fill in the Amount field and finally click on Transact button
5. The System displays Transaction completed successfully message.
Name of use case:Withdraw Money

Flow of events:
2. The Employeeclicks on the Manage Transaction Button and click on Perform transaction.
4. The Employee selects from Transaction Type (i.e Withdrawal)anddesiredAccount
Number from the list and fill in the Amount field and finally click on Transact button
5. The System displays Transaction completed successfully message.
Description of the Customer use cases
Name of use case: Loan detail
Participating actor:Customer
Entry condition: The Customer logs in to the system using his account.
Flow of events:
1. The Customer logs to his account from the homepage of Web based system for Amhara
2. The Customer clicks on the View Loan Button and then Loan Detail Link
3. The system displays loan detail of the Customer.
Name of use case: Loan Request
34

Flow of events:
2. The Customer clicks on the View Loan Button and then Loan Request Link
3. The System allows the Customer to choose from the list of Loan Type and click send
button.
4. The system displays Request submitted to managermessage.
Name of use case: Loan Paid
Flow of events:
2. The Customer clicks on the View Loan Button and then Loan Paid Link
3. The System displays his/her loan paid detail.
Name of use case: EMI
Flow of events:
2. The Customer clicks on the View Loan Button and then EMI Link
3. The System displays the Equated Monthly Installment (EMI) form and the customer fills
on the required fields and clicks the Calculate button.
4. The system views his EMI.
Name of use case: View financial statement
Flow of events:
35

2. The Customer clicks on the View financial Statement Button
3. The System displays the Transaction details of the Customer.
Flow of events:
2. The Customer clicks on the Send Message link
3. The system displays Send Message form page.
4. The Customer selects the receiver (i.e. Manager or Employee) and fills in the subject and
Message field and clicks on the Send button.
Name of use case: Inbox
Flow of events:
1. The Customer logs to his account from the homepage of Web based system
for Amhara Credit and Saving institution North Gondar Area
2. The Customer clicks on the Inbox Button
3. The System displays the inbox of the customer.
3.4.2.2 Class Diagram
The project team used class diagram to describe the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships among objects.
For designing of Class diagram the team has usedUnified Modeling Language (UML). This
diagram is the main building block of our object oriented modeling. The team applies it for both
general conceptual modeling of the systematics of the application, and for detailed modeling
36

translating the models into programming code. The classes in a class diagram represent both the
main objects, interactions in the application and the classes to be programmed.
In the system Classes are abstractions that specify the attributes and behavior of a set of objects
and Objects are entities that encapsulate state and behavior. Each object has an identity: It can be
referred individually and is distinguishable from other objects. Classes represent participating
objects found in use cases and sequence diagrams and describe their attributes and operations.
In mapping the diagram the team used the following criteria:
One to- One relationship:-here when both involved entities exchange primary keys
where the new exchanged primary keys become the new foreign keys of the tables.
One to- many relationships:-here the primary key on the many side has been mapped
to the one side.
Many to- Many relationship- the primary keys of both involved entities will become
foreign to the relationship.
The association of classes is described with diagrams as follows.
37
Fig.4. Association of Customer Class
38
Fig.5 Association of Loan Class
39
Fig.6 Class diagram of the ACSINGA web based System

3.4.2.2.1 Description of class diagram
A. Class name: Customer

Description:
A customer who is already registered.
A customer who can log to the system with one login page.
A customer who has an Account.
40

A customer who can request loan once and after completing the payment
he can request another loan.
A customer who can perform many transactions.
A customer who paid loan many times.
A customer who can select one loan type at once.
A customer who has rejected information.
A customer who view or sent many complaints or messages.
A customer who has one loan accepts.
Methods
Registered ()
Pseudo code: Do
The system registers a customer Information to the database.
Open ()
Pseudo code: Do
The system lets to open an Account type.
View ()
Pseudo code: Do
The system displays the customers financial statement and account
details if the user name and password is correct.
Send ()
Pseudo code: Do
The system lets the customer to send the loan request and complaints.
Calculate ()
Pseudo code: Do
41

The system lets the customer to calculate his or her equated monthly
installment.
B. Class name: Login

Description:
A customer who login to the system.
A customer who has a user name and password to login and visit his or her
status.
Methods
Login ()
Pseudo code: Do
The System lets the customer to enter into his or her account.
C. Class name: Loan
Description:
A person can request loan once.
A person must have a unique account ID to perform request loan.
A person must select loan type to get loan service.
Methods
Request ()
Pseudo code: Do
The system allows the customer to request loan.
Accept ()
The system can accept the customer request.
Reject ()
42

The system can reject the request of the customer based on the rule.
D. Class name: Transaction
Description:
A customer can perform a number of transactions.
A unique Account Number Assigned to perform transaction.
Methods
Cash ()
Pseudo code: Do
The system allows the customer to deposit or withdraw cash.
E. Class name: Account
Description:
The system allows the customer to deposit the minimum balance of

money during registration
Methods
Add ()
Pseudo code: Do
The system saves Account types and minimum balance into the data base.
Update ()
Pseudo code: Do
The system lets to edit Account types and minimum balance.
Delete ()
Pseudo code: Do
The system deletes Account types and minimum balance from the database.
F. Class name: loan _ accept
43

Description:
The customers loan request is accepted if he or she fulfills the criteria of

the system.
Methods
Accept ()
Pseudo code: Do
The system accepts the loan request and saves to the database.
G. Class name: Rejected _ information
Description:
A customer can have loan rejected information.
H. Class name : loan _ paid
Description:
A system lets the customer to pay their loan through manager.
A customer should pay at least the minimum amount of monthly
installment.
Methods
Pay ()
Pseudo code: Do
The system subtracts from the amount of loan he or she has received.
View ()
The system allows the customer to view his/her status.
I.
Class name : complaint

Description:
44

The customer can log in to the system and view complaints or messages
from manager or employee.
The customer can send message when he or she has a complaint.
Methods
Send ()
Pseudo code: Do
The system sends the messages or complaints to the customer.
View ()
Pseudo code: Do
The system shows complaints or messages to the customer from the database.
J.
Class name: Interest
Description
The customer has an interest based on the loan amount.
Method
View ()
Pseudo code: Do
The system lets the customer to view his or her loan interest based on the amount they
have borrowed.
K. Class name: Loan _ type
Description:
There are a number of loan types to be selected when a customer wants to
request loan.
A customer should select one loan type for when he or she request loan to
the system.
The customer must have unique loan id to perform loan service.
45

Methods:
Add ()
The system adds the loan type that the customer selects to the database.
Delete ()
The system deletes the loan type when the institution stops to lend a specific loan
type.
View ()
The system shows the response of the customers request to loan with selected
loan type.
3.4.2.3 Sequence Diagram
As the name indicates the system used sequencediagram to show sequence of activities or how
processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. It shows object interactions arranged in time sequence. It depicts the objects and classes
involved in the scenario and the sequence of messages exchanged between the objects needed to
carry out the functionality of the scenario. Sequence diagrams are typically associated with use
case realizations in the Logical View of the system under development.
With this diagram the project team show, as parallel vertical lines (lifelines), different processes
or objects that live simultaneously, and, as horizontal arrows, the messages exchanged between
them, in the order in which they occur. This allows the specification of simple runtime scenarios
in a graphical manner.
46
Fig. 7 Manager Deposit Money to customers
Fig.8 Customers view loan
47
Fig.9 Employee withdraw Money to customer
48
Fig.10 Manager login to the System
Fig.11 EMI
49
Fig.12 Employee registers customer
3.4.2.4 Activity Diagram
The project team used activity diagram to graphically represent the sequence flow of activities or
workflow of stepwise activities and actions with support for choice, iteration and concurrency. It
also used to model action that has been performed when an operation is executing as well as the
result of those actions. The activity diagram resembles the flow chart that shows the actions and
events as they occur and also the order in which the actions take place and identifies the
outcomes.
In the Unified Modeling Language, activity diagrams are intended to model both computational
and organizational processes (i.e. workflows). Activity diagrams show the overall flow of
control.
50

Fig.13Activity diagram for New Customer
Registration
Fig.14Activity diagram for Withdraw

Money
3.4.2.5 State chart diagram
The project team used state chart diagram to

describe the behavior of the system. State
chart diagrams require that the system
described is composed of a finite number of
states. Hereby each diagram usually represents
objects of a single class and tracks the different
states of its objects through the system.
Fig.15 state chart diagram of the system

3.4.3 ACSI system architecture
3.4.3.1 Overview
The project team used system design modelor system architectureto describe a system, or as a
detailed plan of the system at component level to make it easy for implementation. It is used us to
describe the structure of components, their interrelationships, and the principles and guidelines governing
their design and evolution over time.
Architctural design is used us for identifying the sub-systems making up the system and the
framework for sub-system control and communication. The key tasks of the web based ACSI are
to handle concurrent events from external users and maintain consistency between data resident
on the client, server, database and the data displayed to the end user.
51

The system architecture embodies the major static and dynamic aspects of the system. It is a
view of the whole system highlighting the important characteristics and ignoring unnecessary
details. In the context of this system approach, architecture is primarily specified in terms of
views of five models; the Use-Case model, Analysis Model, Design Model, Deployment model
and Implementation model. These views show the architecturally significant elements of those
models. The models have the following specific characteristics in this system approach: The
Use-Case model shows the thematic use cases related to functionality associated with
distribution The Analysis model illustrates how boundary, control and entity classes are
associated with the thematic use casesidentified in the Analysis. The Design model shows the
design classes that trace the specialized Remote Communication Control classes in
analysis.Finally, the Deployment component model explains how components are assigned to the
system under system design phase particularly.
Under this phase system design components such as subsystem decomposition, deployment
diagram, database Tables, data flow diagram, entity relationship diagram which show the system
clearly are described in detail.
3.4.3.2 Subsystem decomposition
The system design is decomposed from general to subsystems. The responsibilities or roles of
each subsystem are described clearly to be easily implemented. The project team can describe the
decomposition of the system in to main subsystems as follows:
52
Fig.16 Subsystem decomposition diagram

3.4.3.3 Hardware or software mapping
When the project team say hardware/software mapping for the system, it describes how
subsystems are assigned to hardware and off-the-shelf components. It also lists the issues
introduced by multiple nodes and software reuse.
In this system design mainly there are three hardware components. The client side, server side
and database side. When the team applies the system, necessary software will be loaded to each
side hardware components. Network should be installed between each side. Then each sub
system software will be assigned and configured to the mapped hardware. Then the local area
network will be connected to the internet and the system will be functional.
But now it is a design phase. The hardware software mapping of the system is described below
with a simple diagram.
53
Internet
Client
Server
Database
Fig.17 Hardware or software mapping

Subsystems such as: register customer, loan request, view transactional information, withdraw,
deposit are assigned and performed with client.
3.4.4 Deployment Diagram
The project team used deployment diagram to model the physical deployment of objects on
nodes. To describe the system, a deployment diagram would show what hardware components
("nodes") exist (e.g., a web server, an application server, and a database server), what software
components ("artifacts") run on each node (e.g., web application, database), and how the
different pieces are connected. The deployment diagram for the system is drawn below.
54
Fig.18 Deployment diagram of the system

Deployment diagram description:
Browser: online viewers will be able to communicate with the web server using
browser.
Web Server: The project team using apache as the web server, and it will be
responsible for accepting from and responding request sent by the browsers.
Applications: This component will be a web application, made by using PHP i.e.
deposit, withdraw and transfer which will interact with the database.
Synchronize Service: This component will also be a web application, which will be
responsible for sending and receiving data.
Database: This will be responsible for storing information on the computer.
55

3.4.5 Database Tables
The project team use database tables to organize and group the data by common characteristics
or principles. The database contains eleven tables to organize our data. The team has described
database tables of the system as follows.
The project team used description of the data objects or items in a data model for the benefit of
programmers and others who need to refer to them.
Table
1
Accounts
Attributes
Data Types
Contraints
Description
acc_type
varchar(50)
NOT NULL
Account type
Primary key
minbalance`
varchar(20)
NOT NULL
Minimum
Balance
Table.1 accounts table

Table
2
Complaint
Attributes
Data Types
Contraints
Description
Slno
int(250)
NOT NULL
Starting line Number

Primary key
comp_to
varchar(50)
NOT NULL
Complaint To
comp_from
varchar(50)
NOT NULL
Complaint from
Subject
varchar(150)
NOT NULL
Subject of the message
complaint
varchar(750)
NOT NULL
Complaint
comp_date
Datetime
NOT NULL
Complaint date
Table.2. complaint Table
Entity
3
Customer
Attributes
Data Types
Contraints
Description
Custid
varchar (20)
NOT NULL
Customer identification
Primary Key
56

first_name
varchar(50)
NOT NULL
First Name
last_name
varchar(50)
NOT NULL
Last Name
Age
int(3)
NOT NULL
Age
Address
varchar(200)
NOT NULL
Address
Kebele
varchar(35)
NOT NULL
Kebele
Email
varchar(40)
NOT NULL
Electronic mail
Sex
varchar(15)
NOT NULL
Sex
phone_number
varchar(25)
NOT NULL
Phone Number
acc_number
varchar(25)
NOT NULL
Account number
Primary Key
Balance
Float
NOT NULL
Balance
acc_type
varchar(25)
NOT NULL
Account Type
Opendate
Datetime
NOT NULL
Open date
Table.3. customer Table
Table
4
Interest
Attributes
Data Types
Contraints
Description
acc_num
int(20)
NOT NULL
Account number
Primary Key
Date
Datetime
NOT NULL
Date
old_bal
Float
NOT NULL
Old Balance
Interest
Float
NOT NULL
Interest
tot_bal
Float
NOT NULL
Total balance
Table.4.interest Table
57

Table
5
Loan
Attributes
Data Types
Contraints
Description
Custid
int(20)
NOT NULL
Customer Identification
Primary key
loan_type
varchar(50)
NOT NULL
Loan Type
loan_amount
int(20)
NOT NULL
Loan Amount
Duration
int(4)
NOT NULL
Duration
Name
varchar(25)
NOT NULL
Name
Address
varchar(150)
NOT NULL
Address
Profession
varchar(20)
NOT NULL
Profession
Income
int(20)
NOT NULL
Income
Tele
int(25)
NOT NULL
Telephone Number
Email
varchar(30)
NOT NULL
Electronic Mail
Requestdate
Date
NOT NULL
Request Date
Status
varchar(20)
NOT NULL
Status
Attributes
Data Types
Contraints
Description
cust_id
int(20)
NOT NULL
loan_id
int(20)
NOT NULL
Loan Identification
Table.5.loan Table
Table
6
loan_accept
Primary Key
Type
varchar(100)
NOT NULL
Type
Amount
int(50)
NOT NULL
Amount
Duration
int(20)
NOT NULL
Duration
start_date
Datetime
NOT NULL
Start Date
monthly_inst
int(20)
NOT NULL
Monthly Installment
Contraints
Description
Table.6.loan_accept Table
Entity
Attributes
Data Types
58

loan_paid
cust_id
int(20)
NOT NULL
loan_id
int(20)
NOT NULL
Loan Identification
insta_date
Datetime
NOT NULL
Installment Date
pay_date
Datetime
NOT NULL
Payment Date
due_amount
int(20)
NOT NULL
Due Amount
inst_amount
int(20)
NOT NULL
Installment Amount
Balance
int(50)
NOT NULL
Balance
Status
Int(11)
NOT NULL
Status
Primary key
Table.7.loan_paid Table
Table
8
loan_type
Attributes
Data Types
Contraints
Description
loan_type
varchar(100)
NOT NULL
Loan Type
Primary key
Duration
varchar(20)
NOT NULL
Duration
loan_amount
varchar(50)
NOT NULL
Loan Amount
Table.8.loan_type Table
Table
9
login
Attributes
Data Types
Contraints
Description
user_id
varchar(200)
NOT
User id
NULL
DEFAULT '0',
user_password
varchar(200)
NOT
NULL
Primary Key
User Password
DEFAULT '0
user_type
varchar(200)
59
NOT
NULL
User Type

DEFAULT '0'
Question
varchar(200)
NOT NULL
Question
Ans
varchar(50)
NOT NULL
Answer
Table.9.login Table
Table
10 rejected_information
Attributes
Data Types
Contraints
Description
cust_id
varchar(20)
NOT NULL
Primary Key
Information
varchar(500)
NOT NULL
Information
Primary Key
Table.10.rejected_information Table
Table
11 transactions
Attributes
Data Types
Contraints
Description
Tranid
varchar(200)
NOT NULL
Transaction Identification
Trantype
varchar(200)
NOT NULL
Transaction Type
Tranmethod
varchar(200)
NOT NULL
Transaction Method
Date
Datetime
NOT NULL
Date
cheque_num
varchar(25)
NOT NULL
Cheque Number
acc_num
varchar(200)
NOT NULL
Account Number
Amount
varchar(200)
NOT NULL
Amount
current_balance
Float
NOT NULL
Current balance
Remarks
varchar(200)
NOT NULL
Remark
Custid
varchar(20)
NOT NULL
Customer identification
Table.11.transactions Table
60
3.5 Specification
3.5.1 Hardware specification
Hardware and software are components of any system. For the web based system hardware
describes the physical aspects of computers and related devices. Some of the hardware
requirements used to develop this project includes the following:
CD,CD-R,CD-RW
Flash disk, memory reader.
Personal computer
Table: 12 hardware specification
Item no
Hardware
Specification/use
RAM
Process data
Desktop computer
To do overall activities
Flash disk
Used for back up and store the data
CD-RAW Raw
To take data during various collection method
Note book
3.5.2 Software specification
As described earlier to develop web based system hardware and software materials are vital
components.
To develop web based system for ACSI North Gondar branch, the researcher uses the following
necessary software tools:
Xampp server
PHP
Micro media Dreamweaver 6/8
Adobe reader
Notepad
Microsoft office
61

My SQL database
Visual Paradigm UML and others if necessary.
The following table illustrates software specification of the project.
Table 13: software specification

Item no
Software
Specification/use
Microsoft
Write and Process data
Visual Paradigm UML
To draw diagrams
Adobe reader
To read PDF documents portable document

format
XAMPP Server
To provide response for user
micromediadreamweavercs6
To write code in simple way
Not pad
To write the source code
MY SQL database
Used for managing and creating database
PHP
To create codes
3.6Requirements Specifications
The following sections will introduce the numerous requirements of the system from the point of
view of different users and will introduce a number of decisions that have been made regarding
implementation.
3.6.1 Functional requirements
The system the team develops has different functions or features which are actions of the system
to satisfy the system needed and be acceptable to the user.
62

Customer can request details of the last n number of transactions he/she has performed on any
account. The functional requirements that will provided by the new system include: Register customers to open account.
Customer can request loan
Depositing money for customers who have opened account
Withdraw money from saving account for non-fraudulent customers
Customer can send complaints or messages to Manager or Employee
Customer can view his financial statement. He/she can also take print out
the report.
The system is providing balance enquiry service and
Calculate equated monthly installment
3.6.2 Non-functional requirements
In the system which the team develops, these are requirements which are not the functionalities of
a system but features, characteristics and constraints of a system. These include:
Reducing the response time
Providing a system with user friendly interfaces
Provides a menu based functions
Secure access of confidential information.
flexible service based architecture will be highly desirable for future extensions
3.7 Implementation
This phase consists of implementing the requirements and design into code, data and
documentation and following coding methods and standards. Unit testing is also usually a part of
software implementation. Implementation includes the following points:
i.
Implement the software design into software code.
63

ii.
Ensure that software coding methods, standards, and/or criteria are adhered to and
iii.
iv.
v.
verified.
Ensure that the software code is unit tested per the plans for software testing.
Provide a software version description document for each software release.
Provide and maintain traceability from software design to the software code.
The role of this chapter of the document is to describe the issuesraised during the implementation
phase of the project. The chapter incorporates:
3.7.1 Techniques of implementation
The project team used latest and simple technologies to implement this project such as PHP and
HTML to implement the interfaces and MySQL server for the database. First the project team
implements the interfaces based on the use cases. Then the team implements the database based
on the class diagram they have designed. Finally connect the two by calling one to the other and
the team link pages to go forward and back by using java script and sessions. When the team
writes codes they test each code to save time and effort.
Coding: - with this phase all the works during analysis and design will be turned on to a
functional system prototype which is divided into three parts.
Interface implementation
Database implementation
Logical implementation (implements the server side functionality of the system).
Interface Implementation
The project team implements basic pages/interfaces of the system based on the use case diagram
they have been designed. Mainly there are three interfaces for the three actors such as manager
login page, employees login page and customers login and accessing page. Under these pages
there are subpages through which subtasks are performed by the actors based on the use case
modeled. These pages were included as parts of the system in order to increase its
dynamicity.The project team used PHP and HTML to implement interfaces of the system.
Database implementation
64

The team implement databases of the system based on the class diagram the team has been
designed. The team used MySQL 5.5.8 for the database implementation.
The system which the team implements involve in a central database system that accessing and
storing runs on the server or host computer. Then the employers access the database through the
remote terminals. The foremost advantage of centralized system is centralized security and the
ability to handle enormous amount of data on storage devices. The database application on the
client or employer side referred to as front end, which handles the screen input output
processing. The back end on the server handles data processing where the front-end application
sends across the network to the server.
The system can give users the ability to access back end databases in real time. Users can submit
queries against the entire database from the main server to obtain the most up-to-date data.
Reasons of selecting client/server system
To use this web based system in the institution the team should make employers pc as client and
the main office workstation as server. These is because
The speed of the database is not tied to work stations speed, as bulk of database
processing is done at the back end.
Reduces the load on the network instead of sending the entire data back and forth on
the wire.
It provides data integrity
Database on another partition corrects problems in case the server crashes.
Here the project team aimed of using a client side script of JavaScript. The client side scripting
validates user input, accesses the browser, and enhances the page with active components. And
also can access the browser. And java script is supported by Microsoft explorer which the team
deal on.
Scripts on the server side enables to generate response for clients to obtain the most current
information from the database by connecting to the web server.
Implementing client side functionality: While sharing of the system, pcs of the institution
offices become as Client stations and accessing of the main branch station database.
65

Implementing server side functionality: The server side functionality involves connecting
pages with the database.
3.7.2 Sample Input or output Screens
Home page of ACSI North Gondar Area Web Based system
Fig.19 Homepage of ACSINGAWBS
66
Login page of ACSI North Gondar Area Web Based system
Fig.20 Login page of ACSINGAWBS
67
Login Page for ACSI North Gondar Area Web Based system if you forgotten your Password.
68

Fig.21 Forgotten your Password
Manager Homepage of ACSI North Gondar Area Web Based system
Fig.22 Manager Homepage of ACSINGAWBS
69
Employee Homepage of ACSI North Gondar Area Web Based system
Fig.23 Employee Homepage of ACSINGAWBS
70
Employee Perform Transaction Page
Fig.24Employee Perform Transaction Page of ACSINGAWBS
71
Customers Homepage of ACSI North Gondar Area Web Based system
Fig.25Customer Homepage of ACSINGAWBS
72
Customers View Financial Statement Page of ACSI North Gondar Area Web Based system
Fig.26Customers View Financial Statement page of ACSINGAWBS

73
3.7.3 Sample codes
Manager performs transaction

<?php
session_start();
if(isset($_SESSION['username'])){
?>
<html><head><title>Transactions</title>
<?php
include 'db_connect.php';
$dates=getdate();
$curdate= $dates['year']."-".$dates['mon']."-".$dates['mday'];////print $curdate;
if(isset($_POST['Submit'])) ///forsubmit data
{ $curdate=$_POST['date'];}
$result = mysql_query("Select * from transactions where date = \"$curdate\"",$link) or
die("Database Error");
?><body><TABLE cellSpacing=0 cellPadding=5 width="75%" border=0 align="center" >
<tr><TD width=1288 background="images/top.gif" height=10><STRONG>
<a
href="admin_data.php"><FONT
face="Verdana,
Arial,
Helvetica,
sans-serif"
color="#000000" size=3>Home </FONT></a>

</STRONG></TD></TR><TR><TD width=738 background="images/top_2.gif" height=9>
<?php $modes=$_GET['mode'];
if($modes=='admin') {
print "<a href='tran_do.php?mode=admin'>"; }
else if($modes=='employee') {
74

print "<a href='tran_do.php?mode=employee'>"; }
else {
print "<a href='tran_do.php?mode=cust'>";
} ?><b></b>
<FONT face="Verdana, Arial, Helvetica, sans-serif" color="#000000"><STRONG>
<B> Perform Transaction</B></STRONG></font>
<font size="2" face="Verdana, Arial, Helvetica, sans-serif" color="#ffffff">
</a></TR><TR>
<TD style="BORDER-BOTTOM: #e5e5e5 5px solid" width=738 height=190 width=150
background="images/3_1.jpg"><DIV align=right>
<form name="Form1" method="post" action=""><p> </p>
<table width="426" border="0" align="center">
<tr><td width="420"><div align="center">
<font face="Verdana, Arial, Helvetica, sans-serif" >
<font color="#0000FF"></font></font></div></td></tr></table>
<TABLE width="30%" height="30%" border=3 align=center cellPadding=3 cellSpacing=0
class=rt id="rt" ><TR>
<TD class=sectionhead align=middle colSpan=2>
<div align="center" class="style2"><B>Date(yyyy-mm-dd)</B></div>
</TD><TD class=secondalt align=center>
<?php
print "<input name=\"date\" value=$curdate size=20>";
?></TD></TR></table><div align="center"><p>
<input name="Submit" type="submit" class="admin_add_items" value="Fetch">
</p></div><DIV align="center">
75

<table width="75%" border="0" cellpadding="2" cellspacing="1" class="man_auth" >
<tr><th width="50"><span class="style6">Transaction Id </span></th>
<th width="60"><span class="style6">Transaction Type</span></th>
<th width="60"><span class="style6">Transaction Method </span></th>
<th width="10"><span class="style6">Date </span></th>
<th width="50"><span class="style6">Account Number </span></th>
<th width="50"><span class="style6">Amount </span></th>
<th width="50"><span class="style6">Remarks </span></th></tr><tr>
<?php
while($row = mysql_fetch_array($result, MYSQL_BOTH)){?></a></div></td>
<td><div align="left">
<?php
echo $row[0]; ?></a></div></td><td><div align="left">
<?php
echo $row[1];
?></div></td><td>
<?php echo $row[2];?>
</a></div></td><td><div align="left">
<?php echo $row[3]; ?>
76

</td></tr>
<?php }
?>
</table><p><FORM><p align="center">
<INPUT
TYPE="button"
value="Print
Transaction
Details"
onClick="window.print()"
style="font-weight: bold"></p>20342096</FORM></p><p> </p><p>
<input
name="Submit2"
type="button"
class="admin_add_items"
id="Submit2"
onClick="location.replace('./admin_data.php')" value="Cancel" ></div></p>

</p><p> </p><p> </p><p> </p><p> </p><p> </p>
</DIV></TD></TR></TBODY></TABLE></body></html>
<?php }
Else {
echo "Please click here to login " . "<a href=index.php>Login Page</a>"; }
?>
3.8 Testing
Testing is one validation technique of the system with acceptable standard inputs from the
different testing types. Such as:
Unit testing: by which the team tested components individually.
Integration and system testing: the project team has tried to test the system for its integration
that justifies that major components of the system are working as per the requirements gathered.
77

The project team conduct test to get information about the quality of the product or service
under test. It can also provide us an objective, independent view of the software to allow the
business to appreciate and understand the risks of implementation. During this stage issues such
as that of web application security, the functioning of the site, its access to handicapped as well
as regular users and its ability to handle expected functions has been checked. The team used
system testing for validating and verifying whether the system:
Meets the requirements that guided its design and development,
Works as expected,
Can be implemented with the same characteristics,
And satisfies the needs of the institution.
3.8.1. Test Plan Overview
This sub topic describes the plan for testing the system against its requirements. The purpose of
these system test plan is to make sure that the system complies with the definition of the software
requirements.
The test plan focuses on how the testing for the project will proceed, which units will be tested
and what approaches (and tools) are to be used during the various stages of testing. The test Plan
is a collection of all test specifications for a given area of the system. The Test Plan contains a
high-level overview of what is tested for the given feature area. Test case specification has to be
done separately for each unit.
The team considered the following major tasks to prepare system test plan and performing the
system tests:
Designing the system tests.

Ensuring that all environmental needs are satisfied for the system tests.
Completing the integration tests. Performing system tests.
Writing a test report and, if necessary, problem reports.
3.8.2. Features to be tested
The major features to be put in the test check list and performed through the system test process
depending on the system testing requirements include:
-
Customer ,Employee and Manager Login page

Customer Registration form
Deposit form
78

-
Withdrawal form
Complaints Form
Add loan type
Create password
3.8.3 Testing Approach
For the test plan the team used both the two popular approaches of system testing. Because both
of them have different roles for the effectiveness of the system. The properties tested by one
approach are not covered by the other. That is why use two approaches.
Static vs. dynamic testing approach
Static testing: this method is used us for review, inspection and verification of the
system. In this method the team can check source code structure by using programming
tools/text editors or the team can check syntax and data flow as static program analysis
by using compilers (pre-compilers).
Dynamic testing: the team used this approach for actually executing programmed code
with a given set of test cases and to validation it. Typical techniques for this are either
using stubs or drivers or execution from a debugger environment.
3.8.4 Testing materials
No special resources are required for testing the system beyond those already needed for
development.
The following are list of materials such as hardware requirements, software requirements and
people or focus groups used for testing each features.
Laptops
Software the team used for development such as xampp Server, browsers, operating
systems, application softwares(Office, UML),Dreamweaver
Web Server machine(pc with web server software as web server)
Database server (pc with database server software)
People like project team, focus groups, organizational person: for crowd test
79

3.8.5 Test Case Specification
The team has to develop test case specifications from the test plan and are the second phase of
the test development life cycle. It should explain "how" to implement the test cases described in
the test plan.
With test Case Specification the team describes the purpose of a specific test, identify the
required inputs and expected results, provide step-by-step procedures for executing the test, and
outline the pass/fail criteria for determining acceptance.
3.8.5.1 Test case specification identifier
The project should use unique identifier to identify this test case specification, its level and the
level of software that it is related to. Preferably the case specification level will be the same as
the related software level. Ideally the case naming convention should follow the same general
rules as the software it is related to. This is to assist in coordinating software and test ware
versions within configuration management. Such as:
Unique "short" name for the case

Version date and version number of the case
Version Author and contact information
Revision history
Input data and expected results of the systemafter testing.

N
Test case name
Test procedure
Precondition
ExpectedOutpu
result
Output
Customer
Fills First Name, Last Manager Home Added to the Success
Registration form
Name, Age, Address, page,
database,
Email, Contact number
Employee
added to the
home page
database
o
1
Login form
Fills
User
Name, HOME
80
Display
Not
login Success

Password
successfully,
Pleas enter the
correct user id
or password
Add Loan type
Manager
Fills
Type,
Loan Loan type page
Duration,
Add
to
the Success
database
Amount.
or
Not add to the

database
Create Password
Manager
Fills Set password,
Add
to
the Success
Password,
confirm
database
or
password,
secrete
Record
is
question,
Answer,
already exist
Authentication type
Table.14. Input data and expected results of the system after testing.
Input data and expected results of the systemnot yet tested.

N
Test
name
Deposit
case Test procedure
Precondition
ExpectedOutpu
result
Transaction number, Transaction Transaction
Transaction
type
method, Page
Completed
Amount,
Successfully
Account
,Transaction
number,
Remark
2
Withdrawal
Transaction number, Transaction Transaction
Transaction
type
Completed
,Transaction
method,
81
Output

Account
number,
Amount, Page
Successfully
Remark
Table.15. Input data and expected results of the systemnot yet tested.
3.8.5.2 Test items
The scope of the system testing encompasses the systems based features, computer software,
hardware, and their interfaces. The software to be tested is the web based system. Information on
what the system must do can be found in the Software Requirements Document. Information on
how the system works is listed in the Architectural Design Document and the Detailed Design
Document.
Each test specification should contain the following items:
Case No.: The test case number should be signed with its identifier
Title: the title of the test.
ProgName: the program name containing the test.
Author: the person who wrote the test specification.
Date: the date of the last revision to the test case.
Background: (Objectives, Assumptions, References, Success Criteria): Describes in
words how to conduct the test.
Expected Error(s): Describes any errors expected
Reference(s): Lists of reference documentation used to design the specification.
Script: (Pseudo Code for Coding Tests): Pseudo code (or real code) used to conduct the
test.
82

3.8.5.2.1 Input specifications
The team has to identify all inputs required to execute the test case. Again these may vary based
on the level the case is written for. The team has to be sure to identify all required inputs not just
data elements and values. Input specifications include:
Data: Values, Ranges and Sets

Tables
Human actions
Conditions: States, Initial, Intermediate and Final
Files
Databases: Control files, Transaction files,
Relationships: Timing
3.8.5.2.2 Output specifications
Identify all outputs required to verify the test case. Again these may vary based on the
Level the case is written for. Again the team have to be sure to identify all required outputs not
just data elements and values.
Test Case 1. Register Customer

Test Case Identifier
Field
Test Item
Input Type
Output
Test case1.01
First Name
Character
/\@,
Invalid First Name

otherwise Valid
Test case1.02
Last Name
Character
/\@,
Invalid Last Name

otherwise Valid
Test case1.03
Age
Number
Less than 18 Invalid age otherwise

years
83
valid

Test case1.04
Email
Character
a-z@a-z.com
Valid
otherwise
Invalid
Test case1.05
Phone Number
Number
0-9
Valid
otherwise
invalid
Table16. Test Case 1.Register Customer
Test Case 2. Login

Test
Case Field
Test Item
Input Type
Output
Character
/\@,
Invalid
Identifier
Test case2.01
User Id
User
Id
otherwise Valid
Test case2.02
Password
Character
Empty
Invalid
Password
otherwise Valid
Table.17 Test Case2.Login
Test Case 3. Add Loan Type

Test
Case Field
Test Item
Input Type
Output
Character
/\@,
Invalid Loan Type
Identifier
Test case3.01
Loan Type
otherwise Valid
Test case3.02
Duration
Number
0-9
Valid
Duration
otherwise Invalid
Test case3.03
Amount
Number
0-9
Valid
Amount
otherwise Invalid
84

Table.18 Test Case 3.Add Loan Type
Test Case 4. Create Password
Test
Case Field
Test Item
Input Type
Character
Empty
Output
Identifier
Test case4.01
Create
Password
Password
not
be
must
empty
otherwise Valid
Test case4.02
Confirm
Character
Empty
Password
Confirm Password
must not be empty
otherwise Valid
Test case4.03
Secret
Select
Select
question
Valid
Secret
question otherwise
Invalid
Test case4.04
Answer
Character
Correct
Valid
otherwise
Invalid
Table. 19. Test Case4.Create Password
3.8.5.2.3 Environmental needs
The system test includes Hardware configurations and limitations, system software (e.g.,
operating systems, compilers and tools), other software applications, facilities, training).
Definitely a setup of software and hardware on which the testing team performs testing is test
environment. It consists of the Test Server setup, Network setup, Test PC set up, Reporting
environment setup etc. Lets go in details now.
Setup of Test Server: Every test cannot be appropriate in local machine so the team need
to set up test server with xampp for php, java based applications with mail servers.
Network set up: network with internet or without internet, with in the same network or
private network for testing, so that the congestion that is occurred during testing doesnt
hamper
the
other
members
involved
content writers etc.)
85
in development
(developers,
designers,

Test PC setup: Setting up the needed OS for this web application testing then the team
have to setup different browsers for different testers and different OS family too.
Bug Reporting environment set up: Creating a project, assigning testers so that testers
can login, post the bug properly and developers and designers can see it and fix it.
3.8.5.2.4 Special procedural requirements
The system Test Procedures describe the test preparations, test cases, and test procedures to
beused to perform qualification testing of the system or subsystems. These include:
Test preparations, including hardware and software.
Test descriptions, including: Test identifier, System requirements addressed by the test
case, Prerequisite conditions, Test input, Expected test results, including criteria for
evaluating results, and assumptions and constraints, Criteria for evaluating results.
Requirements traceability.
Identification of test configuration.
3.8.5.2.5 Inter case dependencies
The project team has to identify any prerequisite test cases. It is also recommended that the
relationship of test cases be documented at both ends of the relationship.
Loan depends on registration.

Loan request depends on loan type and loan amount
Loan paid depends on loan amount
Withdrawal and Deposit of money depends on account number.
Financial statement Depends on Transaction(deposit or withdrawal)
3.9 Documentation
After the completion of the proposed system everything that the project team members
discussion and activities, process procedures will be documented. The documentation phase
explains how it operates or how to use it, or may mean different things to people in different
roles.
Technical: Manuals, instructions, tutorials, procedures, specifications, etc., that accompany a
piece of equipment or software, and provide guidance for its proper use and maintenance.
86

3.10 Evaluation
The final project was evaluated weather the system good or not; weather it satisfies the user need
or not. It involves the analysis of costs, outcome or impact, implementation as well as the need
for the project. During evaluation the project team checks the results and evaluates the success of
the project. Furthermore the project evaluated by professionals of Information science and other
related expert invited guests.
In the process of this new project evaluation, evaluators were able to critically reflect their
experiences together, through a series of visits and workshops.
Section 4: RESULT and DISSIMINATION

4.1 Results achieved
The team can describe the results of the project in two categories as a summary:
Outputs of the project
Secure and accurate database: It is an important output both for the organization
to store, manage and access their employees and customers data, for the
employees and customers to access their data in the organization through internet
anywhere. It is also important for the flow of information timely, securely and
evenly in the organization.
Online financial services: It includes fast, clear, secure and easy services such as:
loan service, deposit service, withdraw information, system which calculate
interest for clients, customer information delivery service
And it will have User friendly and interactive interface for both employees and
customers.
Outcomes of the project
The project enables the organization to have an automated and online micro finance system for
processing of client information and providing financial services for customers.
87

The project enables customers and employees to access their data at any time
anywhere through internet.
The project reduces the manual work of the organization
The project enables the organization to compete with other institutions by making its
services that it delivers efficient and effective.
It reduces the work load of the employees and redundancy of work
Knowledge and experience gain for the project team
And other outcomes such as: security of data ensures data accuracy; minimum time
needed for the various processing, speed of services, and reduce error of financial
works.
4.2 Dissemination
Dissemination is the process of making the results and deliverables of a project
available to the stakeholders and to the wider user. Dissemination is essential for takeup, and take-up is crucial for the success of the project and for the sustainability of
outputs in the long term. The project work is basically do the web based system of
ACSINGA in such easy way and it is disseminated to ACSINGA for managing its
asset properly and to the community.
All dissemination should have a purpose, and support or inform project development
in some way. The purpose of the activity may be to:
Raise awareness let others know what the team are doing
Inform educate the community
Engage get input/feedback from the community
Make sustainable ensure that the effects would be sustained after the project.
4.2.1. Dissemination method
Publications
The project team have planned to present the project and describing its results
through publication (like Credit and savings multimedia service, radio air time
program).
Conferences and workshops
and also the project team have planned to present the project when the organization
prepares conferences, workshops, or case studies based on the technology and related
issue.
Website
88

Most projects create a web page or web site to explain the project aims and objectives
and to disseminate information about project activities and results. As a result the
investigators have decided to advertise the project through internet.
SECTION FIVE
5. Budgeting
5.1. Budget of the project
Table 20: Budget for Stationary
S/n
Items
Measurement
Quantity
Unit Price
Total
A4 Paper
Ream
90.00
180.00
Pen
PCS
10
5.00
50.00
DVD-RW
PCS
25.00
50.00
Flesh disk(8GB)
PCS
280.00
280.00
Grand Total
560.00
Table 21: Service expenses

S/n
4
5
7
8
6
Grand total
Description
Printing
Copy
Telephone
Binding
Miscellaneous expenses
Total expense
100.00
50
150.00
30.00
200.00
530.00
Table 22: Budget Summary

S/n
Description
Total expense
89
Remark

1
Stationary
560.00
Service
530.00
Grand total
1,090.00
90

SECTION SIX
6. Action Plan
91

Table.23:Project-schedule
92

Section 7 conclusion and Recommendation
7.1 conclusions
Generally, as the world becomes more of a global village being run by paperless systems, the
idea of a cashless society is the hope of the future. Thus more innovations will still evolve which
will make cashless transactions easily accessible and affordable.
Credit and saving institutions provide a broad range of financial services such as deposits, loans
payment services, money transfers, and insurance to poor and low income households and their
micro enterprises. There is growth and expansion of microfinance programs and increasing
attention to microfinance as a poverty reduction strategy throughout our country.
For these rapidly growing micro-finance institutions in Ethiopia, the key to survival and
profitability lies in lowering the operational and transactional cost and having effective control,
compliance and reporting mechanisms that would subsequently result in timely recovery. This
dual requirement of low cost and timely monitoring and reporting can only be met with the
help of technology that can even be applied down to the unit, or transaction, level.
Automation of credit and saving functions that includes deposits, withdrawals, loans, cash
management and accounting operations is the key to lowering per transaction cost and long term
success of micro-finance institutions.
In addition, the web based system solution should help the growing number of credit and saving
institutions to lower their per-transaction cost which in turn will help the poor and low income
households gain the benefits of credit and saving. Based on these survival and profitability need
credit and saving of institutions, the team develop this financial Software system for ACSI NGA.
This implementation of a web based solution will not only help the institution but also promote
education for the project team in the field of information technology.
The project team began the project by laying out the foundation that dictates the development
process. This involved identifying and stating the problems of the current manual system, review
of related literatures such as some researches and projects conducted on microfinance and
banking systems, describing the functionalities and scope of the proposed system, defining the
system development methodology, identifying resource requirements, and setting the project
schedule.
93

The team performed requirements analysis to discover the needs of the new solution to
proposed system. This phase consists of drawing out functional and non-function
requirements of the system. And then the team performed objects oriented analysis and
object oriented design.
In analysis, the team tried to model the new and proposed system using UML diagrams:
use case diagrams, sequence diagrams, Class diagrams, Activity diagrams. The team
gave a clear preview of what the new system might look and feel with our user interface
design and documentation.
In design phase, the team extended our work in analysis with more models. The Class
diagrams in analysis were extended in design to step closer to implementation, while
deployment and component diagrams were also drawn.
In implementation part, the team has done Conversion of manual financial system to
web based system with basic stated functionalities for the Amhara credit and saving
institution North Gondar Area.
The key benefits of this project are the following:
Amhara Credit and Saving Institution North Gondar Area will benefit with
implementation and integration this Software into their current systems to
survive and prosper in this growing industrial country.
There will be reduction in per-transaction cost and less administrative and
operational cost.
The product will yield enhanced compliance and reporting
The paper work will overcome by being computerized.
The database access to the whole employees and customers will be achieved
through the result of central DBMS with exact database report.
The number of employers needed was reduced to the economic benefit of the
institution.
Retrieval of customer information will be achieved online through internet.
Time and money loss of customers is reduced due browsing report techniques
7.2 Recommendation
Improved access to credit and saving services can enable the poor to smooth out their
consumption, manage their risks better, build their assets, develop their micro-enterprises,
enhance their income-earning capacity, and enjoy an improved quality of life.
94

Supporting the credit and saving sector with the Information Communication Technology (ICT)
is a major strategy to provide quality service to the clients. Automated systems offer real time
information flow. One way in which automated systems reduce human error and repetition is by
automatically populating some fields with information.
As the project team has described in chapter one there are different researches conducted about
credit and saving institutions. But in almost all institutions the system is running manually. The
team has reviewed a number of related researches and other documents to understand the
services or functionalities performed in this institution. On the basis of the research works and
documents, the team has successfully designed and implemented online CS. But for the future as
the services of the institution becomes increased, this system should be improved by adding
functions and using better technologies. So, future works that the project team proposed are:
Maintaining the system according to the services of the organization after applying and
testing the acceptance of the project by the organization
Connecting the system with other financial organizations or banks.
Applying Mobile Transactions in Micro finance System
Transfer of money from one account to other account.
References
1. YigremKassa (2010). Regulation & Supervision of Microfinance Business in
Ethiopia. Ethiopia press, National Bank Of Ethiopia
2. WoldayAmha (Dr.) (2007). Review Of Microfinance Industry In Ethiopia: Regulatory

Framework And Performance. Ethiopia: Printed in Ethiopia, Occasional Paper No. 2
95

3. ACSIS.c (2004). Call for Consultancy Service- on MIS Automation Unpublished
document.Gondar
4. Gary M. Woller (2004). Entrepreneurial Finance and Business Ventures Journal of

Brigham Young University, Vol. 9, Issue 1, pp. 1-26
5. Armendariz, Beatriz and Morduch, Jonathan (2005). The Economics of Microfinance.
The MIT Press, Cambridge, USA.
6. Gebrehiwot A. (2002). Microfinance Institutions in Ethiopia: Issues of Portfolio Risk,
Institutional Arrangements and Governance, in Microfinance Theory, Policy and
Experience in Zaid N. et al. (eds). Mekelle University: Mekelle, Ethiopia.
7. Federal Democratic Republic of Ethiopia (1996). Proclamation to provide for the
Licensing and Supervision of the Business of Micro Financing Institutions Federal
Negarit journal: Proclamation No. 40/1996, Addis Ababa, Ethiopia.
8. Tb. MaulanaKusuma (2006). System Testing and Implementation. Available at

http://staffsite.gunadarma.ac.id/mkusuma retrieved in 20may, 2013
Appendixes
A. ACSI System Users manual/guide
System Manager
System manager has a highest power of the system.
He or she registers customers and employees, update customers details and employee
details, and deletes customers and employee details.
Set Password for customers and employees, update passwords for customers and
employees.
Perform Transactions (i.e Deposit and Withdrawal) for Customers and employees.
Manage loan(check loan request, processes loan)
Steps how manager processes customer loan request
96

1. Login to the ACSI system
2. Click Manage Loan Button
3. Click Check loan request Button from the customers
4. Admin views the loan request from customers and decide the loan to be accepted or
rejected based on the criteria.
5. Finally either the Loan can be sanctioned or cannot be sanctioned.
How to Apply for Loan?
To apply for a loan a person should be registered by going to the ACSI in depositing 50 birr to
open account.
After registration, he or she has got a customer id (user id) and password.
By entering to the website of ACSI he or she can apply for loan in the following loan types.
These areas of loan are:
-
Manufacturing, Petty Trade, Service, Urban Agriculture and, Construction
Steps to go
1.
2.
3.
4.
5.
6.
Login to ACSI System

Click on View Loan Button
Click on Loan Request Button
Selects from the Loan type(i. e Petty trade, Urban Agriculture, etc)
Click on Send button
Customers can view the details like loan type, Loan Amount, Duration, profession, and
Gross annual income

7. Click Send button.
B. Data collection method
Questions
Questions that the team used for interview to collect necessary information
1.
2.
3.
4.
5.
6.
When the institution was started its service?

What are services or functionalities that institution provides for customers?
Do all the service operations performed manually?
How about the satisfaction of customers with the current manual system?
What about the profitability of the institution with this manual system?
The project team wants to develop web based system for your institution. What are
the basic functionalities that you need to be included in the system?
97

7. What services you need to be added from those that the institution currently
providing?
8. Could you tell us the current operational procedure detail?
a. What are the main actors of the system?
b. Could you tell us the operational roles of each actor?
i. What is the role of the employees?
ii. What is the role of the customers to get service?
iii. What is the role of the manager?
c. Could you show us the organizational structure?
C. Accomplished Forms
Fig.27. Example of a Dposite slip, using flat rate calculation manually
98

Moges

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Moges

Enviado por

Direitos autorais:

Formatos disponíveis

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Table: 1 Accounts table .... 59

Table 6: loan accept Table .... 62

Web Based System for ACSINGA

Fig. 1: Architecture of the system...,,,. 17

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Statement of the Problem..............................................................................3

1.3. Objective of the project.................................................................................... 4

Scope of the project....................................................................................... 4

1.5. Limitation and Delimitation of the project........................................................5

Background CSI in Ethiopia............................................................................ 6

The Review of CSI system in Ethiopia............................................................8

Web Based System for ACSINGA

Section 7 conclusion and Recommendation.............................................................97

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Web Based System for ACSINGA

Employees are overloaded by the paper work

Client dissatisfaction due to service delay

It has a disadvantage on the competitive advantage on other related institution

It is redundant, not economical and not flexible

Hindrance of smooth information flow among stake holder

It needs large space for storage of document

Imposes work load on employees and dissatisfaction

Difficulty to trace information easily

Difficulty of identifying the background of the customer

Absence of simple and comfortable working system.

Absence of methods to specify deep need of the customer.

Absence of reliable record keeping due to manual working system.

Web Based System for ACSINGA

The specific objectives of the project are the following:

Model and designing the solution to meet requirements of the system.

To recommend additional projects if any.

1.4 Scope of the project

Handle client information

Web Based System for ACSINGA

1.6. Significance of the project

Web Based System for ACSINGA

It enhances accuracy, speed, efficiency, flexibility, reliability, and

2.1. Background CSI in Ethiopia

Web Based System for ACSINGA

the credit and saving institutions in Ethiopia to show impressive

Web Based System for ACSINGA

2.2. The Review of CSI system in Ethiopia

76.8% of the population is living in rural area where there main

activity is subsistence agriculture. Sectored breakdown of goods and services produced

Web Based System for ACSINGA

Web Based System for ACSINGA

strategy throughout the country leads to use information technology to

address services easily and to enhance the satisfaction of the customers.

3.2. Data collection method

Web Based System for ACSINGA

Web Based System for ACSINGA

3.3. System Analysis

Web Based System for ACSINGA

Web Based System for ACSINGA