UNITY UNIVERSITY

SCHOOL OF COMPUTATIONAL SCIENCE AND ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE

Credit and Saving Management System

A Senior Project Documentation Submitted to Unity University

In Partial Fulfillment of the Requirement for the Degree of Bachelor of Science in
Computer science

By

Name ID
Mohammedyasin Abdulaziz 58405E
Rediet Tekola 57004E
Yonas Abraham 57383E
Zelalem Gebru 58161E

Supervised by: Instructor Girma Aweke

Date: June 18, 2018

 CREDIT AND SAVING MANAGEMENT SYSTEM

Approval letter
We, undersigned hereby declare that this senior essay is our original work prepared under
the guidance of M.R Girma Aweke. All the sources of material used for the paper have been
duly acknowledged.

Name Signature
1. Mohammedyasin Abdulaziz ------------------------
2. Rediet Tekola ------------------------
3. Yonas Abraham ------------------------
4. Zelalem Gebru ------------------------

This is to certify that I have read this project and that in my opinion it is fully adequate, in
scope and quality, as a project for the degree of Bachelor of Science.

Name of Advisor: ______________________

Signature: ___________________________

Examining committee members name and signature

Examiner Name Signature Date

1. Examiner 1 ------------------------------------------------ ------------------------ ------------------------

------------------------ ------------------------
2. Examiner 2 -----------------------------------------------

------------------------ ------------------------
3. Examiner 3 -----------------------------------------------

------------------------ ------------------------
4. Examiner 4 -----------------------------------------------

It is approved that this project has been written in compliance with the formatting rules laid
down by the School of Computational Science and Engineering of Unity University.

I
 CREDIT AND SAVING MANAGEMENT SYSTEM

Acknowledgment
First and for most we would to express our deepest gratitude to our advisor Girma Aweke
for his excellent guidance, patience, and useful critiques throughout the project, without
which this project documentation may not have been completed successfully.

We wish to extend our gratitude to Addis Credit and Saving Institution staffs and customers
who gave enough information for our interviews and questionnaire with patience and full of
voluntariness.

Furthermore, our gratitude goes to the computer science department lab assistances that
provided the necessary resources and platforms for the successful accomplishment of each
task.

Last but not least, we are thankful to our lecturers and classmates on the computer science
program for made our academic and social life comfortable at Unity University.

II
 CREDIT AND SAVING MANAGEMENT SYSTEM

Executive Summery
The purpose of this document is to offer readers a general vision of characteristic, structures
and behaviors in the financial services provided by Addis Credit and Savings Institution. In
each case a brief description of the financial service is presented, along with its current
situation and problematic, some relevant evidence and considerations of appropriateness as
well as recommendations that the study suggests.

In the current documentation, it is proposed that, data is gathered through interview

supplemented by office observation and existing document analysis. We conduct
observation in order to analyze the conditions to which the existing system is acting. Then,
the data is analyzed and can be conducted to determine the key outcome of the method, so
that it is possible to avoid tedious paper work service given by Addis Credit and Savings
Institution to appropriate levels of quality service hence make the practice easily and
effectively viable in the long run.

On the other hand, in our country, there is a need to increase the efficiency of service so that
it competes with other countries system. There are a number of different methods through
which efficiency can be improved. However, for the current study, it is proposed to identify
problems in the Addis Credit and Savings Institution. Finally, The Project team designed the
appropriate model for the existing system as well as the proposed system using different
modeling techniques.

III
 CREDIT AND SAVING MANAGEMENT SYSTEM

Contents
Approval letter ........................................................................................................................................I
Acknowledgment ...................................................................................................................................II
Executive Summery ..............................................................................................................................III
CHAPTER ONE ........................................................................................................................................1
INTRODUCTION .....................................................................................................................................1
1.1. Introduction .............................................................................................................................1
1.2. Project Background ..................................................................................................................1
1.2.1. Vision ..................................................................................................................................2
1.2.2. Mission ...............................................................................................................................2
1.3. Advantage of Credit and Saving Management System ..........................................................2
1.4. Statement of the Problem .......................................................................................................3
1.5. Objectives .................................................................................................................................4
1.5.1. General Objective...............................................................................................................4
1.5.2. Specific Objectives..............................................................................................................4
1.6. Feasibility Study of the New System .......................................................................................4
1.6.1. Economic Feasibility ..............................................................................................................4
1.6.2. Technical Feasibility...............................................................................................................5
1.6.3. Operational Feasibility...........................................................................................................5
1.7. Scope of the Project .................................................................................................................5
1.8. Limitation of the Project ..........................................................................................................5
1.9. Tools and Methodologies ........................................................................................................5
1.8.1. Data collection Methods ....................................................................................................5
1.8.2. System Design Methods .....................................................................................................6
8.1.3. System Development Tools................................................................................................7
8.1.3.1. Scripting Languages ..........................................................................................................7
8.1.3.2. Web Development tool ....................................................................................................7
8.1.3.3. Database management software .....................................................................................7
8.1.3.4. Documentation tool .........................................................................................................7
8.1.3.5. Modeling software ...........................................................................................................7
1.10. Deliverables of the Project ......................................................................................................8
1.11. Beneficiaries of the project......................................................................................................8
1.11. Schedule .................................................................................................................................10

IV
 CREDIT AND SAVING MANAGEMENT SYSTEM

CHAPTER TWO .....................................................................................................................................11

PROJECT MANAGEMENT.....................................................................................................................11
2.1. Introduction ...........................................................................................................................11
2.2. Project Planning .....................................................................................................................12
2.2.1. Work Breakdown Structure (WBS)...................................................................................12
2.3. Resource Planning ..................................................................................................................13
2.3.1. Material Resource Planning .............................................................................................13
2.3.2. Human resource planning ................................................................................................13
2.3.3. Software Resource ...........................................................................................................14
2.4. Financial Plan .........................................................................................................................14
2.4.1. Human Resource Plan ......................................................................................................15
2.4.2. Material Resource Plan ....................................................................................................15
2.4.3. Software Resource ...........................................................................................................15
2.4.4. Contingency cost ..............................................................................................................16
2.5. Process Model ........................................................................................................................16
2.5.1. Waterfall Model ...............................................................................................................17
2.6. Team Organization .................................................................................................................18
2.7. Risk Mitigation and Management .........................................................................................18
CHAPTER THREE ..................................................................................................................................24
REQUIREMENT ANALYSIS....................................................................................................................24
3.1. Introduction ...........................................................................................................................24
3.2. Overview of Existing system ..................................................................................................24
3.2.1. Players in Existing System ................................................................................................25
3.2.2. Major Activities in the Existing System ............................................................................25
3.2.3. Preserved Activities from the Existing System .................................................................29
3.2.4. Bottlenecks of the Existing System Using PIECES Framework .........................................29
3.3. Proposed System....................................................................................................................31
3.3.1. Functional Requirement...................................................................................................31
3.3.2. Non Functional Requirement ...........................................................................................32
3.4. Essential use case diagram ....................................................................................................32
3.6.1. Actor Identification of Existing System ............................................................................33
3.6.2. Use case Identification of Existing System .......................................................................33
3.5. Essential User Interface Prototype ........................................................................................34

V
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.6. User Interface flow diagram ..................................................................................................39

3.7. Class Responsibility Collaboration (CRC Cards).....................................................................39
3.8. Business Rule ..........................................................................................................................40
CHAPTER FOUR....................................................................................................................................41
SYSTEM DESIGN...................................................................................................................................41
4.1. Introduction ...........................................................................................................................41
4.2. Purpose of the System ...........................................................................................................41
4.3. Design Goals ...........................................................................................................................41
4.3.1. Performance Criteria ........................................................................................................42
4.3.2. Security Criteria ................................................................................................................42
4.3.3. Cost Criteria ......................................................................................................................42
4.3.4. Maintenance Criteria .......................................................................................................42
4.3.5. End user Criteria ...............................................................................................................42
4.4. Design Trade off .....................................................................................................................42
4.5. System Use Case Modeling ....................................................................................................43
4.5.1. Use case Identification .....................................................................................................43
4.5.2. System Use Case Diagram ................................................................................................44
4.5.3. Use case Description ........................................................................................................45
4.6. Sequence Diagram .................................................................................................................51
4.7. Activity Diagram .....................................................................................................................63
4.8. Class Diagram .........................................................................................................................69
4.9. Database Design .....................................................................................................................71
4.10. Access Control and Security ...................................................................................................72
4.11. Component Diagram ..............................................................................................................73
4.12. Deployment Diagram .............................................................................................................73
4.13. UI Design.................................................................................................................................74
Refer ence .....................................................................................................................................80
Appendix ..............................................................................................................................................81

VI
 CREDIT AND SAVING MANAGEMENT SYSTEM

List of Figures
Figure 1. 1 Project schedule ................................................................................................... 10
Figure 2. 1 Process Model ...................................................................................................... 16
Figure 2. 2 Waterfall Model ................................................................................................... 17
Figure 3. 1 Essential Use Case Modeling ................................................................................ 34
Figure 3. 2 Login User Interface Prototype ............................................................................ 35
Figure 3. 3 New Customer Form user Interface Prototype .................................................... 35
Figure 3. 4 Deposit user Interface prototype ......................................................................... 36
Figure 3. 5 Withdrawal User Interface Prototype .................................................................. 36
Figure 3. 6 Transfer User Interface......................................................................................... 37
Figure 3. 7 Balance User Interface ......................................................................................... 37
Figure 3. 8 Search user interface Prototype........................................................................... 38
Figure 3. 9 New user Interface Prototype .............................................................................. 38
Figure 3. 10 User Interface Flow Diagram .............................................................................. 39
Figure 4. 1 System Use Case Diagram .................................................................................... 44
Figure 4. 2 Sequence Diagram for Login ................................................................................ 51
Figure 4. 3 Sequence Diagram for Register Employee ........................................................... 52
Figure 4. 4 Sequence Diagram for Generate Report .............................................................. 53
Figure 4. 5 Sequence Diagram for Approve Transaction ....................................................... 54
Figure 4. 6 Sequence Diagram for Create New Account ........................................................ 55
Figure 4. 7 Sequence Diagram for Add Loan .......................................................................... 56
Figure 4. 8 Sequence Diagram for Deposit Money ................................................................ 57
Figure 4. 9 Sequence Diagram for Withdraw Money ............................................................. 58
Figure 4. 10 Sequence Diagram for Transfer Money ............................................................. 59
Figure 4. 11 Sequence Diagram for Create User Account ...................................................... 60
Figure 4. 12 Sequence Diagram for Change Password........................................................... 61
Figure 4. 13 Sequence Diagram for View Transaction ........................................................... 62
Figure 4. 14 Activity Diagram for Login .................................................................................. 63
Figure 4. 15 Activity Diagram for Register Employee ............................................................. 64
Figure 4. 16 Activity Diagram for Generate Report................................................................ 64
Figure 4. 17 Activity Diagram for Approve Transaction ......................................................... 65
Figure 4. 18 Activity Diagram for New Account ..................................................................... 65
Figure 4. 19 Activity Diagram for Deposit .............................................................................. 66
Figure 4. 20 Activity Diagram for Withdraw ........................................................................... 66
Figure 4. 21 Activity Diagram for Transfer Money ................................................................. 67
Figure 4. 22 Activity Diagram for Add Loan............................................................................ 67
Figure 4. 23 Activity Diagram for User Account ..................................................................... 68
Figure 4. 24 Activity Diagram for Change Password .............................................................. 68

VII
 CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 25 Activity Diagram for View Transaction ............................................................... 69

Figure 4. 26 Class Diagram ..................................................................................................... 70
Figure 4. 27 Database Design ................................................................................................. 71
Figure 4. 28 Component Diagram .......................................................................................... 73
Figure 4. 29 Deployment Diagram ......................................................................................... 74
Figure 4. 30 Home Page UI ..................................................................................................... 75
Figure 4. 31 New Customer home Interface .......................................................................... 75
Figure 4. 31 Customer Home Page UI .................................................................................... 75
Figure 4. 32 Customer profile UI ............................................................................................. 76
Figure 4. 33 System Admin Home UI...................................................................................... 76
Figure 4. 34 Manager Home UI .............................................................................................. 77
Figure 4. 35 Deposit UI ........................................................................................................... 77
Figure 4. 36 Balance Transfer UI ............................................................................................ 78
Figure 4. 37 Withdraw UI ....................................................................................................... 78
Figure 4. 38 Officer UI............................................................................................................. 79

VIII
 CREDIT AND SAVING MANAGEMENT SYSTEM

List of Tables
Table 1. 1 Project Deliverables ................................................................................................. 8
Table 2. 1 Work Breakdown Structure .................................................................................. 13
Table 2. 2 Material Resource Planning ................................................................................... 13
Table 2. 3 Human resource planning..................................................................................... 14
Table 2. 4 Software Resource ................................................................................................. 14
Table 2. 5 Human Resource Financial Plan............................................................................. 15
Table 2. 6 Material Resource Financial Plan .......................................................................... 15
Table 2. 7 Software Resource Financial Plan.......................................................................... 15
Table 2. 8 Contingency cost.................................................................................................... 16
Table 2. 9 Team Organizing .................................................................................................... 18
Table 2. 10 Risk-Computer Crash ........................................................................................... 19
Table 2. 11 Risk-Late Delivery................................................................................................. 20
Table 2. 12 Risk-Incompatibility ............................................................................................. 20
Table 2. 13 Risk-End User Resistant ....................................................................................... 20
Table 2. 14 Risk- Change in requirement ............................................................................... 21
Table 2. 15 Risk-Lack of Experience........................................................................................ 21
Table 2. 16 Risk-Database stability ......................................................................................... 22
Table 2. 17 Risk-Poor Quality Documentation ....................................................................... 22
Table 2. 18 Risk-Poor comments in code ............................................................................... 23
Table 3. 1 CRC Card ................................................................................................................ 40
Table 4. 1 Use Case Description for Login .............................................................................. 45
Table 4. 2 Use Case Description for Create Account .............................................................. 45
Table 4. 3 Use Case Description for Approve Transaction ..................................................... 46
Table 4. 4 Use Case Description for Add Loan ....................................................................... 46
Table 4. 5 Use Case Description for Deposit Money .............................................................. 47
Table 4. 6 Use Case Description for Withdrawal Money ....................................................... 47
Table 4. 7 Use Case Description for Transfer Money ............................................................. 48
Table 4. 8 Use Case Description for Transfer Money ............................................................. 48
Table 4. 9 Use Case Description for Change Password .......................................................... 49
Table 4. 10 Use Case Description for Change Password ........................................................ 49
Table 4. 11 Use Case Description for Get Report ................................................................... 50
Table 4. 12 Use Case Description for Create User Account ................................................... 50
Table 4. 13 Access control and Security ................................................................................. 72

IX
 CREDIT AND SAVING MANAGEMENT SYSTEM

Abbreviation
ADCSI ……………………………………………….…. Addis Credit and Saving Institution
CSS …………. ……………………………………..... Cascading Style Sheets
HTML …………………………………………………... Hyper Text Markup Language
OOD ………………………………………….………... Object Oriented Design
PHP ………………………………………………….... Hypertext Preprocessor
WBS …………….……………………………………... Work Breakdown Structure
UML ……………...……………………………………. Unified Modeling Language
TR ………….………………………………………... Technical Requirement
CRC ………...…………………………………………. Class Responsibility Collaborator
BR ……………………………………………………. Business Rule
GUI ……………………………………………………. Graphics User Interface
UI ……………………………………………………….User Interface

X
 CREDIT AND SAVING MANAGEMENT SYSTEM

CHAPTER ONE

INTRODUCTION
1.1. Introduction

Technology plays a vital role on one’s country development in different sectors. Among these sectors;
Micro finance institutions takes a huge part serving the low income society. In Ethiopia, even though the
idea of utilizing computer solutions is still at its lowest level, many service-rendering businesses have
recently begun using such inevitable technologies. Among them, financial institutions such as banks
and insurance companies are benefiting greatly from them (Gebremedhin, Ethiopia:, 22 April 2016).

However, for the growing number of micro finance firms (firms providing small scale credit and saving
services for the community), although a limited number of special systems (Microsoft Excel) exist,
there is still a need for computer solutions for the industry. Automation of the system will enhance
service efficiency of microfinance firms by eliminating the shortcomings and limitations of the
existing systems (Gebremedhin, Ethiopia:, 22 April 2016).

Therefore, the present project is initiated so as to build a better and efficient computer solution that can
serve and enhance the business transactions of a microfinance firm called Addis Credit and Saving
Institution (ADCSI). The system is expected to provide up to date information and better service for
customers.

1.2. Project Background

ADCSI is a region-based micro finance institution established to serve people residing in the City of
Addis Ababa in January 27th 2000GC. Addis Credit and Saving S.C. were legally registered by the
National Bank of Ethiopia, according to according to Proclamation No.40/1996 (About Us: Major
Activities of the Institution, n.d.).

ADCSI was established to give full support to micro and small scale business operators in Addis
Ababa and Oromia region surrounding Addis Ababa, Burayu and Sululta. As per the revised
proclamation No. 626/2009, ADCSI has an objective to collect deposits and extend credit to rural and

1
 CREDIT AND SAVING MANAGEMENT SYSTEM

urban farmers, and people engaged in other similar activities as well as micro and small scale rural and
urban entrepreneurs (Addis Credit and Saving Institution, n.d.)

The major operations that are performed by ADCSI are saving, loaning, deposit, and withdrawal of
money. But most of these operations are performed manually. Customers in this organization get the
services by having manual saving, withdrawal account book. Until now these manual operations takes
much time.

ADCSI is still using a manual system so this project aims to up stand to interconnected system through
online managing system. The existing system aggravates user’s dissatisfaction. This is being
repeatedly reflected in its inability to avoid customer complaints related to service inefficiency and
document handling/management. But the system solves complaints provided by the customer providing
at hand solutions means that customer’s physical presence is not expected to the company to view its
information.

1.2.1. Vision

To become a sustainable financial institution, active contributor towards poverty reduction effort and
would like to see improvements in the life of low-income people (Addis Credit and Saving Institution,
n.d.).

1.2.2. Mission

To contribute to the eradication of poverty and unemployment prevailing in Addis Ababa and
surrounding through providing demand driven financial services is a sustainable way with special
focus to women (Addis Credit and Saving Institution, n.d.).

1.3. Advantage of Credit and Saving Management System

The outcome of this project will give the following advantage: -

 Promotes efficient and effective credit and saving management system for ADCSI by
focusing on those services that still require physical presence at the organization.
 Enables users to get fast and fascinating services by reducing the flow of human traffic and
long queues in all branches of the organization.
 It saves a lot of time to the customers and convenient to access information.

2
 CREDIT AND SAVING MANAGEMENT SYSTEM

 Improved accessibility of data and data can be shared easily.

 Integrity can be maintained.
 Centralized information control.
 Contributes in realizing organizational goals and objectives by supporting organizations
employees in updating and upgrading their careers with good Banking services, and
 Helps the project team to put their theoretical knowledge in to practice.

1.4. Statement of the Problem

With the problems and limitations associated with manual banking procedure as witnessed in ADCSI,
compiled with the problems associated with the existing application programs even much more in the
presence of serious technological advances aimed at improving information system. In ADCSI, the
customer registered or account created in a specific branch cannot be used in another branch. For
example; if the customer wants to get information (such as; total amount of money the customer
required to pay, closing date of the loan), customers must visit the organization and this results
wastage of time and money.

So the existing system leads the project team to conclude the following problems.

 Most operations are carried out manually.

 Customers are required to appear in person to get information about their transaction status as well
as the current issues of the organization.
 Due to the existing system, the customer doesn’t use their account in different branches of the
organization.
 Activities related to performance, information, and efficiency is a major problem.
 One of performance related problem is when the number of customer increases the response time
of the system serving the customers becomes so slow as the system performs its tasks manually.
 Volume of bulky paper work requires large number of man power managing the day-to-day
activities in the institution.
 To generate various types of reports timely, it requires more skilled experience and data is not
flexible.

3
 CREDIT AND SAVING MANAGEMENT SYSTEM

1.5. Objectives

1.5.1. General Objective

The general objective of the project is to develop a web based Credit and Saving Management System
for ADCSI.

1.5.2. Specific Objectives

To achieve the general objective, the following specific objectives are set

 Gather required information for the new system.

 Identify the limitation of the existing system and analyze how ADCSI works.
 Study the different characteristics of the ADCSI through interview, observation and document
analysis.
 Identify user requirements.
 Specifying and analyzing the functional and non-functional requirements of the new system.
 Proposing an appropriate system.
 Modeling and developing the new system entire form.
 Designing friendly user interface.
 Designing database to the system that can hold all the information.
 Implementing the new system.
 Testing the implemented system.
 Maintaining the new system.

1.6. Feasibility Study of the New System

The Feasibility Study is the preliminary study that determines whether a proposed systems project is
financially, technically and operationally viable. The Alternatives Analysis, usually included as part of the
Feasibility Study, identifies viable alternatives for the system design and development.

1.6.1. Economic Feasibility

In respect of the project significance the expected cost is worth carrying and the project team can
afford it; hence the project is economically feasible.

4
 CREDIT AND SAVING MANAGEMENT SYSTEM

1.6.2. Technical Feasibility

We believe that building a working system with acceptable throughput, response time and other
performance parameters will involve thorough technical knowledge and technology availability.
Despite this fact we will strive to apply all our knowledge and consult different resources so that the
project will technically be feasible.
1.6.3. Operational Feasibility
The new system will support the major activities of ADCSI and will take advantages to solve the
problems outlined in the statement of the problem section. Besides, all the staffs working on the
system can operate the system with little training. Therefore, it can be said that it is operationally
feasible.

1.7. Scope of the Project

The scope of this project is limited to the activities of the operations unit of the credit and saving system
in ADCSI which include opening of saving and loan account, deposit of funds, withdrawal and transfer
of funds. The new system embraces customer relation management (i.e. it ranges from handling
information about the customers involved in saving account and loan account). The data used by the
system is stored in a database that will be the center of the remainder of the process after initial signing
up been made.

1.8. Limitation of the Project

The new system does not include mobile phone applications which run on android or IOS platform but
since the new system is developed in PHP and provide a web based service, customers can access their
account information through the web site using built in or third party browsers installed in their smart
phones. In addition, users must be familiar with basic computer skills or smart phone use to access the
system (website).

1.9. Tools and Methodologies

1.8.1. Data collection Methods

Data collection mechanism helps as a dawn way to the future system and to find a clear help
mechanism for developing the project accordingly. For the successful completion of this project, data
gathering and analysis techniques are put into use. The data collected focuses on issues like, what is

5
 CREDIT AND SAVING MANAGEMENT SYSTEM

expected from the system? What are the inputs of the system? What are the outputs of the system?
What are the rules of processing the input data? How are they processed? Who requires which data in
what form? etc. We used the following Traditional Requirement Methods. Which are:

1.8.1.1. Document analysis

Studying the documents that are used in the past; It enables us to get more information in order to
understand about problems with the existing system, organizational directions, rules for processing
data, etc.
1.8.1.2. Interview
Interviewing the employees and customers to have reliable and clarified information from users,
managers, workers of the institution. It is used to assure the information which is observed from
documents, forms and reports, etc.
1.8.1.3. Observation
It is used to analyze the conditions to which the existing system is acting. It is useful to observe how
jobs are done, how information flows directly to the users.

1.8.2. System Design Methods

For the system analysis and design steps, we use Object oriented software development methodology,
which uses Unified modeling language (UML). Because of the following features

 Faster Development: OOD has long been touted as leading to faster development. Many of the
claims of potentially reduced development time are correct in principle, if a bit overstated (Object-
Oriented Development, 1997).
 Reuse of Previous work: This is the benefit cited most commonly in literature, particularly in
business periodicals. OOD produces software modules that can be plugged into one another, which
allows creation of new programs. However, such reuse does not come easily. It takes planning and
investment (Object-Oriented Development, 1997).
 Increased Quality: Increases in quality are largely a by-product of this program reuse.
Client/Server Applications: By their very nature, client/server applications involve transmission of
messages back and forth over a network, and the object-message paradigm of OOD meshes well
with the physical and conceptual architecture of client/server applications (Object-Oriented
Development, 1997).
6
 CREDIT AND SAVING MANAGEMENT SYSTEM

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

8.1.3. System Development Tools

8.1.3.1. Scripting Languages

 Java Script: - Client side scripting language to add various Web functionalities, Web form
validations, browser detections, creation of cookies and so on.
 PHP: - Server side scripting language for developing dynamic and interactive web applications.
 HTML: - hypertext markup language to make the web pages more effective as well as efficient.

8.1.3.2. Web Development tool

 CSS: - Cascading style sheets are used to format the layout of Web pages.
 Notepad++: - an application for writing code.

8.1.3.3. Database management software

 MYSQL: - to create and design the database which is used to store the information.
 Xampp server: - for designing and managing the database.

8.1.3.4. Documentation tool

 Microsoft word 2016: - for documenting the corresponding deliverables associated with the
project.
 Microsoft power point 2016: - used to present the documentation project.
 Foxit: - used for reading and editing PDF books.

8.1.3.5. Modeling software

 Microsoft project: - for developing Gantt chart.

 Visio 2016 – a case tool that used to model the new system.

7
 CREDIT AND SAVING MANAGEMENT SYSTEM

1.10. Deliverables of the Project

The system is a web based system that uses internet web technologies to provide information and
services, or other information’s to clients through the internet. It is a web based system whose main
purpose is to publish and maintain data for the customers by using hypertext-based principles.

No Deliverable Deliverable Description

1 Project Proposal Well organized small description of the Main document.
2 Project Management Plan A document designed to guide the control and execution
of the project.
3 Requirement Document User expectation for the website.

4 System Design Specification Overall design of the system architecture.

5 Web Based System Complete Web based system with database that can hold
all the information.
Table 1. 1 Project Deliverables

1.11. Beneficiaries of the project

As mentioned in different sections of this chapter, the new developing system bring significant change
to the users who are participated in the system directly or indirectly. The system brings new additional
efficiency which is capable of performing different tasks quickly and easily with user friendly
environment.

As a result of changing the existing system into computerized system, the customers will be benefited
from time efficiency and data accuracy. Individuals who reside in Addis Ababa and are participating
(or wish to participate) in small and micro finance activities will be benefited. Therefore, beneficiaries
or stakeholders of the new system are:

The Institution (ADCSI)

 The institution will be benefited from using modern system/technologies.

 The institution will gain strategies on control of transactions i.e. easy evaluation and
feedback mechanize.

 The institution will trace customer’s credit status on time, accurately and updated
information (report) regularly.

8
 CREDIT AND SAVING MANAGEMENT SYSTEM

 The institution will solve its problem such as disorganized work flow, redundancy of
data, time taking manual processes and the like.

 The institution will get competitive advantage over its competitor as strong control
operation established.

 The institution will attract more customers.

Employees

 The new system will increase employee’s performance and satisfaction by reducing
work burden.

 The employee can store, filter, and retrieve data’s easily.

 Easy, fast and simple access to the system.
 Reduce occurrence of errors.
Customers

 The customer can easily access information anywhere 24 hours a day and seven days a
week with internet access.

 The system will save time in which the customer could spend it for he’s/her own
business and energy.
 Unnecessary processes will be reduced.
 Accurate and Up-to-date information.

The Project Team

 The project team is benefited from having experience on preparing project

documentation and developing web based systems.

Students

 This project can be used as reference for junior students.

9
 CREDIT AND SAVING MANAGEMENT SYSTEM

1.11. Schedule

Figure 1. 1 Project schedule

10
 CREDIT AND SAVING MANAGEMENT SYSTEM

CHAPTER TWO

PROJECT MANAGEMENT
2.1. Introduction

Project Management is the umbrella under which all the project activities are managed. Although
project activities can be grouped by common objectives (phases), the individual activities that fall
under the Project Management umbrella are unique to each application. The unique nature of these
activities stems from different factors that can affect the success of a project. The experience of team
members, time constraints, budgets, resource availability, maturity of technology, and level of
planning are just a few of these factors, furthermore, the methodologies, techniques and models that
were effective today may not be effective tomorrow (Horine, 2009).

Software Project Management is the collection of techniques used to develop and deliver various
types of software products. This developing discipline includes technical issues such as:

 The choice of software development methodology?

 How to estimate project size and schedule?
 Which programming development environment to use?
 What are the risks to the project success? and
 How to keep the project on schedule.

These choices are then embodied in a software project management plan. Software project
management address both the process of software development and the desired functional
characteristics of the final software development and the desired functional characteristics of the final
software product. A complete software project management plan is the design, implementation,
control and test strategy for a software development process (Horine, 2009).

Effective project management is a vital ingredient in achieving a successful outcome. The objectives
for the project need to be agreed at the outset. In deciding the objectives their implications need to be
considered, in terms of the actual outputs and the impact of these outputs.

11
 CREDIT AND SAVING MANAGEMENT SYSTEM

2.2.Project Planning
2.2.1. Work Breakdown Structure (WBS)
A project work breakdown structure (WBS) is a deliverable or grouping of project work elements
shown in graphical display to organize and subdivide the total work scope of a project.
The WBS is a particularly important project tool. Considerable thought and planning should be given
to its development and implementation so that subsequent changes are minimized. Major revisions to
a WBS require both substantial effort and resources, due to its application to a wide array of project
activities. Project WBSs, which are driven by the scope of a project.

Task code Task Duration (Days) Responsibility

1. Credit and Saving System 54

1.1. Initiation and Planning
1.1.1. Determine project team 1
1.1.2. Develop project proposal 10 MA, RT, YA, ZG
1.1.3. Divide the project in to manageable tasks WBS) 3 MA, RT
1.1.4. Develop project schedule 3 MA, RT
1.1.5. Deliverable: Submit Project Proposal 1
1.1.6. Hold review meeting 1 MA, RT, YA, ZG
1.2. Requirement Analysis
1.2.1. Design interview questions 2 MA, RT, YA, ZG
1.2.2. Conduct interviews 5 MA, YA
1.2.3. Perform an onsite observation 5 RT, ZG
1.2.4. Perform document analysis 3 YA, ZG
1.2.5. Structure gathered requirements 3 MA, RT
1.2.6. Define user requirements 3 MA, RT, YA, ZG
1.2.7. Verify & Approve user requirements 1 MA, RT, YA, ZG
1.2.8. Identify functional and non-functional requirements 2 MA, RT, YA, ZG
1.2.9. Prepare essential use case model 7 RT, YA
1.2.10. Prepare essential user interface prototype 4 MA, RT, YA, ZG
1.2.11. Prepare user interface flow diagram 2 RT, ZG
1.2.12. Prepare class responsibility collaborator (CRC) cards 4 MA, ZG
1.2.13. Identify business rules and change cases 3 RT, YA, MA
1.2.14. System requirement analysis document(SRAD) 2 YA, RT, MA
1.2.15. Deliverable: Submit SRAD 1
1.2.16. Hold review meeting 1 MA, RT, YA, ZG
1.3. Design

12
 CREDIT AND SAVING MANAGEMENT SYSTEM

1.3.1. Initiate design activities 1 MA, RT, YA, ZG

1.3.2. Prepare system use case model 5 RT, YA
1.3.3. Design database 3 YA, MA
1.3.4. Design Graphic User Interface (GUI) prototypes 4 MA, YA
1.3.5. Hold review meeting 1 MA, RT, YA, ZG
1.4. Presentation
1.4.1. Finalize the document 2 MA, RT, YA, ZG
1.4.2. Deliverable: Summit the document 1
1.4.3. Present the document MA, RT, YA, ZG

MA: Mohammedyasin Abdulaziz YA: Yonas Abraham RT: Rediet Tekola ZG: Zelalem Gebru

Table 2. 1 Work Breakdown Structure

2.3.Resource Planning

Resource plan is a plan that involves identifying and allocating the resources that a proposed project
needs to succeed. Summarizes the level of resources needed to complete a project. A properly
documented Resource Plan will specify the exact quantities of labor, equipment and materials needed
to complete the proposed project (Horine, 2009).

2.3.1. Material Resource Planning

Item Quantity Specification Justification
Laptops 4 Ram > 4Gb HDD > 500Gb Working away from the office or at a
CPU > 2.00Ghz different desk is a lot more convenient
to using a laptop than a desktop.
Flash Disks 4 SanDisk 8 Gb To store data and backup of the
project.
DVD-RW 2 DVD-RW To store data and backup of the project
Internet - Internet kiosk and Wi-Fi To collect information
Stationary - Notebooks, Pens, Used for writing, typing and printing.
Papers, Laminator,
pencil, printer.
Table 2. 2 Material Resource Planning

2.3.2. Human resource planning

Human Resources are the peoples who make up the workforce of an organization, business sector, or
economy. "Human capital" is sometimes used synonymously with "human resources",

13
 CREDIT AND SAVING MANAGEMENT SYSTEM

although human capital typically refers to a narrower view (i.e., the knowledge the individuals
embody and economic growth).
Human Resource Head Qualification Responsibilities
Type Count
Project Manager 1 Under graduate The role of the project manager
in computer encompasses: Planning Activity and
science Defining Scope and Sequencing.
Supervising staff.
Requirement 1 Under graduate Interviews future users of a system to
Analyst in computer understand what the desired software
science must do.
Programmer 1 Under graduate Write programs in a variety of computer
in computer languages, Update and expand existing
science programs. Debug programs by testing for
and fixing errors.
Test supervisor 1 Under graduate Test the Quality of the program and look
in computer for bugs, errors and report them to be
science fixed.

Table 2. 3 Human resource planning

2.3.3. Software Resource

No Name Description

1 Operating system Microsoft window 7,10

2 Website Design tool PHP, CSS, HTML, NOTEPAD ++

3 Web browser Google chrome, Mozilla
4 Data Base management system MYSQL, Xampp server
5 Document processing Microsoft office word, Power point, Microsoft
project. (v.2016), Visio

Table 2. 4 Software Resource

2.4. Financial Plan

A financial plan is a comprehensive evaluation of an investor's current and future financial state by
using currently known variables to predict future cash flows, asset values and withdrawal plans.

14
 CREDIT AND SAVING MANAGEMENT SYSTEM

2.4.1. Human Resource Plan

Role Number of people Salary (birr) Total Salary (birr)

Project Manager 1 - -
Requirement 1 - -
Analyst
Programmer 1 - -

Test supervisor 1 - -
Total cost 00.00

Table 2. 5 Human Resource Financial Plan

2.4.2. Material Resource Plan

Item Quantity Unit Price(Birr) Total Price(Birr)

Laptop 4 Pre-owned Pre-owned

Stationary Set Unknown 1,200.00

Flash disk 4 200.00 800.00

DVD-RW 2 25.00 50.00

Internet Service - 0.25 500.00

Total Price 2,550.00

Table 2. 6 Material Resource Financial Plan

2.4.3. Software Resource

Item Quantity Unit Price (Birr) Total Price (Birr)

Microsoft Office 1 150.00 150.00
Anti-virus 1 50.00 100.00

Total Price 250.00

Table 2. 7 Software Resource Financial Plan

15
 CREDIT AND SAVING MANAGEMENT SYSTEM

2.4.4. Contingency cost

Item Price (Birr)

Material Resource Plan 2,550.00

Software Resource plan 250.00

Total price 2,800.00

Table 2. 8 Contingency cost

 The Contingency cost for the project is: (15% * 2,800.00) = 420.00 Birr
 The total cost for the project is: (2,800.00 + 420.00) = 3,220.00 Birr

2.5.Process Model

Software development life cycle (SDLC) is important for the software project success; a good
software engineer must have enough experience and knowledge to select one model from the other
based on the project content. Therefore, we might be required to choose the right SDLC model
according to the specific concerns and requirements of the project (Ambler, 2001).

Figure 2. 1 Process Model

There are various software development life cycle models defined and designed which are followed
during software development process. These models are also referred as "Software Development
Process Models". Each process model follows a Series of steps unique to its type, in order to ensure
success in process of software development. The following are the most important and popular SDLC

16
 CREDIT AND SAVING MANAGEMENT SYSTEM

models followed in the industry, namely: Waterfall Model, Iterative Model, Spiral Model-Model, and
Big Bang Model. We, the developers of Addis credit and saving system, have chosen to use Waterfall
Model hoping to be best fit to our needs of producing the final product (Ambler, 2001).

2.5.1. Waterfall Model

The waterfall Model is a linear sequential flow. In which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of software implementation. This means that any
phase in the development process begins only if the previous phase is complete. The waterfall
approach does not define the process to go back to the previous phase to handle changes in
requirement. The waterfall approach is the earliest approach and most widely known that was used
for software development (Ambler, 2001).

Figure 2. 2 Waterfall Model

Waterfall approach is the first SDLC Model to be used widely in Software Engineering to ensure
success of the project. In "The Waterfall" approach, the whole process of software development is
divided into separate phases. In Waterfall model, typically, the outcome of one phase acts as the input
for the next phase sequentially.
Advantages
 It is very simple to understand and use.
 Easy to explain to the users.
 Stages and activities are well defined.

17
 CREDIT AND SAVING MANAGEMENT SYSTEM

 Helps to plan and schedule the project.

 Verification at each stage ensures early detection of errors/misunderstanding.
 Each phase has specific deliverables.

2.6.Team Organization

The project team selects the controlled decentralized controlled (dc) type of team organization.
The reason for selecting this type is

 Implementation of the problem is made through the assigned team members.

 Communication among team member and individual is horizontal. This enables team members
to have good understanding of what is done, by whom, when and share the experience with
each other.
 Problem solving and decision making will be made at all the team level members.

According to the team organization the following are responsibility of the team member:

No. Activity Responsibility

1 Study the problem YA, MA, RT, ZG
2 Requirement analysis YA, MA, RT, ZG
3 Design YA, MA, RT, ZG
4 Implementation YA, MA, RT, ZG
5 Documentation YA, RT, MA, ZG

Table 2. 9 Team Organizing

MA: Mohammedyasin Abdulaziz YA: Yonas Abraham RT: Rediet Tekola ZG: Zelalem Gebru

2.7.Risk Mitigation and Management

Risk management is the process of identifying, addressing and eliminating potential problems before
they can damage the project. A risk is a potential problem to all system development projects. It
might happen, or it might not. But regardless of the outcome, the strategy for risk management is to
be proactive. A proactive strategy begins before technical work is initiated. Potential risks are
identified and their probability and impact are assessed (Horine, 2009).
- Impact is the effect it will have if the risk occurs.
- Probability is the frequency of occurrence of a given risk

18
 CREDIT AND SAVING MANAGEMENT SYSTEM

The team identifies some risks by discussing on the following generic risk drives.

Project risks: - Threatens the project plan.

Project risk identifies potential budgetary, schedule, personnel, resource, customer and requirement
problem.
Technical risks: - Threatens the quality and timelines of the software.
Technical risk identifies potential design, implementation, and interface and verification problem.
simply the risk associated directly with the knowledge base being employed and its technical aspects
including such things as understanding, reproducibility and the like (Horine, 2009).
Schedule Risk: - is the risk that the project takes longer than scheduled. It can lead to cost risks, as
longer projects always cost more, and to performance risk, if the project is completed too late to
perform its intended tasks fully (Horine, 2009).

Budget Risk: - is the potential for the estimates or assumptions built into a budget to turn out to be
inaccurate.
Operational Risks: - is the prospect of loss resulting from inadequate or failed procedures, systems
or policies. Employee errors, systems failures, fraud or other criminal activities any event that
disrupts business processes.
Based on the above generic risk discussion and results the team identifies the specific risk in the
following table.

Risk Name: Computer Crash Description: The computer has crashed due to virus and
power failure
Mitigation Plan Monitoring plan
Taking steps to make multiple backup When working on the product or documentation, the staff
copies of the software in development member should always be aware of the stability of the
and all documentation associated with it, computing environment they’re working in. Any Changes
in multiple locations. Install an up to date in the stability of the environment should be recognized
antivirus, use power stabilizer and taken seriously.
Risk Management plan
Repair, update the computer. In the event that the computing environment is found unstable, the
development team should work on that system until the Environment is made stable again, or should
move to a system that is stable and continue working there.
Current Status: Has not occurred yet Assigned Team member: Mohammedyasin Abdulaziz

Table 2. 10 Risk-Computer Crash

19
 CREDIT AND SAVING MANAGEMENT SYSTEM

Risk Name: Late Delivery Description: Falling behind schedule would indicate
a potential for late delivery.
Mitigation Plan Monitoring plan
Steps have been taken to ensure a timely A schedule has been established to monitor project
delivery by gauging the scope of project based status. The schedule will be followed closely during
on the Delivery deadline. all development stages.
Risk Management plan
The only course of action available would be to request an extension to the deadline form the
customer.
Current Status: Has not occurred yet. Assigned Team member: Yonas Abraham
Table 2. 11 Risk-Late Delivery

Risk Name: Technology Does Not Meet Specifications Description: specifications differs from
those of the customer needs
Mitigation Plan Monitoring plan
In order to prevent this from happening, meetings (formal The meetings with the customer should
and informal) will be held with the customer on a routine ensure that the customer and our
business. This insures that the product we are producing organization understand each other and
and the specifications of the customer are equivalent. the requirements for the product.
Risk Management plan
Should the development team come to the realization that their idea of the product specifications differs from
those of the customer, the customer should be immediately notified and the steps necessary to rectify this
problem should be done. Preferably a meeting should be held between the development team and the
customer.
Current Status: Has not occurred yet. Assigned Team member: Rediet Tekola
Table 2. 12 Risk-Incompatibility

Risk Name: End Users Resist System Description: End-user’s resistance to information
technology (IT) is a common occurrence when new
information systems are implemented and can greatly
contribute to failure of newly implemented systems.

Mitigation Plan Monitoring plan

In order to prevent this from happening, the The software will be developed with the end user in mind.
software will be developed with the end user in The development team will ask the opinion of various
mind. The user-interface will be designed in a way outside sources throughout the development
to make use of the program convenient and Phases. Specifically, the user-interface developer will be
pleasurable. sure to get a thorough opinion from others.
Risk Management plan
Should the program be resisted by the end user, the program will be thoroughly examined to find the reasons
that this is so. Specifically, the user interface will be investigated and if necessary, revamped into a solution.
Current Status: Has not occurred yet. Assigned Team member: Zelalem Gebru

Table 2. 13 Risk-End User Resistant

20
 CREDIT AND SAVING MANAGEMENT SYSTEM

Risk Name: Changes in requirements Description: in requirements’ gathering

phase customer changes requirements
Mitigation Plan Monitoring plan

In order to prevent this problem, meetings (formal and The meetings with the customer should
informal) will be held with the customer on a routine ensure that the customer and our
business. This insures that the product we are organization understand each other and the
producing, and the requirements of the customer are requirements.
equivalent.

Risk Management plan

Preferably a meeting should be held between the development team and the customer to discuss at
length this issue.

Current Status: Has not occurred yet. Assigned Team member: Yonas Abraham
and Mohammedyasin Abdulaziz

Table 2. 14 Risk- Change in requirement

Risk Name: Lack of Development Experience Description: Failure to communicate clearly

Mitigation Plan Monitoring plan

The development team will be required to learn the Each member of the team should watch
languages and techniques necessary to develop this areas where another team member may be
software. The member of the team that is the most weak. if one of the members is weak in a
particular area it should be brought to the
experienced in a particular facet of the development tools
attention by that member, to the other
will need to instruct those who are not as well versed. members
Risk Management plan

The members who have the most experience in a particular area will be required to help those who don’t
out should it come to the attention of the team that a particular member needs help.

Current Status: Has not occurred yet. Assigned Team member: All team members

Table 2. 15 Risk-Lack of Experience

21
 CREDIT AND SAVING MANAGEMENT SYSTEM

Risk Name: Database is not Stable Description: Most databases have

scholarly/peer-reviewed filter or contain
only scholarly literature. Authority and
trustworthiness are virtually guaranteed
Mitigation Plan Monitoring plan

Developers who are in contact with the database, Each user should be sure that the database
and/or use functions that interact with the is left in the condition it was before it was
database, should keep in mind the possible errors touched, to identify problems. The first
that could be caused due to poor notice of database errors should be brought
programming/error checking to the attention of the other team
members.
Risk Management plan

Should this occur, the developer team would call a meeting and discuss the causes of the database
instability, along with possible solutions.

Current Status: Has not occurred yet. Assigned Team member: Rediet Tekola

Table 2. 16 Risk-Database stability

Risk Name: Poor Quality Documentation Description: Good documentation is both

technically complex and simple to read and
understand: it both has good logical at all
levels of organization and works well for
reader who won’t read more than a few
paragraphs.
Mitigation Plan Monitoring plan
members who are in charge of Developing the Throughout development or normal in and
documentation will keep in contact with each out of house testing, the development team
developer on the team. Meetings will be held and or beta testers will need to keep their
routinely to offer documentation suggestions and eyes open for any possible documentation
topics. topics that have not been included.
Risk Management plan
Should this occur, the project team would call a meeting and discuss the addition of new topics, or
removal of unnecessary topics into the documentation.

Current Status: Has not occurred yet. Assigned Team member: All team members

Table 2. 17 Risk-Poor Quality Documentation

22
 CREDIT AND SAVING MANAGEMENT SYSTEM

Risk Name: Poor Comments in Code Description: peppering your code with lots
of comments is good

Mitigation Plan Monitoring plan

Poor code commenting can be minimized if Reviews of code, with special attention
commenting standards are better expressed. While given to comments will determine if they
standards have been discussed informally, no are up to standard. This must be done
formal standard yet exists. A formal written frequently enough to control comment
standard must be established to ensure quality of quality. If they are not done comment
comments in all code. quality could drop, resulting in code that is
difficult to maintain and update.
Risk Management plan
Should code comment quality begin to drop, time must be made available to bring comments up
to standard. Careful monitoring will minimize the impact of poor commenting. Any problems are
resolved by adding and refining comments as necessary.

Current Status: Has not occurred yet. Assigned Team member: Rediet Tekola

Table 2. 18 Risk-Poor comments in code

23
 CREDIT AND SAVING MANAGEMENT SYSTEM

CHAPTER THREE

REQUIREMENT ANALYSIS
3.1. Introduction

Requirement analysis contains activities conducted to determine the needs or conditions for a new or
altered system and it describes in business terms what must be delivered or accomplished to provide
value. A requirement can be a description of what a system must do, referred to as a functional
requirement. This type of requirement specifies something that the delivered system must be able to
do. Another type of requirement specifies something about the system itself and how well it performs
its functions. Such requirements are often called Non-functional requirements or performance
requirements or quality of services (O.Grady, 1993).

In this phase we try to answer the question “what do the user need and want from the new system?” It
is concerned with the users’ perspective and tries to evaluate whether or not the new system will full
fill the organization system and requirements. Regardless of how impressive or complex the
technological solution might be we need the information system building block for documenting the
information system’s requirements (O.Grady, 1993).

3.2. Overview of Existing system

In this section the team describes the existing system of ADCSI Micro-Finance Share Company.
The team uses techniques such as interview, observation and document analysis to collect the
necessary information about the institution and existing system. The team found out how the
company gives service to the clients, what are the major functions of the system, also the players
of the existing system and finally what are the problems of the existing system from the point of
the clients and the company.

The main objective of this part is to study the management system for ADCSI in detail and identify
the problem as well which is appropriate to design a new system for ADCSI. Generally, the main
issues of this chapter concern’s on describing the major functions of the existing system (with Inputs,
Processes and Outputs) problems of the existing system, and essential modeling.

24
 CREDIT AND SAVING MANAGEMENT SYSTEM

Initially the customer is expected to appear physically at the ADCSI to get the desired service. Since
the ADCSI reaches an agreement with the individual or organization, then there exists a relationship
between the two parties.

Once the relationship occurs, the customer is expected to contact the manager. The manager has to
speak to the new customer and ask for the kind of service he/she want. If the service is saving the
customer is expected to contact the officer. If the desired service is loan, the customer is expected to
contact the manager.

3.2.1. Players in Existing System

1.Customer: This is an actor that should be registered and view every transaction applied to
his/her account.
2.Manager: This is an actor for the existing system who is responsible to manage resources, view
report, register employee, etc.
3.Officer: This is an actor for the existing system who is responsible to register customer, create
accounts and perform transactions.
4.Record keeper: This actor is responsible to manage all files produced by ADCSI.
5.Accountant: This actor is responsible for Calculating Interest, recording financial statements and
generating financial reports.

3.2.2. Major Activities in the Existing System

We describe the major functions performed in the ADCSI with Input, Process and Output as follows:
3.2.1.1. Opening Saving Account

In Opening Saving Account once the customer fulfills the required requirements he/she fills out the
appropriate Saving Account Opening Form. Then the customer is required to place his/her signature
on white paper. After having all the above information required on the customer, he/she is going to be
registered on the system by office, then the officer checks whether the document is filled properly.
Finally, the customer gets account book. Then customer will have a new account and receives the
Pass Book and become officially customer of ADCSI. The Pass Book includes customer name,
nationality, full address, photograph, occupation, saving account number, signature of the institute
officials etc.

25
 CREDIT AND SAVING MANAGEMENT SYSTEM

Input

Customers need to have renewed ID card for individuals.

Two passport size photographs.
Deposit voucher form with the minimum of Five birr as initial deposit.
Appropriately filled Saving Account Opening Form.
Four signatures each on different Account Opening Forms.

Process

The customer fills opening saving account.

The officer verifies the filled information on Saving Account Opening Form, the ID Card/ the
license and verify appropriateness of signature on the specimen signature card.
The Supervisor checks the validity of the overall process.
The Casher receives the initial deposit.
At the last, Supervisor registers the Customer in the Register Book.

Output

 Customer has an Account.

 Customer gets book account.
 Become official Customer of the ADCSI

3.2.1.2. Loan Service

In Loan, if the borrower fulfills the ADCSI requirement depending on the type of loan and if the loan
officer approves the document, then the officer validates the inputs and print new loan coupon which
includes new loan number, name and other fields.

If the borrower wants to pay the money, the customer follows the required manual process and the
office teller update the customer loan profile.

Input
 Salaried or business man borrower (Customer). This enables the ADCSI to determine the
borrowing capacity of the borrower.

26
 CREDIT AND SAVING MANAGEMENT SYSTEM

 The borrower (customer) with guarantee means a fixed asset to ensure the ADCSI that
borrower will return the borrowed money) Which contains full information about the
Customer.
 Singed loan agreement format (the format implies the changes of the interest; the
change is made by ADCSI based on the current country economy, business activity and
fluctuation money).

Process
 Customer requests for loan.
Loan officer receives all the required documents.
Loan officer checks the appropriateness of the documents.
The Loan officer determines the borrowing capacity of the Customer by business rule ADCSI.
The Manager confirms the document and sign (initiate) on the form.
The customer registered.

Output
The Customer gets the requested money from the teller.
The Customer gets the Loan Coupon sheet.

3.2.1.3. Deposit Money

While in Depositing money, once the customer fills the Deposit voucher form with specified amount
of money to be deposited in his/her account, then the customer is required to give passbook and
money with attached voucher to the officer. The officer checks whether the deposit voucher is filled
properly then the officer receives the money and update the customer balance on the passbook.
Finally, the customer gets a copy of deposit voucher with a stamp and officer signature on it.

Input
 Customers need to have passbook.
 Filled deposit voucher with the specified amount of money.
 Money to be deposited.

Process
 The customer fills deposit voucher.

27
 CREDIT AND SAVING MANAGEMENT SYSTEM

 The officer checks the filled information on the deposit voucher matching with the passbook
and count the money to be deposited.
 The Casher receives the deposit.
 At last, the officer updates the customer balance.

Output
 Customer receive copy deposit voucher.
 Customer gets back the passbook with updated balance.

3.2.1.4. Cash Withdrawal

To withdraw cash, the customer required to fill the withdrawal voucher form with specified amount
of money to be withdrawn from his/her account, then the customer gives passbook with attached
withdrawal voucher to the officer. The officer matches the customer identity (photo and signature)
and verifies the withdraw voucher is filled properly. The officer checks if there is enough balance in
the specified account and then gives the requested amount to the customer and update the customer
balance on the passbook.

Input
 Customers need to have passbook.
 Filled withdrawal voucher with the specified amount of money.

Process
 The customer fills withdrawal voucher.
 The officer checks the filled information on the withdrawal voucher matching with the
passbook and identity of the customer.
 The Casher gives the money to the customer.
 Finally, the officer updates the customer balance.

Output
 Customer receives the requested amount of money.
 Customer gets back the passbook with updated balance.

28
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.2.3. Preserved Activities from the Existing System

In the existing system, there are many practices and activities that help to perform the system.
All the activities are almost manual, done by human power. Even if we are going to change the
office system in to computerized, there are some activities preserved in the new system. Some of
these are:

 Any customer needs to visit the office, present the requirements and fill the forms based on
the kind of service he/she needs to be a customer of the institution.
 There are forms [vouchers] to be field to get the corresponding services like saving account
opening form, deposit voucher, and others.
 The institution customer has to have passbook or loan coupon.

3.2.4. Bottlenecks of the Existing System Using PIECES Framework

Performance Related Problem

 When the number of customer increases the response time of the system serving the customers will
decrease because the system performs its tasks manually.
 The productivity of the organization is not effective.
 The work procedure is prone to error.

Information Related Problem

Input

 Mishandling of customer information may be occurring.

 Data is difficult to correct and maintain.
 Redundant information is captured. Customer information is registered in various cards and forms
again and again for example on register book.
 Data is not easily accessible.
 The inputs are not validating (i.e. the system cannot check whether the customer has account
before).
 Data is not well organized.
 Data is not secure from accident or vandalism (damage).
 Information that is difficult to produce (manipulate).

29
 CREDIT AND SAVING MANAGEMENT SYSTEM

Output

 The report may encounter inaccuracy as needed.

 Generating report requires more skilled experience and greater attention.
 Data is not flexible – not easy to meet new information needs from stored data.
Efficiency Related Problem

 Since the work is performed manually the efficiency of the working system is not satisfying.
 As the amount of the customer increase the waiting time of the customer will increase.
 Since the data is stored in redundant manner, the information generated also is redundant.
 Effort required for tasks is excessive.
 Materials required for tasks are excessive.

Control Related Problem

 Information getting to unauthorized people.
 Data privacy regulations or guidelines are being (or can be) violated.
 Input data is not adequately edited.

Economics Related Problem

The departments need many employees and hence it forced to pay huge salary. Manual handling of
data is expansive as compared to automated system. Cost in terms of time is high. In addition to that
it needs more stationary materials due to data duplication, errors, and storage as number of customer
increase.

Service Related Problem

The customers do not get better service as they need, then they may shift to other good service
providers due to the following reasons.
 The system is not coordinated with other systems.
 The system is not compatible with other systems.
 The system is not easy to use and learn.

The project team has been depicted clearly the above problems facing in the existing system. As a
result, new system or solution to solve the above problem is proposed in the next section.

30
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.3. Proposed System

As we have seen in the manual system, the problems encountered in the existing system needs an
automated system that facilitate the transactions carried out in the institution. To computerize the
system is one of the major solutions we have to address the problems of the existing system. This
emphasizes on making and handling the loan and saving activities by using computers and making the
system centralized.

Since the computer is capable of performing and processing many and huge tasks faster, efficiently
and more correctly, it is preferred to apply it on the system. In general: When it is applied, the system
will have better utilization of resources, performance, security, reliability, accuracy and in general
better service grant. As a result, the project team has been listed the following Functional and Non-
functional requirements of the new system.

3.3.1. Functional Requirement

Functional requirement is a description of activities and services that a system must provide. The
project team aims to develop Credit and Saving Management System. These are the features that
system must perform to satisfy the business needs and to be acceptable by the user. After getting a
completion, the system must be able to perform the following.

 The system shall provide different levels of access according to the authority of the user.
 The system shall provide user authentication by asking for a user name and a password to
enforce authority levels.
 The system shall allow the officer to be able to create Loan and Saving account.
 The system shall update every customer’s information.
 A new user can be added to the system only by applying to the administrator.
 The system shall allow the customer to be able to view his/her transaction status.
 The system shall maintain customer information and display identification details of that
particular customer.
 The system shall register employees.
 The system shall generate a report.
 The system shall calculate Interest at the end of the month.
 The system shall be able to generate New account number.

31
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.3.2. Non Functional Requirement

Non-functional requirement describes invisible aspects of the system that are not directly related
to the system but deals with additional quality of the system. The following non-functional
requirements define the needs in terms of performance, design, availability, security, maintainability,
portability, efficiency, and reliability.
TR#.1 The system should be fast and respond quickly for the customers need.
TR#.2 The system should be easy to learn by both sophisticated and novice users.
TR#.3 The system should provide easy, navigable and user friendly interfaces.
TR#.4 The system should have a standard graphical user interface that allows for data entry, editing,
and deleting of data with much ease.
TR#.5 The system should be available 24 hours per day and 7 days per week.
TR#.6 The system security shall be managed by the administrator. Authorized persons on providing
a “user name” and a “password” can log-on. When a user logs on, the system authenticates
him, determines his level of authority, then affords privileged features.
TR#.7 The system should be easy to maintain.
TR#.8 Backups are to be taken regularly and reloading from backups will be done in case of
corruption.
TR#.9 The system should be compatible with different platforms.
TR#.10 The system consistently performs its intended function.
TR#.11 The system must ensure use of services being requested for the user and must respond to user
request as fast as possible.

3.4. Essential use case diagram

Use case Diagram depicts a collection of use cases, actors, their associations, a system boundary
box (optional), and packages (optional). A use case describes a sequence of actions that provide
a measurable value to an actor and is drawn as a horizontal ellipse. An actor is a person, organization,
or external system that plays a role in one or more interactions with your system (actors are drawn as
stick figures). Relationships between actors and classes are indicated in use case diagrams, a
relationship exists whenever an actor is involved with an interaction described by a use case (Horine,
2009).

32
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.6.1. Actor Identification of Existing System

In the use cases an actor interacts with the system to perform a piece of meaningful work that helps
them to achieve a goal and has access to define their overall role in the system and the scope of their
action.in our case: -
 Manager: -a person who is responsible to manage users and approve transactions.
 Officer: - a person who process and control customers request.
 Accountant: - a person who control financial activities of ADCSI.
 Customer: - a person who get service by the system.
 Record keeper: - a person who is responsible of managing data’s and files.
3.6.2. Use case Identification of Existing System

Each Use Case describes the functionality to be built in the new system, which can include another
Use Case's functionality or extend another Use Case with its own behavior. The most important and
basic use cases of this system are the following: -
 Add Loan
 Approve Transactions
 Create New Account
 Calculate Interest
 Deposit Money
 Manage Files
 Produce Report
 Review Report
 Request New Account
 Request Transactions
 Request Loan
 Withdrawal Money

33
 CREDIT AND SAVING MANAGEMENT SYSTEM

Review Report Creat New Account

Add Loan
<<extend>>
Manager <<include>>
Approve transactions
<<include>> Officer
<<include>>

Withdraw money

Calculate Interest
Deposit money

<<include>>
<<include>>
Produce Report
Accountant <<include>>

Request New Account

<<extend>>
Request Transaction

Manage Files

Record
keeper Customer
Request Loan

Figure 3. 1 Essential Use Case Modeling

3.5. Essential User Interface Prototype

An essential user interface prototype also known as an abstract prototype, is a low-fidelity model, or
prototype, of the UI for the new system. It represents the general ideas behind the UI, but not the
exact details. An essential user interface prototype is effectively the initial state-the beginning point-
of the user interface prototype for the new system. It models user interface requirements,
requirements that are evolved through analysis and design to result in the final user interface for your
system, enabling you to explore usability aspects of your system (Object-Oriented Development,
1997).

34
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 3. 2 Login User Interface Prototype

Figure 3. 3 New Customer Form user Interface Prototype

35
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 3. 4 Deposit user Interface prototype

Figure 3. 5 Withdrawal User Interface Prototype

36
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 3. 6 Transfer User Interface

Figure 3. 7 Balance User Interface

37
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 3. 8 Search user interface Prototype

Figure 3. 9 New user Interface Prototype

38
 CREDIT AND SAVING MANAGEMENT SYSTEM

3.6. User Interface flow diagram

User Interface flow diagram is used to model the interactions that users have with a system.
They enable to gain a high level of overview of the UI of the application being developed.

Figure 3. 10 User Interface Flow Diagram

3.7. Class Responsibility Collaboration (CRC Cards)

Using a small card keeps the complexity of the design at a minimum. It focuses designers on the
essentials of the class and prevents them from getting into its details and implementation at a time
when such detail is probably counter-productive. It also discourages giving the class too many
responsibilities. Because the cards are portable, they can easily be laid out on a table and re-arranged
while discussing a design (Ambler, 2001).

39
 CREDIT AND SAVING MANAGEMENT SYSTEM

Customer Officer
Name Officer Name Customer
Account No. Manager Id Manager
Date of birth Gender System Administer
Gender Address
Address Deposit Cash
Photo Withdraw Cash
Signature Transfer Cash
Contact number Process Loan
Deposit Request Request
Withdraw Request Request Approval
Loan Request Provide Information
Transfer Request Provide Forms

Manager System Administrator

Name Customer Name Manager
Id Office Id Officer
Address System Administer Address
Office no Admin system
Provide Provide user
Authorization Account

Table 3. 1 CRC Card

3.8. Business Rule

Business rule is a rule in which the organization uses it to perform any activities. Hence any activities
are expected to be valid with respect the rule. A rule often focuses on access control issue, may also
business calculation, policy of the organization (O.Grady, 1993). Therefore, the following are some
of the rules of the organization:
BR #1. An identification card which shows that the applicant is a resident of Addis Ababa.
BR #2. The applicant shouldn’t have any unsettled loan from any institution including ADCSI.
BR #3. Customer should have a fixed asset (collateral) to loan.
BR #4. Anyone can open a saving account in the institution starting from birr five and above.
BR #5. Maximum loan amount for a new client per individual is 5000 Birr.
BR #6. Minimum loan amount for a group not exceeding more five members is 20,000 Birr.
BR #7. The client is either expected to deposit 5 % of its loan or deducted from his/her loan.
BR #8. The interest rate for saving is 4.5% [not fixed].
BR #9. Customer has to pay a loan with specified time and amount.

40
 CREDIT AND SAVING MANAGEMENT SYSTEM

CHAPTER FOUR

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 (Object-Oriented
Development, 1997). This chapter focuses on transforming the analysis model into the design model
that takes into account the non-functional requirements and constraints described in the problem
statement and requirement analysis sections discussed earlier.

During system design the team concentrates on the process of data structures and software and
hardware components necessary to implement it.

4.2. Purpose of the System

The purpose of designing is to show the direction how the web page is built and to obtain clear
and enough information needed to drive the actual implementation of web page. It is based on
understanding of the model the web page built on system design also focuses on decomposing
the system in to manageable parts. Furthermore, it supports the non-functional requirements of
the system which helps to achieve the functional requirements.

Generally, the objectives of design are to model the system with high quality. The design goals
are derived from non-functional requirements that means non-functional requirement is the
description of the feature characteristics and attribute of the system as well as any constraints
that may limit the boundary of the proposed solution.

4.3. Design Goals

Design goals describe the qualities of the system that developers should optimize. Such goals are
normally derived from non-functional requirements of the system.

The design goal can be generally grouped into five categories. These are: Performance Criteria,
Security Criteria, Cost Criteria, Maintenance Criteria and End User Criteria.

41
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.3.1. Performance Criteria

The system should have a high response time with a maximum throughput. In Addition, the system
should not be taking up too much space in memory. It should perform loan and saving operations in
faster response time and hence the system should be more interactive.

4.3.2. Security Criteria

The system should be robust i.e. it should be able to survive invalid user inputs, fault tolerant, reliable
and available. Furthermore, as the system is handling a sensitive data, high emphasis should be given
with regard to security.

4.3.3. Cost Criteria

The System should be developed with a minimum cost possible. The cost required developing the
system in regard to development cost and maintenance cost to minimize bugs which may appear at
later stage.

4.3.4. Maintenance Criteria

The system should be easily extensible to add new functionality at a later stage. It should be easily
modifiable to make change to features and functionality. The code for the system should be easily
readable, understandable and should easily be mapped to specific requirement.

4.3.5. End user Criteria

The end user criteria are specified in terms of usability of the system. The extent in which the system
will be used by users to achieve a certain goal with efficiency and effectiveness in a specified context
of use. The System should have a simple and understandable GUI (graphical user Interface). It should
include forms, buttons and icons with descriptive names for users to interact easily with the system. It
should give reliable response for the users.

4.4. Design Trade off

Design tradeoff is inevitably in achieving a particular design goal. There should be a balance act to
resolve conflicting requirements. These balancing acts sacrifices one aspect of the software to
strengthen another. These is what is referred as trade off.

42
 CREDIT AND SAVING MANAGEMENT SYSTEM

Security against Usability: Checking the user ID and password before logging into the system is
essential to proceed with other activates. Security checkup takes high response time. Since there are
different users, the system should provide efficient and effective usability with few errors.

Capacity against Performance: The wider the system is in terms of data storage, the lesser the
performance will be in relation to response time. Therefore, the system is intended to provide high
performance with a database capacity.

Development Cost against Functionality: as the team has described in Requirement Analysis and
Proposal, the new system delivers a number of services and functions to its users. To design these
services and functionalities, cost of analysis time, trade-off management time, time for determining
the better way of solving the problem, time for learning and adapting to standard rules and guidelines
are expensed.

4.5. System Use Case Modeling

A use case is a sequence of actions that an actor (usually a person, but perhaps an external entity,
such as another system) performs within a system to achieve a particular goal. Use Case Diagram
depicts the system behavior. The diagram presents a high level view of how the system is used as
viewed from outsider perspective (O.Grady, 1993).

4.5.1. Use case Identification

Each Use Case describes the functionality to be built in the new system, which can include another
Use Case's functionality or extend another Use Case with its own behavior. The most important and
basic use cases of this system are the following: -

 Login
 Deposit Money
 Withdrawal Money
 Transfer Money
 Get report
 Add Loan
 Registering Employee
 Register Customer

43
 CREDIT AND SAVING MANAGEMENT SYSTEM

 Create User Account

 Change password
 View Transaction
 Logout

4.5.2. System Use Case Diagram

Add Customers
Add loan

<<extend>>
<<extend>>
Aprove transaction
Manager <<include>> <<include>>
Create account
<<include>>
View Report
<<include>>
<<include>>
Login <<include>> Deposit money
<<include>> Officer
<<include>>
Add Staff Members <<include>> Withdraw money
<<include>>

Delete staff <<include>>

Members Transfer money
System
administrator

Veiw transaction

Customer

Figure 4. 1 System Use Case Diagram

44
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.5.3. Use case Description

Use Case ID UC1

Use Case Name Login
Participating Users
Actor(s)
Description The “login” use case enables users to login to the system.
Trigger When users want to access the system.
Priority High
Precondition Users Should have Valid User Account
User Action System Response
1. Users clicks login link on home page. 2. The System display login form.
3. Enters username and password, clicks on 4. The System checks the entered value.
“Login” button. 5. If user name and password correct, the
Basic Course of system displays appropriate page.
Action (A5: If user name and password
incorrect).
Alternative course A5: If user name and password incorrect: 6. The use case ends.
of action 1. The System Displays “Wrong Username or Password “message.
2. The use case resumes to step3.
Post Condition Users logged to the system and appropriate page is displayed.
Table 4. 1 Use Case Description for Login

Use Case ID UC 2
Use case Name Create account
Participating Officer
Actor(s)
Description The “Create Account” use case allows the officer to create account for customers.
Trigger When Customers want to have account.
Priority High
Precondition The Officer logs in to the system and the applicant should fulfill all the requirements needed
to create account.
User Action System Response
1. Officer clicks Create Account. 2. The system displays the create account
3. The Officer fills all required information. form.
Basic Course of 4. The counter Officer clicks “Create saving 5. The System checks that all the
Action Account” or” Create Loan Account” button. required information is entered.
7. The officer Confirms “Success message”. 6. The system displays “Successful
8. The Use case ends. message”. (A6: If invalid data entered).
Alternative course A6: If invalid data entered:
of action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition Applicants will have either saving account or loan account of the system.
Table 4. 2 Use Case Description for Create Account

45
 CREDIT AND SAVING MANAGEMENT SYSTEM

Use Case ID UC3

Use Case Name Approve Transaction
Participating Actor(s) Manager
Description The “Approve Transaction” use case enables the manager to check & confirm transaction.
Trigger When there is ongoing transaction carried out by officers.
Priority Medium
Precondition The Manager logged to the system.
Basic Course Actor action System responses
of Action 1. Manager receives approval request. 2. System display ongoing transaction.
3. Manager re the requested transaction. 5. The system displays “Approved
4. The manager clicks the “Approved button”. message”.
6. The use case ends. (A5: If transaction is invalid).
Alternative course of A5: If transaction is invalid:
Action 1. The system displays “transaction rejected message”.
2. The use case resumes to step 3.
Post Condition New loan Type will be created to the system.

Table 4. 3 Use Case Description for Approve Transaction

Use Case ID UC 4
Use Name Add Loan
Participating Actor(s) Officer
Description The “Add Loan” use case enables the Officer to give load to Customer.
Trigger When new customers who want loan arrive.
Priority High
Precondition Customers must have a coupon/account number.
Actor Action System Responses
1. The Officer clicks “Add Loan” link. 2. The system display “Add Loan” form.
3. The Officer filled the form and 4. The System Verify the presence
clicks on “Add Loan” button. of the Account Number. (A4: If invalid
5. The Officer updates the Account account number).
and gives the money to the customer. 6. The system displays successful
Basic Course of Action
7. Officer confirms success “message”. message.
8. The use case ends.
Alternative course of A4: If invalid Account Number:
Action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition Customer will receive loan money.

Table 4. 4 Use Case Description for Add Loan

46
 CREDIT AND SAVING MANAGEMENT SYSTEM

Use Case ID UC5

Use Case Name Deposit money
Participating Actor(s) Officer
Description The “Deposit Money” use case enables the officer to deposit money to customers.
Trigger Customers who want to deposit money arrive.
Priority High
Precondition Customers must have account number.
Actor action System Responses
1. Officer Clicks “Deposit money” on 2. The system display “Deposit form”.
the system. 4. The system Validate the filled Deposit
3. The Officer fills the form on the form.
system and click Save. 6. Update account (A6: If not properly
5. The officer deposit Money to filled).
customer’s account. 7. The system display “success message”.
8. The user confirms “success”
Basic Course of Action message.
Alternative course of 9. The
A6: If ituse caseproperly
is not end. filled
action 1: The System display error message.
2: The use case resumes to step 3.
Post Condition Money deposited to customers account.
Table 4. 5 Use Case Description for Deposit Money

Use Case ID UC6

Use Case Name Withdrawal Money
Participating Actor(s) Officer
Description The “Withdraw Money” use case enables the officer to withdraw money from
Trigger account.
When Customers arrive to withdraw money.
Priority High
Precondition Customers must have account number.
Basic Course of Action Actor action System responses
1. Officer Clicks “Withdraw money” on 2. The system display “Withdraw form”.
the system. 4. The system Validate the filled Withdraw
3. The Officer fills the form on the form.
system and click Save. 6. Update account (A6: If not properly
5. The officer Withdraw Money from filled)
account. 7. The system display “success message”
8. The user confirm “success” message.
9. The use end.
Alternative course of A6: If it is not properly filled:
action 1: The System display error message.
2: The use case resumes to step 3.

Post Condition Money is withdrawal from account.

Table 4. 6 Use Case Description for Withdrawal Money

47
 CREDIT AND SAVING MANAGEMENT SYSTEM

Use Case ID UC7

Use Case Name Transfer money
Participating Actor(s) Officer
Description The “Transfer Money” use case enables the officer to transfer money from sender
account (debit sender) to receiver account (credit receiver).
Trigger When sender want to transfer money to receiver.
Priority Medium.
Precondition Both sender and receiver should have account number.
Actor action System Responses
1. Officer Clicks Transfer money on the 2. The system display Transfer form.
Basic Course of Action system. 4. The system Validate the filled
3. The Officer fills the form on the Transfer form.
system and click Save. 6. Update account (A6: If it is not
5. The officer Transfer Money to other
properly filled)
customer account.
7. The system display “success
8. The user confirm “success” message.
message”.
9.The use case end.
Alternative course of A6: If it is not properly filled:
action 1: The System display error message.
2: The use case resumes to step 3.
Post Condition Money added to receiver’s account and subtracted from sender account.

Table 4. 7 Use Case Description for Transfer Money

Use Case ID UC8

Use Case Name Register Employee
Participating Actor(s) Manager
Description The “Register Employee” use case enables the manager register Employee for
Trigger ADCSI.
When New Employee arrive.
Priority High
Precondition The Manager logged to the system.
Basic Course of Action Actor action System Responses
1. Manager Clicks Add Employee link. 2. System display “Employee
3. Manager fills the form and clicks on Registration” form.
“Register” button. 4. System checks the filled
6. The manager confirms “Successful” information and Save (A4: If filled
message. data is invalid)
7. The use case end. 5. The system displays “Successful
message”.
Alternative course of A4: If filled data is invalid:
Action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition New Employee added to the system.

Table 4. 8 Use Case Description for Transfer Money

48
 CREDIT AND SAVING MANAGEMENT SYSTEM

Use Case ID UC9

Use Case Name Change Password
Participating Actor(s) System administrator
Description The “Change Password” use case enables the System Administer able to change
the passwords.
Priority Medium
Precondition The System Administer logged to the system and remember the old password.
Actor action System responses
1. The System administrator clicks 2. The system displays “Sign UP” form.
“Sign Up link”. 4.The System Validates entered
3. The System administers enter the information and Save. (A4: If the filled
Required information and clicks data is invalid).
“Change Password” Button. 5. The system displays “Successful
Basic Course of Action 6. The System administrator confirms message”.
“successful” message.
7. The use case end.
Alternative course of A4: If filled data is invalid:
Action
1. The system displays error message.
2. The use case resumes to step 3.
Post Condition The password will be Changed.
Table 4. 9 Use Case Description for Change Password

Use Case ID UC10

Use Case Name View Transaction
Participating Actor(s) Officer, Customer
Description The “View Transaction” use case enables the officer to download transaction per
customer request.
Trigger When a Customer requests a statement.
Priority High
Precondition The Officer logged in to the system.
Basic Course of Action Actor action System Responses
1. Officer Clicks “View Transaction” Button. 2. System display “View Transaction”
3. Officer fills the form and clicks on “View” form.
Button. 4. System checks the filled
6. The officer download the statement and information and generates statement
gives to the customer. (A4: If filled data is invalid)
7. The use case end. 5. The system displays generated
statement.
Alternative course of A4: If filled data is invalid:
Action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition Statement is downloaded from the system.

Table 4. 10 Use Case Description for Change Password

49
 CREDIT AND SAVING MANAGEMENT SYSTEM

Use Case ID UC11

Use Case Name Get Report
Participating Actor(s) Manager
Description The “Get Report” use case enables the Manager to view Transaction Reports.
Trigger When a Manager requests a Transaction Report.
Priority High
Precondition The Manager logged in to the system.
Basic Course of Action Actor action System Responses
1. Manager Clicks “Get Report” Button. 2. System display “Get Report” form.
3. Manager fills the form and clicks on 4. System checks the filled
“Generate” Button. information and generates report
6. The Manager downloads the report. (A4: If filled data is invalid)
7. The use case end. 5. The system displays generated
report.
Alternative course of A4: If filled data is invalid:
Action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition Transaction Report is downloaded from the system.

Table 4. 11 Use Case Description for Get Report

Use Case ID UC12

Use Case Name Create User Account
Participating Actor(s) System Administrator, Manager
Description The “Create User Account” use case enables the System Administrator to create
User Account.
Trigger When a Manager requests a User Account.
Priority High
Precondition The System Administrator logged in to the system.
Basic Course of Action Actor action System Responses
1. System Administrator Clicks “Create 2. System display “Create User
User Account” Button. Account” form.
3. System Administrator fills the form and 4. System checks the filled
clicks on “Create” Button. information and creates User Account
6. The System Administrator gives (A4: If filled data is invalid)
username and password to Employee 5. The system displays “Successful
7. The use case end. message”.
Alternative course of A4: If filled data is invalid:
Action 1. The system displays error message.
2. The use case resumes to step 3.
Post Condition User Account is created in the system.

Table 4. 12 Use Case Description for Create User Account

50
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.6. Sequence Diagram

It highlights the sequencing of the interactions between objects. Also, it visualizes the sequence of
call in a system to perform specific functionality. Moreover, the sequence diagram is used primarily
to show the interactions between objects in the sequential order that those interactions occur.
However, an organization's business staff can find sequence diagrams useful to communicate how
the business currently works by showing how various business objects interact (Ambler, 2001).The
main purpose of a sequence diagram is to define event sequences that result in some desired
outcome.

SD: Log in

All actors Main page Login form Validator Login_Account

Click link()

Creat()

Desplay login form()

Enter user name

and password()

Click log in button()

Validate
form()

[If not correct]:

try again()

[if correct]:
login()

Confirm
Successfuly log in()

Stop Stop Stop Stop Stop

Figure 4. 2 Sequence Diagram for Login

51
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Register Employee

Register employee Validator Employee

Manager page

Initiate()

Create()

display register employee form()

fill employee information()

click save()

validate
form()

[if not correct try]: again()

[if correct]:
register employee()

confirm()

successfuly registerd()

Stop Stop Stop Stop

Figure 4. 3 Sequence Diagram for Register Employee

52
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Get Report

Generate Report Validator Transaction

Manager page
click link()

Create()

display report form()

fill and select

report type()

Click send()

[if not correct ]: validate

try again() from

[if correct]:
get report()

confirm()
seccessfuly report generated()

Stop Stop Stop Stop

Figure 4. 4 Sequence Diagram for Generate Report

53
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Approve Transaction

Approve validator Transaction

Manager transaction page
click link()

Create()

transaction approval
request

Click approved
butten()
transaction approved()

confirm()

transaction succesdfuly
aproved()

Stop Stop Stop Stop

Figure 4. 5 Sequence Diagram for Approve Transaction

54
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD creat new account

New account Customer_Account

Officer Validator
page

Initiate()

Create()

display new account form()

fill form and click save()

Check()

[if not correct try]:

again()
[if correct]:
creat new acount()

confirm()

successfuly created()

Stop Stop Stop Stop

Figure 4. 6 Sequence Diagram for Create New Account

55
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Add Loan

Officer Add loan page Validator Loan

click link()

Create()

display add
loan form()

fill the form()

Click Creat()

validate
form

[if not correct ]:

try again()

[if correct]:
add loan()

confirm()
seccessfuly loan created()

Stop Stop Stop Stop

Figure 4. 7 Sequence Diagram for Add Loan

56
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Deposit Money

Deposit money
Officer Deposit controler Customer_Account
page

Initiate()

Create()
fetch deposit type()

display deposit type()

display deposit
type deposit form()

select diposit type()

fill form()
Click save()

Check()

[if correct]:deposit money()

[if not correct ]:

try again()

confirm()

seccessfuly deposited()

Stop Stop Stop Stop

Figure 4. 8 Sequence Diagram for Deposit Money

57
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Withdraw Money

Officer Withdraw page validator Customer_Account

click link()

Create()

display withdraw form()

fill form()

Click save()

validate
form

[if not correct ]:

try again()

[if correct]:
withdraw money()

confirm()

seccessfuly withdrawin()

Stop Stop Stop Stop

Figure 4. 9 Sequence Diagram for Withdraw Money

58
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Transfer Money

Officer Transfer money validator Customer_Account

page

click link()

Create()

display local money

transfer form()

fill form()

Click save()

validate
form

[if not correct ]:

try again()

[if correct]:
withdraw money()

confirm()

seccessfuly transferd()

Stop Stop Stop Stop

Figure 4. 10 Sequence Diagram for Transfer Money

59
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Create User Account

System New user account

Validator Login_account
admin page

Initiate()

Create()

display new user

account form()

fill form and click save()

validate
form()

[if not correct try]: again()

[if correct]:
create user account()

confirm()

successfuly created()

Stop Stop Stop Stop

Figure 4. 11 Sequence Diagram for Create User Account

60
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD Change Password

Change password Validator Login_Account

Adminstrator page
click link()

Create()

display change
passsword form()

fill form()

Click confirm password()

[if not correct ]: validate

try again() from

[if correct]:
change password()

confirm()
seccessfuly pasword changed()

Stop Stop Stop Stop

Figure 4. 12 Sequence Diagram for Change Password

61
 CREDIT AND SAVING MANAGEMENT SYSTEM

SD View Transaction

view transaction validator Transaction

customer page
click link()

Create()
display customer
information form()

enter account number()

Click save()

validate
[if not correct ]: acc no
try again()

[if correct]:
veiw information()

confirm()

seccessfuly customer
information veiwed()

Stop Stop Stop Stop

Figure 4. 13 Sequence Diagram for View Transaction

62
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.7. Activity Diagram

Activity Diagram is a graphical representation of workflow of stepwise activity and action with
support for choice, iteration and concurrency. The activity can be described as an operation of
the system. Therefore, the control flow is drawn from one operation to another. Activity Diagram
are constructed from a limited a number of shapes, connected with arrows (Object-Oriented
Development, 1997). The most important shape types are:

 Rounded rectangular represent actions.

 Diamonds represent decision.
 Bars represent the start (Split) or end (join) of concurrent activities.
 A black circle represents the start (Initial State) of the workflow.
 An Encircled black circle represents the end (Final State).

Activity Diagram for Login

Start

Enter User name and

Password

if not correct

Click Login button

Check user name

and password
if correct

Display appropriate
page

Stop

Figure 4. 14 Activity Diagram for Login

63
 CREDIT AND SAVING MANAGEMENT SYSTEM

Activity Diagram for Register Employee Activity Diagram for Generate Report

Start
Start

Click Register
Click Get Report
Employee

Display Employee Display Report Form

Registration Form

if not correct Fill Form if not correct

Fill Form

Click Get Button

Click Register Button

Check filled form Check filled report

if correct
IF correct
View Generated
Display Message Report

Stop
Stop

Figure 4. 15 Activity Diagram for Register Employee Figure 4. 16 Activity Diagram for Generate Report

64
 CREDIT AND SAVING MANAGEMENT SYSTEM

Activity Diagram for Approve transaction Activity Diagram for New Customer Account

Start

Start
Click Create Account
Button
Receives Approval
Request

Display Create
Account Form
Display Ongoing if unappropraite
request
Transaction

if not correct
Fill Form

Revew the request Click Save Button

if correct

Click Approved
Button

Check filled form

Display Approved if correct
Message
Display Home Page

Stop Stop

Figure 4. 18 Activity Diagram for New Account

Figure 4. 17 Activity Diagram for Approve Transaction

65
 CREDIT AND SAVING MANAGEMENT SYSTEM

Activity Diagram for Deposit Money Activity Diagram for Withdraw Money

Start
Start

Click Withdraw
Click Deposit Money Money

Display Withdraw
Display Deposit Money Form
Money Form

Fill Form
if not correct
Fill Form
if not correct

Click Withdraw
Button
Click Deposit Button

Check filled form

Check filled form
if correct if correct

Display Message Display Message

Stop Stop

Figure 4. 19 Activity Diagram for Deposit Figure 4. 20 Activity Diagram for Withdraw

66
 CREDIT AND SAVING MANAGEMENT SYSTEM

Activity Diagram for Transfer Money Activity Diagram for Add Loan

Start Start

Click Transfer Money Click Add Loan

Button

Display Transfer
Money Form Display Add Loan
Form

if not correct
Fill Form if not correct
Fill Form

Click Transfer Button

Click Create Button

Check filled form

if correct Check filled form
if correct
Display Message
Display Message

Stop
Stop

Figure 4. 21 Activity Diagram for Transfer Money Figure 4. 22 Activity Diagram for Add Loan

67
 CREDIT AND SAVING MANAGEMENT SYSTEM

Activity Diagram for User Account Activity Diagram for Change Password

Start
Start

Click Create User Click Change

Account Button Password

Display Create User Display Change

Account Form Password Form

if not correct Fill Form if not correct

Fill Form

Click Confirm Button

Click Create Button

Check filled form

Check filled form
if correct
if correct
Desplay Message
Display Home Page

Stop
Stop

Figure 4. 23 Activity Diagram for User Account Figure 4. 24 Activity Diagram for Change Password

68
 CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 25 Activity Diagram for View Transaction

4.8. Class Diagram

UML class diagram are the backbone of object oriented modeling. Class model shows the class
of the system, their interrelationship, and the operation and attribute of the class. It shows the
static structure of the model. In particular, the things that exists, their internal structure, and their
relationship to other things. This project used class diagram to design the structure that will be
included on the system (Object-Oriented Development, 1997).

69
 CREDIT AND SAVING MANAGEMENT SYSTEM

Class Diagram For ADCSI Get

Transaction 1..* 1
- Transaction_Id:varchar
- Transaction_Type:string Account
1..*
Get - Previous_Amount:double
- Transaction_Amount:double - Account_Number:varchar
- Transaction_Date:int - Account_Type:string
1
+ Deposit_Money();double - First_Name:atring
+ Withdraw_Money();double - Last_Name:string
Loan_Service + Transfer_Money();double - Gender:string
- Photo:image
- Loan_Id:varchar 1..*
1..* - Signature:image
- Loan_Amount:double - Ocupation:string
- Payment_Interval:int - Phone:int
- Loan_Date:int 1 1 - Date_Created:int 1..*
+ Add_Loan();double has
- Opening_Balance:double
+ Block_Loan_Account();string - Balance:double
+ Create_Account():char
Approve + View_Transaction():char
Perform Create
1
1
Manager Manege Officer
-- 1..* 1
1 --
+ Register_Employee():string
1
+ Get_Report():string Employee + Create_Account():char
+ Block_Loan_Account():string + Deposit_Money():double 1
1
+ Approve_Transaction():string -memberName + Withdraw_Money():double
- Employee_Id:varchar + Transfer_Money():double
- First_Name:string
Use
- Last_Name:string
Manege - Gender:string
- Phone:int
- E-mail:varchar Login_Account
System_Adminstrator 1
- E-mail:varchar
-- - User_Name:string
1 - Pass_Word:varchar
+ Create_User_Account():string 1
Use
+ Change_Password():string + Create_User_Account():string
+ Change_Password():string
1 Manege 1..*

Figure 4. 26 Class Diagram

70
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.9. Database Design

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

PK Acc ou nt_Nu mber

Employee Acc ou nt_Type

Emp_ID Cust_Name

Emp_First_Name Emp_La st_Name

Emp_La st_Name Cust_Gen der

Emp_Gender
Ph oto

Emp_DOB
Signat ure

Emp_Cell_Phone
Cust_Cell_Phone
Emp_E-mail
Cust_E-mail
Customer_Acc nt
Date_Creat ed

Op en ing_Balan ce

Passbook Last_login_Date

Acc ou nt_Stat us
PK Transac tion_ID

Current_Balance
Transac tion_Date

FK Emp_Id
Customer_Name

Bra nch_Cod e

Acc ou nt_Type

System_Admin
credit

PK Admin_ID
Debit

Admin_Firs t_Name
Tot al_Amoun t

Admin_Last_Name
FK Acc ou nt_Nu mber

FK Acc ou nt_Nu mber

FK Emp_ID

Figure 4. 27 Database Design

71
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.10. Access Control and Security

In the system, different actors have access to different information and data. Access control and
security specifies what the user can access or what cannot perform by some user’s. This access
control is verified by which users are granted access and certain privileges to systems, resources
or information. The following table shows access control of our system.

Manager Customer Officer System Admin

Login    

Logout   

Register Employee X X X

Get report X X X

Block loan account X X X

Create user Account X X X

Change password X X X

View transaction   X X

Deposit Money X X X

Loan to customer X X X


Register Customer X X X

Create Book Account X X X

Withdraw money X X X

Transfer Money X X X

Table 4. 13 Access control and Security

72
 CREDIT AND SAVING MANAGEMENT SYSTEM

4.11. Component Diagram

The Component diagram defined set of services such as access, transactions, persistent storage,
and security that support the software. In another hand, it does not describe the functionality of
the system but it describes the components used to make those functionalities. And also used to
model physical aspects of a system. The component modeling describes components of our
system such as operator and administrator and how can they interact with each other depending
on their functionality, and what is there common function that can share by all the components of
our system. It also describes the interaction of our system components with the security control
system (Object-Oriented Development, 1997).

Component Diagram for ADCSI

Transaction
Approval

Account
Manager
Managment

Transaction Security Database

Officer

Registration
System
Administrator

User Account
Management

Figure 4. 28 Component Diagram

4.12. Deployment Diagram

Deployment diagram is used for describing the hardware components where software
components are deployed. Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagrams shows how
they are deployed in hardware. UML is mainly designed to focus on software artifacts of a
system. But these two diagrams are special diagrams used to focus on software components and
hardware components. So most of the UML diagrams are used to handle logical components but
73
 CREDIT AND SAVING MANAGEMENT SYSTEM

deployment diagrams are made to focus on hardware topology of a system. Deployment

diagrams are used by the system engineers (Ambler, 2001). The purpose of deployment diagrams
can be described as:
 Visualize hardware topology of a system.
 Describe the hardware components used to deploy software components.
 Describe runtime processing nodes.

Therefore, in this particular case the team used the following deployment diagram to show the
system.

Figure 4. 29 Deployment Diagram

4.13. UI Design

User Interface Design is the design of websites, computers, machines, mobile devices, and
software applications with the focus on the user’s experience and interaction. 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—what is often called user-centered design.

74
 CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 30 Home Page UI

Figure 4. 31 New Customer home Interface

Figure 4. 321 Customer Home Page UI

75
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 33 Customer profile UI

Figure 4. 34 System Admin Home UI

76
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 35 Manager Home UI

Figure 4. 36 Deposit UI

77
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 37 Balance Transfer UI

Figure 4. 387 Withdraw UI

78
CREDIT AND SAVING MANAGEMENT SYSTEM

Figure 4. 398 Officer UI

79
 CREDIT AND SAVING MANAGEMENT SYSTEM

Reference
Addis Credit and Saving Institution. (n.d.). Retrieved October 10, 2017 from the World Wide
Web: http://www.mbirr.com/serviceprovidersAdcsi.html

Major activities of the institution. (n.d.). Retrieved October 10, 2017 from the World Wide Web:
http://www.adcsi.org/aboutus.html

Gebremedhin, Y. (22 April 2016). Ethiopia: Electronic Cash Payment, Transfer and Transaction
Easing Life in Ethiopia. The Ethiopian Herald, 25.
Horine, G. (2009). Project Mangement Absolute Beginner's Guide (Second Edition ed.). Que,
2009.
Object-Oriented development. (1997). Retrieved October 12, 2017 from the World Wide Web:
http://www.westga.edu/-bquest/1997/object.html
Software-development-life-cycle-models-and-methodologies. (2012). October 02, 2017 from the
World Wide Web: http://www.melsatar.blog.html

Scott W. Ambler (2001). The Object Primer: the application developer’s guide to object
orientation and the UML. 2nd edition, England: The Cambridge University Press.

O.Grady, J. (1993). System Requirement Analysis (First Edition ed.). Michigan: McGraw-Hill.

80
 CREDIT AND SAVING MANAGEMENT SYSTEM

Appendix
Interview Questions
Questions for Employees
1. What kind of services does the existing system provide?
2. Can u tell us step by step how your existing system works?
3. How do you store data's?
4. How do you retrieve data's?
5. How much time does it take to retrieve an individual record or data?
6. What are the rules that you follow when registering new borrower?
7. What kind of tools do you use throughout the process?
8. Do you have security options for data's and files?
9. What are the problems running with the current or manual system?
10. What is the customer feedback?
11. If this system is automated, do you think it will be helpful?

Questions for Customers

7. How do you get information from the institution?
8. Are you satisfied by the service given by ADCSI?
9. How long do you wait for services?
10. What kinds of problems do you face when you need to get service?
11. What kind of service do you expect from ADCSI?
12. Do you think it will be helpful, if this system is automated?

81