Full Document

AMBO UNIVERSITY
Institute of Technology
Department of Computer Science
Final Project
Online saving and credit association management system for Ambo Town
Group members
Name Id
1. Abdi Fikru BRT/2104/08
2. Bontu Gemachu BRT/2268/08
3.Gena Wonbera BRT/2209/08
4. Kumsa Etana BRT/2296/08
5. Nuhamin Adugna BRT/2310/08
6. Obsa Biftu BRT/2236/08
7. Tashita Mama BRT/2244/08
Advisor Dr. Pramod + Mr. Wakjira

This project Submitted to Department of Computer Science, Institute of
Technology, Ambo University, in Partial fulfillment for the requirement of the
Bachelor Degree of Science in Computer Science.
AMBO, ETHIOPIA
[January 08, 2019]
Ambo University Academic Education Evaluation System
Declaration
This is to declare that this project which is produced under the supervision of Dr. Pramod title
“online saving and credit association management system for Ambo Town” is the sole
contribution of the authors and no part here of has been produced illegally which can be
considered as plagiarism. We will be responsible and liable for any consequences if violation of
this declaration is proven.
Date: ________________
Project members:
Name: Abdi Fikru signature_______________________
Name: Bontu Gemachu signature_______________________
Name: Gena Wonbera signature_______________________
Name: Kumsa Etana signature_______________________
Name: Nuhamin Adugna signature______________________
Name: Obsa Biftu signature_______________________
Name: Tashita Mama signature______________________
The project has been submitted for examination with my approval as university advisor.
Advisor name: ____________________signature______________date_____________________
Approval for the examining board:
_____________________________ _________________
Project coordinator signature
______________________________ _________________
Advisor signature
_______________________________ _________________
Examiner signature
Ambo University Institute of Technology Department of Computer science 2011/2019 i

Abstract
The purpose of this project is to develop a Web Based saving and credit association information
management System for Ambo Towns, the system reduces the time and labor required to provide
services, Reduce the error that made by the employers, change the manual storage mechanisms
into computerized system (database), provide fast, efficient, flexible, reliable and secured
services for better satisfaction of customers and improves the motivation of the employees. The
existing system of the organization is facing different problems such as data redundancy, lack of
data security and lots of paper work. To solve this problems 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 used Object oriented approach for both analyzing and
designing the new system.
To change the current manual system to a web based needed different software and hardware
tools such as PHP, MYSQLI and others.
Ambo University Institute of Technology Department of Computer science 2011/2019 ii

Acknowledgment
First of all, we would like to thank GOD for making us able to perform our tasks well, without
the will of GOD everything is impossible. We have a great thanks and appreciation to our
adviser Dr. Pramod and Mr. Wakjira for his excellent advice and supervision.
Next, we’d like to thank our classmates and friends for their wellness to give important
information and ideas for us. And also, we would like to thank association employees for their
good approach at interview time and wellness at giving important information for us.
Generally, we will extend our thanks and appreciation to all individuals that give important
information to us.
Ambo University Institute of Technology Department of Computer science 2011/2019 iii

List of Acronym
CPU central processing unit

CSS cascade style sheet
AT Ambo Town
GB giga byte
GHZ giga hertiz
GUI graphical user interface
HRM human resource management
HTML hypertext markup language
PHP Hyper Text Pre processor
RAM random access memory
UC Use Case
UML unified model language
OOSAD Object Oriented System Analysis and Design
XAMPP X-os, apache, mysql, php, perl.
BR Business Rule
Ambo University Institute of Technology Department of Computer science 2011/2019 iv

Contents
Abstract ......................................................................................................................................................... ii
Acknowledgment ......................................................................................................................................... iii
List of Acronym ........................................................................................................................................... iv
LIST OF FIGURES ..................................................................................................................................... ix
LIST OF TABLES ........................................................................................................................................ x
CHAPTER ONE ............................................................................................................................ 1

1 INTRODUCTION ................................................................................................................................ 1
1.1 Introduction ................................................................................................................................... 1
1.2 Background of Organization ......................................................................................................... 1
1.3 Problem of the statement............................................................................................................... 1
1.4 Objective of the project ................................................................................................................. 2
General Objective ................................................................................................................. 2
Specific Objective ................................................................................................................. 2
1.5 Scope of the Project ...................................................................................................................... 2
1.6 Significance of the Project ............................................................................................................ 3
Target Beneficiaries of the system ........................................................................................ 3
1.7 Methodology of the project ........................................................................................................... 4
Data Sources ......................................................................................................................... 4
Design Methodology ............................................................................................................. 4
Fact finding Techniques ........................................................................................................ 5
System Analysis and Design ................................................................................................. 5
Development tools ................................................................................................................ 5
Testing Procedure ................................................................................................................. 7
1.8 Limitation...................................................................................................................................... 7
1.9 Risk and Contiguous ..................................................................................................................... 7
Ambo University Institute of Technology Department of Computer science 2011/2019 v

Assumptions and Constraints ................................................................................................ 8
Scheduling............................................................................................................................. 8
CHAPTER TWO ........................................................................................................................ 10

2 DESCRIPTION OF EXISTING SYSTEM AND THE PROPSED SYSTEM ................................... 10
2.1 Introduction of Existing System ................................................................................................. 10
Player in the existing system ............................................................................................... 10
Function/Activities in the existing system .......................................................................... 10
Business rules...................................................................................................................... 11
Report generated in the existing system.............................................................................. 11
Forms and other documents of the existing systems ........................................................... 11
Bottlenecks of the existing system ...................................................................................... 12
2.2 Practice to be preserved .............................................................................................................. 13
2.3 The Proposed System .................................................................................................................. 13
Team composition structure ................................................................................................ 14
2.4 Feasibility Analysis ..................................................................................................................... 15
Operational feasibility ......................................................................................................... 15
Technical feasibility ............................................................................................................ 15
Economic feasibility ........................................................................................................... 15
Behavioral/Political feasibility ............................................................................................ 15
Schedule feasibility ............................................................................................................. 16
2.5 Requirement of the Proposed System ......................................................................................... 16
Functional requirement ....................................................................................................... 16
Nonfunctional requirement ................................................................................................. 17
CHAPTER THREE .................................................................................................................. 18

3 SYSTEM ANALYSIS AND MODELING ........................................................................................ 18
3.1 Introduction ................................................................................................................................. 18
3.2 System Requirement Specification (SRS) .................................................................................. 18
System use case identification ............................................................................................ 19
System use case model ........................................................................................................ 21
System use case description ................................................................................................ 22
Ambo University Institute of Technology Department of Computer science 2011/2019 vi

Scenarios ............................................................................................................................. 30
3.3 Object model ............................................................................................................................... 32
Class Diagram ..................................................................................................................... 32
3.4 Dynamic model ........................................................................................................................... 33
Sequence diagram ............................................................................................................... 33
Activity diagram ................................................................................................................. 38
State chart diagram.............................................................................................................. 42
3.5 User interface modeling .............................................................................................................. 44
CHAPTER FOUR ...................................................................................................................... 45

4 System Design .................................................................................................................................... 45
4.1 Introduction ................................................................................................................................. 45
Purpose of the System ......................................................................................................... 45
Design Goal ........................................................................................................................ 46
4.2 Current Software Architecture .................................................................................................... 46
4.3 Proposed Software Architecture ................................................................................................. 46
Overview ............................................................................................................................. 49
Subsystem Decomposition .................................................................................................. 49
Hardware /Software Mapping ............................................................................................. 50
Persistence Data Management ............................................................................................ 50
Access Control and Security ............................................................................................... 51
Global Software Control ..................................................................................................... 52
Boundary Conditions .......................................................................................................... 52
4.4 Subsystem Services ..................................................................................................................... 53
CHARTER FIVE ........................................................................................................................ 55

5 Implementation and testing ............................................................................................................... 55
5.1 Introduction ................................................................................................................................. 55
Final Testing of The System ............................................................................................... 55
Hardware and Software Acquisitions.................................................................................. 56
User manual preparation ..................................................................................................... 56
5.2 Training ....................................................................................................................................... 58
Ambo University Institute of Technology Department of Computer science 2011/2019 vii

5.3 Installation process...................................................................................................................... 58
5.4 Start-up Strategy ......................................................................................................................... 59
CHAPTER SIX ............................................................................................................................. 63

6 Conclusions and Recommendations ................................................................................................... 63
6.1 Conclusion .................................................................................................................................. 63
6.2 Recommendation ........................................................................................................................ 63
References ................................................................................................................................................... 64
Ambo University Institute of Technology Department of Computer science 2011/2019 viii

LIST OF FIGURES
Title page
Figure 1 Online Saving and Credit Management System (WALQO) ........................................... 14
Figure 2 use case diagram ............................................................................................................ 22
Figure 3 Class Diagram of proposed system ............................................................................... 32
Figure 4 sequence diagram for login............................................................................................ 33
Figure 5 sequence diagram for register customer ........................................................................ 34
Figure 6 sequence diagram for create account ............................................................................ 35
Figure 7 sequence diagram for send loan request........................................................................ 36
Figure 8 sequence diagram for view balance ............................................................................... 37
Figure 9 Activity diagram for login .............................................................................................. 38
Figure 10 Activity diagram for create account............................................................................. 39
Figure 11 Activity diagram for send loan request ........................................................................ 40
Figure 12 Activity diagram for view balance ............................................................................... 41
Figure 13 state chart diagram for login ....................................................................................... 42
Figure 14 state chart diagram for register customer ................................................................... 43
Figure 15 user interface prototype ............................................................................................... 44
Figure 16 System Architecture...................................................................................................... 48
Figure 17 Deployment diagram .................................................................................................... 50
Figure 18 Persistence Data Management .................................................................................... 51
Figure 19 activate Xamp ............................................................................................................... 59
Figure 20 Configuration of Xamp................................................................................................. 60
Figure 21 User interface Home page ........................................................................................... 60
Figure 22 Admin page .................................................................................................................. 61
Figure 23 Manager page .............................................................................................................. 62
Ambo University Institute of Technology Department of Computer science 2011/2019 ix

LIST OF TABLES
Title Page
Table 1 hardware requirements ...................................................................................................... 5

Table 2 software requirements........................................................................................................ 6
Table 3 for the schedule of the project............................................................................................ 9
Table 4 for prescription paper from customer to accountant/worker of association ................... 12
Table 5 Team composition structure............................................................................................. 14
Table 6 use case identification...................................................................................................... 19
Table 7 use case description for login .......................................................................................... 22
Table 8 use case description for register customer ...................................................................... 23
Table 9 use case description for create user account ................................................................... 25
Table 10 use case description for send loan request .................................................................... 26
Table 11 use case description for approve loan request .............................................................. 27
Table 12 use case description for view report .............................................................................. 28
Table 13 use case description for view balance ........................................................................... 29
Table 14 Scenarios ....................................................................................................................... 30
Table 15 Subsystem services ......................................................................................................... 53
Ambo University Institute of Technology Department of Computer science 2011/2019 x

CHAPTER ONE
1 INTRODUCTION
1.1 Introduction
As we know today, the world is in technological area so the world is being coming to one
village. As a result, we should to develop an automated system for Ambo Town credit
association management system.
Ambo Town employee’s saving and credit association is an organization under the control of
Ambo Town employees that provides saving and credit services for employees in the Town that
wants to use the services. The association manages different employees like accountants,
cashers, and other members
This system provided service to employees of Ambo Town for saving and loan money. In once
credit association the using of money must be performed properly.
1.2 Background of Organization

Ambo Town employee’s saving and credit association was initially established in March 2007
E.C. at the time of establishment there were 100 members. The current number of members in
the association is 3000.Among those members 2450 are females and 550 are males.
At the beginning of the association there were no regular accountants, among the members of the
association candidates accountants were working. Currently there are 2 regular accountants.
The project is helpful to keep detail information about members, keep record of all modification
and it provides security using login form and using encryption mechanism that are not done in
the existing system. The system what we are going to develop solves the problems of the existing
systems work
1.3 Problem of the statement

There are many problems in Ambo Town employees ‘saving and credit association of the
existing system since every process are paper based and users information are copied more than
one paper. Generally processing user information in the existing system takes excess time, costs
and effort.
Ambo University Institute of Technology Department of Computer science 2011/2019 1

Some of the problems are:
 The customer can’t easily view his/her balance: - since the system is paper based it is
difficult to view balance easily
 Difficult to shares information easily in the association: - information sharing among
parents is time consuming.
 Post meeting date is difficult and time consuming: - because the meeting date must be
uploaded on different areas of the campus in order to late the members .
 Calculating loan and deposit interest is difficult and not free from errors:-because all the
calculation processes are performed by the accountant so errors may be occurred
 Giving response for loan request takes long time:-since there are many processes to
response for loan request it is time consuming by the current system
 The customer must be registered on three papers:-used to protect data from lost
1.4 Objective of the project

General Objective
The general objective of the proposed system is to develop web-based employee’s saving and
credit association information management system for Ambo Town(WALQO).
Specific Objective
The specific objectives of the proposed system is list of objectives that are useful to achieve the
general objectives
 To develop a system that registers and modifies member information easily.

 To develop a system that calculate loan and deposit interest easily
 To develop a system that shares information easily in the association
 To develop a system that provides fast services.
 To develop a system that makes members able to view their balance easily.
 To develop a system that makes members to send requests easily.
 To develop a system that makes members to view response easily.
1.5 Scope of the Project

The scope of the project covers the development of web-based saving and credit association
information management system in Ambo Town.
The proposed system supports society that are living in Ambo Town to be a member and get
service like request loan and deposit money.

The proposed system performs different tasks some of are:
 Register new member
 Send loan request
 View response
 view balance
 Provide information to the users/generate report
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 Customer
 Reduce the time and labor required to get services from the association.
 To give/accept necessary information easily.
 It enhances accuracy, speed, and security of services.
 For their better satisfaction with fast services provided by the employees
 Enables the user to interact with the system easily because the system is user friendly
For employees
 The system takes the calculate loan and deposit interest tasks that are performed by the
employees in the existing system
 reducing the broad manual work
For association
 Reduce the cost because of reduced number of employee.
The system makes the association database accurate and secured.
Target Beneficiaries of the system

There are two beneficiaries in our system. These are:
 The organization:-The first beneficiaries of this proposed system is the organization by

itself (mainly manager/finance officer) that has full access to the system. the system
provides efficiency ways for recording the customer information and searching some
records of the customer. It can save resources like working time, increase efficiency,
increase performance of the system.

 Customer:-a person who has some saving problems or need advice from the manager.
1.7 Methodology of the project

To develop this project the team used data sources, design methodology and object-oriented
system development methodology. Because this object oriented methodology has the following
purposes:-
Simplicity:- software objects model real world objects, so the complexity of our project is
reduced and the program structure is very clear.
Increased Quality:- Increases the quality of our project by-product of this program reuse.
Faster Development:- Object oriented development leads to faster of project development.
Maintainable:- Object oriented methodology makes code more maintainable. Objects can be
maintained separately, making locating and fixing problems easier.
Data Sources
The data source for this study was primary data sources and secondary data sources. The primary
data collection have been done through questionnaires, group discussion and interview and the
secondary data sources was from Magazines, books, reports, woreda sectors, journals, articles,
related literatures, website and the like.
Design Methodology
To design the system, the project team has chosen Object Oriented Modeling techniques and
unified modeling language tools. Reason for choosing:
It enables us to comprehensively model a system before we develop it.
Modification of the object implementation is easy because objects are loosely coupled.
Understanding of the structure is easy because object oriented modeling and tools used to
represent real world entities

Fact finding Techniques
Interview
We made an interview questions with the employees of Ambo Town employee’s saving and
credit association to get information that are useful for developing our system.
Observation
We observed the working mechanism of the existing system
Document analysis
We read the document which is prepared by the association that explains about the association
feature.
System Analysis and Design
 To develop this system we prefer OOSAD (Object Oriented System Analysis and
Design) methodology.
 This is because an OOSAD provides the following advantages Promotes better
understanding of user requirements.
 Leads to clear design by using use case, activity diagrams and sequence diagrams.
 Allows to breakdown complicated systems into smaller, clearly defined and more
manageable parts.
 Enables the standardization of objects which increases design understanding and
decreases the risk associated with project development.
Development tools
We can see development tools in to ways hardware part and software part.
Hardware requirements
Hardware parts are the physical part that can be touchable and visible components that are
necessary to develop a system. The hardware required to develop the proposed system are:
Table 1 hardware requirements
Tools Activities
Personal computer (PC) Almost all tasks of our project are performed on computer.
RAM 4GB To store the file temporarily

CPU Intel(R) Core(TM) used to process instruction
i3-4160 CPU @
3.60GHz:
Hard disk: store large file permanently
Software requirements
The software parts are the instructional components used to develop a system. Software parts to
develop system are as follows:
Table 2 software requirements
Tools Activities Why?
Sublime, Code writing. Easy to use.
notepad++
MYSQLI For designing the database. Database server for PHP.
server
MS word 2019 Documentation. Easy to use.
E-draw max, to design Unified Modeling Easy to design diagram.
Visio Language (UML) diagrams.
HTML Client side coding. It works with PHP.
XAMP Server to test the system by running. Easy to use.
CSS Style/beautify the content. It works with HTML and PHP
Web For browsing and running the system Better for displaying webpage
browser(Google
chrome)
apache Web server Web server for PHP
Snipping tool Capturing images Easy to use

Testing Procedure
To test the entire system as a whole with all forms, code, modules, we use Black Box
testing or System tests. Thus the team members test all the functionalities in the System.
All errors in the forms, functions, modules are tested. Testing is the most important to
determine the quality of the system.
Online saving and credit Association system in Ambo Town 2019
AU-IOT Campus Department of computer science
It used to identify what the error of the system or either to check the system has error or not,
either an expect input gives the actual output or not and check the integration of the classes
produce real object. For instance, we will use black box testing, unit testing and integration
testing.
Unit testing
First we will tests each unit at each system. So, if a problem is encountered it will immediately
maintain at which the problem is occurred.
Integration Testing
After we test each unit of the proposed system we will perform an integration test to check
whether the system meets all the functional requirements. When a number of components are
complete; it will test to ensure that they integrate well with each other, the operating system, and
other components.
System Testing
For verifying as the whole system is functioning in integrated manner and helping in striving
planned goal. System testing is comparing Function of the system developed in relation with
expected function of the system.
1.8 Limitation
 The system have a link with bank manually.
 The system does not include any financial transaction.
1.9 Risk and Contiguous

Unfortunate failure of system: To handle this problem the teams have some method to resist
not completely but partially by using back up mechanisms using flash disks and CD and by
storing the data in more than two computers.

Power problem: we use PC to cover the gap happened to our project during power failure.
Virus attack: It is difficult to control data from virus but try to scan the data, installing and
updating antivirus software.
Time management problem: this problem by working cooperatively, divide our time by
schedule for each phase of the project and we try to use the schedule effectively. Two of our
group members go to their original homeland while in the process of project development as
result of cold war exist in our campus to solve this problem the remaining group member
together covers this member work. Therefore whatever situation happen or occurred that hinder
during the progression of the project the team try to select the best option to do what expected
and reform it. Risk analyses are to solve the above problems that have used different techniques
for protecting the data from infection. The methods include:-
 Making copies in CD-ROM, Flash, other materials for computer failure.

 System Failure: to solve this problem the workers must take backup file by using external
hard drive daily.
 Power Failure:-when power failure occurs the organization must use a backup generator.
 By updating the antivirus software.
Assumptions and Constraints

Constraints are situations or uncomfortable conditions that restrict us from fully achieving the
Constraints goal of our project. The major constraints of the proposed system are:
 Computers.
 Internet.
 Electric power.
Because the proposed system is depending on the above constraints. We assume that there is
internet access and electric power and also needs computers. So electric power and Internet
connection must need to the system to work as intended.
Assumptions
 Every computer should have Ethernet connection.

 The users will have sufficient knowledge of computers.
 The users must know either Afan oromo or English language.
Scheduling
The department gave us calendar for our phase one (documentation part) of project according to
the following chart.

Table 3 for the schedule of the project

CHAPTER TWO
2 DESCRIPTION OF EXISTING SYSTEM AND THE PROPSED

SYSTEM
2.1 Introduction of Existing System

In the existing system the organization is done manually and also the association accepts
feedback from customer only on the meeting date because of manual working.
The accountant in the association registers customer and their information such as their name,
address, phone number, birth date and so on, when they want to save or take loan money. In
general, the existing system of Ambo Town employee’s saving and credit association is difficult
to access and manage customer’s account because all the activities are done manual based
system by going to the association office physically and after waiting a long queue the
association attendant take customer information.
Player in the existing system
 Manager: a person who manages and coordinates the system activities.

 Loan committee: to approve or deny loan request
 Accountant: a person who calculate saving and loan interest rate, generate report,
register customer
 Customer: The people who get service like loan money, deposit money and withdrawal
money from the association.
 HRM officer: To check the customer is the member of town and free from loan at the
time of loan request
 Finance officer: Snip from salary for deposit and loan.
Function/Activities in the existing system

To request for loan the customer must go to the HRM enters applicant, and then go to the
association and asks for loan, the accountant in the association register the request and forwards
it to the loan committee, according to the customer capacity to loan the loan committee approve
or deny the request and forwards the response to the main committee, the main committee
forwards it to the manager and the manager forward to accountant, the accountant gives loan

money for the customer if the request is approved. The accountant calculates the saving and loan
interest rate for the customer of the association.
To request for withdraw the customer must go to the association, the accountant in the
association register the request and forwards it to the manager and send back to accountant.
Business rules
A business rule is an operating principle or policies that must be fulfilled in order to the system
function properly and effectively. It often pertain to access control issues, business calculations,
or operating polices and principles of the organization.
 BR1: when customers want to get service they must be registered first to the association.
 BR2: the customer before send loan request applicant in human resource management.
 BR3: the minimum amount of money to loan is 50birr.
 BR4: In order to get loan the loan request must be approved by loan committee.
 BR5: the customer must be in this town(Ambo).
 BR6: the customer can’t take loan more than ones until it repays 1/3 of the loan.
 BR7: the maximum amount of loan money the member can take is 5times of the
deposited money.
Report generated in the existing system

In the existing system generating the overall report of the organization is done manually and also
the association accepts feedback from customer only on the meeting date because of manual
working.
The accountant in the association registers customer and their information such as customer
name, phone number, occupation, address. The customer saves money monthly according to
his/her income by agreement with the association.
Forms and other documents of the existing systems

There are forms available for customer to be filled by their information such as their name,
address, and account number and so on, when they want to save or take loan money.
 To request for loan the customer must go to the HRM enters applicant, and then go to the
association and asks for loan, the accountant in the association register the request and
forwards it to the loan committee, according to the customer capacity to loan the loan
committee approve or deny the request and forwards the response to the main committee, the

main committee forwards it to the manager and the manager forward to accountant, the
accountant gives loan money for the customer if the request is approved. The accountant
calculates the saving and loan interest rate for the customer of the association.
 To request for withdraw the customer must go to the association, the accountant in the
association register the request and forwards it to the manager and send back to accountant.
Forms from prescribe to Accountant
Table 4 for prescription paper from customer to accountant/worker of association
Bottlenecks of the existing system

 Performance (in response to time)
In terms of performance, the existing/manual system is not as satisfactory because it is slow/time
consuming; energy consuming and Searching files from some documents can take time so long.
 Input(Inaccurate/redundant/flexible)Output
In the existing saving and credit management system for Ambo town, the information of a
certain customer could be redundant and inflexible and these inputs may lead to create confusion
and unnecessary and produce inaccurate output.
 Security and Controls
Since every file and record of the status of patient information is stored in the manual way, it is
difficult to control and secure these manual files. The existing manual system is not secure there
is no authentication mechanism for documenting information.
 Efficiency

It is difficult to whirl through papers to check the health mark of individuals in the intended
clinic. It is also difficult to list all the appointments with patients on the paper, the paper may
lose.
2.2 Practice to be preserved

The main activities that are performed in the manual system will be transfer by designing the
corresponding simulation of those activities. That is each activity that is transfer to the system
are designed and online to achieve the best functionality.
 The Manager can control the overall activity in the system.
 The Manager, Customer, technician and other worker are governed by the business rule.
2.3 The Proposed System

The proposed system is highly computerized in which the data related to user accounts will be
secured highly with high accuracy that even reduced the machine damage and human made
errors and the system is highly efficient to offer best services to the customers as well as
organization because it has user friendly access that customers less time when compare with a
manual system. When the data is entered it will check for its validity. Appropriate massages are
provided as when needed. The data entry screen is design such a way that all the data
manipulates can be performed, it also provide record viewing facilities. Our Project developing
as per the below figures. In the below fig (a) this project is use for online saving and credit
system, the user can register first and then login. When user login successfully they will perform
the operation like money withdraw, deposit, view balance, view meeting date etc. Admin has all
authority to handle all the user account in a sequence to avoid unauthorized user. Manager can
update customer data like address, contact number etc. as well as they link number with
customer account number using online saving and credit system. customer can deposit money,
withdraw and check account balance through online saving and credit system.

Figure 1 Online Saving and Credit Management System (WALQO)
Team composition structure

In our project, we have seven (7) members where each of us has specified work and also the
project is supervised by two of our members. The following are the types of tasks and as well as
the responsibility each of us can have.
Table 5 Team composition structure

Task Name Student Name Phone number ID.NO
Project manager 1.Gena Wonbera 0919295551 BRT/2209/08
2.Obsa Biftu 0915989545 BRT/2236/08
System analyst Obsa Biftu 0915989545 BRT/2236/08
Tashita Mama 0963099959 BRT/2244/08
Bontu Gemechu 0938060006 BRT/2268/08
System designer Gena Wonbera 0921332891 BRT/2209/08

Nuhamin Adugna 0923380973 BRT/2310/08
Abdi Fikru 0955392010 BRT/22104/08
Kumsa Etana 0911903785 BRT/2296/08
Programmer 1.Gena Wonbera 0919295551 BRT/2209/08
2.Obsa Biftu 0915989545 BRT/2236/08
Testing All team

Project adviser Dr.Pyramod vs Mr.Wakjira.
2.4 Feasibility Analysis

It is an analysis of the ability to complete a project successfully, taking into account Operational,
technological, Behavior/political, economical and other factors.
Operational feasibility
It is the measure of how well the solutions for problems will work in the association.
The project will 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.
Technical feasibility
It’s a measure of whether the proposed system is user friendly and enables users to maintain
when problems occur or not.
Our system is technically feasible due to the following reason:-
 Member can adapt the system easily.
 No need of much more skill
 Developed with in the latest technology.
 Users can maintain problems easily.
Economic feasibility
Economic feasibility is the analysis of a project's cost benefit analysis in an effort to determine
whether or not it is logical and possible to complete. Our proposed project is economically
feasible because it has less expensive when compared to the existing system, so the project helps
in reducing the cost.
Behavioral/Political feasibility
Behaviorally/politically this project will meet all legal and ethical requirements of the project are
applied. The system we are going to developed is not conflict with any government directives or
cannot interfere with any political issue and with any cultural aspects. So our project is
Behaviorally/politically feasible.

Schedule feasibility
The schedule for this project will be feasible due to wealthy information exchange between the
developing team, Advisor and the organization. And also the time set to develop the system is
enough to complete at the predefined day and time. The project team members expected the
Project to be completed on time without any delay.
2.5 Requirement of the Proposed System

Functional requirement is described as what the system is done by identifying the necessary task
, action or activity that must be accomplished.A System Requirement Specification(SRS) is a
document or set of documentation that describes the features and behavior of a system or
software application. It includes a variety of elements that attempts to define the intended
functionality required by the customer to satisfy their different users. In addition to specifying
how the system should behave, the specification also defines at a high-level the main business
processes that will be supported.
Functional requirement
Functional requirement is described as what the system is done by identifying the necessary task,
action or activity that must be accomplished. User requirement that are all about the functionality
of the system.
These kinds of requirement are directly related to the system, to user, and stockholders.
The proposed system has the following functional requirements:-
 Manager register new customer
 Manager view loan request.
 Manager updates customer information up on it required.
 System calculate interest rate for loan and deposit money
 Customer view their balance
 Manager announces meeting date.
 Manager view report such as amount of deposit money, amount of loan money, amount
of customer.
 Manager view report such as amount of deposit money, amount of loan money, amount
of customer.
 Customer send feedback

 System administrator block user
 System administrator register employee
 Customer send loan request
 Manager view approve loan request
 Finance view approve loan request checked by manager.
Nonfunctional requirement
Non-Functional requirement explains and describes requirements that support the system but
they are not part of the system functionalities. Generally nonfunctional requirements describe the
quality of the system.
Performance: Since the system is web based the deliver response time of the system should be
very fast. It perform its activity that are relating to the vote is accurately.
User interface: the system have interface for every user.
Security and access permissions: this system has user name and password to login to the
system for perform the tasks and also the data base uses the encryption methods in order to
protect the data.
Backup and Recovery: This system allows backup and recovery by displaying the message box or the
system warns the users who want backup and recovery.
Resources, usability, availability: the customer to access the system at any time 24/7 hour.
Speed: The system has quick response time.

CHAPTER THREE
3 SYSTEM ANALYSIS AND MODELING

3.1 Introduction
The purpose of modeling is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It focuses on
understanding the model how the software will be built. In order to make the implementation
easy the design is very essential. The project development team used an object oriented system
Analysis and development methodology.
Because the Object system development approach gives easier and natural way to break down
problems into simple, small and manageable components so that it reduces the vague appearance
of the big problem. Moreover, it is predominately used and popular method in present software
development trend. The major activities described in this chapter are system requirement
specification, constructing a use case diagram; use case description, constructing sequence and
activity diagram analysis level class diagram and user interface prototype about the proposed
system.
3.2 System Requirement Specification (SRS)

A System Requirements Specification (SRS) is a document or set of documentation that
describes the features and behavior of a system or software application. It includes a variety of
elements that attempts to define the intended functionality required by the customer to satisfy
their different users. In addition to specifying how the system should behave, the specification
also defines at a high-level the main business processes that will be supported.
Based on this designing our target is providing the online saving and credit management system
to the Ambo town. Under this system requirement specification we can describe the use case
identification and use case diagram.

System use case identification
A use case is a function that the system performs. Use Case represents interaction between the
user and the system. In system use case, we include high-level Implementation decisions. The
following use cases have been identified from the system specification.
Table 6 use case identification
Use case name Use case ID Include
Login UC1
Register customer UC2 Login
View feedback UC3 Login
Manage account UC4 Login
View customer UC5 Login
View new customer UC6 Login
View meeting date UC7 Login
Change password UC8 Login
Back up DB UC9 Login
Restore DB UC10 Login
View log file UC11 Login
Post meeting date UC12 Login
View withdraw request UC13 Login
View loan close request UC14 Login
View approve loan UC15 Login
Revise meeting date UC16 Login
View monthly report UC17 Login
Register repay money UC18 Login
Send report for deposit UC19 Login
Update customer info UC20 Login
View reported response UC21 Login
UC22
Send loan request

UC23 Login
View loan request
UC24 Login
Approve loan request
Reject loan request UC25 Login
Register representative UC26 Login
View deposit report UC27 Login
View report UC28
View loan report UC29 Login
Send request UC30 Login
cancel request UC31 Login
View balance UC32 Login
Approve withdraw request UC33 Login
Reject withdraw request UC34 Login
Logout UC35 Login
Actor: system Administrator:
 Back up DB
 Restore DB
 View log file
 view feedback
 view meeting date
 Change password
Actor: manager:
 post meeting date
 View withdraw request
 View loan close request

 View approve loan
 Approve withdraw request
 Reject withdraw request
 Revise meeting date
 View feedback
 View customer
 Change password
Actor: customer
 send request
 cancel request
 view response
 view balance
 send feedback
 view meeting date
 change password
Actor: finance officer
 view money.
 Send approval form.
 view customer.
 view feedback.
 change password.
System use case model

A use case diagram is a graphic depiction of the interactions among the elements of a system.
Use case diagrams consist of actors, use cases and their relationships. The diagram is used to
model the system/subsystem of an application.
 Boundary: - indicates the scope of your system.
 Actors: - An actor is a person, organization, or external system that plays a role in one or
more interactions with your system.
 Use cases, which the specific roles are played by the actors within and around the system.
 relationships:- relationships between actors and the use cases

Figure 2 use case diagram
System use case description

Table 7 use case description for login
Use case name Login
ID UC1
Actor System admin, manager, customer, finance officer.
Description The user enters authorized username and password in

order to access the system.
Precondition The user should have username and password.
Post condition The user successfully login to the system

Basic course action User action System response
1. Open home page.

2. Display the login
3. Enter the authorized page with login form.
username, password in the
login form.
4. Click on login button 5. Check the authorized

username, password.
6. If the username,
password and role is
correct login in the
system.
Alternative course of action A: if step 3 is invalid

A1: check the user have user name and password
A2: restart from step 3
Table 8 use case description for register customer

Use case name Register customer
ID UC2
Actor manager
Description The manager register new customer to the system

Precondition The manager must login to the system
Post condition Display message that indicates the success

of the operation
1. Login in the system. 2 Display manager

page.
3. Open customer
registration page.
4. Display customer
5. Enter the appropriate registration page.
information on the form.
6. Click on register button.

7. Check the filled
information.
8. If the filled
information is correct
the system registers the
new customer in the
system database and
display successful
message.
Alternative course of action A: If the filled information is incorrect

A1: the system display error message
A2: restart from step 5

Table 9 use case description for create user account
Use case name Create user account
ID UC4
Actor manager
Description The manager creates user name and password for

users
Precondition manager first login to the system
Post condition Successfully create account
1. login in the system 2 Display manager

3. Open the create account page
page. 4.Display create new
account form
5. Fill use name and
password.
6. Click on create button.

7. Check the filled
information on the
form.
8. If the filled
information is correct
the system saves on the
system database.

Alternative course of action A: system display ‘’account is not created message’’.
A1: repeat from step4.
Table 10 use case description for send loan request

Use case name Send loan request
ID UC22
Actor customer
Description Send request for loan by specifying the amount of

money it requires
Precondition The customer must login to the system
Post condition Successfully send request
1. first the customer login

2 Display customer
to his page
page
3. Open a page for Loan

Request.
4. Display Loan
5. Fill the appropriate Request form.

.
information on the form.

7. Click on request button.
6 Check the filled
information on the
form
8. If the filled
information is valid the
system displays
successful message.
Alternative course of action A: If the customer did not fulfill the requirement
A1: system display error message

A2: restart from step 4.
Table 11 use case description for approve loan request

Use case name Approve loan request
ID UC24
Actor manager
Description Receive customer requests , the system check the

conditions and accept or reject the request
Precondition The manager must login to the system
Post condition Successfully see the request
1. Login in to the system. 2 Display the manager

page.
3. Open view loan request
page. 4. Display the loans
request table.
5. manager click status
button
6. If the request
information is fulfilling the
criteria the system accept
the request.
Alternative course of action A: If the request information is not fulfilling the

criteria
A1: the system reject the request
Table 12 use case description for view report

Use case name view report
Id UC28
Actor Finance officer,

manager,customer,Admin

Description View monthly activity in the association
Pre-condition Finance officer,customer,Admin,

manager login to the system
Post condition Display monthly report
Basic course action User action System

response
1. login to the system

2.display
3. click view report finance
button officer,custome
r,Admin and
5. Click report button manager page
4. display
report button
6. display
monthly report
Table 13 use case description for view balance

User case name View balance
Id UC32
Actor customer
Description customer wants to view their balance
Precondition customer first login to the system
Post condition View necessary balance

Basic course of action User action System
response
1.login to the system

2.display
3.click view balance customer page
button 4. display
balance
Scenarios
Table 14 Scenarios
Construct Description Syntax
Use case A sequence of action including the 聽
function that system can perform to
Use case
interact with actor of the system
name聽
Actor A coherent set of role that users of the

use case play when interacting with these
use case
聽 Actor name
聽
System boundary Represents boundary between physical
system and the actor who interact with
the physical system
Association The participation of actors in use case

that is instance of actor and instance of
use case communicate with each other

Extended The relationship from an extension use
case to base use case specify how the
behavior for extension use case can be
inserted into behavioral defined for the
<<extends>>
base use case. <-----------------------
An extend relationship between two use

case indicates alternative behavior.
Use or include A relationship from use case to an
inclusion use case specifying how the
behaviors use case for the inclusion uses <<include>>
--------------------------------->
case inserted to the behavior for the base
use case.
An include relationship between use
cases indicates where one use case

always includes the behavior of
another.
Generalization Taxonomic relationship between more
general use case and more specific use
case

3.3 Object model
Class Diagram
The class diagram in the unified modeling language is a type of static structure diagram that
describes the structure of a system by showing the system's class, their attributes, operations (or
methods), and the relationships among objects.
The class diagram is the main building block of object oriented modeling. Classes in a
Class diagram represent both the main elements, interactions in the application, and the classes
to be programmed
Figure 3 Class Diagram of proposed system

3.4 Dynamic model
Sequence diagram
Sequence diagrams are used to formalize the behavior of this system and to visualize the
communication among objects. The diagrams show the flow of messages from one object to
another, and as such correspond to the methods and events supported by a class/object. These
typically show a user or actor, and the objects and components they interact with in the execution
of a use case. A sequence diagram is a Unified Modeling Language (UML) diagram that
illustrates the sequence of messages between objects in an interaction. A sequence diagram
consists of a group of objects that are represented by lifelines, and the messages that they
exchange over time during the interaction.
Figure 4 sequence diagram for login

Figure 5 sequence diagram for register customer

Figure 6 sequence diagram for create account

Figure 7 sequence diagram for send loan request

Figure 8 sequence diagram for view balance

Activity diagram
Activity diagram is UML behavior diagram which shows flow of control or object flow with
emphasis on the sequence and conditions of the flow. An activity diagram visually presents a
series of actions or flow of control in a system similar to a flowchart or a data flow diagram.
Activity diagrams are often used in business process modeling
Some of the activity diagrams of the project known as Ambo town online saving and credit
association information management system are:
Figure 9 Activity diagram for login

Figure 10 Activity diagram for create account

Figure 11 Activity diagram for send loan request

Figure 12 Activity diagram for view balance

State chart diagram
State chart diagram shows the change of an object through time from one state to the other state.
State chart modeling is used to show the sequence of states that an object goes through, the
events that cause the transition from one state to the other and the actions that result from a state
change. State chart diagram describes the flow of control of the proposed system from one state
to another state to describe the system dynamically. States are defined as a condition in which an
object exists and it changes when some event is triggered. The following figure shows the state
of the objects.
Figure 13 state chart diagram for login

Figure 14 state chart diagram for register customer

3.5 User interface modeling
User interface modeling is to indicate the surface that can be used by user and the system to
communicate to each other. User interface design is the overall process of designing how a user
will be able to interact with a system. The goal of user interface design is to make the user's
interaction as simple and efficient as possible, in terms of accomplishing user goals.
User interfaces describes how the user interacts with the new system interfaces. User interface
guides the user with user friendly commands how to operate the system. Most of the time user
interfaces does not need training of users, because users expected only now commands. User
interface is a complex task that focuses all the applying common UI design principles and
techniques, applying the station chosen interface design standards and involving our UI design.
Figure 15 user interface prototype

CHAPTER FOUR
4 System Design
4.1 Introduction
System design is the transformation of the analysis model into a system design model. System
design is the first part to get into the solution domain in a software development. Design focus on
transforming the analysis model into the design model that takes into the nonfunctional
requirements and constraints described in the problem statement and requirement analysis.
The purpose of design is to determine how to build the system and to obtain information needed
to drive the actual implementation of the system. The focus is particularly on the solution domain
rather than on the problem domain.
Purpose of the System

The goal of this phase is transforming the analysis model to design (solution) model which takes
into account the non-functional requirements that are described in the requirement analysis
phase. While developing online saving and credit management system, there are a lot of design
considerations to be taken. The system includes the following design considerations:-
 User friendly
Our system should be designed in easy way. It is not difficult to learn or to understand.
The system interface will be well-organized, easy to locate different tools and options.
 Simplify
The system should be designed with a primary focus of simplicity for users. Users should
be able to use the system intuitively and with minimum training.
 Reliability
The system is able to perform required function under stated conditions for a specified
period of time.
 Performance
The system will be designed by considering performs tasks with in a time frame that is
acceptable for the user, and does not require too much memory.

Design Goal
Design goals describe the qualities of the system that the developers should consider. These
goals can be inferred (the act or process of deriving logical conclusions from premises known or
assumed to be true) from the nonfunctional requirements.
It includes the following goal:-
Performance: The system should respond fast with high throughput, i.e. it should perform
saving and deposit processing in a time less than 3 minutes and when users retrieve request
information online it should respond at least before the session expires.
Dependability
The system should be robust (strong) i.e. it should be able to survive invalid user inputs, fault
tolerant, reliable and available. Since the system stores sensitive data, high emphasis is given to
security to withstand malicious attacks. The system shouldn’t allow non-authorized users to
access customer/employ personal data or modify.
Maintenance: - The system should be easily extensible to modify, add new functionality,
portable to different platforms. The code for the system should be easily readable,
understandable and should be easily mapped to specific requirements.
End User Criteria: - The system should have simple and understandable graphical user
interface such as forms and buttons which have descriptive names. It should give reliable
response for each user request at least before the session expires.
4.2 Current Software Architecture

There is no current software system in Ambo University that accomplishes similar tasks with our
system. Saving and Credit is a manual in many of organization including Ambo Town.
For instance, customer use manual and also employee cheek their result manually. This is very
difficult, since they work manually.
4.3 Proposed Software Architecture

The proposed system of online saving and Credit management system is the right software to be
incorporated into the computerized of the system for helping the organization needs with respect
to skillful Human Resource. The proposed system use three-tier architectures to design our
system. Because 3-tier Architecture increases performance, flexibility, maintainability,

Reusability, and scalability while hiding the complexity of distributed processing from the
users/clients.
The data Layer maintains the applications data such as customer data , employee data and saving
and deposit data. The middle layer (web/application server) implements the business logic,
controller logic and presentation logic to control the interaction between the application’s clients
and data. The controller logic processes client requests such as requests to view customer result,
to retrieve data from the database. The business logic dictates how clients can and cannot access
application data and how applications process data.
A web server is a program that runs on a network server (computer) to respond to HTTP
requests. HTTP is the standard protocol for transfer data across the internet. The client layer is
the applications user interface containing data entry forms and client side applications. It displays
data to the user.
The client layer interacts with the web/application server to make requests and to retrieve data
from the database. It then displays to the user the data retrieved from the server.

Figure 16 System Architecture

Overview
Design is a process of describing, organizing and structuring system components at
architectural design level and detailed design level. It converts functional models from
analysis into models that represents the solution. This chapter describes about the system
design for online saving and credit of Ambo Towns (WALQO). In this phase we illustrates
design goal of the project, proposed software architecture, subsystem decomposition,
deployment modeling, persistence modeling, access control and security.
Subsystem Decomposition
From the functional requirements we identified in the system analysis section, the
Fictional/imagine system consists of the following subsystems:
 Customer full fill online request form.

 System evaluate in automated way.
 Manage user account
 Authentication user
 Manage customer information
 Online view balance
Customer gates service–user or Customer can take service after manager accept them. They send
request and view answer on system immediately after the system display information of
customer.
Login _ enables the system to be accessed by system users. Users in order to interact with the
system must first interact with the login interface. It authenticate the user
Manage user account-enables the manager of the system to interact with the system in order to
administrate it. Admin can create user account, block user account and reactive user account.
Manage customer information-manager manage customer information. Manager can update

information, search information, and update/add information.

Hardware /Software Mapping
The system interface is built by using HTML and CSS. The validation of the system will be done
by JavaScript. The system interface which will interact with the database will be programmed in
PHP and the databases will be done in MySQLi, and the web server will be run on Apache
<<Application server>>
<<Client machine>> PHP <<database server>>
Web browsers Mysql

HTTP Apache server
HTTP
Figure 17 Deployment diagram
Persistence Data Management

The service must store in database to access in customer, answer is store in database, and the
customers’ result persistently kept in the database. The user account Information, which keeps
data of the user name, pass keys and user levels, is the one that will enable the system to provide
the access rights according the user Level. The other important customer information storage
which keeps customer information.

Figure 18 Persistence Data Management
Access Control and Security

The online saving and credit management system is the system that covers the activities like the
Admin manage user account manage question includes: create, block, reactive and view
feedback.
As a result our systems accessed by different account levels.
 Admin register employee and manage database.

 The manager can view customer, view request and manage customer information.
 Finance give money for customer.
 Customer send request and also see the result.
Multiple levels of security protect sensitive documents and files from unauthorized viewers.
Each user has a security access level and each document has a sensitivity level.

Depending upon the access level of the user, they will see only the list of documents that is
appropriate for their security access level. Generally, all users have their own user names and
passwords to control security access levels and document sensitivity level.
Global Software Control

Online saving and credit association of ambo town(WALQO) software architecture is to have an
explicit, decentralized software control. The system's dynamic control is distributed among
different controllers such that each object delegates some responsibility to other objects. The
request initiations are event driven:
 The admin initiates the UI Subsystem by logging into the system and can perform several
sub operations.
 The customer, employer and association subsystem is initiated after login into the system
and can perform several sub operations.
 The Database Subsystem can be initiated at any point by all Subsystems except the UI
Subsystem. Any request (send request/cancel) to the repository initiates the Database
Subsystem. The system stores its contents in the database between executions. When the
application is run again, it retrieves the contents from the previous execution. Any
change in the contents during this execution updates the database.
Boundary Conditions
 Startup goes to system URL and login.
Shout Down. Click logout and close browser.
Error Conditions:
Logging in
 Username or password field cannot be blank.
 Password and Username don’t match.
 Username is wrong does not exist.
 Users setting.
 User is unable to change certain setting.
 Data Entry.
 The system fails the customer are entering information.

 Communication between Admin/Manager/other employee.
 The communication line with the manager fails.
 The power may have lost.
 Monitor display
 The system crashes or the backup also crashes.
 The system hangs up.
 The desktop application may be fail up.
 Relative view for all information of
customer.
 Search criteria do not return all views.
4.4 Subsystem Services

We try to describe the services of each subsystem as follows
Table 15 Subsystem services
Service Name Service Input Service Output Service Description
Log In Module User name and If the user name and Authenticates and
password to enter in the password matches authorizes the user
to the system the main form will be
displayed if not
correct notify the user
System manager customer information Saving to the Register the customer

Module recorded database information

System Admin Enters needed Manipulated data Takes action on all the
module information to data
manipulate the DB.
System finance Wait for report Gives finance Finance service

complete
Service access What request to get Generate result after Reports the customer
Module service. they complete service services access
information from the
database

CHARTER FIVE
5 Implementation and testing
5.1 Introduction
In this chapter we mainly focuses on the implementation part, implementation concerned with
the type of material (Hardware and software required), techniques to develop the systems,
samples codes of the system, data preparation, how to install the system, some testing
techniques, start up strategy for the new installed system are briefly described in this part of
documentation.
Final Testing of The System

Testing is an improvement phase. This phase involves testing of developed system using
different form of data. Testing is vital to the success of the system. Testing is the process of
executing a program with the explicit intention of finding errors that is making the program fail.
System testing is the stage of implementation, which is aimed at ensuring that the system works
accurately and efficiently before live operation commences.
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. Every module of the System
is separately tested. I.e. the team tests every module by applying some selection mechanism.
Integration and system testing: In this testing part, all the modules will be combined
together and tested it for its fitness with each other and with the systems functionality .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.
System Testing
Here we compile the whole system stating from initial and proceed testing the whole system to
check out for the errors and flow control of the system.

Hardware and Software Acquisitions
For the project implementation we used the following hardware and Software is used.
Hardware
 Server:
 for connection to the client computer (to host the system).
 Computers.
 Network connection (cables).
 Printer to print soft copy.
 Flash
Software
For the System implementation the following software’s are used
 MySQLi and PHP

 Microsoft Office word 2016
 Window 10
 Notepad++/sublime text.
 XAMP server.
User manual preparation

Before using the systems the system admin first must create account for any employee and
Manager create account for Customer after that any allowed user can access the system.
As Customer:
The customer log into the system using username and password for:
 Send Request.
 View balance.
 Send feedback.
 View meeting date.
 Change password.

As Manager:
Login using username and password to:

 Register Customer
 View request.
 Generate report.
 Approve/reject request.
 Post meeting date.
 View feedback.
 View customer.
As Admin:

 Register employee.
 Manage account
 View feedback.
 Backup database.
 Restore database.
 View log file.
As Finance:

 View customer.
 Send approval form.
 View money.

5.2 Training
Training is the process of teaching or learning a skill or job. Training is needed for two
reasons:
 If users are not adequately trained they will not operate the system correctly or
efficiently.
 If users fill that they are being asked to perform tasks that are outside their
capabilities, they may become demoralized and separated. User training must be
providing to user of the system in order to help them become equated with the
system. Users are vital part of any system. The introduction of new system must
mean changes in roles and relationship, if system being introduced is proposed by
web based saving and credit management system. It is less likely to be successful.
Therefore it is crucial to plan and provide proper training to the web based saving
and credit management system involved.
5.3 Installation process

Installation
After installing both notepad++/sublime and XAMP/WAMP server software do the following
steps ONLINE SAVING AND CREDIT ASSOCIATION MANAGEMENT SYSTEM FOR
AMBO TOWN(WALQO).
Step1
 Get the folder “Register “from the Developing Team.
Step 2
 In Xamp Copy the folder to WWW folder in the c:/programfiles/wamp After doing these
steps again, copy the folder “Register” from the Developing Team then.
Step3
 Paste into the folder” htdocs “in the C:/xampp.
Step4

 Installation is finished.
5.4 Start-up Strategy

Startup Strategy
 Steps1
 Activate Xamp server from the Desktop or Start up Menu if it’s not activated.
 Click on start -->Xamp server.
Figure 19 activate Xamp

Step2
 From this the start menu click on -> start.

Figure 20 Configuration of Xamp
Step3
 The you can interact with the system.
Figure 21 User interface Home page
 Interface of admin page.

Figure 22 Admin page
 Interface of manager: register Customer.

Figure 23 Manager page

CHAPTER SIX
6 Conclusions and Recommendations

6.1 Conclusion
The internet has become a major resource in modern business, online saving and credit
has gained significance. We have design the project to provide the user with easy
navigation, retrieval of data and necessary feedback as much as possible. A good user
design must be accompanied with user friendly to online application logic. It should be
convenient for the customer to view the contents of their balance and to be able to enroll
in service of every time. The online application described in this project provides a
number of features that are designed to make the customer and worker in easy way and
save time properly. Finally, we concluded our project have some best features that makes
customer/employees of ambo town satisfied by our system and take this features as our
strength.
6.2 Recommendation
The system recommends the following
 Since our project is effective and efficiency in saving resources we recommended that
this project is only for Ambo town. If the project inclusive all fresh man is Good but to
do this, it must have integrated with customer placement systems
 We recommended for another developer of online saving and credit management system
to add other local language.
 We recommended West show zone Ambo town to apply our system starting from 2012
because it save time.
 We also recommended this system have some limitation this occurs because of lack of
time and connection in our university so we strictly recommended that university must
fulfill material in learning and teaching process.

References
(1) (Unpublished) Ambo Town employee's saving and credit association rule and regulation,
2007.
(2) definition of system requirement specification

https://www.inflectra.com/ideas/topic/requirements-definition.aspx , accessed december 3 2010
1:30:23 AM
(3) Functional requirement vs nonfunctional requirement www.google.com/ , accessed

December 5 2010 2:23:12 AM
(4)UML use case diagram https://www.smartdraw.com/use-case-diagram/ accessed december

10 2010 3:04:45AM
(5) UML diagram, https://www.tutorialspoint.com/uml/uml_class_diagram.htm accessed

December 15 2010 1:21:03AM

Full Document

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Full Document

Uploaded by

Copyright:

Available Formats

AMBO UNIVERSITY

Advisor Dr. Pramod + Mr. Wakjira

Ambo University Institute of Technology Department of Computer science 2011/2019 i

Ambo University Institute of Technology Department of Computer science 2011/2019 ii

Ambo University Institute of Technology Department of Computer science 2011/2019 iii

CPU central processing unit

Ambo University Institute of Technology Department of Computer science 2011/2019 iv

CHAPTER ONE ............................................................................................................................ 1

Ambo University Institute of Technology Department of Computer science 2011/2019 v

CHAPTER TWO ........................................................................................................................ 10

CHAPTER THREE .................................................................................................................. 18

Ambo University Institute of Technology Department of Computer science 2011/2019 vi

CHAPTER FOUR ...................................................................................................................... 45

CHARTER FIVE ........................................................................................................................ 55

Ambo University Institute of Technology Department of Computer science 2011/2019 vii

CHAPTER SIX ............................................................................................................................. 63

Ambo University Institute of Technology Department of Computer science 2011/2019 viii

Ambo University Institute of Technology Department of Computer science 2011/2019 ix

Table 1 hardware requirements ...................................................................................................... 5

Ambo University Institute of Technology Department of Computer science 2011/2019 x

1.2 Background of Organization

1.3 Problem of the statement

Ambo University Institute of Technology Department of Computer science 2011/2019 1

1.4 Objective of the project

 To develop a system that registers and modifies member information easily.

1.5 Scope of the Project

Ambo University Institute of Technology Department of Computer science 2011/2019 2

1.6 Significance of the Project

Target Beneficiaries of the system

 The organization:-The first beneficiaries of this proposed system is the organization by

Ambo University Institute of Technology Department of Computer science 2011/2019 3

1.7 Methodology of the project

Faster Development:- Object oriented development leads to faster of project development.

related literatures, website and the like.

It enables us to comprehensively model a system before we develop it.

Ambo University Institute of Technology Department of Computer science 2011/2019 4

System Analysis and Design

Ambo University Institute of Technology Department of Computer science 2011/2019 5

Ambo University Institute of Technology Department of Computer science 2011/2019 6

1.9 Risk and Contiguous

Ambo University Institute of Technology Department of Computer science 2011/2019 7

 Making copies in CD-ROM, Flash, other materials for computer failure.

Assumptions and Constraints

 Every computer should have Ethernet connection.

Ambo University Institute of Technology Department of Computer science 2011/2019 8

Ambo University Institute of Technology Department of Computer science 2011/2019 9

2 DESCRIPTION OF EXISTING SYSTEM AND THE PROPSED

2.1 Introduction of Existing System

Player in the existing system

 Manager: a person who manages and coordinates the system activities.

Function/Activities in the existing system

Ambo University Institute of Technology Department of Computer science 2011/2019 10

Report generated in the existing system

Forms and other documents of the existing systems

Ambo University Institute of Technology Department of Computer science 2011/2019 11

Bottlenecks of the existing system

Ambo University Institute of Technology Department of Computer science 2011/2019 12

2.2 Practice to be preserved

2.3 The Proposed System

Ambo University Institute of Technology Department of Computer science 2011/2019 13

Team composition structure

Table 5 Team composition structure

System designer Gena Wonbera 0921332891 BRT/2209/08

Ambo University Institute of Technology Department of Computer science 2011/2019 14