mobile banking for bunna international bank last

JIMMA UNIVERSITY

INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTING

PROGRAM: COMPUTER SCIENCE

REQUIRMENT SPECIFICATION, ANALYSIS AND SYSTEM DESIGN

OF MOBILE BANKING FOR BUNNA INTERNATIONAL BANK

BY

Name ID

1. Solomon Demissie 05474/03

2. Yohannes Alemu 01973/03

3. Kidus H/Michael 01900/03

4. Dawit Gezahegn 01860/03

Advisors

Name Signature

1. Mr. Michael Shiferaw (MSc)

Co-advisors

Name Signature

1. Mis. Jiya

Submission to: Department of computing, NOS Chair

ii

Contact Information

This project report is submitted to the Department of Computing at Jimma University in

partial fulfillment of the requirements for the degree of Bachelor of Science in Computer

Science.

Author(s):

Solomon Demissie [email protected]

Yohannes Alemu [email protected]

Kidus H/Michael [email protected]

Dawit Gezahegn [email protected]

University Advisor/supervisor(s):

Mr. Michael Shiferaw [email protected]

Chair of the Advisor: Networking and OS

Department name: Computing

Co-supervisor:

Mis. Jiya

Department: Computing

iii

Intellectual Property Declaration

This is to declare that the work under the supervision of Mr. Michael Shiferaw having title

Mobile banking system for Buna International Bank carried out in partial fulfillment of the

requirements of Bachelor of Science in 2013/14 is the sole property of the Jimma University

and the respective supervisor and is protected under the intellectual property right laws and

conventions. It can only be considered/ used for purposes like extension for further

enhancement, product development, adoption for commercial/organizational usage, etc., with

the permission of the University and respective supervisor.

This above statement applies to all students and faculty members.

Date: ______________

Author(s):

Name:

Solomon Demissie Signature: _____________________

Yohannes Alemu Signature: _____________________

Kidus H/Michael Signature: _____________________

Dawit Gezahegn Signature: _____________________

iv

Anti-Plagiarism Declaration

This is to declare that the above industrial project produced under the supervision of Mr.

Michael Shiferaw having title Mobile banking system for Buna International Bank is the

sole contribution of the author(s) and no part hereof has been reproduced illegally (cut and

paste) which can be considered as Plagiarism. All referenced parts have been used to argue

the idea and have been cited properly. I/We will be responsible and liable for any

consequence if violation of this declaration is proven.

Date: ______________

Author(s):

Name:

Solomon Demissie Signature: _____________________

Yohannes Alemu Signature: _____________________

Kidus H/Michael Signature: _____________________

Dawit Gezahegn Signature: _____________________

v

Acknowledgment

As the beginning we would like to thank GOD for making us present and capable of doing

this industrial project. Also we would like to thank our Advisors Instructor Mr. Michael

Shiferaw and Instructor Jiya for their guidance in developing this project documentation.

We are also very grateful and extend our thanks to staff members of Jimma university

department of computer Science who have involved in performing this project by giving

different advises to us.

vi

Abbreviations

Abbreviations Meaning

IVR Interactive Voice Response

OOP Object Oriented Programming

UML Unified Modeling and Language

SMS Short Message Service

JDBC Java Database Connection

GSM Global System for Mobile Communications

DBMS Database Management System

CSO Customer Service Officer

UML Unified Modeling Language

CSM Customer Service Manager

Definition

Electronic banking: Use of computers and telecommunications to enable banking transactions

to be done by telephone or computer rather than through human interaction. (In this

document it refers two electronic devices laptop and computers).1

Multiple approach technology: Is using SMS, browser or apps to access the functionalities

given by the bank.

1 Electronic banking http://encyclopedia2.thefreedictionary.com/electronic+banking (By

encyclopedia2)

vii

Abstract

The title of the project is Mobile banking system for Buna International Bank. The main

objective of this project is to design and implement a mobile banking for Bunna international

bank that support any type of mobile phone.

The model which we have designed is going through stages of the life cycle of one of the

latest and the most important methods for object-oriented software engineering which is agile

development methodology.

The steps that are done under agile development methodology are gathering information,

analyze and design the system, implement, test and evaluate our system. Gathering

information is done by interviewing and observation techniques. System analysis and design

takes place using UML.

The possible outcomes of this system are performing the following activity by user using

their mobile: transfer money, check account balance, view transaction history and view

exchanged rate.

Security is the major issue in our project. The system provides the username and password

authentication method and encryption of the data. Beside the authentication the system will

verify the user phone number to check the request really comes from the users mobile phone.

viii

Contents

Organization of the project ...................................................................................................................xiii

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

1. Introduction ........................................................................................................................................ 1

1.1 Background ................................................................................................................................... 1

1.2 Statement of the problem ............................................................................................................ 3

1.3 Objective ....................................................................................................................................... 4

1.3.1 General Objective .................................................................................................................. 4

1.3.2 Specific Objective ................................................................................................................... 4

1.4 Scope ............................................................................................................................................. 4

1.5 Significance of the project ............................................................................................................ 5

1.6 Methodology ........................................................................................................................... 5

1.6.1 Requirement gathering methods ........................................................................................... 6

1.6.2 Analysis and design the system ............................................................................................. 6

1.6.3 Coding .................................................................................................................................... 7

1.6.4 Testing and acceptance .......................................................................................................... 7

1.6 Feasibility study............................................................................................................................. 8

TIME SCHEDULE .................................................................................................................................... 10

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

Analysis ................................................................................................................................................. 11

2.1 Existing system description ......................................................................................................... 11

Major functions of the bank ......................................................................................................... 11

2.1.1 Opening Book Account......................................................................................................... 11

2.1.2 Deposit Money ..................................................................................................................... 12

2.1.3 Withdraw Money ................................................................................................................. 12

2.1.4 Transfer Money .................................................................................................................... 12

2.1.5 Check .................................................................................................................................... 13

2.2 Proposed system ......................................................................................................................... 13

2.2.1 SMS (Short Message Service) Mobile Banking ..................................................................... 14

2.2.2 Internet Browser Mobile Banking ........................................................................................ 15

2.2.3 Downloadable Mobile Banking ............................................................................................ 15

Business Rule of the proposed system ............................................................................................. 17

2.3 System Requirement ................................................................................................................... 18

ix

2.3.1 Non functional requirements ............................................................................................... 18

2.3.2 Functional requirements ...................................................................................................... 19

Use case diagram .............................................................................................................................. 20

2.3.4 Object Model ....................................................................................................................... 38

2.3.5 Class Diagram ....................................................................................................................... 50

2.3.6 User Interface....................................................................................................................... 52

CHAPTER THREE .................................................................................................................................... 65

Design .................................................................................................................................................... 65

3.1 Overview ..................................................................................................................................... 65

3.2 Purpose and goals of design ....................................................................................................... 65

3.3 Proposed software architecture ................................................................................................. 66

3.3.1 Subsystem decomposition ................................................................................................... 68

3.3.2 Component diagram ............................................................................................................ 70

3.3.3 Deployment diagram ........................................................................................................... 70

3.4 Persistence modeling for object oriented database ................................................................... 71

3.5 Access control and security......................................................................................................... 73

Conclusion ......................................................................................................................................... 74

Appendix ........................................................................................................................................... 75

x

List Of tables

Table 1 Description of Login Use Case Process Flow ............................................................ 21

Table 2 Description of See Profile Use case Process Flow ..................................................... 22

Table 3 Description of Change Password use case Process Flow .......................................... 23

Table 4 Description of Check Balance Use case Process Flow .............................................. 24

Table 5 Description of Fund Transfer Process Flow .............................................................. 26

Table 6 Description of View Transaction History Use case Process Flow ............................. 27

Table 7 Description of Add Contact Process Flow ................................................................. 28

Table 8 Description of Delete Contact Process Flow ............................................................. 29

Table 9 Description of View Contact Process Flow ................................................................ 30

Table 10 Description of Login Process Flow .......................................................................... 30

Table 11 Description of Customer Registration use case process flow................................... 32

Table 12 Description of Edit Customer Account use case process flow.................................. 33

Table 13 Description of Create Account use case process flow .............................................. 35

Table 14 Description of Delete Account use case process flow .............................................. 36

Table 15 Description of View User Account use case process flow ........................................ 36

Table 16 Description of approve customer use case process flow .......................................... 38

Table 17 Description of collaboration of customer class ........................................................ 49

Table 18 Description of collaboration of customer service officer class ................................ 50

Table 19 Description of collaboration of transfer class .......................................................... 50

Table 20 Description for Access control and security ............................................................. 73

xi

List of Figures

Figure 1Agile Development Methods ........................................................................................ 6

Figure 2Time schedule ............................................................................................................. 10

Figure 4 Use case diagram for Mobile Banking Application .................................................. 20

Figure 5 Sequence Diagram for login ..................................................................................... 38

Figure 6 Sequence Diagram for View Profile ......................................................................... 39

Figure 7 Sequence Diagram for Transaction history .............................................................. 39

Figure 8 Sequence Diagram for Fund Transfer ...................................................................... 40

Figure 9 Sequence Diagram for Add Contact ......................................................................... 40

Figure 10 Sequence Diagram for Customer Registration ....................................................... 41

Figure 11 Sequence Diagram for Create account ................................................................... 41

Figure 12 Sequence Diagram for Delete account ................................................................... 42

Figure 13 Sequence Diagram for Change password ............................................................... 42

Figure 14 Sequence Diagram for Query balance .................................................................... 43

Figure 15 Sequence Diagram for create contact ..................................................................... 43

Figure 16 Sequence Diagram for Delete contact .................................................................... 44

Figure 17 Activity Diagram for login ...................................................................................... 44

Figure 18 Activity Diagram for View Profile .......................................................................... 45

Figure 19 Activity Diagram for Transaction history ............................................................... 45

Figure 20 Activity Diagram for Fund Transfer ....................................................................... 46

Figure 21 Activity Diagram for Add Contact .......................................................................... 46

Figure 22 Activity Diagram for Customer Registration .......................................................... 47

Figure 23 Activity Diagram for Create account ...................................................................... 47

Figure 24 Activity Diagram for Delete account ...................................................................... 48

Figure 25 Activity Diagram for Change password ................................................................. 48

Figure 26 Activity Diagram for Check balance ....................................................................... 49

Figure 27 a Conceptual class diagram for mobile banking application ................................. 51

Figure 28 Showing the structure and navigation of the Interfaces ......................................... 52

Figure 29 a splash for opening the application ....................................................................... 53

Figure 30 Login User Interface ............................................................................................... 54

Figure 31 Main Menu User Interface ...................................................................................... 55

Figure 32 Setting User Interface ............................................................................................. 56

Figure 33 View Profile User Interface .................................................................................... 57

xii

Figure 34 Change password User Interface ............................................................................ 58

Figure 35 Balance query User Interface ................................................................................. 59

Figure 36 Fund transfer User Interface .................................................................................. 60

Figure 37 Manage Contact User Interface .............................................................................. 61

Figure 38 Add contact User Interface ..................................................................................... 62

Figure 39 Delete Contact User Interface ................................................................................ 63

Figure 40 Transaction history User Interface ......................................................................... 64

Figure 41 System Architecture for Mobile Banking Application............................................. 67

Figure 42 System Architecture for Mobile Banking Application............................................. 68

Figure 43 Decomposition of Mobile Banking .......................................................................... 69

Figure 44 Component diagram for admin functionalities ....................................................... 70

Figure 45 Component diagram for customer functionalities .................................................. 70

Figure 46 Deployment Diagram for Mobile device ................................................................. 71

Figure 47 Deployment Diagram for Mobile device persistent ................................................ 71

Figure 48 Persistence diagram ................................................................................................ 72

xiii

Organization of the project

This document consists of four chapters. Chapter one give description on the project we are working

on, that is Mobile banking. The main objective of this chapter is to give an introduction about the

system like its scope, objectives, methodologies, etc Chapter two focuses more about the system

requirement specification or analysis. In the third chapter the design phase of the proposed system is

explained and the last chapter is writing the code based on the design that has been created in design

phases.

CHAPTER ONE

1. Introduction

1.1 Background

Bunna International Bank S.C. has joined the Banking industry of Ethiopia following the

favorable economic developments witnessed in the country during the last decade and the

continuously growing needs for Financial Services. The Bank officially begin its operation on

October 10, 2009 with subscribed & paid up capital of Birr 308 million and Birr 156 million,

respectively. Moreover, the Bank has more than 11,200 shareholders, which makes it one of

the strong and public based private Banks in Ethiopia. 2

The first bank in Ethiopia called Bank of Abyssinia was opened in Feb.16, 1906 by the

Emperor Minilik II. The society at that time being new for the banking service, bank of

Abyssinia had faced difficulty of familiarizing the public with it. It had also need to meet

considerable cost of installation.3

Banks accept Deposits; make Loans; Provide Safety and Act as Payment Agents. Mostly

banks work is related to money. Money was originally a physical substance like gold and

silver. Today, although much of the money used by individuals in their everyday transactions

is still in the form of notes and coins, its quantity is small in comparison with the intangible

money that exists only as entries in bank records.4

Ethiopia uses the term Birr to pay for goods and services. The birr is the unit of currency in

Ethiopia. On 23 July 1945, notes were introduced by the State Bank of Ethiopia in

denominations of 1, 5, 10, 50, 100 and 500 birr. The National Bank of Ethiopia was

established by imperial proclamation 207 of 27 July 1963 and began operation on 1 January

2 Company Profile http://www.bunnabanksc.com/pages/CompanyProfile.html (By

www.bunnabanksc.com/)

3 History of banking http://www.nbe.gov.et/aboutus/index.html (By www.nbe.gov.et)

4 Electronic Money, or E-Money, and Digital Cash

http://projects.exeter.ac.uk/RDavies/arian/emoney.html (By Roy Davies Sunday 15 Dec 2013)

Mobile banking system for Buna International Bank

2

1964. The National Bank of Ethiopia took over note production in 1966 and issued all

denominations except for the 500 birr.5

With the advancement of technology today Ethiopia started to use Electronic money.

Electronic money is money that is exchanged electronically. This involves the use

of Electronic devices, computer networks, the Internet and digital stored value systems.

Examples of electronic money are bank deposits and electronic funds transfer (EFT).6

Mobile devices are one of the electronic devices that give us many services. Mobile banking

is one of the services given by mobile devices. Mobile banking is a system that allows

customers of a bank to conduct a number of financial transactions through a mobile device

such as a mobile phone, personal digital assistant or other devices that can connect to mobile

telecommunication networks. Or Mobile banking is a way for the customer to perform

banking actions on his or her cell phone or other mobile device. It is a quite popular method

of banking that fits in well with a busy, technologically oriented lifestyle. It might also be

referred to as M-banking. Mobile banking allows the user to log into his or her account from

a cell phone, and then use the phone to make payments, check balances, and transfer money

between accounts. This type of banking is meant to be more convenient for the consumer

than having to physically go into a bank, log on from their home computer, or make a phone

call.7

Mobile banking offers many advantages. The biggest benefit of mobile banking is that users

have more control of their money. There are no Internet connections everywhere the user

goes but there is a telecommunication network connection in most places that let the user to

access his/her account through text messaging. It also let users to access their account

anytime they want and offers things people can do every day, such as looking at account

activity, exchange rate and transfer money.8 An additional benefit of mobile banking is that it

offers the possibility to use e-banking (electronic banking) functionalities via a mobile phone.

I.e. customers can access their bank account from their cell phone using an internet. Mobile

5 Ethiopian Birr, http://en.wikipedia.org/wiki/Ethiopian_birr (By Wikipedia.com Sunday 15 Dec

2013) 6 Electronic Money, http://en.wikipedia.org/wiki/Electronic_money ( By Wikipedia.com Sunday 15

Dec 2013) 7 What is Mobile Banking, http://www.wisegeek.com/what-is-mobile-banking.htm (By wiseGEEK.com Sunday 15 Dec 2013)

8 5 reasons to use mobile banking, http://www.bankrate.com/finance/savings/5-reasons-to-use-mobile-banking-1.aspx (By Constance Gustke Sunday 15 Dec 2013)


3

banking is a sub of electronic banking that provides anywhere, anytime access. We can use

mobile banking via SMS. It could also be implemented using browsers or Apps. Electronic

banking offers anytime access using two approaches, browsers and applications, from

electronic devices that have connected to the WEB. Therefore, customers using mobile

banking have a greater flexibility than users of other electronic banking.9

The three widely available types of mobile banking technology are via text messaging,

browsers and applications. Texting is the simplest method for many. Most people do their

mobile banking in the way using their Web browser accesses their online account. But

downloadable applications are expanding quickly.

This project is concern on the development of a mobile banking system for Bunna

International Bank. The developing system includes multiple approach technology for mobile

banking aiming to support any type of cell phone.

1.2 Statement of the problem

Bunna international bank has 43,922 customers at the end of the February 2012 and most of

the customers are very familiar with how a bank operates.10 The concept is very simple; we

take our money to the bank and they will keep it safe for us and we can collect it later. We

walk into our local bank to deposit a check or to make a withdrawal. To do this we need to

wait until our turn has come. Time is the most valuable thing in life, but we waste this time

with the lines associated with doing even the most basic tasks in bank.

People do business anytime and anyplace, and banks have a crucial point in business. But

banks wont work 365 days in a year. They wont give service in holydays, in Sunday and

most banks after Saturday afternoon. As a result, works that should be done will be delayed.

There is no bank that gives service 24 hours a day in Ethiopia. Banks are opened from 8: 00

a.m. to 5:00 p.m. We cant visit banks after regular business hours. We just have to wait until

the next day to get service.

9 The role of mobile banking in enhancing economic development,

http://www.academia.edu/3045375/The_role_of_mobile_banking_in_enhancing_economic_developm

ent, (By Suad Beirovi Sunday 15 Dec 2013) 10 Bunna international bank annual report

http://webcache.googleusercontent.com/search?q=cache:QaAz3Ja798IJ:www.bunnabanksc.com/Dow

nload/BIB%2520Annual%2520Report%2520Eng%25202013.pdf+&cd=3&hl=en&ct=clnk&gl=et

(By webcache.googleusercontent.com/)


4

In our day today lives we need money in different situations like during traveling, in

vacation, in shopping, in emergency cases We may dont have enough money in our

pocket. Therefore, we have to go to our nearest bank and get money from our account. This

process takes time. Our situation may do not let us to take that much time.

Setting up bank branches is not only expensive it is also time consuming. It is obvious that it

takes much more time for bank branches to reach the entire population. In that case, many

people cant get the services.

In summary

Availability: Service not available any time & everywhere.

Very Slow: Doesnt let clients to access money fast.

Time Consuming: The traditional (existing) banking system is time consuming.

Expensive: Setting up bank branches is expensive and also time consuming.

1.3 Objective

1.3.1 General Objective

The general objective of this project is to design and implement mobile banking system for

Buna international bank with multiple approach technology.

1.3.2 Specific Objective

In order to achieve the above general objective we:

Identify the problem of existing system.

Perform requirement analysis.

Design the system architecture for the proposed system.

Develop an interactive user interface.

Write the code based on the design.

Build a good security system.

1.4 Scope

The scope of this project is to design and implement mobile banking for Buna international

bank using multiple approach technology with some major functionality. Also to integrate

IVR for the browser and app approaches.


5

Our scope is limited to on giving the above functionalities. Other functionalities given by the

bank like loan, Check, and Money exchange are out of our scope.

1.5 Significance of the project

Mobile banking is a type of technology that minimizes a lot of customers problem. It reduces

the time wasted in going to banks to stay on queues, the flow of human traffic and long

queues at banks. Most customers are more comfortable paying for goods via their mobile

phones and tablets. Obviously Financial institutions offering mobile services will have an

advantage when it comes to attracting new customers.

Mobile banking is more interactive and easy to use, as we can use it anytime and anywhere. It

creates a banking system that is easily accessible by customers from the comfort of their

homes, offices etc. It also let blind persons access their account without anyone help by the

leading of the IVR (Interactive voice response) in the system. Additionally, it encourages

new customers to join the bank as the system improves the customer care service. As a

whole, mobile banking lets people to follow technologically oriented lifestyle as they will

have more control of their money.

1.6 Methodology

Methodology is a series of choices how to perform gathering information, analyze and design

the system, implement, test and evaluate using different ways and methodologies. Most used

methodologies are prototyping, iterative, incremental, waterfall, agile, etc. Among them we

select agile development methodology for our system. The requirements for agile

development are Requirement gathering, analysis and design, coding, testing and acceptance.

The advantage of agile development method is incremental (multiple releases), cooperative (a

strong cooperation between developer and client), straightforward (easy to understand and

modify) and adaptive (allowing for frequent changes).


6

Figure 1Agile Development Methods

1.6.1 Requirement gathering methods

Interview: Customers need fast and reliable service from banks. They are tired of the

paper work. Most customers complain that they cant get the services when they want

because of the banks will be closed on holydays and after the regular business hours.

And also most customers will be happy if they monitor their money in the bank.

Mobile banking will let them to remove all this problems of the customers.

Observation: It is observed that people do not like to be hold in the process of

banking system. Also to fee their bill they will waste a lot of time. They also waste a

resource by going to the bank. During shopping or in some situations peoples may not

have enough money. Because of that they will be destructed from doing what they

want. Also customers wont get bank branches around them as the branches dont

setup to reach all over the population.

1.6.2 Analysis and design the system

We need a method for analyzing a problem to be solved, a plan for the design of the solution

and a construction method that minimizes the risk of error. We have chosen the Object

oriented approach (OO) to follow for our proposed system.

Object-Oriented programming (OOP) is an approach to designing modular reusable software

systems. A module is a component of a larger system that interacts with the rest of the system

in a simple and well-defined manner. The object-oriented approach is a logical extension of

structured programming. The central concept of OOP is the object, which is a kind of


7

module containing data and subroutines. An object is a kind of self-sufficient entity that has

an internal state (the data it contains) and that can respond to messages (calls to its

subroutines). 11

We select OOP because it produces solutions that are12

easier to write

easier to understand

contain fewer errors

Reduction of development time

Reduction of time and resources required to maintain existing systems

Increase code reuse

We have used EDraw Max application for UML Diagrams (for Use Case diagram, Sequence

diagram, Class diagram, Activity diagram, State chart diagram, component, and deployment

diagram). Eclipse software to design the proposed system. It is a multi-language integrated

development environment (IDE) comprised a base workspace and an extensible plug-in

system for customizing the environment.

1.6.3 Coding

The next step after design is to write a code for the system. We use java programming

language to write the code and an SQL language for the database.

1.6.4 Testing and acceptance

The system will be tested at every individual step of the system. This helps to identify the

errors and to correct them. It will be easy to deliver a system that is acceptable by the user if

we know what the user requirements are.

11 Dilemma Between the Structured and Object-Oriented Approaches to Systems Analysis And Design, http://webcache.googleusercontent.com/search?q=cache:JP-

rIS659RMJ:https://mis.uhcl.edu/rob/Professional/Publications/Dilemma%2520of%2520Structured%2520and%2520OO%25

20Methodology.pdf+&cd=2&hl=am&ct=clnk&gl=et (By Mohammad A. Rob Sunday 15 Dec 2013 )

12 Dilemma Between the Structured and Object-Oriented Approaches to Systems Analysis And Design, http://webcache.googleusercontent.com/search?q=cache:JP-

rIS659RMJ:https://mis.uhcl.edu/rob/Professional/Publications/Dilemma%2520of%2520Structured%2520and%2520OO%25

20Methodology.pdf+&cd=2&hl=am&ct=clnk&gl=et (By Mohammad A. Rob Sunday 15 Dec 2013 )


8

We have used Microsoft word 2007 to prepare documentation, Microsoft PowerPoint for

presentation, and Gantt Chart software to schedule time.

1.6 Feasibility study

Feasibility study is made to see if the project on completion will serve the purpose of the

organization for the amount of work, effort and the time that spend on it. It lets the developer

predict the future of the project and the usefulness.

By using the gathered information on the requirements for mobile banking we do feasibility

study from different perspectives. We can see from its technical, operational, time and

economical points of view. The system exactly provides most of the functions of the bank.

Technically it is possible to access one server by electronic devices using the web if the user

has access privilege. In the existing banking system computers are connected to the bank

server using the web technology. To do tasks tellers will login to the system and access the

server. In the mobile banking system customers has all the privilege on their account. They

can login to the system remotely by using their mobile phone and access their account. That

goes to the proposed system is technically feasible.

From our observation most customers have the awareness of how to use a mobile phone. The

application is also easy to understand. So, customers can do any of the operations without any

problem. This system is operational feasible since the users are familiar with the technologies

and any transaction operation will be synchronized. Also the system is very friendly and to

use.13

According to the data we gathered from the interviews and also from the observation we have

concluded that the application is time feasible. To determine the time feasibility of the system

we should take into consideration the time that will be taken by the customer when using this

application compared with the existing banking system. In the existing system it is observed

the customers need to go to the bank physically to get any of the services given by the bank,

or they need to go to the ATM machine to use their visa card. This is a very time consuming

system to both the customers and the bank itself. But if mobile banking is implemented the

customers need not to go physically to the bank. They just can get most of the services that is

given by the bank from their mobile phone. The mobile banking system will reduce the time

13 seminarprojects.com, http://seminarprojects.com/Thread-mobile-banking-full-report (By seminarprojects.com Monday 16 Dec 2013)


9

that the customers will waste by going to the bank and wait for the queue. This makes the

system time feasible.

One of the factors, which affect the development of a new system, is the cost it would

require. As we understand during in the interview this is how the tellers do. They send a

query to the server from their system to do some task, and then the server will reply based on

the query. In the mobile banking system the customer is considered as a teller which controls

its own account, the customers mobile phone is considered as the tellers system. So, to

implement this system the only need from the customer is to have a mobile phone; the bank

needs a server, which already exists, that will check and perform tasks. The softwares that is

needed to develop the system already exists. As all the resources are already available, it give

an indication of the system is economically possible for development.14 The customers also

need not to waste their money by taking a taxi or drive to the bank.

14 https://www.classle.net/projects/node/1512 (By www.classle.net 12/22/2013)

TIME SCHEDULE

Figure 2Time schedule

CHAPTER TWO

Analysis

System analysis is a process of gathering and interpreting facts, diagnosing problems and the

information to recommend improvements on the system. It is concerned with becoming

aware of the problem, identifying the relevant and decisional variables, analyzing and

synthesizing the various factors and determining a satisfactory solution or program of

action.15

2.1 Existing system description

There is no existing mobile banking service for Bunna bank. The bank uses the traditional

banking system. A detailed study has been made on the traditional system of the bank by

techniques like interviews and observation. The data collected by these sources also has been

studied to arrive to a conclusion. The conclusion is an understanding of how the system

functions.

The major operations in the existing system of Buna bank are: Account Opening, Deposit,

Transfer and Withdrawal. In the existing system to get cash, to make a deposit, or to check

account balance, users need to visit their banks local branch, wait in line for a teller, and

show their bank book at the window to make any transactions. Some banks apply an ATM to

let their customers withdraw money without going to the bank.

Major functions of the bank

2.1.1 Opening Book Account

The person who want to open bank account, he is expected to full fill the requirements that

are needed from him/her. That is filling personal information (like full name, address),

photo, and minimum account balance for the first time. If the person completes all

requirements he can get the book account immediately. The personal information is filled on

the form that is given from the bank.

15 Banking system, https://www.classle.net/projects/node/1512 (By www.classle.net 12/22/2013)


12

2.1.2 Deposit Money

To depose money the major criteria is having book account. The customer takes a deposit slip

and enters:

Her/his name

The date

The account number

The amount to deposit both in words and numbers.

Then, the customer would sign in the slip and take it to the teller along with her/his account

book and the money. The teller will process the deposit and give the account book to the

customer after updating the amount of money in the account book.

2.1.3 Withdraw Money

The customer takes a withdrawal slip and enters:

Her/his name

The date

The account number

The amount to withdrawal both in words and numbers.


book. The teller will process the withdrawal and give the money and the account book to the

customer.

2.1.4 Transfer Money

The customer takes a transfer slip and enters:

Her/his name

The date

The account number

The amount to transfer both in words and numbers.

The receiver account number and address.


book. The teller will process the transfer and while processing if the amount of money set to

transfer is greater than the deposit money in the sender account the transaction will not be

performed, else the transaction processed. If the money to be transferred is less than 3000, the

teller processes the transfer. But if it is greater than 3000 birr, then the manager need to sign

on the slip first. After that the teller will transfer the money.


13

2.1.5 Check

A check tells the bank how much money the customer wants to transfer, when to transfer it,

and to whom the customer wants to pay.

A check should contain:

Address: address should be pre-printed on the check.

Date Line: write the date that you write the check.

Payee Line: write the name of the person to whom the check is for.

Amount Filed: write the amount of the check in numbers.

Memo Line: write the purpose of the payment.

Signature Line: sign your signature.

After the customer fill out this things he/she will give it to the receiver. The receiver takes it

to the bank and gives it to the teller. Then the teller will check number for check card

transaction, date of the check, the individual who the payment was for, the amount of the

payment, the balance of the customer account. If all things are correct the teller debit amounts

from the previous balance and add credit amounts to the receiver balance.

The drawbacks of the traditional banking system is it needs more man power; it is time

consuming; it consumes large volume of paper work; it also needs manual calculations;

there is no direct role for the customers or in other words, customers does not manage their

money directly; and customers do not get service in non regular business hours and holidays.

2.2 Proposed system

Overview

The aim of proposed system is to develop a mobile banking system for bunna bank. The

proposed system can overcome most of the limitations of the existing system. The system

provides proper security and reduces the manual work.

The proposed system has the ability to give most of services that is given in the existing

system using a mobile device. Customers can transfer money from their account to others,

they can pay bill after registering to the organization, check their account balance, show

transaction history, and change their password. It is also possible for blind persons to use this

application with the help of IVR that integrated in the system.


14

Bunna bank deploys the mobile banking application (MBunna app) to customers mobile, and

signing it with customers unique SIM and gives username and password to access their

account remotely. Mobile clients of this system are required to be registered to mobile

banking application service to use this application in their mobile phones. The banks server is

connected to customers mobile to answer the requests and transactions performed remotely.

Bank server has stored information to keep necessary data about customers profile.

The MBunna application can be used as a normal banking method instead of going to the

bank. MBunna application is protected using mobile user unique user name and passwords

and operations like bill payment and transfer require PIN confirmation to perform the

transaction. Every time payment or transfer transactions performed, synchronization on

banks database is performed.

MBunna has a Downloadable application that allows the customer to download MBunnas

Mobile Banking Application. It is for customers who have a smart mobile apparatus which

allows downloading the mobile banking application.

If the customers handset cant support the downloadable app they can get MBunnas service

using a browser. In this case customers need to have a mobile handset that supports an

internet browser so that she/he can access the URL of mobile banking service.

MBunna application also supports Short Message Service (SMS). SMS shall mean a text

messaging service component of phone; using standardized communications protocols that

allow the exchange of short text messages. For the purpose of this procedure SMS mobile

banking is applicable for all mobile phones that can send and receive SMS.

2.2.1 SMS (Short Message Service) Mobile Banking

The SMS mobile banking supports the following functionalities:

Check Balance: this allows viewing a real time account balance.

Account History: allows viewing the last six transactions.

Transfer Money: allows transferring money from one own account to another account.

Changing PIN: allows PIN changing.

Help: list all commands that customer can use to perform mobile banking service in SMS

mobile banking.


15

2.2.2 Internet Browser Mobile Banking

The internet browser mobile banking supports the following functionalities:


Account History: allows viewing the last ten transactions.




mobile banking.

2.2.3 Downloadable Mobile Banking

The downloadable mobile banking supports the following functionalities:


Account History: allows viewing the last six transactions.




mobile banking.

Mobile banking service process

1. The CSO (Maker) guides the customer to mobile banking application form.

2. The CSO (Maker) verifies if the applicant is account holder of the bank, and if not, will

ask the applicant to open account, which shall be linked to mobile banking service.

3. The CSO (Maker) verifies the customers signature on the application form, and makes

the customer sign on the terms and conditions.

4. The CSO (Maker) extracts corresponding customer ID and account number from the

database and fills it on the application.

5. The CSO (Maker) registers the customer information including her/his mobile phone

number, and the security question and answers into the mobile system and forwards the

application form to the CSO (Checker).

6. The CSO (Maker) provides the user guide to the customers and informs the customer that

mobile banking services will be activated within three days.


16

7. The CSO (Checker) checks that all requirements and the detail in the application form

have been correctly completed and forwards the application to the Customer Service

Manager (CSM).

8. The CSM completes the applications summary form based on the customer applications

and forwards to the branch controller.

9. The Branch Controller makes sure that all details including customers ID and account in

the application form and applications summary form have been correctly completed

before it delivered to the higher office.

10. The branch controller forwards the application summary to the higher office.

Application Processing at Higher Office

1. The CSO checks the completeness of Applications Summary submitted from the

branches.

2. The CSO searches the customer information using primary key of mobile phone number,

and links or map the customer ID with the MBunna application and forwards the

application summary form to the controller.

3. The CSO forwards the verified and authenticated lists of customers for mobile service

activations to the branch CSO.

Mobile Banking Service Activation at Branch

1. The CSM contacts customer to activate her/his mobile banking services immediately after

receiving customers list from the Higher Office.

2. The CSM deliver the activation code and user guideline to the customer.

Change of Mobile Phone Number

When the customer changes her/his mobile phone number, she/he shall appear in person to

the branch and request mapping of his new phone mobile number to the mobile banking

service.

1. The CSO (Maker) guide the customer to fill the application for changing of mobile

number.

2. The CSO (Maker) identifies the customers and verifies the signature of the mobile

number change application form.


17

3. The CSM verifies the customer based on the security questions and checks that all

requirements and the detail in the mobile phone number change application form have

been correctly completed and forwards the application to the CSO (Maker).

4. CSO (Maker) register the new mobile phone into MBunna application by editing the

existing mobile number, and forwards the application form to the CSM.

The system is very simple in design and to implement. The system requires very low system

resources. It has got the following features:-

Security of data

Ensure data accuracys

Minimize manual data entry

Minimum time needed for the various processing

Better service

User friendliness and interactive

Business Rule of the proposed system

1. Maximum daily fund transfer to predefined beneficiary shall be Birr 25,000.

2. Maximum daily fund transfer to own account shall be unlimited.

3. Maximum daily fund transfer to another Buna Bank account holder shall be Birr 25,000.

4. Customers can make transfers/payments till their account balance available is greater than

25 birr.

5. When a customer forgets his/her pin, she/he shall appear in person to the branch and

present PIN resetting request.

6. Entering the wrong PIN three times will block the Buna m-banking service facility for the

day and two such consecutive blockages will de-activate the customer account and the

customer should reregister for the facility as per the procedure laid for the same.

7. When a customer changes her/his mobile phone number, she/he shall appear in person to

the branch and request mapping of his new mobile phone number to the mobile banking

services.

8. The bank may terminate or suspended the services under the facility without prior notice

if the customer has violated the terms and conditions lay down by the bank or on the

death of the customer when brought to the notice of the bank.


18

2.3 System Requirement

2.3.1 Non functional requirements

A non-functional requirement is a requirement that specifies criteria that can be used to judge

the operation of a system, rather than specific behaviors. It defines how a system is supposed

to be. Non-functional requirements are often called qualities of a system.16

Response time: In order to meet clients satisfaction the system use a fast internet to

perform the required banking system in 6 second response time and with maximum

throughput. The application may give us an error message Bad connection when

loading takes too long. This is an expected error message by the application.

Performance: The memory used to deploying and while performing the system in

clients mobile need not be excessive.

Security: Security requirements are important factors in this system as classified data

will be stored in the database. User validation done during login to insure that the user

is valid and that the user only has access to his/her permitted data. A confirmation

request should be applied for authentication of every transaction. Also the system uses

an HTTPS to communicate with the server.

User friendly interface: The system will have consistent interface formats and button

sets for all forms in the application. It will be user friendly.

Ease accessibility: Mobile banking is easily accessible. Mobile Banking will put

customers important, real-time banking details right in their hand wherever they are

letting the customer manage, move and monitor their money from their phone.

Maintenance: MBunna application should be easily modifiable to make changes to

the features and functionalities like if the rule of the bank changes the system should

give the capability to modify the previous rule.

Extensibility: MBunna application can be easily extensible to add new features at a

later stage like check service.

The system should be accurate, complete and consistence. On the other hand, the

documentation should be attractive, easy to give information and it should contain complete

information.

16 Non functional requirements, http://en.wikipedia.org/wiki/Non-functional_requirement (By

Wikipedia 12/22/2013 )


19

2.3.2 Functional requirements

Functional requirement defines a function of a system or its component. Functional

requirements may be calculations, technical details, data manipulation and processing and

other specific functionality that define what a system is supposed to accomplish. Generally,

functional requirements are expressed in the form "system must do ".17

Functionalities of MBunna application:-

Check Account Balance: This allows the customer to view a real time account balances.

Fund Transfer: This allows the customer to transfer money from his own account to other

accounts.

View Transaction History: allows viewing the transactions history or statements the

customer made previously.

Manage Account: This allows the customer to view his profile and change his password.

Manage Contact: allows the customer to add contacts, delete and view contact from its

account list.

Manage Customer Account: This allows the CSO to register, edit and view details of

customers for MBunna application.

Manage Customer Security: This allows the CSO to add, delete and view customers

account.

View Currency Exchange: This includes currency information.

2.3.3 Use case Diagram

Use case is a list of steps, typically defining interactions between an actors and a system, to

achieve a goal. The actor can be a human or an external system.

Actors

Customer: the client of the bank that use the application.

CSO: employee of the bank who manages customer account.

CSM: manager of the bank who control the CSO.

17 Functional requirement, http://en.wikipedia.org/wiki/Functional_requirement (By Wikipedia

12/22/2013 )


20

Use case diagram

Figure 3 Use case diagram for Mobile Banking Application

2.3.3.1 Use case Documentation

MBunna Application: Login Use case Process Flow

Use Case Name: Login

Actors: Customer

Description: Authenticate to mobile Banking application.

Trigger: The Customer launches the application.

Preconditions: 1. The application is launched.

2. The Customer must have an activated user


21

name and password.

Post conditions: The application main menu is loaded.

Normal Flow:

1. The Customer runs the application.

2. The application prompts the customer to

insert user name and password, and account

number.

3. The customer enters the user name and

password followed with activated bank

account number.

4. The application verifies the specifications and

main menu is loaded.

Exceptions:

3a.If the Customer insert invalid user name or

password or account number

1. The application prompts the customer to

insert correctly (less than 4 times)

2. The customer inserts invalid entry.

3. The application terminates process and

deactivates the login form.

Table 1 Description of Login Use Case Process Flow

MBunna Application: See Profile Use case Process Flow

Use Case Name: See Profile

Actors: Customer

Description: A Customer sees profile (name, account

number, gender, etc) in the application.

Trigger: The Customer presses the SEE PROFILE

button.


22


2. The Customer has login and main menu

is loaded.

Post conditions: Personal profile displayed to the Customer.

Normal Flow: 1. The user presses the SEE PROFILE

button.

2. The application displays the Customer

profile with not editable format.

Table 2 Description of See Profile Use case Process Flow

MBunna Application: Change Password use case Process Flow

Use Case Name: Change Password

Actors: Customer

Description: Customer set a new PASSWORD for the

application.

Trigger: The Customer presses the CHANGE

PASSWORD button.



is loaded.

Post conditions: Customer will get a new Password.

Normal Flow: 1. The Customer presses the Change

Password button.

2. The application with a fill interface

prompts the customer to insert the old

PASSWORD and the new PASSWORD

and ask to re-type.

3. The customer inserts the previous


23

PASSWORD, the new PASSWORD and

type again to confirm.

4. The application validates the old

PASSWORD and check the confirmed

PASSWORD.

5. The Customer presses SAVE button.

6. The Application saves the PASSWORD.

Exceptions:

3a. If the customer enters an invalid old

PASSWORD.

1. The change is disapproved

2. Message to customer to re-enter old

PASSWORD

3. The application resumes on step 2 of

normal flow

3b. If the customer re-types an invalid new

PASSWORD.


2. Message to customer to re-enter

PASSWORD


normal flow

3c. If the customer inserts characters that

does not include capital letters, small letters,

number and symbols for the new

PASSWORD.


2. Message to customer to include capital

letters, small letters, number and symbols


normal flow

Table 3 Description of Change Password use case Process Flow


24

MBunna Application: Check Balance Use case Process Flow

Use Case Name: Check Balance

Actors: Customer

Description: A Customer sees account balance in the

application.

Trigger: The Customer presses the CHECK

BALANCE button.



is loaded.

Post conditions: The customers account balance will be

displayed in the screen.

Normal Flow: 1. The Customer presses the CHECK

BALANCE button.

2. The application displays the Customer

account balance in the mobile phone

screen.

Table 4 Description of Check Balance Use case Process Flow

MBunna Application: Fund Transfer use case Process Flow

Use Case Name: Fund Transfer

Actors: Customer

Description: Customer wants to make transfer to another

account.

Trigger: The Customer presses the FUND

TRANSFER button.


25



is loaded.

Post conditions: Customer account balance is reduced by the

amount of the transfer and added to the

receivers account.

Normal Flow: 1. The Customer presses the FUND

TRANSFER button.

2. The application prompts the Customer to

insert the amount of money and

receivers account number.

3. The Customer insert amount of money to

transfer and receivers account number.

4. The database checks available

Customers account balance.

5. The application checks the recipient

account availability.

6. The Customer presses the send button.

7. The application prompt Customer to

verify the PASSWORD.

8. The application sends the specified

amount to recipient and sends a delivery

report to the Customer.

9. The application updates the balance to the

sender and recipient bank account.

Exceptions: 4a.If the user account balance is not

sufficient

1. The transaction terminated.

2. The application notifies the Customer that

he/she have inefficient account balance.

3. The application resumes from step 2 in


26

normal flow.

5a.If the recipient account is not available

1. The application notifies the Customer the

specified recipient account is not valid.

2. The application prompt to insert a valid

recipient account number (less than 4

times)

3. The Customer inserts not valid recipient

account number.

4. Transaction is terminated.


normal flow.

7a. The verified PASSWORD is not valid

1. The application prompt to inset a valid

PASSWORD (less than 4 times)

2. The Customer inserts not valid

PASSWORD.

3. The application terminates transaction.


normal flow.

Includes: Synchronies Balance

Table 5 Description of Fund Transfer Process Flow

MBunna Application: View Transaction History Use case Process Flow

Use Case Name: View Transaction History

Actors: Customer, CSO

Description: A user can check his/her transaction log or

activity made in different time intervals, see a

time managed transaction history.


27

Trigger: The user presses TRANSACTION

HISTORY button.



is loaded.

Post conditions: The log of previous transactions is displayed

for user.

Normal Flow: 1. The user presses TRANSACTION

HISTORY button.

2. The application list transaction histories.

Table 6 Description of View Transaction History Use case Process Flow

MBunna Application: Add Contact Process Flow

Use Case Name: Add contact

Actors: Customer

Description: Customer saves contact information those

he/she make transfer frequently

Trigger: Customer presses ADD CONTACT button

Preconditions: The application is launched. The Customer

has login and main menu is loaded.

Post conditions: The Customer saves the contact and adds to

the application contact list.

Normal Flow: 1. The Customer presses the ADD

CONTACT button.

2. The application prompt to insert new

contact detail and account number.

3. The Customer inserts the new contact


28

detail.

4. The application check if the contact does

not exist then adds to contact list.

Exceptions: 4a. If the application found the contact

already exist


contact already exists and asks to replace

contact.

2. The Customer cancels or approves the

operation.

3. The application resumes from step 2 of

the normal flow.

4b. If the contact account is not available

(invalid)


specified contact account is not valid.

2. The application prompt to insert a valid

contact account number (less than 4

times)

3. The Customer inserts not valid contact

account number.

4. Operation is terminated.


normal flow.

Includes: Check contact

Table 7 Description of Add Contact Process Flow

MBunna Application: Delete Contact Process Flow

Use Case Name: Delete Contact

Actors: Customer


29

Description: Customer delete contacts from its contact list

Trigger: Customer presses DELETE CONTACT

button



Post conditions: The Customer deletes the contact from

contact list.

Normal Flow: 1. The Customer presses the DELETE

CONTACT button.

2. The application prompt to choose

contact.

3. The Customer chose the contact.

4. The application removes the contact the

contact list.

Table 8 Description of Delete Contact Process Flow

MBunna Application: View Contact Process Flow

Use Case Name: View contact

Actors: Customer

Description: Customer sees contacts information which

found on his/her contact list.

Trigger: Customer presses VIEW CONTACT button



Post conditions: The Customer sees the contact information.


30

Normal Flow: 1. The Customer presses the VIEW

CONTACT button.

2. The application display contacts detail.

Table 9 Description of View Contact Process Flow

MBunna System: Login Use case Process Flow

Use Case Name: Login

Actors: Administrator, Customer Service Officer (CSO)

Description: Authenticate to mobile Banking system.

Trigger: The Customer launches the system.

Preconditions: 1. The system is launched.

2. The user must have an authorized user name

and password.

Post conditions: The application main menu is loaded.

Normal Flow:

1. The user runs the system.

2. The system prompts the user to insert user

name and password.

3. The user enters the user name and password.

4. The system verifies the specifications and

main menu is loaded.

Exceptions: 3a.If the user insert invalid user name or password

1. The system prompts the user to insert

correctly.

2. The system resume to step 2 in normal form

of the process flow

Table 10 Description of Login Process Flow


31

MBunna system: Customer Registration use case process flow

Use Case Name: Register Customer Account

Actors: Customer Service Officer (CSO)

Description: The CSO registers the customer in the Bank

customer service list.

Trigger: The CSO presses the REGISTER button.

Preconditions: 1. The user must be customer of the bank.

2. The application is launched.

3. The CSO has login and main menu is

loaded.

Post conditions: Customer has been added in customers

account list.

Normal Flow: 1. The CSO presses the REGISTER button.

2. The system allows the CSO to select

account type as single user or

organizational user.

3. The system accepts the selected choice.

4. The system displays registration form.

5. The CSO fills the form.

6. The CSO submits the form.

7. The system validates for complete and

appropriate form data.

8. The system checks duplication for

customer data.

9. CSO save customer data

Exceptions: 5a. if the CSO do not fill all the required

fields

1. Message to CSO to fill the required fields


32

of the form.

2. The system goes to step 4 having no

change with the filled fields of the form.

8a. if there is a duplication

1. Message to CSO customer already exist


change with the filled fields of the form

Table 11 Description of Customer Registration use case process flow

MBunna system: Edit Customer Account use case process flow

Use Case Name: Edit Customer Account

Actors: Customer Service Officer (CSO)

Description: The CSO edits the customer in the Bank

customer service list.

Trigger: The CSO presses the EDIT CUSTOMER

ACCOUNT button.



loaded.

Post conditions: Customers information has been edited in

customers account list.

Normal Flow: 1. The CSO presses the EDIT CUSTOMER

ACCOUNT button.

2. The system displays edit form.


4. The CSO submits the form.


appropriate form data.


33

6. The system checks duplication for

customer data.

7. CSO update customer data.

Exceptions: 5a. if the CSO do not fill all the required

fields


of the form.



8a. if there is a duplication

1. Message to CSO customer already exist


change with the filled fields of the form

Table 12 Description of Edit Customer Account use case process flow

MBunna System: Create Account use case process flow

Use Case Name: Create User Account

Actors: Administrator

Description: CSO change default account and create one

supper admin account and gives privilege for

managing other user accounts.

Trigger: The CSO presses the CREATE ACCOUNT

button.



loaded.

Post conditions: CSO creates and gives authentication for

users.


34

Normal Flow: 1. The CSO presses the CREATE

ACCOUNT button.

2. The system allows the CSO to select

account status.

3. The system accepts the selected choice.

4. The system gives account privileges for

the selected user type.

5. The system displays account registration

form.


7. The system allows the CSO to submit the

form.


appropriate account creation.

9. The system checks duplication for user

account.

10. The system notifies successful

registration.

11. The system display user account

information.

Exceptions: 6a. If the CSO do not fill all the required

fields


of the form.



9a. If the system gets duplication of user

name

1. System announces duplication of user

name.

2. The system suggests the CSO to change


35

user name.


change with the previous filled fields of

the form.

Table 13 Description of Create Account use case process flow

MBunna System: Delete Account use case process flow

Use Case Name: Delete User Account

Actors: CSO

Description: CSO deletes other users account.

Trigger: The CSO presses the DELETE ACCOUNT

button.



loaded.

Post conditions: The user account will be deleted from the

database.

Normal Flow: 1. The CSO presses the DELETE

ACCOUNT button.

2. The system allows the CSO to insert

account number for searching.

3. The system accepts the inserted account

number.

4. The system displays customer profiles

5. The CSO deletes the user account.

Exceptions: 2a. If the CSO do not insert a valid account

1. Message to CSO to insert valid account

number


36

2. System goes to step 2 in normal flow of

the process flow.

Table 14 Description of Delete Account use case process flow

MBunna System: View User Account use case process flow

Use Case Name: View User Account

Actors: CSO

Description: CSO sees users account information which

found on his/her account list.

Trigger: CSO presses VIEW USER ACCOUNT

button

Preconditions: The application is launched. The CSO has

login and main menu is loaded.

Post conditions: The CSO sees the user account information.

Normal Flow: 1. The CSO presses the VIEW USER

ACCOUNT button.

2. The application display users account

detail.

Table 15 Description of View User Account use case process flow

MBunna System: Approve Customer use case process flow

Use Case Name: Approve Customer

Actors: CSM

Description: CSM approves the customer registration, the

customer security account and money

transfer.


37

Trigger: CSM presses APPROVE CUSTOMER

button.

Preconditions: The application is launched. The CSM has

login and main menu is loaded.

Post conditions: The CSM approves or reject the customer

registration, the customer security account

and money transfer.

Normal Flow: 1. The CSM presses the APPROVE

CUSTOMER button.

2. The system allows the CSM to choose a

service from customer registration, the

customer security account and money

transfer.

2.1.If customer registration is chosen, then an

interface to approve customer registration

is displayed.

2.2.The CSM get accept and reject button for

each customer to be registered.

2.3.If customer security account is chosen,

then an interface to approve customer

security account is displayed.

2.4. The CSM get accept and reject button

for each customer to be approve changes

in customers account (i.e. username &

password).

2.5.If money transfer is chosen, then an

interface to approve money transfer is

displayed.

2.6.The CSM get accept and reject button for

each transfer to be approved or not to be


38

approved

Exceptions: 2.5a. The money transfer approval message

displayed to the CSM only if the transferred

money is more than 3000 birr.

Table 16 Description of approve customer use case process flow

2.3.4 Object Model

2.3.4.1 Sequential Diagram

A sequence diagram is an interaction diagram that shows how processes operate with one

another and in what order. It is a construct of a Message Sequence Chart. A sequence

diagram shows object interactions arranged in time sequence. It depicts the objects and

classes involved in the scenario and the sequence of messages exchanged between the objects

needed to carry out the functionality of the scenario. 18

MBunna: Mobile banking system

Figure 4 Sequence Diagram for login

18Sequence diagram http://en.wikipedia.org/wiki/Sequence_diagram (By wikipedia)


39

Figure 5 Sequence Diagram for View Profile

Figure 6 Sequence Diagram for Transaction history


40

Figure 7 Sequence Diagram for Fund Transfer

Figure 8 Sequence Diagram for Add Contact


41

Figure 9 Sequence Diagram for Customer Registration

Figure 10 Sequence Diagram for Create account


42

Figure 11 Sequence Diagram for Delete account

Figure 12 Sequence Diagram for Change password


43

Figure 13 Sequence Diagram for Query balance

Figure 14 Sequence Diagram for create contact


44

Figure 15 Sequence Diagram for Delete contact

2.3.4.2 Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities and

actions with support for choice, iteration and concurrency. In the Unified Modeling

Language, activity diagrams are intended to model both computational and organizational

processes (i.e. workflows). Activity diagrams show the overall flow of control.19

MBunna: Mobile banking system

Figure 16 Activity Diagram for login

19 Activity diagram http://en.wikipedia.org/wiki/Activity_diagram ( By wikipedia )


45

Figure 17 Activity Diagram for View Profile

Figure 18 Activity Diagram for Transaction history


46

Figure 19 Activity Diagram for Fund Transfer

Figure 20 Activity Diagram for Add Contact


47

Figure 21 Activity Diagram for Customer Registration

Figure 22 Activity Diagram for Create account


48

Figure 23 Activity Diagram for Delete account

Figure 24 Activity Diagram for Change password


49

Figure 25 Activity Diagram for Check balance

2.3.4.3 Collaboration Responsibility class (CRC) model

A Class Responsibility Collaborator (CRC) model is a collection of standard index cards that

have been divided into three sections, those sections are, class: represents a collection of

similar objects, responsibility: is something that a class knows or does, and collaborator: is

another class that a class interacts with to fulfill its responsibilities.

Customer

Responsibility Collaboration

CustomerID

Account number

Account

Contact

Transfer

User

Table 17 Description of collaboration of customer class

Customer Service Officer (CSO)



50

Customer

Account

User

Table 18 Description of collaboration of customer service officer class

Transfer


TransferID

TransferDate

TransferAmount

Customer

Account

Contact

Table 19 Description of collaboration of transfer class

2.3.5 Class Diagram

A class diagram in the Unified Modeling Language (UML) is a type of static structure

diagram that describes the structure of a system by showing the system's classes, their

attributes, operations (or methods), and the relationships among the classes.20

20 Design Goals, http://msdn.microsoft.com/en-us/library/aa291862%28v=vs.71%29.aspx (By

microsoft12/25/2013 )

Figure 26 a Conceptual class diagram for mobile banking application

2.3.6 User Interface

MBunna mobile banking application has user friendly user interfaces for users ease

interaction and understanding to perform banking from their mobile phone. There are eight

services in the System in addition to Help. The overall structure of the application is

relatively simple, as shown in the following diagram.

Figure 27 Showing the structure and navigation of the Interfaces

A mobile user can have several operations to do. Bellow is listed s

mobile banking for bunna international bank last

Documents

dawit gezahegn signature

kidus hmichael signature

solomon demissie signature

yohannes alemu signature

jiya department

michael shiferaw msc

os department

university advisorsupervisors