Introduction

Banking is becoming a more and more technology savvy industry largely due to
mobile technologies. According to a survey by Statista, the number of mobile users
is steadily growing. The number of people using banking is also progressive. So,
this is the main factor that determine the need for developing our Get-save app.

Purpose

Project Scope
Our app has full functionality that mobile banking has. And in addition, the
application can connect all of the banks and any transaction is conducted on any
bank as if the user has account on that bank. This mobile app is used by a user to
depose, transfer, withdraw(cash) balance from any bank to other banks even a user
has no bank account on other bank. i.e. a user having bank account on commercial
bank can operate any kinds of transaction on other private banks and vice versa.

Overall Description:
2.1 product perspective

Banking system is one of the most important and basic need for our country to contribute a lot in
economy sector. In current existing system of banking, the users to use online transaction they
need to have bank accounts in the same bank to perform transactions. To save money the user
must go on their bank account existing banks or agents. The process should be requiring many
security issues. The net banking process can take more time. most of banking transactions
process are done during bank working time. Due to this, the service is limited with time. In
addition to that It does not provide direct transactions from one bank to another bank.

Diagram of current banking System

The proposed system introduces multibanking system. These application helps users to save their
time and use all features that are available in all bank. The bank users able to make online
transaction with all banks using his bank account. Any kind of transactions are maintained by the
system. This system will act like a mediator between banks and users and a mediator between
one bank with other banks. The system works in cooperation with the existing banking system.
Users can maintain single username and password and contact only one customer care service for
any problems.

Diagram of the proposed System.

2.2 product functions
The main purpose of multi banking System is to inter connect banks and facilitate the bank
transaction. And in order to improve saving culture and enable the users to save, transfer, and
withdraw money any time anywhere. The System enables, saving, transfer, withdraw, view
balance based on parameters submitted by the user.

To transfer the required parameters are: -

 Multi banking Account number of sender

 Multi banking Account number of receiver
 Sender password
 Amount

To save the required parameters are: -

 Multi banking Account number of agent

 Multi banking Account number of saver
 Agent password
 Amount

To cash with draw the required parameters are: -

 Multi banking Account number of withdraw requester

 Multi banking Account number of agent
 withdraw requester password
 amount

To view balance, the required parameters are: -

 Multi banking Account number

 password

The System also controls the user status based on specific parameters, including
  Current password
 Account number of the user

In general system should embody the following features and functions:

 Should be dynamic, not static.

 Should able to perform view balance, saving, transfer, withdraw according to user
‘s option.
 Should provide administrative security
 Should ideally provide a GUI for all components, such as for users to submit
request.
 Should give transaction history for users.

2.3 User classes and characteristics

The possible user class in this system are: -

Bank customers
Frequency of use-: user class is the most common one as it is the one most often used as during
the usage of the system, specially to get services from system will have to be logged onto the
application in order to use the systems features like view balance, transfer, save and withdraw
and can see their transaction history.

Technical Expertise:

The users should know the basic operation of mobile.

• Privilege Levels: the customer of the bank have the following privileges

 View balance: By using this functionality user can view their balance.
 Transfer Amount: By using this functionality user can transfer money from his
account to other accounts of same bank or other banks.
 Transaction Reports: By using this functionality user can get all his transaction
reports.
Bank accountants
Frequency of use: register their user to mutibanking system.
Technical Expertise: Knowledge of computer.
Privilege Levels: add his bank users to the multibanking system.

2.4 General constraints

The constraints of our system includes the internet access to log in to the system and perform the
appropriate actions. the actions may be save, transfer, withdraw and view balance. The network
is running windows server operating system. For testing purposes, a simulating tool needs to be
used which may have to be specially designed if a generic one is not readily and
freely available.

2.4 user documentation

There must be a user manual for administration, configuration and usage of system. The manual
is better to be digitalized. The system should be preferable in the ease of use and all document
need to be easy to understand by document audience.

2.4 Assumption and dependency

 There may be failure of network connection
 The workability of the system should be assumed in the perspective of customers and
Banks.

Specific Requirements
This section contains all of the functional and quality requirements of the system. It
gives a detailed description of the system and all its features. In software
development phase requirement specification is the main activity that should be
done. Requirement specification is an agreement between the end user and the
system developer.
 User Requirements
User requirement is a document that defines what a multiBanking system
must be able to solve the problems which defined by potential users of the
system. These requirements are classified into functional requirement and
non-functional requirements. The user requirements specification should be
independent of any solution-oriented bias and must use terminology from
the problem domain of the users.

3.1.1. Functional User Requirements

These requirements describe the interactions between the system and its environment. The
environment includes the user and any other external system with which the system interacts.
This requirement document is prepared with some balance of scope, time, cost and quality
considerations. Operations of the system, which can be realized under the time and resource
limits, are included in the requirements document. This section is organized by the processes and
features encapsulated in multi banking System. The system should provide what the system
should react to particular inputs, and how the system should behave in particular situations. It
specifies the software functionality that the developers must build into the product to enable
users to accomplish their tasks. The system functional requirement grouped in to bank user,
system administrator and any bank. Functional requirements that must be included in the system
are listed below:

System Administrator functional requirement

Requirement ID REQ-1

Requirement The system shall allow multi banking administrator to create

new user account.

Description

Source
Priority
Related
Requirements

Requirement ID REQ-2

Requirement The system should allow multi banking administrator to login to

the system using his/her username and password.

Description

Source

Priority
Related
Requirements

Requirement ID REQ-3

Requirement The system shall allow multi banking administrator to change

password.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-4

Requirement The system shall allow multi banking administrator to view all
transaction.

Description

Source

Priority
Related
Requirements

Requirement ID REQ-5

Requirement The system shall allow multi banking administrator to logout.

Description

Source

Priority
Related
Requirements

…
Bank customer functional requirement
Requirement ID REQ-6

Requirement The system should allow customers to login to the system using
his/her account number and password.

Description

Source

Priority
Related
Requirements

Requirement ID REQ-7

Requirement The system shall allow the user to view balance.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-8

Requirement The system shall allow the user to transfer money to in the
same bank account.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-9

Requirement The system shall allow the user to transfer money to other
bank account.

Description

Source

Priority
Related
Requirements

Requirement ID REQ-10
Requirement The system shall allow users to withdraw.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-11

Requirement The system shall allow users to deposit.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-12

Requirement The system shall allow users to view his recent transaction
history

Description
Source

Priority
Related
Requirements

…
Requirement ID REQ-13

Requirement The system shall allow users to logout.

Description

Source

Priority
Related
Requirements

Agents
Requirement ID REQ-14

Requirement The system shall allow agent to login.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-15

Requirement The system shall allow agent to cash money to multibanking

customers.

Description

Source

Priority
Related
Requirements

Requirement ID REQ-16

Requirement The system shall allow agent to deposit Multibanking

customer’s money

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-17

Requirement The system shall allow agents to logout.

Description

Source

Priority
Related
Requirements

Bank functional requirement

Requirement ID REQ-18

Requirement The system shall allow the bank to integrate to our platform.

Description

Source

Priority
Related
Requirements

…
Requirement ID REQ-19
 Requirement The system shall allow the banks to register their customers
to our platform

Description

Source

Priority
Related
Requirements

3.1.2. Non -Functional Requirements

Non-functional requirements are requirements about how system should behave while
performing operations. They are related to the product of system properties and qualities. This
are constraints on the services which the system is offering. for example, timing of operation,
way to response in particular condition. The non-functional requirements which concerned in
this system are listed below: -

Requirement Id NFREQ-1
Requirement Usability
Description The multi banking System should provide a help
and support menu in all interfaces.
The system should be easy to use for customers of
the system.
The user of system should be satisfied after using
multi banking system.
The system should be consistence
Source Developer
Priority High

Requirement Id NFREQ-2
Requirement Performance
Description The system should response each instruction
conducted by the user fast as much as possible
The system should response the tasks in few
resources wasted.
Generally, our system should be efficient.
Source Developer
Priority High

Requirement Id NFREQ-3
Requirement Reliability
Description The System should not fail more than 30
minutes in 24 hours.
The System should be easily recoverable.
The System should be accurate.
The multibanking system must do what users
supposed to do.
Source Developer
Priority High

Requirement Id NFREQ-4

Requirement Availability

Description The multi banking system should be available

24 hours a day in 7 days a week

The System should be accessed in any device

 that the user wants to use.

The System should be accessed via internet or

its own Network

Source developer(network admin)

Priority High

Requirement Id NFREQ-5

Requirement Portability

Description The System Should be platform Independent.

It can be accessed by any browser Mozilla,
chrome or internet explore

Source Developer

Priority High

Requirement Id NFREQ-6

Requirement Security

Description The system should have username and

password to prevent from unauthorized access.

The system should use encryption

The system should Identify client side and

server side uses

Source Developer

Priority High
Requirement Id NFREQ-7

Requirement Maintainability

Description The System should be Maintained by well-

trained technicians.

The users report the problems of the System in

space provided in the interface after using and
the System can be maintained by technicians.

3.2 System requirement

System requirements are detail of functional and non-functional requirements written for
developers. They must be specified clearly and rigorously. for example, when the user selects an
icon representing an external file the effect of the selection is to apply the tool associated with
the type of external file to the file represented by the selected icon. The system requirements will
be developed through object oriented analysis and design methods by the use of UML model
language

3.2.1 Use case diagram

A use case is a description of how a person who actually uses that process or system will
accomplish a goal. Or it can be defined as a methodology used in system analysis to identify,
clarify, and organize system requirements. The use case is made up of a set of possible sequences
of interactions between systems and users in a particular environment and related to a particular
goal. A use case diagram is a sequence of actions that provide a measurable value to an actor so
it is the best way to capture the functional and non-functional requirements of the system. Use
case diagram components are actors, use cases and system boundary.
4 External interface Requirement
This section provides a detailed description of all inputs into and outputs from the system. It also
gives a description of the hardware, software and communication interfaces and provides basic
prototypes of the user interface. External requirement defines the interaction points between a
system and entities that communicate with the system. Specific areas of interest include user
interfaces, hardware interfaces, software interface and communication interface

interfaces.

4.1 User Interfaces

The minimal requirements are that the user would have an account and would be able to interact
with the system through the application, or through the interface provided. There will be a
different command for each of the following actions. At a first time a user see operation lists and
perform his operation based on his interest. User interface to be designed must be developed in
such a way that the application is easy to understand the system. The system design must almost
be easy to
understand in where what features are located and how to use them. Sample user interface this
system are:-
 Multi Banking system

Register users

Account number

Bank name

Phone number

Register

4.2 Hardware Interfaces

Since the multi banking system is web based so there is no designate hard ware it does not have
any direct hard ware interfaces. The database and network connection is managed by the erver.

4.3 Software interfaces

The system communicates with Ethiopian tell communication server in order to verify the phone
number. In addition, communicate with banks servers to cross check the data. The
communication between the database and the web consists of operation concerning both reading
and modifying the data.

4.4 Communications Interfaces

The communication between the different parts of the system is important since they depend on
each other. This system allows users to communicate using send and receive request form.
However, in what way the communication is achieved is not important for the system.

5. Analysis Models
It is a representation of a system that allows for investigation of the
properties of the system and,
prediction of future outcomes, such as activity diagram, sequence diagram.

5.1 Sequence Diagrams

A sequence diagram shows an interaction arranged in time sequence. In
particular, it shows the instances participating in the interaction by their
“lifelines” and the stimuli that they arranged in time sequence. It does not
show the associations among the objects. In our case we construct a
sequence diagram to show how processes operate with one another and in
what order for each use cases. It depicts how actors that are involved in the
scenario and the sequence of messages exchanged between them in the
sequential order that those interactions and involvement occur.
1 Login

2 view balance

3 transfer money

4 cash with draw

5 save money

6 Register users

7 logout

5.2 Activity Diagrams

An activity diagram is a variation of a state machine in which the states
represent the performance of actions or sub activities and the transitions are
triggered by the completion of the actions or sub activities. It represents a
state machine of a procedure itself.