0% found this document useful (0 votes)

412 views113 pages

Web-Based Credit System for Gondar Union

This document describes a project to develop a web-based credit and savings system for the University of Gondar Employees' Union in Ethiopia. A group of five students list themselves as members of the project team. The system will be developed to fulfill requirements for the students' bachelor's degrees in Information Science from the University of Gondar. It will allow employees to manage credit and savings accounts online rather than with a paper-based system. The document includes sections on objectives, scope, literature review, system design, implementation, testing, and recommendations.

Uploaded by

Dagem Gissila

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

412 views113 pages

Web-Based Credit System for Gondar Union

Uploaded by

Dagem Gissila

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

UNIVERSITY OF GONDAR

FACULTY OF INFORMATICS
DEPARTMENT OF INFORMATION SCIENCE

Web based credit and saving system for University of Gondar

Employee’s union work Association

Group Member ID
1. Abebe Mekie 9015/06
2. Adiyam Nega 0935/06
3. Henok Desalegn 1097/06
4. Roba Jarso 1183/06
5. Tebibu Solomon 1219/06

A project document submitted to Department of Information Science, Faculty of

Informatics, and University of Gondar in partial fulfillment for the award of the
degree of Bachelor in Information Science.

Gondar, Ethiopia
June, 2016
Approval sheet
This proposal project en-titled “Web Based System for University of Gondar Employee’s
credit and saving union work association” 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.

Research and Scholarly Communication Management Team Leader.

Principal Advisors

Signature Date

AlehegnAdane …………………. …………..

TsehayDiges ………………… …………..

Dr V Rama Devi ………………… …………..

Gondar, Ethiopia

i
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 project proposal effectively beyond what we had anticipated. Next
we would like to express our deepest gratitude to our advisors Alehegn Adane, Dr V Rama Devi
and Tsehay Diges who contributed all their idea in order to make this project proposal the best as
much as they can. Thus we are very grateful for all these; the project team thanks the University
of Gondar Employees credit and saving union work association’s administration members who
helped us by providing all important information needed for the fulfillment and successful
completion of the work.

ii
Table of Contents
Approval sheet ......................................................................................................................................... i
Acknowledgement .................................................................................................................................. ii
List of Tables ........................................................................................................................................... v
List of Figures ......................................................................................................................................... vi
Acronyms and Abbreviations ................................................................................................................. vii
Abstract ............................................................................................................................................... viii
Chapter One ............................................................................................................................................ 1
Introduction ........................................................................................................................................ 1
1.1 Background History of the Organization ..................................................................................... 1
1.2 An Overview of the Existing System............................................................................................ 1
1.3 Statement of the Problem .......................................................................................................... 3
1.4 Objective of the project ............................................................................................................. 5
1.5 Project Scope ............................................................................................................................. 6
1.6 Significance of the project .......................................................................................................... 7
1.7 Limitation and Delimitation of the project .................................................................................. 7
Chapter Two............................................................................................................................................ 9
Literature Review ................................................................................................................................ 9
2.1 The Review of CSI system in Ethiopia........................................................................................ 11
2.2 The Historical Development of the CSI in Ethiopia .................................................................... 12
Chapter Three ....................................................................................................................................... 14
Project Design and Methodology ....................................................................................................... 14
3.1 Data Collection Methods .......................................................................................................... 14
3.2 Feasibility Analysis ................................................................................................................... 15
3.3 Proposed System ..................................................................................................................... 17
3.4 Requirements Specifications .................................................................................................... 20
3.5 Specification ............................................................................................................................ 21
3.6 System Analysis........................................................................................................................ 22
3.7 System Design .......................................................................................................................... 44
3.8 Data Dictionary ........................................................................................................................ 56
3.9 Implementation ....................................................................................................................... 60
3.10 Testing and Evaluation Methods ............................................................................................ 70

iii
3.10.2 Evaluation ............................................................................................................................... 77
Chapter Four ......................................................................................................................................... 79
RESULT and DISSIMINATION .............................................................................................................. 79
4.1 Results achieved ...................................................................................................................... 79
4.2 Dissemination .......................................................................................................................... 80
Chapter Five .......................................................................................................................................... 81
Conclusion and Recommendation...................................................................................................... 81
5.1 Conclusions .............................................................................................................................. 81
5.2 Recommendation..................................................................................................................... 83
Reference .............................................................................................................................................. 84
Appendix ............................................................................................................................................... 85
Sample Code ......................................................................................................................................... 86

iv
List of Tables
Tables Page

Table 1: Account table---------------------------------------------------------------------------------56

Table 2: Customer table--------------------------------------------------------------------------------57

Table 3: Loan Table------------------------------------------------------------------------------------58

Table 4: Login table------------------------------------------------------------------------------------58

Table 5: Transaction table-----------------------------------------------------------------------------59

Table 6: Reservation table-----------------------------------------------------------------------------60

Table 7: Input data and expected results of the system after testing-------------------------------------------73

Table 8: Input data and expected results of the system not yet tested------------------------------74

Table 9: Test Case 1.Register Customer--------------------------------------------------------------76

Table 10: Test Case2.Login----------------------------------------------------------------------------76

Table 11: Test Case4.Create Password----------------------------------------------------------------77

v
List of Figures
Fig.1 architecture of the system-------------------------------------------------------------------------19

Fig 2. Usecase Diagram ---------------------------------------------------------------------------------25

Fig 3. Activity diagram for New Customer Registration-----------------------------------------------38

Fig 4. Activity diagram for Withdraw Money-----------------------------------------------------------39

Fig 5. State chart diagram of the system----------------------------------------------------------------40

Fig 6. Staff Deposit Money to Customers----------------------------------------------------------------41

Fig 7. Customers View Loan----------------------------------------------------------------------------41

Fig 8. Staff Withdraw Money for Customers-----------------------------------------------------------42

Fig 9. Manager/Admin Login in to the System---------------------------------------------------------42

Fig 10. EMI-----------------------------------------------------------------------------------------------43

Fig 11. Staff Registers new Customers/Employee------------------------------------------------------43

Fig 12. Association of Customer Class------------------------------------------------------------------46

Fig 13. Association of Loan Class-----------------------------------------------------------------------47

Fig 14. Class Diagram of Web based UoG Employees credit and saving system ---------------------------------------48

Fig 15. Subsystem decomposition Diagram--------------------------------------------------------------53

Fig 16. Hardware/software mapping---------------------------------------------------------------------54

Fig 17. Deployment diagram of the system--------------------------------------------------------------57

Fig 18. Homepage of the System-------------------------------------------------------------------------63

Fig 19. Login page of the system-------------------------------------------------------------------------64

Fig 20. Admin Page of the system-----------------------------------------------------------------------65

Fig 21. Manage Customer on Admin page of the system----------------------------------------------66

Fig 22. New customer’s registration page of the system----------------------------------------------67

vi
Acronyms and Abbreviations
CSI- Credit and Saving Institution

EMI-Equated monthly installment

HTML-Hypertext markup language

IT-Information Technology

MIS-Management Information System

UML-Unified Modeling Language

UoG – University of Gondar

CSS – Credit and Saving System

vii
Abstract
The purpose of this project which is entitled Web Based credit and saving System for University
of Gondar employees union work association, the system is Reduces 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. The existing system of the organization is facing different problems such as data
redundancy, lack of data security and lots of paper work. To do this proposal the project team
used different data collection methods such as Interview, Document analysis and Practical
observation. In order to analyze and design the system we are going to use Object oriented
approach for both analyzing and designing the new system. 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.

viii
Chapter One
Introduction
1.1 Background History of the Organization
University of Gondar employee’s credit and saving union work association refers to an array of
financial services, including loans and savings. University of Gondar employee’s credit and
saving union work association is one of the largest and coordinated associations with many
members mainly serving employees (at any level) of the University of Gondar. It is found at
Gondar which was the former Ethiopian capital city and one of the oldest and historical cities of
all time in the country specifically at CMHS campus of the University.
The association was established in 1985 E.C as a mini saving and credit association with only 20
members and only one accountant. Dues of members were only 2-3 birr per month by the time as
the association started. Later in 1995 E.C grown to be fully functional, coordinated with many
workers working under it and serving vast amount of employees in the university. The
association is ruled under administering committee which is consists of chairman, assistant
chairman, and clerk and committee members. Now the association has five accountants to
facilitate the work of the association having a vision of serving all the society/employees of
university.
The association has now around 3200 members who are employees of the university at different
campuses. Now the capital of the association has risen to 22 million. Any regular employee can
be a member of the association if he/she is willing to contribute 5% of his/her salary.
Headquarter of University of Gondar employee’s credit and saving union work association is
located at the university’s Medical campus.

1.2 An Overview of the Existing System

The association has big responsibility to serve a large number of university staffs who has being
increasingly affected by different financial difficulties; The management of the association is
concerned with increasing effort in keeping the records of the client and recording their
daily,monthly,annual and cumulative amount of their financial status on ledger. It maintains full
information of the clients served in the association for the purpose of future use.

1
Every activity inside the association is performed manually. New employee’s registration, loan
requests are also performed manually in a paper work. The records are kept manually putting the
records of members on subsidiary ledger in order to calculate individual members financial
status this process may result errors and also loss of records.
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. Efficient use of
technology can help improve efficiency, and increase outreach, credit and saving association’s
still find it difficult to harness the potential and avoid the pitfalls. Some of the core benefits of
web based system are, Cross platform compatibility, more manageable, highly deployable,
secure live data, and Reduced costs.

Supporting University of Gondar employee’s credit and saving union work association with the
Information Communication Technology (ICT) is a major strategy to provide quality service to
the staff/members. 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.

Staffs and employees University of Gondar employee’s credit and saving union work association
are facing difficulty in accessing and managing their accounts because the activities of this
accounts can't be done unless on the association provide cards manually.

This is what led us to do this project, help the University of Gondar employee’s credit and saving
union work association saving time and effort wasted on the search for individuals to access each
member’s account and information, by providing the association’s services at anytime, anywhere
through the website.

2
1.3 Statement of the Problem
Web based employee’s credit and saving association is defined as the automated delivery of new
and traditional credit and saving products and services directly to customers through electronic,
interactive communication channels that allows customers to submit their instructions,
applications for different services, queries in their account balances. It includes the systems that
enable financial association’s customers, individuals or businesses, to access their accounts
(association account), make transactions, or obtain information on financial products and
services through a public or private network, including the Internet. Staffs access its services
using an intelligent electronic device, such as a personal computer (PC).

It identifies a particular set of technological solutions for the development and the distribution of
credit and saving services, which rely upon the open architecture of the Internet. With the
implementation of Web based credit and saving system, it maintain a direct relationship with the
end users via the web and are able to provide a personal characterization to the interface, by
offering additional customized services.

According to the interview made with the manager, even if most of activities are done manually,
there is semi automates activity that is recording customer’s 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. Obviously the organization has got lots of business related problems that can be
solved by applying the computer system methodologies. The Association is facing many
problems in the current working environment from those we have tried to mention major once
below.

 Lack of security of data

 Data/file/information redundancy.
 Difficulty to generate monthly transaction report due to Absence of reliable record
keeping
 The manual system has no easy balance inquiry (enquire) facility.

3
 Members can’t request details of his/her last transactions he has performed on his/her
account.

 Consumes large volume of paper work

 Needs manual calculations
 It needs large space for storage of document
 Difficulty to trace information easily
To avoid all these problems and make the working more accurately the system needs to be web
based.

4
1.4 Objective of the project

1.4.1 General objective

The general objective of the project is to develop a Web based credit and saving system for
University of Gondar Employee’s union work Association .

1.4.1 Specific objective

The specific objectives of the project are the following:

 To create a system that reduces the manual work in the institution.

 To automate all the financial works in the association.

 To develop a system in which all transaction are available and easy.

 To develop user friendly interface.

 To develop a system that can generate monthly report.

 To develop a system that shares information easily in the association..

 To develop a system that provides fast and secured services.

5
1.5 Project Scope
The scope of this project focus on developing a Web based credit and saving system for
University of Gondar Employee’s credit and saving union work Association. Our project is
mainly focused to automate the manual system that has being used by the association currently
and to develop a web based system for the association in a way that it could greatly increase the
working efficiency of the association. The project is set to be completed by the end June, 2016.

And the web based system performs the following tasks:

 Register new customers/members

 Handling loan Service
 Handling saving deposit
 Handling withdraw money information
 Handle employee information database

6
1.6 Significance of the project
The significance of a project can be categorized into different areas depending up on to whom
the benefit goes.

 For the association: For university of Gondar credit and saving union work association, it
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 staffs of the association: the project is important to access their associations data easily
anywhere, reduce their work load and labor, reduce redundancy of work, to generate reports
for managers and higher officials, it changes the manual storage mechanism in to
computerized system and it makes them to be motivated for their job.
 For members:
 Reduce the time and labor required to get services from the institution.
 Reduce the error that made by the employees.
 It enhances accuracy, speed, and security of services.
 For their better satisfaction with fast services provided by the employees.
 For the project developers: For the project developers help for the fulfillment of Bachelor
degree in Information science and team member can get experience.
 Know the knowledge how business transactions takes place
 Helps us gain knowledge on web development in depth

1.7 Limitation and Delimitation of the project

1.7.1 Limitations

As there are obstacles on the road of success, for accomplishing our project we have faced a
number of limitations which affect how our work is interpreted. among these the following are
main.

 Lack of adequate and accurate data when the teams gather it.
 Difficulty to easily understand the business rules of the association.
7
1.7.2 Delimitations
When we started this project the team has proposed a number of functionalities to be included in
this project. We have listed these functionalities in the scope part of this project document. But
due to limitations some of these functionalities are excluded from implementation. Such as:

 Transfer of money from customer’s account to another account.

 Performing Public service billing or payment

8
Chapter Two
Literature Review
The main purpose of this section is to introduce and imply how microfinance institutions are
operating now days, in this section, In order to understand functionalities of credit and saving
institutions and financial operational procedures for the university of Gondar employee’s credit
and saving union association. We perform a comprehensive review of a number of related
articles and address the issues of CSAs sustainability; Features of Web based credit and saving
association’s management practice.

Savings is money put aside by an individual or household for use in the future. A key to good
money management, savings help individuals and households manage risk, deal with
emergencies, smooth income, build assets, and meet financial goals. People save by putting
money aside when it comes in and by spending less when it goes out.

Savings services allow savers to store excess amount for future use and to obtain returns on their
investments.

Saving ought to have started before the birth of Jesus Christ in the Roman Empire. Its adventure
is very much linked with the origin of money where merchants used to keep (save) their precious
metals with the gold smiths who would give them back their gold when they are back after their
businesses (Cox, 1996:84).

Throughout time, all around the world, households have saved: as insurance against
emergencies, for social and religious obligations for investments and for future consumption
(Rutherford, 1999).

Credit is defined as the power or ability to obtain goods and services in exchange for a promise
to pay for them later. Credit services enable the use of anticipated income for current investment
or consumption. Overall microfinance service can help low-income people reduce risk, improve
management, raise productivity, obtain higher returns on investments, increase their incomes,
and improve the quality of their lives and those of their dependents.

Credit is widely available from informal commercial money holders but typically, as will be
documented, at very high cost to the borrowers – especially poor borrowers. Banks generally

9
assume that providing small loans and deposit services would be unprofitable. It is widely
believed – wrongly, as will be demonstrated – that the cost of delivering small-scale financial
services at the local level is too high for nonsubsidized institution and that the informal financial
market satisfies demand. NGOs and other nonbank financial institutions have led the way in
developing appropriate credit methodologies for low-income borrowers. But with few
exceptions, these institutions are able to operate only on a very small scale.

Credit and saving Associations is a source of financial services for entrepreneurs, self-
employees and small micro enterprise lacking access to banking and related services.

Saving and credit cooperatives (SACCOs) which are known as the credit unions in some other
countries are defined as cooperatives which furnish their members with convenient and secure
means of saving money and obtaining credit at reasonable rates of interest The saving and credit
cooperatives are usually organized within a group which is already join together by a bond of
common interests such as workers in same factory or members of the same community who are
fairly well acquainted with one another. Furthermore, the savings and credit cooperatives are 10
cooperative organizations which are guided by the practices, philosophy and principles of the
cooperative movement. They differ from the rest of other cooperatives, because they are
financial cooperative organizations with a social context (Kabuga and Batarinyebwa, 1995).

Non-governmental credit schemes and informal sources of finance such as Rotating Saving and
Credit Associations, known as Iquub and Iddir, and money lenders have existed in Ethiopia for
many years (Aredo D., 1993).

A system is a set of interacting or interdependent component parts forming a complex/intricate

whole.Every system is delineated by its spatial and temporal boundaries, surrounded and
influenced by its environment, described by its structure and purpose and expressed in its
functioning (Alexander Backlund, 2000)

Web based system is a client-server software application in which the client (or user interface)
runs in a web browser. Web based are popular due to the ubiquity of web browsers, and the
convenience of using a web browser as a client to update and maintain web applications without
distributing and installing software on potentially thousands of client computers is a key reason
for their popularity, as is the inherent support for cross-platform compatibility. Common web

10
based systems include webmail, online retail sales, online auctions, and many other functions.
(Daniel Nation, 2014)

Banks and the World Wide Web: In the 1990s, banks realized that the rising popularity of the
World Wide Web gave them an added opportunity to advertise their services. Initially, they used
the Web as another brochure, without interaction with the customer. Early sites featured pictures
of the bank's officers or buildings, and provided customers with maps of branches and ATM
locations, phone numbers to call for further information and simple listings of products.

2.1 The Review of CSI system in Ethiopia

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

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.

Currently CSA is one of the most powerful tools for combating poverty primarily by
providing loan to the poor section of the society. There is growth and expansion of
microfinance programs and increasing attention to microfinance as a poverty reduction
strategy throughout the country.

11
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 CSAs (Gebrehiwot,A. ,2002).

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

2.2 The Historical Development of the CSI in Ethiopia

CSA 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 CSA is limited to about twelve years. The
first group of few CSAs was established in early 1997 following the issuance of Proclamation
No. 40/1996 in July 1996.

The objective of the CSAs 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.

12
Since then these CSAs have been playing the role of promoting and accessing financial services
to mainly the rural area. The CSA sector is growing in terms of number and size. The sector is
currently serving more than 2.3 million clients.

Savings and credit cooperatives in Ethiopia have no very long origin. The first savings and credit
cooperative in Ethiopia was established in 1964 by employees of Ethiopian Airlines by the
initiative of interested individual Ethiopians who have foreign countries exposure and peace core
workers of foreign origins. During the same period, savings and credit cooperatives were
established by employees of Ethiopian Road Authority and the Telecommunication Agency
(Dejene, 1993).

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

This growth and expansion of CSAs programs and increasing attention to CSAs 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.

University of Gondar employee’s credit and saving union work association is one of CSAs found
in Ethiopian organizations. Its service that it provides for the employees becomes wide. But still
it uses manual system. This system can’t make its service efficient and effective. So, to make its
service better and to compete with other CSAs needs to use computerized and web based system.

Our proposed system is targeted on implementing web based system for University of Gondar
employees credit and saving union work association, of which to automate current manual
operations in the existing system and it will be more beneficiary than that of using the manual
system. The system will have an online members registration, loan request, account detail
checking, membership withdrawal features that make activities of the association easier.

13
Chapter Three
Project Design and Methodology
Methodology or SDLC (System Development Life Cycle) is defined as the process of
developing system or software to meet certain requirements. It covers many activities; starts
from understanding why the system should be built, studying the project feasibility, analyzing
problems, choosing the system design and architecture, implementing and testing it, up to
delivering the system as product to the user.

3.1 Data Collection Methods

In order to gather the information required for the project, we have used different methods to
collect data. Including:-

 interviews
 observation
 document analysis
These are among the different methods of collecting the data and information required for the
proposed system.

3.1.1 Interviews
This is one of the methods used for the collection of data which is mostly used method. We have
used interview method to gather direct information from users and administrators. We have the
chance of asking different questions to the association’s employee as well as chairman of the
administrating committee for obtaining the required information and data. We have collected
enough information and we could make another appointment if we want additional information
concerning the existing system.

3.1.2 Observation
This is another type of method for collecting data and information in which we have witnessed
the actual events which is happening in the association. In this method all we have to do is
observing and note down the events that we observed, so here we have observed some events
like, employees are keeping customer file manually, the dissatisfaction of clients by the service,
calculation errors, the time taken to search clients file, takes large space for storing the files, and
lack of data security are some of them.

14
3.1.3 Document analysis
This method of collecting a data is analyzing the document prepared and stored in the current
system. We will analyze different documents like forms (registration forms, loan request forms
and the like) and report samples in the existing system. We will try to identify the problems of
the existing system and develop the new system standing from what we have analyzed from the
Document about activities and functions performed by the association.

3.2 Feasibility Analysis

Feasibility study is made to see if our project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets us
to see the future of the project and the usefulness. A feasibility study of our systems proposal is
according to its workability, which is the impact on the university of Gondar employee’s credit
and saving union work association, ability to meet their user needs and effective use of
resources. An analysis and evaluation of a proposed project, is to determine if it is technically
feasible, if it is feasible within the estimated cost, and if it will be profitable.

Feasibility studies are almost always conducted where large sums are at stake. It also called
feasibility analysis (Alviya Noor, 2011).

Any developed software has to satisfy the criteria for feasibility. This project is also going to
satisfy the following criteria’s for feasibility.

3.2.1 Economical feasibility

Economic feasibility is the measure of cost effectiveness of the project. The developed system
must be justified by cost and benefit. That is why sometimes economic feasibility is called cost
benefit analysis. One of the factors, which affect the development of a new system, is the cost it
would require. Economical Feasibility can be related to tangible and intangible benefits or costs.
Tangible cost are measured in terms birr like hardware while intangible costs cannot be easily
measured in birr like loss of members goodwill and loss of employee morale. As mentioned in
the problem statement, currently the University of Gondar employee’s credit and saving union
work association is exposed for unnecessary economical wastes in different ways such as man
power and time to calculate manually, documentation materials, calculation tools etc.

But in our system these unnecessary wastes have been reduced. It has the required number of
computers and infrastructure. But there will no more manual work and manual materials. The
15
requirement for hardware and software, by the new system is of low cost and needing very less
maintenance cost. There is no need to buy anything extra for the system.

If the benefit in the long run compensates for the cost expend in the designing and
implementation of the system. The cost factor of the system involves the Manpower cost,
Hardware cost, and the Software cost.
Manpower Cost: There is no need to employ any extra person to use this system as its very user
friendly and very easy to learn too.
Hardware Cost: The hardware cost is very less. So this system is economically regarding
hardware cost.
Software Cost: The software needed for the development of the project is nil as we are using
Free and Open Source Software (FOSS) like PHP. Since the system is developed as part of
project work, there is no manual cost to spend for the proposed system. Also all the resources are
already available, it give an indication of the system is economically possible for development.
Since most budgets of the system are not continuous, cost of the project is economically feasible.

3.2.2 Technical Feasibility

The Technical Feasibility is concerned with specifying the equipment’s and software that will
successfully satisfy the user requirements. It is the measure of practicality of the specific
technical solution and the availability of technical resources and expertise. This system has been
implemented in the association by technical computer professionals and there are computers in
the organization which are ready for the proposed system, so the development of the new system
is technically feasible. The proposed system is technically feasible as the resources
(equipment’s) that are needed for the proposed system are easily available and uses easy method
as well as user friendly programming languages for developing and also it is easy to run once
after the system is developed. The system developed in such a way that the necessary functions
and performance are achieved within the constraints. Our system will be developed within latest
technology. Through the technology which may never become obsolete after some period of
time, due to the fact that any version of same software supports older versions, so the system
may still be used. The Programming Language, Database and server that we have used are a free
and open source so we can find and use them; this also makes the proposed system technically
feasible.

16
3.2.3 Operational Feasibility
Is the measure of how well the solutions for problems will work in the association? In our case,
the system which we will develop is operationally feasible and improves the current operations
of the association. The project would be beneficial because it satisfies the objectives when
developed and used. And as well the new system brings an easy and user friendly working
environment that helps the employees get services from anywhere as well as the association
workers to handle tasks easily. All Operational aspects are considered carefully and conclude
that the system is operationally feasible.

3.2.4 Legal Feasibility

Legal feasibility is a determination of whether the proposed system violates on any known Acts
or pending legislations. We are using Free and Open Source Software (FOSS) like PHP so the
proposed system does not violate any legal Acts. Thus, it is legally feasible.

3.3 Proposed System

To avoid all limitations existing in the association and make the operations and activities more
accurate the system needs to be computerized and should perform some of the activities online.

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 a wide range manual work.

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

 Greater efficiency.

 Better service.

 User friendliness and interactive.

17
3.3.2 Description of the proposed system
Activities in the system are segregated into two sections and a number of modules or activities to
be accomplished. This will be described as follows:

Client side

Depositing money: This module covers how customers save their money in association
whenever they want. Major function of the Association is to mobilize savings by
encouraging employees of the university to save some portion (5% and above) of their
monthly salary. Some of the mechanism of persuading people to save is by paying
interest for the saved and deposited amount, by making them aware of the benefits of
being a member of the Association. 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/member of the Association can withdraw his money from his saving account
is performed by the 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 Association can apply for loan request to the
association’s loan committee of the system online based on the certain criteria set by
the institution. Current deposit received by the association is not kept idle. After
keeping certain cash reserves above the minimum balance, the loan is given by the
Association to the needy borrowers after a minimum of six months being a member.
He/ she take the loan physically from the Association.

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.

18
Customer information delivery: The system provides online information delivery
service for the customers of the association. Any customer can access information from
the website of the association through his/her address using password from 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.

Server Side

Approver: This activity/module is utilized by Managers/Administrators 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. And the manger/Administrator
also approves reserved registrations of new employees.

Information & Report: Allows the Manager/Administrator to monitor the existing

information, appending information to its existing information, verifying new
customers and acknowledging them.

3.3.3 System Architecture

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

19
sends its response back to the browser which displays the output on web page to the user. 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.4 Requirements 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.4.1 Functional requirements

The system which we have developed has different functions or features which are actions of the
system to satisfy the system needed and be acceptable to the user.

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 Staff

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

20
 Provides a menu based functions

 Secure access of confidential information.

 flexible service based architecture will be highly desirable for future extensions

3.5 Specification
Hardware and software are components of any system.

3.5.1 Hardware specification

For the proposed system, hardware specification 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

3.5.2 Software Specification

As described earlier to develop any system hardware and software materials are vital
components.
To develop the proposed web based system, we will use the following necessary software tools:
 Xampp server
 Micro media Dreamweaver CS 6/8
 Adobe reader
 Notepad ++
 Microsoft office word and power point
 Visual Paradigm
 Edraw, UML and others if necessary.

21
3.6 System Analysis
We should have to follow SDLC (System Development Life Cycle) as conceptual model because
it is used in project management to describe the stages involved in the system that we have
proposed to develop from an initial feasibility study through maintenance of the completed
application.

System Development Life Cycle is a framework through which we can describe the activities
performed at each stage of the system development.

We 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 we have proposed 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
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.

We have listed functionalities or activities performed in the University of Gondar Employees

credit and saving union work association and identify by whom each operations are performed.
Then we have 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 and on the computer and sees to it that the rough image made of the system comprises

22
of all the requirements or not. Once this is done, we have selected and finalized a best suited
design for the development of the system.

System Coding: in this stage the programmer translates the design into code. Like this after
finishing the design we have tried to convert the design into coding to make it real. The coding
step was time consuming and involves number of errors.

System testing: Once our group is through with the coding stage we tested the systems and sees
to it that it is working correctly as per the expectations or not. we corrected the flaws in the
system if any.

Systems Implementation: in this phase we have to implement the system and receive feedback
from the users of the association.

Systems Maintenance and test: This is the last stage of the SDLC, in this stage our group
understands the problems or errors occurred when the team implements the system and
feedbacks received from users. Then we have to maintain the system and see to it that it working
within 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.

We used Object Oriented approaches to analyze the system, to develop the new system which is
now becoming increasingly popular because of its ability to thoroughly represent complex
relationship, as well as to represent data and process with consistent notation throughout the
system.

We have used UML in Object Oriented Approach. From the different types of UML, we used
Use Case Diagram, Class Diagram and Activity Diagram as much as possible.

3.6.1 Analysis of activities

The system is built from different operational activities accomplished in the Association. These
different activities are performed by assigned actors that each activity concerned.

This section covers the detailed 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).
23
3.6.1.1 Use Case Diagram
We have 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. We have 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 system’s object and their interaction with
each other with the users of the system.

Identification of Actors’

The following actors are used in our system

 Manager/Administrator
 Employee/Staff
 Customer/Member

Identification of Use Case

The following use cases were identified

 Manage Customer
 Manage Account Type
 Manage Loan
 Manage Transaction
 Manage Deposit
 Manage Employee
 View Financial Statement
 Approve Loan Request
 Approve Reserved Employee
 Messaging

24
University of Gondar Employees Credit and Saving Union Work
Association

Approve
Registration

Manage
Loan

Manager Manage
Account

Create
Password Customer

Messaging

Registration

Manage
Employee
Transaction

Manage
Customer

Messaging

Fig 2. Usecase Diagram

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 University of Gondar Employees Credit and Saving Union Work Association
2. The Manager and the Employee clicks on the View Financial Statement button
3. The system displays View Financial Statement page
4. The Manager Selects from the lists of the desired Account Number from the combo box
and clicks on the Financial Detail Button
5. The system displays Financial Statement report of the customer.

Name of use case: Add New Account Type – this feature is not a part of the Associations
activities because now there is no other account types rather only saving account. But included
for a future use if the Association provides different types of accounts.
28
Participating actor: Manager

Fig 3. Activity diagram for New Customer Registration

38
Fig 4. Activity diagram for Withdraw Money

3.6.1.3 State chart diagram

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

39
Fig 5. state chart diagram of the system

3.6.1.4 Sequence Diagram

As the name indicates the system used sequence diagram 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 we 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.

40
Fig 6.. Staff Deposit Money to Customers

Fig 7. Customers View Loan

41
Fig 8.. Staff Withdraw Money for Customers

Fig 9.. Manager/Admin Login in to the System

42
Fig 10. EMI

Fig 11.. Staff Registers new Customers/Employee

43
3.7 System Design
We have used Object Oriented method (approach) to develop our system, the reason behind
choosing OOA is that it’s best 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 also used us for analyzing, designing and implementing the system by applying the object-
oriented prototype and visual modeling throughout the development life cycles to foster better
stakeholder communication and product quality. Its additional advantages that made 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.

 Reusability of analysis, design and programming results.

 Increased consistency among all the models developed during Object Oriented Analysis,
design and implementation

3.7.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 easy to 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.

44
 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 University of
Gondar Employees Credit and Saving Union Work Association.
 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 it runs.
 Security: The system security is taken in to consideration to make association
information and financial cases secure and confidential.

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.7.2 Class Diagram

We 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 we have used Unified 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 systematic of the application, and for detailed modeling 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 we have used the following criteria:

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

-user_id : varchar
1 Customer
1 -cust_id : varchar
-password : varchar -information : varchar
+login() -cust_id : varchar +view()
-fname : varchar
-lname : varchar
Has Has
-age : int
-salary : float
-address : varchar
1 -college : varchar 1
-department : varchar
-email : varchar
-sex : varchar Loan Request
-contact_no : int
-acc_no : int -cust_id : varchar
-balance : int -fname : varchar
-open_date : datetime -lname : varchar
Loan Accept Can request -college : varchar
+open() -depatment : varchar
-cust_id : varchar +view() -status : varchar
-loan_id : varchar -salary : float
-loan_amount : float
1 +request()
-amount : float
+add()
-duration : int +register() -email : varchar
-start_date : datetime 1 -contact_no : int
-monthly_inst : float -loan_amount : varchar
-duration : datetime
+accept()
-request_date : datetime

+requets()
+accept()
+reject()

Fig 12. Association of Customer Class

46
Fig 13.. Association of Loan Class

Login_accept Rejected_Information
-customer_id: varchar -cust_id : varchar
-loan_id: varchar -information
information : varchar
-loan_amount: float Customer Has +reject()
-duration: int 1
-customer_id : varchar
-start_date: datetime -fname : varchar
-monthly_inst: float Has -lname : varchar
Loan_Paid
1
+accept() -salary : float -customer_id: varchar
-address : varchar -loan_id: int
-college : varchar -inst_date: datetime
Interest -department : varchar -pay_date: datetime
-email : varchar -inst_amount: int
-acc_no: int 1 -loan_amount: varchar
-date: datetime -contact_no : int
1 Has 1 -acc_no : int
1 Perform -balance: float
-previous_balance: float -status: varchar
-interest: int -amount: float
-balance : float +pay()
-total_balance: float
-sex: varchar +view()
+view()
-salary: float
-open_date: datetime Account
1 Has
+contact() 1 -acc_type:
acc_type: char
+open()
-min_balance:
min_balance: float
Transaction +request()
+view() +add()
-customer_id: varchar +send() +update()
-transaction_id: int +register() +delete()
1 -transaction_type: char +calculate()
-date: datetime Has
-cheque_no: int
-acc_no: int
1
-amount: float Loan
-current_balance: float -customer_id:
customer_id: char
+cash() Can Perform -loan_amount:
loan_amount: float
+cheque()
1 -duration:
duration: int
-name:
name: varchar
Login 1 -address:
address: varchar
-salary: float
-user_id:
user_id: varchar
-amount:
amount: float
-password:
password: varchar
-contact_no:
contact_no: int
+login() -request_date:
request_date: datetime
-status:
status: varchar
+request()
+accept()
+reject()

47
Fig 14. Class Diagram of Web based UoG Employees credit and saving system

Description of class diagram

A. Class name: Customer

Description:

 A customer who is already registered.

 A customer who can log to the system using login page.

 A customer who has an Account.

 A customer who can perform transactions.

 A customer who has rejected information.

 A customer who view or sent many complaints or messages.

 A customer who has requested for loan.

Methods

Pseudo code: Do

The system registers a customer’s Information to the database

Open ()

Pseudo code: Do

The system lets to open an Account.

View ()

Pseudo code: Do

The system displays the customers’ financial statement and account

details if the user name and password is correct.

Send ()

48
Pseudo code: Do

The system lets the customer to send the loan request and complaints.

Calculate ()

Pseudo code: Do

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

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

 A person must specify amount of loan to get loan service.

Methods

Request ()

Pseudo code: Do

The system allows the customer to request loan.

49
Accept ()

The system can accept the customer request.

Reject ()

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
50
The system deletes Account types and minimum balance from the database.

F. Class name: loan _ accept

Description:

 The customer’s 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: Interest

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

3.7.3 System Architecture

Overview

We used system design model or system architecture to 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.

Architectural 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 credit
and saving system 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.
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 cases identified 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.
52
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.

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. We can describe the
decomposition of the system in to main subsystems as follows:

Fig 15. Subsystem decomposition Diagram

Hardware or software mapping

When we 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

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

Client Internet Server

Database

Fig 16. Hardware/software mapping

Subsystems such as: register customer, loan request, view transactional information, withdraw,
deposit are assigned and performed with client.

3.7.4 Deployment Diagram

We 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 17. Deployment diagram of the system

Deployment diagram description:

Browser: online viewers will be able to communicate with the web server using
browser.

Web Server: using apache as the web server, and it will be responsible for accepting
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.8 Data Dictionary
We used 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.

Description of the data objects or items in a data model are used for the benefit of programmers
and others who need to refer to them.

Table Attributes Data Types Contraints Description

1. Accounts acc_type varchar(50) NOT NULL Account type

Primary key

Min_balance varchar(20) NOT NULL Minimum Balance

Table 1: Account table

Entity Attributes Data Types Contraints Description

2.Customer Cust_id varchar (20) NOT NULL Customer identification

Primary Key

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

Email varchar(40) NOT NULL Electronic mail

56
Sex varchar(15) NOT NULL Sex

Contact number varchar(25) NOT NULL Phone Number

acc_number varchar(25) NOT NULL Account number

Primary Key

Balance Float NOT NULL Balance

College varchar(25) NOT NULL College/Faculty

Department varchar(25) NOT NULL Dept/Sector

Open_date Datetime NOT NULL Open date

Table 2: Customer table

Table Attributes Data Types Contraints Description

3. Loan Cust_id int(20) NOT NULL Customer Identification

Primary key

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

College varchar(20) NOT NULL College/Faculty

Department Varchar(20) NOT NULL Dept/sector

Salary float(20) NOT NULL Monthly Salary

57
Email varchar(25) NOT NULL Electronic mail

Contact_no Int(10) NOT NULL Phone Number

Request_date Datetime NOT NULL Loan Request Date

Table 3: Loan Table

Table Attributes Data Types Contraints Description

4. Login user_id varchar(200) NOT NULL DEFAULT '0', User id

Primary Key

user_password varchar(200) NOT NULL DEFAULT '0 User Password

user_type varchar(200) NOT NULL DEFAULT '0' User Type

Question varchar(200) NOT NULL Question

Ans varchar(50) NOT NULL Answer

Table 4: Login table

Table Attributes Data Types Contraints Description

5. Transaction Tran_id varchar(200) NOT NULL Transaction Identification

Tran_type varchar(200) NOT NULL Transaction Type

Tran_method 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

58
Amount varchar(200) NOT NULL Amount

current_balance Float NOT NULL Current balance

Remarks varchar(200) NOT NULL Remark

Cust_id varchar(20) NOT NULL Customer identification

Table 5: Transaction table

Entity Attributes Data Types Contraints Description

6.Reservation Cust_id varchar (20) NOT NULL Customer identification

Primary Key

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

Email varchar(40) NOT NULL Electronic mail

Sex varchar(15) NOT NULL Sex

Contact number varchar(25) NOT NULL Phone Number

acc_number varchar(25) NOT NULL Account number

Primary Key

Balance Float NOT NULL Balance

College varchar(25) NOT NULL College/Faculty

Department varchar(25) NOT NULL Dept/Sector

59
Open_date Datetime NOT NULL Open date

Table 6: Reservation table

User Modules
The system is consists of three main modules as below:

 Administrator module
 Staff module
 Customer module

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

ii. Ensure that software coding methods, standards, and/or criteria are adhered to and
verified.
iii. Ensure that the software code is unit tested per the plans for software testing.
iv. Provide a software version description document for each software release.
v. 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.9.1 Techniques of implementation

We 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 we implemented the
interfaces based on the use cases. Then we implemented the database based on the class diagram
that has been 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 we write codes we tested
each code to save time and effort.

60
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

We implemented basic pages/interfaces of the system based on the use case diagram that have
been designed. Mainly there are three interfaces for the three actors such as manager login page,
employee’s login page and customer’s 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. Weused
PHP and HTML to implement interfaces of the system.

Database implementation

We implemented databases of the system based on the class diagram that we have designed.
And used MySQL 5.5.8 for the database implementation.

The system which we implemented involves 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
61
 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 we used 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 we 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 association
offices become as Client stations and accessing of the main branch station database.

Implementing server side functionality: The server side functionality involves connecting
pages with the database.

62
3.9.2 Sample Input or output Screens

Home page of UoG Employees Credit and Saving Association Web Based system

Fig 18. Homepage of the System

63
Login page of UoG Employees Credit and Saving Association Web Based system

Fig 19. Login page of the system

64
Admin Page of UoG Employees Credit and Saving Association Web Based system

Fig 20. Admin Page of the system

65
Manage Customer Page of UoG Employees Credit and Saving Association Web Based
system

Fig 21. Manage Customer on Admin page of the system

66
Register New Customer Page of UoG Employees Credit and Saving Association Web Based
system

Fig 22. New customer’s registration page of the system

67
Staff’s Homepage of UoG Employees Credit and Saving Association Web Based system

Fig 23. Staff Homepage of the system

68
Customer Homepage of UoG Employees Credit and Saving Association Web Based system

Fig 24. Customer’s Homepage of the system

69
3.10 Testing and Evaluation Methods

3.10.1 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: we have tried to test the system for its integration that justifies
that major components of the system are working as per the requirements gathered.

We have conducted 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 association as well as its members.

3.10.2 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:
70
 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.10.3 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
- Withdrawal form
- Loan Form
- Create password

3.10.4 Testing Approach

For the test plan we 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 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.

71
3.10.5 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 that we used for development such as xampp Server, browsers, operating
systems, application software’s(Office, UML),Dreamweaver
 Web Server (Apach)
 Database server (MySQL)
 People like us, focused groups, organizational person: for crowd test

3.10.6 Test Case Specification

We have 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.10.6.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

72
Input data and expected results of the system after testing.

N Test case name Test procedure Precondition ExpectedOutpu

result Output
o
1 Customer Fills First Name, Last Manager Home Added to the Success
Registration form Name, Age, Address, page, database, Not
Email, Contact Employee added to the
number, college, home page database
department
2 Login form Fills User Name, HOME Display login Success
Password successfully,
Pleas enter the
correct user id
or password
3 Create Password Manager Fills Set password, Added to the Success
Password, confirm database or
password, secrete Record is
question, Answer, already exist
Authentication type

Table 7: Input data and expected results of the system after testing.

Input data and expected results of the system not yet tested.

N Test case Test procedure Precondition ExpectedOutpu Output

o name result
1 Deposit Transaction number, Transaction Transaction Transaction Success
type ,Transaction method, Page Completed
Account number, Amount, Successfully
Remark

73
2 Withdrawal Transaction number, Transaction Transaction Transaction Success
type ,Transaction method, Page Completed
Account number, Amount, Successfully
Remark

Table 8: Input data and expected results of the system not yet tested

3.10.6.2 Test items

The scope of the system testing encompasses the system’s 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.

74
3.10.6.2.1 Input specifications
We have to identify all inputs required to execute the test case. Again these may vary based on
the level the case is written for. We needed 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.10.6.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 we 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 valid

75
Test case1.04 Email Character a-z@a-z.com Valid otherwise
Invalid

Test case1.05 Phone Number Number 0-9 Valid otherwise

invalid

Table 9: Test Case 1.Register Customer

Test Case 2. Login

Test Case Field Test Item Input Type Output

Identifier

Test case2.01 User Id Character /”\@,‘ Invalid User Id

otherwise Valid

Test case2.02 Password Character Empty Invalid Password

otherwise Valid

Table 10: Test Case2.Login

Test Case 4. Create Password

Test Case Field Test Item Input Type Output

Identifier

Test case4.01 Create Character Empty Password must

Password not be empty
otherwise Valid

Test case4.02 Confirm Character Empty Confirm Password

Password must not be empty

76
otherwise Valid

Test case4.03 Secret Select Select Valid Secret

question question otherwise
Invalid

Test case4.04 Answer Character Correct Valid otherwise

Invalid

Table 11: Test Case4.Create Password

3.10.2 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 we have checked the results and evaluate 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.

 Compared the new system with the existing system

 Examined the system by professionals
 Request the user to give comment about the system
 Examined the system for its effectiveness

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

77
Any system should have documentation that helps the user of the system by preparing the
methodology how the system was done and prepare manual how to use code to be tested and
manipulated. It also provides documentation how to solve the problem when it occurs.

78
Chapter Four
RESULT and DISSIMINATION

4.1 Results achieved

We 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 employee’s and customer’s 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 request service, deposit information, 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 credit and saving system
for processing of client information and providing financial services for customers.

 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

79
 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
take-up, 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 develop web based system
of UoG Employees credit and saving union work association in such easy way and it
is disseminated to the association 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 we has done
Inform – educate the system users
Engage – get input/feedback from the system users
Make sustainable – ensure that the effects would be sustained after the project.

4.2.1 Dissemination method

 Publications
we have planned to present the project and describing its results through publication
(like Credit and saving’s multimedia service, radio air time program).
 Conferences and workshops
and also we have planned to present the project when the organization prepares
conferences, workshops, or case studies based on the technology and related issue.
 Website
 Most projects create a social media account or pages 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.

80
Chapter Five
Conclusion and Recommendation
5.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 association 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 too. There is growth and expansion of credit and saving programs and
increasing attention to credit and saving as a poverty reduction strategy throughout our country.

For these rapidly growing credit and saving associations 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
associations 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
of such associations, we have developed this credit and saving Software system for UoG
Employee’s credit and saving union work association.

This implementation of a web based solution will not only help the association but also promote
education for the project team (us) in the field of information technology.

We 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

81
systems, describing the functionalities and scope of the proposed system, defining the system
development methodology, identifying resource requirements, and setting the project schedule.

 We have 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, we 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, we 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, we have done Conversion of manual financial system to web
based system with basic stated functionalities for the UoG Employee’s credit and saving
union work association.

The key benefits of this project are the following:

 UoG Employee’s credit and saving union work association 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

82
5.2 Recommendation
Improved access to credit and saving services can enable the poor employees to smooth out their
consumption, manage their risks better, build their assets, enhance their income-earning capacity,
and enjoy an improved quality of life.

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 we have described in chapter two there are different researches conducted about credit and
saving associations. But in almost all associations the system is running manually. We have
reviewed a number of related researches and other documents to understand the services or
functionalities performed in these associations. On the basis of the research works and
documents, we have successfully designed and implemented online CSS. But for the future as
the services of the associations 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 Credit and Saving System
 Transfer of money from one account to other account.

83
Reference
Proclamation to provide for the Licensing and Supervision of the Business of Micro Financing
Institutions. (1996). Federal Negarit journal.

Gebrehiwot,A. (2002). Microfinance Institutions in Ethiopia: Issues of Portfolio Risk,

Institutional Arrangements and Governance, in Microfinance Theory, Policy and
Experience . Mekelle, Ethiopia: Mekelle University.

Colombage, S. (2004). Microfinance as an instrument for small enterprise development:

opportunities and constraints. Central Bank of Sri Lanka.

Rutherford, S. (1999). Savings and the poor: the Methods, Use and Impact of Savings by the
poor in East Africa. Kampala: Microsave.

Wolday, A. (2007). Review Of Microfinance Industry In Ethiopia: Regulatory Framework And

Performance. Addis Ababa, Ethiopia.

84
Appendix
 What is the official Name of the association?
 When the organization did have been established?
 How many members were there by the time of establishment?
 How much was the first deposit?
 What was the motive/reason for the establishment?
 What is your total capital now?
 What are the requirements for new member registration?
 What is the list amount to be deposited?
 How the transactions are performed?
 How did you store individual records?
 What are the prerequisites to apply for loan?
 How is the management of the association?
 How many members are there?
 How many employees do you have?
 What are the visions and missions of the organization?
 What problems are you facing?

85
Sample Code
Sample Code for Login
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<?php
session_start();
?>

<html>

<head>
<title>Login...</title>

<?php

include 'db_connect.php';
$result=" ";
@session_start();
if (isset($_POST['Login']))
{

$username = $_POST['username'];
$password = $_POST['password'];

$result = mysql_query("Select * From login where user_name='$username'and

user_password='$password'",$link);
$count=mysql_num_rows($result);
if ($count==0)
{
$_SESSION['msg']="Incorrect Username. Please make Some Correction!!!";
/* if ($result) { echo $msg;} */
}
else
{
while($row = mysql_fetch_array($result, MYSQL_BOTH))
{
86
$usr_pwd=$row['user_password'];
$type=$row['user_type'];
if($usr_pwd!=$password )
{
$_SESSION['msg']="Incorrect Password. Please make Some
Correction";

/* if ($result) { echo $msg;} */

}
else
{
if($type=='Customer')
{
$_SESSION['username']=$_POST['username'];
//include "cust_data.php";
header('Location:cust_data.php');
exit(0);

}
else if($type=='Teller')
{

$_SESSION['username']=$_POST['username'];
//include "teller_data.php";
header('location:teller_data.php');
exit(0);
}
else
{

$_SESSION['username']="Manager";
//include "admin_data.php";
header('location:admin_data.php');
exit(0);

}
}
}
87
}

?>
<table align="center" width="1100px" bgcolor="#FFFFFF">
<tr>
<tr>
<td width="100">

</td>
</tr>
<tr>
</tr>
<TR>
<TD width=128 height=500 bgcolor="#CCCCFF"> <DIV align=right>
<form name="Form1" method="post" action="" onsubmit="return
Blank_TextField_Validator()">
<br>
<TABLE width="45%" height="30%" border=4 align=center cellPadding=5 cellSpacing=0 t
id="rt">

<TBODY>
<TR>
<TD class=sectionhead align=middle colSpan=2><div align="center">Enter your
username and password below!</div></TD>
</TR>
<TR>
<TD class=firstalt align=middle width="33%"><span class="style16">User
Id:</span></TD>
<TD width="67%" align=left class=firstalt><input name="username" type="text"
id="username" maxlength="20" size="20" tabindex="1">
</TD>
</TR>
<TR>
<TD class=secondalt align=middle><span class="style16">Password :</span><BR>
</TD>
<TD class=secondalt align=left><input name="password" type="password"
id="password2" maxlength="20" size="30" AUTOCOMPLETE="OFF" tabindex="2" ></TD>
</TR></TBODY></TABLE>
<p align=center><font color="#FF3399">Forgotten your Password ? <a
href='../ab/forgotten.php'>Click here...</a></font></p>

88
<p align="center"><font color="#FF0000"> <?php if(isset($_SESSION['msg']))echo
$_SESSION['msg'];?></font></p>

<input name="Login" type="submit" class="admin_add_items" value="Login">

</p>
</form>

</TD>
<div>

</body>
</html>

Sample Code for New Customer Registration

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<?php
@session_start();

if(!isset($_SESSION['username']))
{
header('Location:login.php');
}
?>

89
<?php
@session_start();

if(isset($_SESSION['username']))
{
?>
<html>
<head>
<title>Customer Details Entry Form</title>

<?php
include 'db_connect.php'; //Connect mysql database
$today= date("Ymd H:i:s"); //get todays date
$result ="";
$max=mysql_query("select max(custid),max(acc_number) from customer ");
$acc=mysql_query("select acc_type from accounts order by acc_type");

//$opendate= $dates[year]."-".$dates[mon]."-".$dates[mday];

if(isset($_POST['Submit'])) ///forsubmit data

{
$custid=ucwords($_POST['custid']);
$first_name=ucwords($_POST['first_name']);
$last_name=ucwords($_POST['last_name']);
$age=ucwords($_POST['age']);
$address=ucwords($_POST['address']);
$Kebele=ucwords($_POST['Kebele']);
$email=$_POST['email'];
$sex=ucwords($_POST['sex']);

$opendate=ucwords($_POST['opendate']);

$contact_number=ucwords($_POST['contact_number']);
$acc_number=ucwords($_POST['acc_number']);

$acc_type=ucwords($_POST['acc_type']);

$bal=mysql_query("select minbalance from accounts where acc_type='$acc_type'");

while($row=mysql_fetch_array($bal,MYSQL_BOTH))
{
$balance=$row[0];
}

$mondate=mktime(0,0,0,date("m"),date("d"),date("Y")+1);
$d=date("Y-m-d",$mondate);
90
$interest=($balance*0.03);
$total_balance=$balance+$interest;
mysql_query("Insert into interest(acc_num,date,old_bal,interest,tot_bal)
values('".$acc_number."','".$d."','".$balance."','".$interest."','".$total_balance."')");

if (!preg_match ("/^[a-z]+$/i", stripslashes(trim($first_name)))) //Accept characters only

{
echo "<script>JavaScript: alert('First Name should be letters only!')</script>";

//exit(0);
}
else
{
if (!preg_match ("/^[a-z]+$/i", stripslashes(trim($last_name)))) //Accept characters only
{
echo "<script>JavaScript: alert('Last Name should be letters only!')</script>";

//exit(0);
}

else
{
if(!preg_match ("/^[0-9]+$/i", stripslashes(trim($age)))) //Accept Numeric only
{
echo "<script>JavaScript: alert('Enter Valid Data for Age !')</script>";

//exit(0);
}
else
{
if (!preg_match("/\w+([-+.]\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*/",$email)) //validating email
{
echo "<script>JavaScript: alert('Invalid Email Address!')</script>";

//exit(0);
}

else
{
if(!preg_match ("/^[0-9]+$/i", stripslashes(trim($contact_number)))) //Accept Numeric only
{
echo "<script>JavaScript: alert('Enter Valid Data for Contact Number!')</script>";

//exit(0);
}

else
91
{
$result = mysql_query("Insert into customer values('".$custid."','".$first_name."',

'".$last_name."','".$age."','".$address."','".$Kebele."','".$email."','".$sex."','".$contact_num
ber."','".$acc_number."','".$balance."','".$acc_type."','".$opendate."')");

$db_close=mysql_close();

if ($result )
{
$dmode=$_GET['mode'];
echo "<script>JavaScript: alert('Added to database...')</script>";
//echo "<p>Click <a href='add_data.php?mode=$dmode'> here </a> to add another";
//exit(0);
}
else
{
echo "<script>JavaScript: alert('Not Added to database...')</script>";
//echo "<p>Click <a href='add_data.php?mode=$dmode'> here </a> to go back";
//exit(0);
}
} //
}////
}/////
}
}
}

?>
<table width="1100px" height="500" border="0" align="center" bgcolor="#CCCCFF">
<tr><td width="110" bgcolor="">

<strong><font color="#CC0000" size=3>R E G I S T E R 

CUSTOMERS</font></strong><br>
<br>
</td></tr>
<tr>
<td width="180" valign="top">
<table width="180">
<tr>
<td width="180">

<a href="admin_data.php" target="_parent" class="button2">Manager Home

          </a>
</td>
</tr>
<tr>
92
<td width="180">
<a href='add_data.php?mode=admin' class="button2">Register
Customers  </a><br> </td>
</tr>
<tr>
<td width="180">
<a href='crt.php?mode=admin' class="button2">Set Password
            </a><br
> </td>
</tr>
<tr>
<td width="180">
<a href='update_cust.php?mode=admin' class="button2">Update
Customers    </a><br>
</td>
</tr>
<tr>
<td width="180">
<a href='admin_cust_del.php?mode=admin' class="button2">Delete Customers   
  </a><br>
</td>
</tr>
<tr>
<td width="180">

<a href="logout.php" class="button2"> Log Out

             
         </a>
</td>
</tr>

</table>
</td>

<td width="1px" valign="top">

<?php
if($_GET['mode']=='admin')
{
print "<a href='admin_data.php'>";
}
else
if($_GET['mode']=='teller')
{
print "<a href='teller_data.php'>";
93
}
else
{
print "<a href='cust_data.php'>";
}
?>

<TD style="BORDER-BOTTOM: #e5e5e5 5px solid" width=638>

<form name="Form1" method="post" action="" onsubmit="return

Blank_TextField_Validator()">

<TABLE width="65%" height="150" border=3 align=center cellPadding=3 cellSpacing=0

class=rt id="rt">

<TR>
<TD class=sectionhead align=middle colSpan=2><div align="center">Enter The
Customer Details Below !</div></TD>
</TR>
<TR>
<TD class=firstalt align=middle width="41%"><div align="left"
class="style1">Customer Id :</div></TD>
<?php
while($cust = mysql_fetch_array($max, MYSQL_BOTH))
{
if($cust[1] == null)
$maxaccnum="100001";
else
$maxaccnum=$cust[1]+1;
if($cust[0] == null)
$maxcustid="600001";
else
$maxcustid=$cust[0]+1;
}
print "<TD width=\"59%\" align=left class=firstalt >";
print "<input name=\"custid\" type=\"text\" id=\"username2\"";
print "value=$maxcustid maxlength=\"10\" size=\"10\" tabindex=\"1\" readonly=\"readonly\" >";
print "</TD></TR>";
?>
<TR>
<TD class=secondalt align=middle><div align="left" class="style2"><B>First Name
:</B><BR>
</div></TD>
94
<TD class=secondalt align=left><input name="first_name" type="text"
id="first_name" maxlength="40" size="40" AUTOCOMPLETE="OFF" tabindex="1" ></TD>
</TR>
<TR>
<TD class=firstalt align=middle width="41%"><div align="left" class="style1">Last
Name :</div></TD>
<TD width="59%" align=left class=firstalt><input name="last_name" type="text"
id="last_name" maxlength="40" size="40" tabindex="2">
</TD>
</TR>
<TR><TD class=secondalt align=middle><div align="left"
class="style2"><B>Age</B><BR>
</div></TD>
<TD width="59%" align=left class=firstalt><input name="age" type="text" id="age"
maxlength="40" size="40" tabindex="2"></TD>
</tr>
<tr>
<TD class=secondalt align=middle><div align="left"
class="style2"><B>Address</B><BR>
</div></TD>
<TD class=secondalt align=left><textarea name="address" size=100
tabindex="3"></textarea></TD>
</TR>
<TR>
<TD class=firstalt align=middle><div align="left" class="style2"><B>E- mail
:</B></div></TD>
<TD align=left class=firstalt><input name="email" type="text" id="email"
maxlength="40" size="40" tabindex="4">
</TD>
</TR>
<TR>
<TD class=secondalt align=middle><div align="left" class="style2"><B>Sex
:</B><BR>
</div></TD>

<TD class=secondalt align=left><input name="sex" type="radio" id="sex" value="Male"

maxlength="6" size="20">Male
<input name="sex" type="radio" id="sex" maxlength="6" value="Female"
size="20">Female</TD>
</TR>
<TR>
<TD class=secondalt align=middle><div align="left" class="style2"><B>Open date :
</B><BR>
</div></TD>

<TD class=secondalt align=left>

95
<input name="opendate" type="text" value=<?php $dates=date("Y-m-d"); echo $dates ; ?>
maxlength="20" size="20" AUTOCOMPLETE="ON" tabindex="6" readonly=\"readonly\">

</TD>
</TR>
<TR>

<TD class=firstalt align=middle><div align="left" class="style2"><B>Phone Number

:</B></div></TD>
<TD align=left class=firstalt><input name="contact_number" type="text"
id="contact_number" maxlength="15" size="20" tabindex="6">
</TD>
</TR>
<TR>
<TD class=secondalt align=middle width="41%"><div align="left"
class="style1">Account Number :</div></TD>

<?php
print "<TD width=\"59%\" align=left class=secondalt><input";
print " name=\"acc_number\" tabindex=\"7\" type=\"text\" ";
print " value=$maxaccnum";
print " maxlength=\"20\" size=\"20\" tabindex=\"1\" readonly=\"readonly\"></TD>";
?>

<TR>
<TD class=firstalt align=middle width="41%"><div align="left"
class="style1">Account Type :</div></TD>
<TD class=secondalt align=left><select name="acc_type" AUTOCOMPLETE="ON"
tabindex="8" >
<?php
while($acctype = mysql_fetch_array($acc, MYSQL_BOTH))
{
print "<option>$acctype[0]</option>";
}
print "</select>";
?></TD>
</TR>

</TABLE>
<div align="center">
<p>
<input name="Submit" type="submit" class="admin_add_items" value="Add">
  
<input name="Submit2" type="button" class="admin_add_items" id="Submit2"
onclick="location.replace('./customer_accounts.php')" value="Cancel" >
96
</div>
</form>

</DIV>

</td></tr></table>

</TR>

</TABLE>

</body>
</html>
<?php
}
else
{
echo "Please click here to login " . "<a href=index.php>Login Page</a>";
}
?>

97
Sample Code for Performing Transaction
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>

<?php
session_start();

if(isset($_SESSION['username']))
{
?>
<html>
<head>
<title>Transactions...</title>

<?php
include 'db_connect.php'; //Connect mysql database
$today= date("Y-m-d H:i:s"); //get todays date
$result ="";

$acc=mysql_query("select acc_number from customer");

if(isset($_POST['Submit'])) ///forsubmit data
{
$tid=$_POST['tranid'];
$trantype=ucwords($_POST['trantype']);
$tranmethod=ucwords($_POST['tranmethod']);
$date=date("Y-m-d");
@$chequenum=$_POST['chequenum'];
$acc_num=ucwords($_POST['acc_num']);
$amount=ucwords($_POST['amount']);
$remarks=ucwords($_POST['remarks']);

if(!preg_match ("/^[0-9]+$/i", stripslashes(trim($amount)))) //Accept Numeric only

{
echo "Enter Valid Data for Amount!";exit(0);

else
{
$forward=true;
if($trantype=="Withdrawal")
98
{
$valid=mysql_query("select balance from customer where acc_number=$acc_num");

while($res = mysql_fetch_array($valid, MYSQL_BOTH))

{
if($amount>$res[0])
{
echo "<script>JavaScript: alert('Amount insufficient!')</script>";

$forward=false;
}

else
{
$forward=true;
$updateamount=$res[0]-$amount;
}

}
}

else
{
$cid=mysql_query("select custid from customer where acc_number=$acc_num");
while($result = mysql_fetch_array($cid, MYSQL_BOTH))
{
$customerid=$result[0];
}
$custid=$customerid;

$valid=mysql_query("select balance from customer where acc_number=$acc_num");

while($res = mysql_fetch_array($valid, MYSQL_BOTH))
{
$updateamount=$amount+$res[0];
$interest=($updateamount*0.03);
$total_balance=$updateamount+$interest;
$result1 = mysql_query("Insert into transactions
values('".$tid."','".$trantype."','".$tranmethod."','".$date."','".$chequenum."','".$acc_num."','".$am
ount."','".$total_balance."','".$remarks."','".$custid."')");
mysql_query("update customer set balance=$total_balance where acc_number=$acc_num")or
die("Non0o");
mysql_query("update interest set old_bal=$updateamount ,interest=$interest ,
tot_bal=$total_balance where acc_num=$acc_num") or die("Nono");
$db_close=mysql_close();
}
if ($result1 )
{
99
$dmode='$_GET[mode]';

echo "<script>JavaScript: alert('Transaction completed

successfully')</script>".header('location:tran.php?mode=$dmode');
//echo "<p>Click <a href='tran.php?mode=$dmode'> here </a> for another transaction";exit(0);

}
else
{
echo "Transaction failure";
echo "<p>Click <a href='tran_do.php?mode=$dmode'> here </a> to go back";
}
exit(0);
}

if($forward==true)
{
$cid=mysql_query("select custid from customer where acc_number=$acc_num");
while($result = mysql_fetch_array($cid, MYSQL_BOTH))
{
$customerid=$result[0];
}
$custid=$customerid;
$interest=($updateamount*0.03);
$total_balance=$updateamount+$interest;
$result=mysql_query("update customer set balance=$total_balance where
acc_number=$acc_num");
mysql_query("update interest set old_bal=$updateamount,interest=$interest ,
tot_bal=$total_balance where acc_num=$acc_num");
$result1 = mysql_query("Insert into transactions
values('".$tid."','".$trantype."','".$tranmethod."','".$date."','".$chequenum."','".$acc_num."','".$am
ount."','".$total_balance."','".$remarks."','".$custid."')");
$db_close=mysql_close();
if ($result1 )
{
@$dmode=$_GET['mode'];
echo "<script>JavaScript: alert('Transaction completed
successfully')</script>".header('location:tran.php?mode=$dmode');

echo "<p>Click <a href='tran.php?mode=$dmode'> here </a> for another transaction";exit(0);

}
else
{
echo "Transaction failure";
echo "<p>Click <a href='tran_do.php?mode=$dmode'> here </a> to go back";
100
}
} //
}
}
?>
<table width="1100px" height="500" border="0" align="center" bgcolor="#CCCCFF">
<tr><td width="110" bgcolor="">

<strong><font color="#CC0000" size=3>T R A N S A C T I O N  

PROCESS</font></strong><br>
<br>
</td></tr>
<tr>
<td width="180" valign="top">
<table width="180">
<tr>
<td width="180">
<a href="admin_data.php" class="button2">Manager Home
         </a>
</td>
</tr>
<tr>
<td width="180">
<a href="logout.php" class="button2"> Log Out
             
        </a>
</td>
</tr>
</table>
</td>
<td width="500px" valign="top">

<table width="426" border="0" align="center">

<TABLE width="65%" height="30%" border=3 align=center cellPadding=3 cellSpacing=0

class=rt id="rt">
101
<TBODY>
<TR> <TD class=sectionhead align=middle colSpan=2><div
align="center">Transaction Process</div>
</TD>
</TR>
<TR>
<TD class=firstalt align=middle width="41%"><div align="left" class="style1">Transaction
Number :</div>
</TD>
<?php
$tran=mysql_query("select max(tranid) from transactions");

while($tid = mysql_fetch_array($tran, MYSQL_BOTH))

{
if($tid[0] == null)
{
$tmax="900000";
}
else
{
$tmax=$tid[0]+1;
}
}
//print "<td class=firstalt><b><font size=4>";
//print $tmax;
print "<TD width=\"59%\" align=left class=firstalt><input";
print " name=\"tranid\" type=\"text\" tabindex=\"1\" ";
print " value=$tmax";
//print $tmax;
print " maxlength=\"100\" size=\"10\" tabindex=\"1\" readonly=\"readonly\">";
print "</font></b></TD></TR>";
?>
<TR>
<TD class=secondalt align=middle><div align="left" class="style2"><B>Transaction
Type:</B><BR> </div>
</TD>
<TD class=secondalt align=left>
<select name="trantype" tabindex="2" AUTOCOMPLETE="ON" tabindex="2" >
<option value="Select">Select</option>
<option>Deposit</option>
<option>Withdrawal</option>
</select>
</TD>
</TR>

<TR>

102
<TD class=firstalt align=middle width="41%"><div align="left" class="style1">Transaction
Method :</div>
</TD>

<TD width="59%" align=left class=firstalt>

<select name="tranmethod" tabindex="3" onclick='onindexchange()' >
<option value="Select">Select</option>
<option value="Cash">Cash</option>
<option value="Cheque">Cheque</option>
</select>
</TD>
</TR>

<font size=4>
<?php
$date=date("Y-m-d");
echo $date;

?>
</font>
</TD>
</TR>
<TR>
<TD class=firstalt align=middle><div align="left" class="style2"><B>Cheque Number
:</B></div>
</TD>
<TD align=left class=firstalt><input name="chequenum" type="text" maxlength="40"
size="40" tabindex="5">
</TD>
</TR>
<TR>
<TD class=secondalt align=middle><div align="left" class="style2"><B>Account Number
:</B><BR> </div>
</TD>
<TD class=secondalt align=left><select name="acc_num" AUTOCOMPLETE="ON"
tabindex="6" >
<option value="Select">Select</option>
<?php
while($accnum = mysql_fetch_array($acc, MYSQL_BOTH))
{
print "<option>$accnum[0]</option>";
103
}

print "</select>";?>
</TD>
</TR>
<TR>
<TD class=firstalt align=middle><div align="left" class="style2"><B>Amount :</B></div>
</TD>
<TD align=left class=firstalt><input name="amount" type="text" maxlength="20" size="20"
tabindex="7">
</TD>
</TR>
<TR>
<TD class=secondalt align=middle width="41%"><div align="left" class="style1">Remarks
:</div>
</TD>
<TD width="59%" align=left class=secondalt><input name="remarks" type="text"
id="acc_number" maxlength="20" size="20" tabindex="8">
</td>
</tr>
</TBODY>
</TABLE>
<div align="center"> <p>
<input name="Submit" type="submit" class="admin_add_items" value="Transact"
onclick=onindexchange()>

<input name="Submit2" type="button" class="admin_add_items" id="Submit2"

onclick="location.replace('./tran.php')" value="Cancel" ></div> </p>
</form> </DIV>

</TD>
</td></tr></table>
</TR> </TBODY>
</TABLE>
<div id="footer">
<br>
<p align="center"> </p>
</div>
</body>
</html>
<?php
}
else
{
echo "Please click here to login " . "<a href=index.php>Login Page</a>";
}
?>
104

Web Based Class Schedule Management System
No ratings yet
Web Based Class Schedule Management System
19 pages
Web Based Finance System
50% (2)
Web Based Finance System
65 pages
UOG Online Complaint System Project
100% (1)
UOG Online Complaint System Project
76 pages
Arba Minch University Institute of Technology School of Graduate Studies (MSC Program)
0% (1)
Arba Minch University Institute of Technology School of Graduate Studies (MSC Program)
4 pages
Final CH 1 Software Project Decument
No ratings yet
Final CH 1 Software Project Decument
75 pages
Web-Based Class Scheduling Project
No ratings yet
Web-Based Class Scheduling Project
10 pages
Unity University: Course: OOSAD, Project Report Title: Tax Management System
No ratings yet
Unity University: Course: OOSAD, Project Report Title: Tax Management System
10 pages
Computerized Exam System Overview
No ratings yet
Computerized Exam System Overview
64 pages
Web-Based Fisha Car Broker System
No ratings yet
Web-Based Fisha Car Broker System
70 pages
Online Distance Education System Project
No ratings yet
Online Distance Education System Project
94 pages
Web-Based Clinic Management System
No ratings yet
Web-Based Clinic Management System
89 pages
Online Voting Presentation Printsecond2
No ratings yet
Online Voting Presentation Printsecond2
96 pages
Proposal Naol Teshome
100% (1)
Proposal Naol Teshome
14 pages
Vital Event Management System in Soddo
No ratings yet
Vital Event Management System in Soddo
16 pages
Web-Based Employee Performance System
No ratings yet
Web-Based Employee Performance System
81 pages
Full Documentations
No ratings yet
Full Documentations
90 pages
Assosa University Credential Verification
No ratings yet
Assosa University Credential Verification
16 pages
Library Management System Project
No ratings yet
Library Management System Project
25 pages
Employee
No ratings yet
Employee
21 pages
Online Cafeteria System for Wollega University
No ratings yet
Online Cafeteria System for Wollega University
87 pages
Web-Based Vital Event Management System
100% (2)
Web-Based Vital Event Management System
63 pages
Arsi University ICT Infrastructure Overview
100% (1)
Arsi University ICT Infrastructure Overview
22 pages
Debre Tabor University: Faculity of Technology
No ratings yet
Debre Tabor University: Faculity of Technology
11 pages
Proposal Guide Line
No ratings yet
Proposal Guide Line
5 pages
Final Documentation
No ratings yet
Final Documentation
81 pages
j27 Request For Expressions of Interest Pmo Nidp 3
100% (1)
j27 Request For Expressions of Interest Pmo Nidp 3
3 pages
Kombolcha Transport Management System
No ratings yet
Kombolcha Transport Management System
25 pages
Web-Based Blood Bank System North Gondar
100% (1)
Web-Based Blood Bank System North Gondar
121 pages
Web-Based Exam System for Teachers
100% (1)
Web-Based Exam System for Teachers
77 pages
Restaurant Management System Proposal
No ratings yet
Restaurant Management System Proposal
12 pages
Automated Vital Events Registration System
No ratings yet
Automated Vital Events Registration System
71 pages
Fire Alarm System Design Proposal
No ratings yet
Fire Alarm System Design Proposal
32 pages
Keede Proposal For30072024
No ratings yet
Keede Proposal For30072024
41 pages
Intra-College Communication Web App
No ratings yet
Intra-College Communication Web App
40 pages
Robe City Web-Based Registration System
No ratings yet
Robe City Web-Based Registration System
96 pages
AUWC Registration System
No ratings yet
AUWC Registration System
127 pages
B.Tech Project: Automated Scheduling
100% (1)
B.Tech Project: Automated Scheduling
72 pages
College Admission System SRS
100% (1)
College Admission System SRS
30 pages
Credit and Saving Management System
No ratings yet
Credit and Saving Management System
96 pages
Assosa University College of Computing and Informatics Department of Computer Science
No ratings yet
Assosa University College of Computing and Informatics Department of Computer Science
22 pages
Predicting Bank Customer Churn
No ratings yet
Predicting Bank Customer Churn
134 pages
Biometric Attendance System Project
0% (1)
Biometric Attendance System Project
56 pages
Bahir Dar University: Institute of Technology Faculty of Computing MSC Program in Computer Science
No ratings yet
Bahir Dar University: Institute of Technology Faculty of Computing MSC Program in Computer Science
11 pages
Farm Assistant Web Service System
No ratings yet
Farm Assistant Web Service System
4 pages
Online Voting System New Edition 2024
No ratings yet
Online Voting System New Edition 2024
52 pages
Web-Based Vehicle System Project
No ratings yet
Web-Based Vehicle System Project
83 pages
Industrial Phase 1
50% (2)
Industrial Phase 1
45 pages
Haramaya University
No ratings yet
Haramaya University
1 page
Computer Security - Threats and Solutions
No ratings yet
Computer Security - Threats and Solutions
7 pages
Online Trade Registration System Project
100% (1)
Online Trade Registration System Project
79 pages
Debremarkos University Duplication Center
No ratings yet
Debremarkos University Duplication Center
67 pages
Web Based Custoamer Survice Management System For Hossana Town Water Supply Enterprise
No ratings yet
Web Based Custoamer Survice Management System For Hossana Town Water Supply Enterprise
42 pages
WSU Condo Management System
No ratings yet
WSU Condo Management System
95 pages
ABEBE and Gash Research Final
100% (1)
ABEBE and Gash Research Final
27 pages
Documentation Abdi
No ratings yet
Documentation Abdi
180 pages
Web-Based Bidding System Project
No ratings yet
Web-Based Bidding System Project
97 pages
School Management System
No ratings yet
School Management System
62 pages
Ethiopian Railway Ticket Booking System Final Year Project
No ratings yet
Ethiopian Railway Ticket Booking System Final Year Project
98 pages
Online Clearance System for Students
No ratings yet
Online Clearance System for Students
6 pages
Industrial Project of Billing System
No ratings yet
Industrial Project of Billing System
96 pages