CHAPTER ONE

INTRODUCTION

1.1 Introduction to Online Banking System

Online Banking System refers to systems that enable bank customers to Access accounts and
general Information on bank products and services through a personal computer or other intelligent
device. The chances and threats that the internet symbolizes is no longer news to the present day
banking sector. No traditional bank would dare face investment analysts without an Internet
strategy. The main intention behind the commencement of electronic banking services is to provide
the customers with an alternative that is more responsive and with less expensive options. With
options just a click away, customers have more control than ever. Their expectations are usability
and real-time answers. They also want personal attention and highly customized products and
services.

1.2 Background of Online Banking System

The precursor for the modern home online banking services were the distance banking services
over electronic media from the early 1980s. The term online become popular in the late ‘80s and
referred to the use of a terminal, keyboard and TV (or monitor) to access the banking system using
a phone line. “Home Banking” can also refer to use of a numeric keypad to send tones down a
phone line with instructions to the bank. Online Bank Services started in New York in

1981 when four of the City’s major banks (Citibank, Chase Manhattan, Chemical and Manufacturers
Hanover) over home banking services

1
With the advent of the Internet and Internet-related services, technological conveniences and
advances have somehow made their way into our daily lives and have now become a major part of
us. So, it comes as no surprise to us that the banking industry has also developed into a major
presence over the Internet as well.
With the increasing popularity of the internet, more and more industries are seeking ways to utilize
this popular medium in an effort to keep up with the changing technological preferences of their
customers. These days you can do just about anything online from grocery shopping to. The
possibilities of the internet are seemingly endless and the banking industry has decided that it will
not be left behind. While most people have at least heard of online banking, the majority of them
have probably not tried it yet. Maybe it's because we find more comfort in working with real people
and real paper when it comes to money matters rather than performing transactions in the seemingly
impersonal universe of the World Wide Web.

Some banking applications are available in the market. A considerable amount of research has been
done in past few months on this project. Many banks had migrated from paper based banking
system to electronic online banking. Each bank had its own, user friendly interface, which helps its
customers to interact with their account at their ease. A wide variety of Online Banking applications
are available in the market which in turn help the bank to function smoothly. All banks which are
using online banking application uses the same basic principle.

Axis Bank has excellent features, which allows customers to check their accounts and view their
statements. The best thing about this bank’s system allows us to schedule payments and do online
transactions. The security feature is the best; it gains the trust of the customer and allows them to
do their transitions in an efficient and secure manner. However, the interface is very complicated
for novice users. The interface for credit card customer is confusing Canara Bank One of the
finest bank of India, who perform their transactions online. The security issues are wonderful, and
it allows the customer to view their transactions, pay bills online, ATM/branch locator and provide

2
1.3 PROBLEM STATEMENT

The purpose of this project is to develop an on-line banking system that provides customers with

the facility to check their accounts and do transactions on-line. The system will provide all the

banks facilities to its customers when their authentications [user id and password] matches,

including viewing account information, performing fund transfers, giving the customer an option

of changing address, password retrieval, performing transactions, viewing transactions and locate

bank branches. The system allows and should allow customers to view their personnel accounts

and to pay bills online from their account. The system should assign a unique transaction number

to every transaction that a user makes.

The Administrator will administer both normal bank account. The administrator have the ability to

perform various operations like creating a normal bank account for the customer and performing

functions like transfers, withdrawals and deposits when the customers want teller transactions. The

administrator also has the privilege to close the customer’s account on the request of the bank

customer. The customer should be able to access his/her account from anywhere just by inputting

the correct user-id and password.

1.4 RESEARCH QUESTION

This study’s main questions include

A. Why Large Banks in the world prefer to migrate to online banking system.
B. How is the security threats in internet banking system
C. How most people dare to use online banking system instead of paper banking D. Is the reliability
of this system High or low

3
1.5 PURPOSE OF THE PROJECT

The main purpose for this study is to build online banking system that will assist people in

different locations of the world to access the bank and make their registrations as new customers.

1.6 PROJECT OBJECTIVES

A. To study how easier systems for online banking systems or other systems related operated.

B. To analyze, design and build online banking system.

C. To implement and test online banking system.

1.7 THE SCOPE OF THE PROJECT

This system is based on with use of internet technology that simplifies to serve the customers at any

time anywhere within the universe.

The scope of this project is limited to the activities of the operations units of the banking

system which includes opening of Account, Deposit of funds, Electronic funds transfer, and

balance.

4
1.8 SIGNIFICANCE OF THE PROJECT

The general importance of this study is to migrate from paper banking to online banking system

to shop online and easily access the bank every time anywhere. Indeed this system helps customers to

use a system that allows to pay bills, to transfer fund and access the bank account without going one of

the branches of the bank.

It also helps customers to get Monthly statement, request cheque and gives ability to access the easiest

and fastest way to the account.

1.8 PROJECT ORGANIZATION

Here we discuss chapters. The remaining chapters include Literature review, the next

chapters will be Requirement analysis, System design, System development and the final chapter is

Conclusion and recommendation.

5
 CHAPTER TWO

LITERATURE REVIEW

2.1 INTRODUCTIN

The literature review focuses on factors associates with high rates of readmissions of the Online

Banking System. The literature review is aimed at establishing what is already know about the

study topic and to identify gaps in the existing literature. In this chapter literature review is arranged

in Concepts, opinions or ideas from author/ experts, previous work/ existing systems,

Gap analysis and directions, Chapter Summary

2.2 CONCEPTS, OPINIONS, OR IDEAS FROM AUTHORS/ EXPERTS

The early version of what was considered online banking began in 1981. New York City in the U.S.A

was the first place to test out the innovative way of doing business by providing remote services as

four of its major banks-Citibank, Chase manhattan, Chemical bank and

Manufacturers Hanover – made home banking access available to their customers. Throughout online

banking history, customers have been slowly to adopt this new method of banking. In

6
1981 customers didn’t the new initiative, so the online banking system failed to gain momentum

until the next wave of innovation in the middle of 1990s.the conveniences of internet Banking

became obvious to many customers: online interest rates that were higher than those regular

banks, greater access to accounts and online banking transfer to name a few. Still other customers

were hesitant at first to use this new banking system because they were unsure of how it worked

and didn’t trust the security features of online banking.

As the evolution of online banking continued, it slowly began to gain popularity in e-commerce.

By 2000 online banking had become mainstream: an overwhelming 80 percent of banks in USA

were offering internet banking service. In 2001 Bank of America made History as the first

financial institute to gain more than 3 million online banking customers, about 20 percent of its

customer base.

The review revealed that most studies were not underpinned by a theoretical framework and the

commonly used theories which were adapted and extended by the researchers included TAM

(16.5%), DOI (2.7%), DTPB (2.7%), TRA (2.1%) and UTAUT (1.1%) (AbuShanab, Pearson and

Setterstrom, 2010; Sukkar and Hasan, 2005; Adesina and Ayo, 2010; Echchabi, 2011). Analysis

of the results for the African Continent shows that Nigeria has had a good number of research

articles in the area of EB and IB adoption-12 articles (6.4%) of all articles reviewed. Many

African countries have no research articles on IB at all and Africa continues to be the highly

under-researched continent in the area of information and communication technology and

information systems research as a whole (Mbarika and Okoli, 2005). This review therefore

justifies the existence of a research gap on the adoption and implementation of IB in many

African countries including Cameroon (0.5%) where the researchers are basing their ICT

research, which had just 1 article in the review. This research classification also considered the

work of Shao (2007) to focus on developing countries only and has shown that more research is

7
needed in the Caribbean, African and South American regions in the area of IB diffusion,

adoption and implementation

Online banking has become widespread in the world in recent years. Especially in Africa online

banking method is rare in only a few countries like South Africa, Egypt and Nigeria. The reason behind

how the population of the African Continent didn’t adopt online banking System so vastly is that: most

of the people don’t trust e-Banking System because their fear security threats of their accounts. There

is also another main reason that restricts some of the Customers to put their money on internet

accounts. That is internet accessibility, because Africa is not developed well in internet. Awareness of

online banking system is somehow a problem because majority of the people are unawareness.

In Somalia internet banking system is not so popular according to neighbor countries. After collapse

of central Somali government the country is not developing well so some technological

development and their uses are absent now. Some of the banks in Somalia like Salam Somali

Bank achieved some little advances. Salam Somali Bank is the first Bank in Somalia that brought

Automatic Teller Machine (ATM). Premier Bank is another Bank in Somalia which provides VISA

Card and MASTER Card.

2.3 PREVIOUS WORK/ EXISTING SYSTEMS

Many researchers argue that while e-banking (or internet banking) using a PC channel was the

most advanced trend and the cutting edge competitive advantage in the banking industry during the

last two decades, many other researchers believe that the PC-based internet banking is on its

eminent way towards being obsolete. The future of e-banking is steadily and heavily heading

towards the use of mobiles in conducting banking transactions.

8
In 2010, Lloyds Banking Group became the first bank in the UK to offer mobile banking services

that allow funds transfer between bank accounts within the same bank through mobile

applications run by a mobile money network called “Monilink”. Customers were required to

download these applications software to their phones equipped with internet access and color

screens, enabling the mobile based banking transactions that are so easy and fast, and require only

entering a six digit PIN code. It only cost them £2.50 a month. Considering that 95% of the UK

population is estimated to own a smart mobile phone, this had revolutionized the ebanking

services in that country, even though the mobile banking is primarily used for basic transactions

and payments. The customers still prefer PC- based internet channel for the more sophisticated

transactions. Experts expect that within the next five years mobile banking will become the main

channel of providing most of the banking services and transactions, thanks to the fast-paced

technological advancements in the smart-phone industry.

Currently OBS become portable because many Telecommunication companies made their own online

bill payment, transaction, Transfer to another account using Mobile phones that works as OBS.

2.4 GAP ANALYSIS AND DIRECTION

This research aimed to focus on strengths and weaknesses in the main areas (which will later be

defined as dimensions) in the Somali e-banking sector and compares it with the same areas in the

global e-banking industry. As a result e-banking is to be presented from the perspective of the

banks, their objectives and impact of e-banking as well as e-banking from the perspective of the

customers which comprises their desired benefits and cultural influences. Lastly, e-banking

9
dimensions such as the infrastructure readiness level, regulations of e-banking or legal coverage,

respectively, and the readiness of the users of e-banking culturally and behaviorally are analyzed.

The research suggests some recommendations for enhancement as related to each of the examined

dimensions

2.5 CHAPTER SUMMARY

In this chapter we discussed many sections such as introduction to study, then we

discussed concepts ideas or opinions from other authors related to our system, and

also we discussed the existing systems related to our system and lastly we conclude

this chapter comparison among the different systems that we studied in this chapter.

10
 CHAPTER THREE

REQUIREMENT ANALYSIS

3.1 INTRODUCTION

This chapter will describe the requirement analysis used in this project, and will be defined how

the project problem has been solved. It starts with the project approaches and followed by a

presentation of the project design, the data collection tools and further more a description of how

the data is analyzed. So it also presents the user requirement analysis process of the study. It

outlines user requirement specification, data gathering techniques and procedures which were

used. It requires a carefully planning and thinking on the part of the system analyst. Analyzing

system means to plan how the various parts of the system are going to achieve the desired goal.

So this chapter presents a more description of the research methodology used in this research.

This chapter clearly explains all activities needed to be done in order to achieve the objectives of

the research. This includes the user requirement analysis, preliminary investigation, organizational

profile, current system, the limitations of the current system, data gathering, Data flow diagram

DFD, unified modeling language UML, problem statement, feasibility study, technical feasibility,

Operational feasibility, schedule feasibility, feasibility report, user requirement specification, new

proposed system, solution strategy, system requirement specification, list of events, converting

events into process, regrouping and chapter summary.

11
3.2 USER REQUIREMENT ANALYSIS

User requirement analysis is one of the imports steps followed when system is developing

in order to recognize that the system will serve or cover the basic needs of the user.

This system uses as analysis instrument to the UML to define the projected system’s analysis stage

activities and lastly we present result of the system analysis phase

The requirements can be defined as “A complete understanding of the software development

effort. No matter how well designed or well coded, a poorly analyzed and specified program will

disappoint the user and bring grief to the developer.”

System requirements should set out what the system should do rather than how this is done. A

requirement may be a functional requirement, that is, it describes a system service or function.

Alternatively, it may be a non-functional requirement. A non-functional requirement is a constraint

placed on the system (for instance, the required response time) or on the development process

(such as the use of a specific language standard).

The Design process involves developing several models of the system at different levels of

abstraction. As a design is decomposed, errors and omissions in earlier stages are discovered.

Design is a creative process. Although methods and guidelines are helpful, judgment and flair are

still required to design a software system.

Requirements may be either:

12
• Functional, describing the facilities of the system
• Non-functional, describing constraints which may impact later development phases

3.3 PRELIMINARY INVESTIGATION

Scope was determined and eventually, research proposal is evaluated. If the proposal is

not accepted a further investigation should be made in the problem. However, if it is accepted,

the literature of the research area is studied. The literature review provides important information

that has been published about the research area. This initial information paves the way for official

data collection which includes both primary data and secondary data (secondary data were also

collected during literature review section) after sufficient data is collected then the data is

analyzed. The result of data analysis lead to attain the objectives of the research and perhaps the

approval or disapproval of the research hypothesis objectives and research scope were

determined and eventually, research proposal is evaluated. If the proposal is not accepted a

further investigation should be made in the problem. If it is accepted, the literature of the research

area is studied. The literature review provides important information that has been published

about the research area.

Main Reasons for Systems Projects Preliminary Investigation A.

Project Level

In this section, we discuss the main reasons for systems projects, which are described below.

Improved service

Systems requests are often aimed at improving service to customers, suppliers, or users within the

company. A bank or a mutual fund company may want to allow their account holders to check

13
account balances from the company Web sites, or a university may want to create an online

registration system.

Support for new products and services.

The current system doesn’t s support may new products or services. Recent years technologies

advanced and its vulnerability increased that is why OBS doesn’t support may unknown soft wares

and Hardware.

Better performance

The current system might not meet performance requirements. For example, the systems might be

old and hence slow to respond data inquiries, have limited flexibility, or be unable to support

company growth.

System performance can be increased by combining processes, streamlining a process through the

elimination of unnecessary or duplicated steps, integration of systems and sub-systems, and so on

More information stronger controls

The system might produce information that is insufficient, incomplete, or unable to provide company’s
changing information need.
For example, a system that tracks customer orders might not be capable of analyzing marketing needs.
The business might need to keep track of some key information that can not be obtained from the current
system.

14
Stronger controls

A system may not have all controls on accurate data entry, leading to inaccurate data entry and storage,
loss of income, and even system failure.
A system may not have all security required by the company for different users. Common user
controls include login passwords to programs and databases, various levels of systems access (menus
level, form level, field level, etc.)
Reduced operating costs

The current system could be expensive to operate and maintain as a result of technical problems, design
weaknesses, or the changing demands of the business.

B. Thesis Level
a. Academic study
b. Experiment
c. Problem analysis and solving
d. Or anything that reflects the understanding of an existing body of theory or knowledge
related to current problem

3.3.1 ORGANIZATIONAL PROFILE

The project is intended to provide online banking facilities such as checking accounts,

withdrawals, and making transfers over World Wide Web. Customer is supposed to provide login

id and password to access his bank account online. With proper authorization the customer will be

allowed to perform various banking activities. In addition to conventional banking services the

customer is also facilitated with service like create new account.

There are two major ends in this project the customer end and the administrator end.

• Customer end is the end where customers make requests to view their account information update

information and do transactions or pay certain bills. • Administrator end is responsible for

15
validating the user i.e. not allowing any unauthorized person to access the account. In event of a

customer forgetting the Login password, provision has been made to provide password through a

secure passage. Administrator is responsible for adding customers without affecting existing

customers

3.3.2 CURRENT SYSTEM

Online banking system is a service application that is based on the modern technology of the

internet and remote location services. It is also a phenomenon that facilitates the way customers

interact with their bank accounts without going to the bank’s place and easily access to the bank

using internet. Customers are allowed to access the bank and register then create an account,

after their account creation their can make transaction like deposits, withdrawals, Transfer money

to other account.

3.3.3 THE LIMITATIONS OF THE CURRENT SYSTEM

The current system has less security.

The current system doesn’t have recovery of data.

Loan facilities, credit card login is not being provided.

It provides banking facilities to personal banking.

a. Administration problems

In this system there may be some problems such as the admin can’t monitor who is going to join

his bank because terrorist and thieves can also make an account in your bank, if so the government

16
and security agencies will blame your bank as packing terrorists and many violence oriented

persons.

b. Technical problems
Technical problems could occur if a specific technical information system Failed to work properly

and the availability of technical resources to develop, purchase, install and operate the system.

Often new technologies have its own problems

c. Other limitations
There are also other limitations of OBS which include the user can’t request loans because this project

is online so it is very difficult to accept loans to unknown customers around the world.

The user’s account may be less security and vulnerable to security threats.

3.4 DATA GATHERING

There are several techniques to make data gathering such as Interviews, Observations,
Questionnaire, surveys and so on. We will use the first two techniques which are described below
and questionnaire if required:

Interviews

An interview is "a formal face-to-face meeting, especially, one arranged for the assessment of the

qualifications of an applicant, as for employment or admission. In the context of banking system,

the interview is the primary techniques for information gathering during the systems analysis

phases of project development phases. It is a skill which must be done by every analyst in order to

17
know what information you have gathered, the quality and in-depth of that information.

Interviewing, observation and research are the primary tools in the data gathering of the project.

When we were collecting the data, we met the directors of Mogadishu Banks.

Observations

Observation is a data collection method used to gather detailed information about a situation or

event. Observation data is used to describe the setting, activities, participants, and the meaning

of the observations from the observer's perspective.

Observation data should be factual, accurate, and detailed, but not so detailed as to include
irrelevant or trivial information that makes the description difficult to understand. The best
observational data allows the reader to fully understand the situation.
Observational methods are ideal for gathering data related to user-centered issues, such as the
usability of your digital library. Observational methods are also ideal for providing information
about the impact and uses of your digital library in real-life settings.

Surveys and Questionnaires

Surveys and Questionnaires are used to obtain information about workloads, reports received,
volumes of transactions handled, and types of job duties, difficulties, and opinions of how the job
could be performed better or more efficiently.

3.4.1 DATA FOLLOW DIAGRAM (DFD)

A DFD is a graphical representation of the "flow" of data through an information system. Data

Flow Diagrams is a common form of process modeling which represent a logical model that shows

what the system does, not how it does it.

DFDs graphically show the movement and transformation of data in the information system. DFDs

use four symbols: Process is a unit of work that operates on the data. The process may be automated

18
or manual. The symbol for a process is a rounded rectangle; Data flow is a named flow of data

through a system of processes, data flow is shown as a directed line on the diagram; Data store is a

logical repository of data. It may be an automated file, a paper file, etc. a data store is shown as an

open-ended rectangle; External Entity is a source or destination of data.

The external agent occurs outside of the system of processes. An external agent is depicted by an
overlapping rectangle. Several different versions of DFDs exist, but they all serve the same purpose. In
this project will use popular version called the Gene and Sarsen symbol set which is shown in Figure
1.1.

Process

Data Flow

Data Store

External Entity

Figure 1.1: DFD

19
3.4.2 UNIFORM MODELING LANGUAGE (UML)

UML stands for Unified Modeling Language; The UML is the standard language for visualizing,

specifying, constructing, and documenting the products of a software-intensive system. It can be

used with all processes, throughout the development life cycle, and across different implementation

technologies.

3.5 PROBLEM STATEMENT

Problem statement defines the limitations and problems which the current system has. My analysis
towards the problem statement of the current system and discovered the following different types
of problems listed below.

System Problems

The security of the previous system is very week rather than in our system.

The system needs more employees, since it’s partially computerized

The current system doesn’t provide loans.

The bank’s services are restricted to the bank’s Customers.

Data of the depository have limited back-up.

The present system has less safety.

It is not compatible with the growing data of the customer’s bank.

The system can’t perform a quick search.

20
 Other Problems

Less security for data.

It’s difficult to review their account balance.

It is not compatible with the growing data of the customer’s bank.

So as system developers, realized that customer’s only get confidence for what interprets from
their requirements and designed to them.

3.6 FEASIBILITY STUDY

Feasibility study is a vital part of s systems project to evaluate and measure the system against the

expected performance, shaping objectives, study how beneficial the development of the system to

the organization. It has three yardsticks to predict a system’s success: technical

feasibility, operational feasibility and Schedule feasibility.

If I get boundless resources and unlimited time, I would not need to study feasibility study, but it

is necessary to make an initial review to decide whether it deserves further study, although it is an

ongoing task that must be performed throughout the systems development process.

The objective of this feasibility study is to find whether or not OBS project can be done and to suggest

possible alternative solutions.

21
3.6.1 TECHNICAL FEASIBILITY

Technical feasibility is the measure of the practicality of a specific technical information system

solution and the availability of technical resources to develop, purchase, install and operate the

system. Often new technologies are solutions looking for a problem to solve.

The assessment is based on an outline design of system requirements in terms of Input, Processes,

Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data,

trends, frequency of updating, etc. in order to estimate whether the new system will perform

adequately or not. Technological feasibility is carried out to determine whether the company has

the capability, in terms of software, hardware, personnel and expertise, to handle the completion of

the project.

Hardware requirements

Choice1

Server side
No Description Quantity Unit Price Amount

1 Pentium 4, Dual Core 5 $550 $2750

CPU 3.6 GHZ, HDD

500GB, RAM 4GB

2 All-In-One Printer with 3 $80 $240

scanner and copy.

Total $2990

22
Table1.1: Hardware Requirements, Choice 1 server-side

Client side
No Description Quantity Unit Price Amount

1 Pentium 4, Dual Core 15 $450 $6750

CPU 2.6 GHZ, HDD

500GB, RAM 4GB

2 All-In-One Printer with 10 $80 $800

scanner and copy.

Total $7550

Table 1.2: Hardware Requirements, Choice 1 client-side

Choice2

Server side
No Description Quantity Unit Price Amount

1 Pentium 4, CPU 3.6 2 $550 $1100

GHZ, HDD 160GB,

RAM 2GB

2 Olium Printer with 2 $70 $140

scanner.

23
 Total $1240

Table 1.3: Hardware Requirements, Choice 2 server-side

Client side
No Description Quantity Unit Price Amount

1 Pentium 4, CPU 3.6 12 $550 $6600

GHZ, HDD 160GB,

RAM 2GB

2 Olium Printer with 5 $70 $350

scanner.

Total $6950

Table 1.4: Hardware Requirements, Choice 2 client-side

Choice3

Server side
No Description Quantity Unit Price Amount

1 Pentium 4, CPU 3.2 1 $450 $450

GHZ, HDD 80 GB,

RAM 12 GB

24
2 HP Desk Jet Printer 1 $50 $50

Total $500

Table 1.5: Hardware Requirements, Choice 3 server-side

Client side
No Description Quantity Unit Price Amount

1 Pentium 4, CPU 3.2 8 $450 $3600

GHZ, HDD 80 GB,

RAM 12 GB

2 Odium Printer with 1 $50 $50

scanner.

Total $3650

Table 1.6: Hardware Requirements, Choice 3 client-side

Software requirements

Choice1

Server sid e
No Description Quantity Unit Price Amount

1 Window Server 2008 1 $140 $140

2 Window XP Service 1 $90 $90

Park3

3 Visual Studio 2010 1 $130 $130

25
4 MS SQL Server 2008 1 $65 $65

Total $425

Table 1.7: Software Requirements, Choice 1 server-side

Client sid e
No Description Quantity Unit Price Amount

1 Window XP Service 1 $90 $90

Park3

Total $90

Table 1.8: Software Requirements, Choice 1 client-side

Choice2

Server sid e

No Description Quantity Unit Price Amount

1 Window Server 2008 1 $140 $140

2 Window XP Service 1 $70 $70

Park3

3 Visual Studio 2010 1 $110 $110

4 MS SQL Server 2008 1 $65 $65

Total $385

Table1. 9: Software Requirements, Choice 2 server-side

26
 Client side

No Description Quantity Unit Price Amount

1 Window 2008 Service 1 $70 $70

Total $70

Table 1.10: Software Requirements, Choice 2 client-side

Choice3

Server sid e

No Description Quantity Unit Price Amount

1 Window Server 2003 1 $120 $120

2 Window XP Service 1 $50 $50

Park2

3 Visual Studio 2008 1 $85 $85

4 MS SQL Server 2005 1 $45 $45

Total $300

Table 1.11: Software Requirements, Choice 3 server-side

27
 Client side

No Description Quantity Unit Price Amount

1 Window XP Service 1 $50 $50

Park2

Total $50

Table 1.12: Software Requirements, Choice 3 client-side

3.6.2 OPEARATIONAL FEASIBILITY

Operational Feasibility means that the projected system will be used effectively after it has been
developed. It is a measure of how well the new system solves the problems, and takes advantage
of the opportunities identified during scope definition and how it satisfies the requirements
identified in the requirements analysis phase of system development.

Choi ce1: Full Training

Cost(Contract) Amount

10 trainers $100 $1000

50 Users $5 $250

Table 1.13: Operational feasibility, Choice 1 Full Training

28
 Choice 2: Medium Training

Cost(Contract) Amount

6 trainers $80 $480

30 Users $3 $90

Table 14: Operational feasibility, Choice 2 Medium Training

Choi ce3: Low Training

Cost(Contract) Amount

5 trainers $60 $300

25 Users $2 $50

Table 1.15: Operational feasibility, Choice 3 Low Training

3.6.4 FEASIBILITY REPORT

We have been discussed in the analyze phase, especially in the feasibility study, as it is standard feasibility

study consist of three main parts and each of them has its own cost.

After a long discussion and analysis in terms of quality and quantity based on the needs of the

company, we recommend to use the company maximum features of the equipment and tools we

mentioned above in table 2 so these facilitates to get high performance, speed, and sufficient

capacity for future backup and restore

In our new system, we have three different choices of training which it costs the following various stages:

Full Training cost estimated is $1250

Medium Training cost estimated is $570

29
 Low Training cost estimated is $350

But we recommend to provide full training to both users and trainers, in addition to that the

full feature of the hardware and software requirement both technically and operationally costs

$12305 so that this system needs hardware supplements such as HP laser inkjet 2050 printer and

both server side and client side computers for high speed and capacity, the most total requirement

hardware is mentioned above in the technical table.

3.7 USER REQUIREMENT SPECIFICATION

One of the most important of user requirement specification is that they need a web based

application that serves as online since the old system was based on a desktop application with many

different limitations and drawbacks but the new system allows you to make Deposits, Withdrawals with a

single click of a mouse, another important factor is to make depositing, withdrawing living in

another country in the globe through the internet. The new Mogadishu Online Banking System is

fast, efficient and effective. Over the internet, transactions are usually performed and executed at a

more rapidly rate than ATM's. In addition to that, MOBS offer the capability to handle numerous

bank accounts from one site to another.

3.7.1 NEW PROPOSED SYSTEM

The chapter discovered several limitations and drawbacks that the current system meets during the

problem statement in preliminary study. The new system is based on with use of internet technology

that simplifies to serve the customers at any time anywhere within the universe in addition to that

the new system guarantees to solve all the drawbacks of the current system.

30
The new system uses numerous transactions at a time. Also this system will be implemented using

Microsoft ASP.NET 4.0 (VB.NET 2010) & Microsoft SQL Server 2008 R2 so that this system

takes the benefits of the ASP.NET features. This new system will solve all limitations listed in the

problem definition section and, after analyzing feasibility study we choose the following options

Technical:

Hardware

Server side

No Description Quantity Unit Price Amount

1 Pentium 4, Dual Core 5 $550 $2750

CPU 3.6 GHZ, HDD

500GB, RAM 4GB

2 All-In-One Printer with 3 $80 $240

scanner and copy.

Total $2990

Table 2.1: Hardware Requirements, Choice 1 server-side

Client side

No Description Quantity Unit Price Amount

31
 1 Pentium 4, Dual Core 15 $600 $9000

CPU 2.6 GHZ, HDD

500GB, RAM 4GB

2 All-In-One Printer 10 $80 $800

Total $7550

Table 2.2: Hardware Requirements, Choice 1 client-side

Software

Server sid e

No Description Quantity Unit Price Amount

1 Window Server 2008 1 $140 $140

2 Window XP Service P3 1 $90 $90

3 Visual Studio 2010 1 $130 $130

4 MS SQL Server 2008 1 $65 $65

Total $425

Table2.3: Software Requirements, Choice 1 server-side

Client sid e

No Description Quantity Unit Price Amount

1 Window XP Service P3 1 $90 $90

Total $90

Table 2.4: Software Requirements, Choice 1 client-side

32
 Operational

Choice1: Full Training

Estimated Cost Amount

10 trainers $100 $1000

50 Users $5 $250

Table 2.5: Operational feasibility, Choice (1): Full Training

Economic

Choices Technical Operational Total

1 $ 11055 $ 1250 $12305

Table2.6: Selected Economical way

3.7.2 SOLUTION STRATEGY

When discovered the current system’s problem, I decided to develop a new system, which stands the need of the Online

Banking System. As an individual decided to take PHP as front end and MS-SQL Server 2008 R2 as back end as

solution strategy for the problem, because ASP.NET is powerful server-based technology from Microsoft, designed to

create dynamic and inter active HTML pages for your World Wide Web or corporate internet.

ASP.NET is now considered an integral part of working with windows on the internet.

33
3.7.3 SYSYTEM REQUIREMENT SPECIFICATION

The new system of OBS Produces daily, weekly, Monthly and yearly report as an output

The new system updates data after every transaction as a process

The response time must not exceed four seconds in the full hardware and software
requirements as a process

The new system must provide log-on security at the application level

System Interface

Application would be a self-contained system. It will not access

data of any other application nor will other application have access

to its data

2.4.1 User interface

Application will be accessed through a Browser Interface. The interface would be viewed

best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully

compatible with Microsoft Internet Explorer for version 6 and above.

No user would be able to access any part of the application without logging on to the system.

34
 Hardware Interface

Server-side Client-side

Intel Pentium 4, Dual Core 3.6 Intel Pentium III or above.

4GB RAM 512 MB RAM

500 GB hard disk 40 GB hard disk

Network Adaptor (NIC). Network Adaptor (NIC).

Table2.7: Hardware Interface

Software Interface

Server-side Client-size

Windows 2003 server Microsoft Windows

MS-SQL SERVER 2008 9x/me/2000/XP/Vista/Win7

ASP.NET 4.0 Microsoft Internet Explorer 6.0 or above

Table2.8: Software Interface

3.7.3.1 LIST OF EVENTS

1. Customer requests for registration

2. Give Customer registration form to fill

3. Customer is requested to fill his/her information

4. Check if Customer already exists

35
5. Perform the registration for the customer

6. Display Account Creation page to the customer

7. Ask Account type

8. Pay account creation Service

9. Fill required Account info

10. Verify Account info

11. Accomplish Account creation process

12. Customer requests to deposit money

13. Check if customer account number and his/her signature are valid or not

14. Reject if account information is invalid

15. Accept if account number or signature is valid

16. Save deposit money

17. prepare customer balance sheets

18. Customer requests to withdraw money

19. Verify customer account number and his/her signature

20. Reject if account information is invalid

21. Accept if account information is valid

22. Verify old balance equal or greater than customer’s demand

23. Reject if amount is not equal his/her balance or less than 10

24. Accept if amount is equal his/her balance or greater than 10

25. Allow customer to withdraw his/her money

26. Manager requests all transaction report

36
 CHAPTER FOUR

SYSTEM DESIGN

4.1 INTRODUCTION

This chapter discusses about the designing phase which is the most important phase of software
development. It requires a careful planning and thinking on the part of the system designer.

Designing software means how to plan the various parts of the software to achieve the desired goal
it should be done with greatest care because if the phase contains any error, then that will affect the
performance of the system. As a result it may take more processing time more response time extra
coding workload etc.

Software design sits as the technical heart of the software engineering process and I applied
regardless of the software process model that is used after the software requirements have been
analyzed and specified, software design is the first of the three technical activities designing, coding
and testing that are required to build and verify the software. Each activity transforms information
in such a manner that ultimately results in validated computer software.

The remaining parts of this chapter we discuss the followings design goal which makes the system
easy and flexible for use, Database design, and the ERD diagrams, Data dictionary, Table Design
and Form design, report design, finally chapter summary will be concluded.

4.2 DESIGN GOALS

37
 • Make system easy and flexible for users: End users who aren’t programmers should be apple
to have an extreme amount of control over their purposes, this could be used efficiently and
system could act as catalyst in achieving objectives.
• Make the system compatible: it should fit in the total integrated system, future maintenance an
enhancement must less.

• Efficiency: It is generally considered to be the most important. Given a piece of hardware on

which the system will run and a piece of software to run it, the design should make full and
efficient use of the facilities provided. The users should interact with the system without any
delay.

• Integrity: this means that the system should be accurate as possible. The problem of preserving
the integrity of data can be viewed at a number of levels. At a low level, it concerns ensuring that
the data are not corrupted by hardware or software errors. At higher level, the problem of
preserving integrity concerns maintaining and accurate representation of the real world.

• Reliability: The system is able to perform a required function under stated conditions for a
specified period of time.

• Reusability: the system is able to add further features and modification with slight or no
modification.

4.3 DATABASE DESIGN

Designing a Database is an important task; building or constructing a database starts with a design.
After all, you wouldn’t try to build a house without a blueprint, and most people wouldn’t attempt
to prepare a new dish without a recipe. Like these other tasks, having a good design for your
database is a major first step in creating a successful project.

In designing a database application, you must set up not only the program’s routines for maximum
performance, but you must pay attention also to the physical and logical layout of the data storage.
A good database design does the following:

• Provides minimum search times when locating specific records.

• Stores data in the most efficient manner possible to keep the database from growing too large.

38
 • Makes data updates as easy as possible.
• Is flexible enough to allow inclusion of new functions required of the program.
• When you’re creating the design for your database, you must keep several objectives in mind
although meeting all these design objectives is desirable, sometimes they are mutually exclusive.

Figure 4.3 Database Design

4.4 ENTITY RELATIONSHIP DIAGRAM (ERD)

An entity relationship diagram (ERD) is a model that identifies the concepts or entities that exist in
a system and the relationships between those entities. An ERD is often used as a way to visualize
a relational database: each entity represents a database table, and the relationship lines represent
the keys in one table that point to specific records in related tables. ERDs may also be more
abstract, not necessarily capturing every table needed within a database, but serving to diagram the
major concepts and relationships. This ERD is of the latter type, intended to present an abstract,
theoretical view of the major entities and relationships needed for management of electronic
resources.

The building blocks of an Entity Relationship Diagram

Entity: An entity is an object that exists and distinguishable from other object.

39
 A person, place, object, event or concept in the user environment about which the organization
wishes to maintain data.

Attribute: A named property or characteristic of an entity that is of interest to an organization.

Relationship: A relationship is an association of entities where the association includes

one entity from each participating entity type where relationship type is a meaningful
association between entity types.

Entity Relationship Diagram Symbols

Entity Relationship diagram is used to represent database schema.

A rectangle represents an entity set.

A Diamond represents Relationship

An ellipse represents an attributes.

Lines represent linking of attributes to entity sets & of entity sets to relationship
sets.

Entity set Relationship Attribute Line

Figure 4.4 Entity Relationship Diagram Basic Symbols

40
Figure 4.4.1 shows Entity relationship for online banking system

Types of Relationship in ERD

Relationship is an association among one or more entities. This relationship can be broadly
classified into one-to-one relation, one-to-many relation, many-to-many relation and recursive
relation.

One to many Relationship Type: The relationship that associate one entity to more than one
entity is called one to many relationship: - Example is country having states for one country
there can be more than one states hence is an example one to many relationship.

One to one Relationship Type: One to one relationship is a special case of one to many
relationships. True one to one relationship is rare. The relationship between the president
and Country is an example is one to one relationship.

Many to Many Relationship Type: The relationship between EMPLOYEE entity and

41
 PROJECT entity is an example of many to many relationships. Many employees will be
working in many projects hence the relationship between employee and project is many to
many relationships.

Many to One Relationship Type: The relationship between EMPLOYEE and

DEPARTMENT is an example of many to one relationship, there may be EMPLOYEE
working in one DEPARTMENT. Hence relationship between EMPLOYEE and
DEPARTMENT is many to one relationship.

Table3.1: Relationship types

4.4.1 De-normalization of entity relational diagram

The word ‘de-normalization’ is used to describe changes to the table design that cause the physical
tables to differ from the normalized entity relationship diagram. ‘De-normalization’ does not mean
that anything goes. The development of properly de-normalized data structures follows software
engineering principles that insure that information will not be lost.

When tables are normalized asset of related tables that make up the database are obtained, the relational
model prescribes normalization as must for all tables.

It may not be very practical in real life to do so.

Since speed of queries and therefore speedy retrieval of data is vital and sometimes critical too.

42
Sometimes redundancies have to be permitted in a table.
The intentional introduction of redundancy in tables to improve the performance of the database is
called de-normalization. We need to add these new entities:-
Accounts

Deposit

Withdrawal

Transfer

4.4.2. NORMALIZATION

Normalization is the process of organizing data in a database. This includes creating tables and
establishing relationships between those tables according to rules designed both to protect the data
and to make the database more flexible by eliminating two factors: redundancy and inconsistent
dependency. Redundant data wastes disk space and creates maintenance problems. If data that
exists in more than one place must be changed, the data must be changed inexactly the same way
in all locations. Inconsistent dependencies can make data difficult to access; the path to find the
data may be missing.

Normalization is the analysis of functional dependencies between attributes. It is the process of

decomposing relations with anomalies to produce well-structured relations. Well-structured
relation contains minimal redundancy and allows insertion, modification, and deletion without
errors or inconsistencies. Normalization is a formal process for deciding which attributes should be
grouped together in a relation. It is the primary tool to validate and improve a logical design so that
it satisfies certain constrains that avoid unnecessary duplication of data. Normalization theory is
based on concepts of normal forms. A relational table is said to be a particular normal form if it
satisfied a certain set of constraints.

Purpose of normalization

Normalization allows us to minimize insert, update, and delete anomalies and help maintain data
consistency in the database.

43
 To avoid redundancy by sorting each fact within the database only once

To put data into the form that is more able to accurately accommodate change

To avoid certain updating "anomalies"

To facilitate the enforcement of data constraint

To avoid unnecessary coding.

The degree of normalization is defined by normal forms. The normal forms in an increasing level
of normalization are first normal form (1NF), second normal form (2NF), and third normal form
(3NF). Each normal form is a set of conditions on a schema that guaranties certain properties
relating to redundancy and update anomalies.

Normalization Rules

Eliminate repeating groups in individual tables.

Create a separate table for each set of related data.

Identify each set of related data with a primary key.

Eliminate redundant data.

Eliminate columns not dependent on the primary key.

4.5 DATA DICTIONARY

Data dictionary, or data repository, is central store house of information about System’s data. We
will use it to collect, document, and organize specific facts about system include the data flows,
data stores, external entities, and processes. The data dictionary also defines and describes all data
elements and meaningful combinations of data elements.

NO Data Field Data Type Constraint

44
1 Identity Card Int Primary

2 Full Name Varchar( 45)

3 Password Varchar( 20)

4 Re-enter Password Nvarchar(30)

5 Deposit NVarchar(20)

4.6 TABLE DESIGN

Figure 4.6.1 Shows Account No Table

45
Figure 4.6.1 Shows Event Table

Figure 4.6.1 Login Table

Figure 4.6.1 Shows My account Table

46
6.7 FORM DESIGN

Figure 4.7.1 Registration form

Figure 4.7.2 Login form

47
Figure 4.7.4 Transactions form

Figure 4.7.4 Check Balance form

48
4.8 REPORT DESIGN

Figure 4.8. Report design

49
4.9 CHAPTER SUMMERY

This chapter discusses about the design and the implementation of the project. Software and

database design were the following steps of this chapter which was the conversion of the

requirement analysis, to show the interior design of the system. After that we discussed the database

Design, ERD, Data Dictionary, Table Design, Form design and etc., although we have covered

majority of the project still we are .going to the coding step of the project.

50
 CHAPTER FIVE

SYSTEM DEVELOPMENT

5.0 INDRODUCTION

This chapter discusses about system development of Online Banking System after making
designing, a programmer must make sure that its code whether it is correct or not, later the codes
are tested in groups, and finally the development must be tested for entire system. The structure of
this chapter contains the followings in section1 we will discuss the coding phase which makes the
system easy understandable for coding; in section II will also be concentrate Types of Testing, and
the User Documentation will be discuss in section III, and in section IV an Implementation will be
conducted.

After design, a programmer must make sure it coding correctly Later, Programs are tested in groups,
and finally the development must be tested entire system. The first step is to compile program using
a case tool or language compiler. This chapter can contain these parts: Coding phase, types of
tasting, user documentation, implementation and chapter summary.

5.2 CODING PHASE

When the design is complete, most of the major decisions about the system have been made. What
is next is to translate the design of the system into code in a given programming language; this
phase is called Coding Phase.

51
For My design in chapter 4, the goal of this phase is to implement the design in the best possible
manner. The coding phase affects both testing and maintenance strongly. A well written code
reduces the testing and maintenance effort.

Since the testing and maintenance cost of software are much higher than the coding cost, the goal
of coding should be to reduce the testing and maintenance effort. Hence, during coding the focus
should be on developing programs that are easy to write. Easiness and clearness should be tried
during the coding phase.
Once coding phase is completed, the next phase is testing and debugging. Testing phase is the
process of executing a program or system with the intent of finding errors. Or, it involves any
activity aimed at evaluating an attribute or capability of a program or system and determining that
it meets its required results. Although crucial to software quality and widely deployed by
programmers and testers, software testing still remains an art, due to limited understanding of the
principles of software. The difficulty in software testing stems from the complexity of software:
we cannot completely test a program with moderate complexity, Testing Can be Logging testing
or case testing.

The purpose of testing can be quality assurance, verification and validation, or reliability
estimation. Testing can be used as a generic metric as well. Correctness testing and reliability
testing are two major areas of testing. Software testing is a trade-off between budget, time and
quality. The complete coding phase of the project can be achieved on the attached Compact Disk.

5.2.1 Module: contains connection and disconnection of database

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>welcome</title>
<style type="text/css">
<!--
.style2 { color:
#FF00FF; font-
weight: bold; font-
size: 18px;
}

52
-->
</style>
</head>
<body>
<table width="3078" height="1087" border="0">
<tr>
<td width="3072" height="111" background="jabrapic/ONLINE Banking SYSTEM.jpg">&nbsp;</td>
</tr>
<tr>
<td background="image/Options_01.gif" height="33">&nbsp;</td>
</tr> <tr>
<td background="image/asdljfsl (28).jpg" valign="top"height="805"><table width="1300" height="132"
border="1">
<tr>
<td background="jabrapic/images3.jpg"width="360" height="126" >&nbsp;</td>
<td background="jabrapic/images14.jpg" width="288">&nbsp;</td>
<td width="425" background="image/Bag_of_cash.gif">&nbsp;</td>
</tr>
</table>
<table width="3072" height="273" border="0">
<tr>
<td bgcolor="#00CC99" width="154" class="style2"><div align="right"><a href="index.html">Home
pege</a></a></div></td>
<td width="154">&nbsp;</td>
<td width="154" height="29">&nbsp;</td> <td
valign="top"width="318">&nbsp;</td>
<td width="1382">&nbsp;</td>
<td width="706">&nbsp;</td>
<td width="78">&nbsp;</td>
<td width="92">&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="main.php">SystemLogin</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td rowspan="2">&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>

53
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr> <tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a href="myacct.php">My
Account</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="balance.php">Balance</a></div></td>
<td>&nbsp;</td>
<td><div align="center"><a href="admin.html" class="style2"></a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="deposit.php">Deposit</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td rowspan="5" align="center" valign="top"><strong class="style2"><a href="YouTube - For the
love of money-O' jays Full Version.flv">ilove money </a></strong></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="transaction.php">Transaction</a></div></td>
<td>&nbsp;</td>
<td><div align="center"><a href="Client Login.html" class="style2"></a></div></td>
<td>&nbsp;</td>

54
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="withdrawal.php">Withdrawal</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="transfer.php">Transfer</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
<tr>
<td bgcolor="#00CC99" class="style2"><div align="right"><a
href="register.php">Registeretion</a></div></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr> <tr>
<td height="46" bgcolor="#00CC99" class="style2"><h2 align="right"><img
src="jabrapic/tell_a_friend.png" width="51" height="39" /><a href="Abaut.php">About us
</a></div></h2></td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td> </td>

55
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</table>

<table width="1199" height="364" border="0">

<tr>
<td background="image/033898A.jpg" width="382" height="358" ><img src="jabrapic/01dollars-
animation.gif" width="299" height="203" /></td>
<td width="263">&nbsp;</td>
<td valign="top" background="image/asdljfsl (232).jpg" width="532"><img
src="jabrapic/images7.jpg" width="168" height="161" /> <p><img src="jabrapic/imagesr.jpg"
width="159" height="126" /></td>
</tr>
</table>
<p>&nbsp;</p></td>
</tr>
</table>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
</body> </html>

5.3 TYPES OF TESTING

5.3.1 Unit Testing: In Personal Computer programming, unit testing is a method by which
individual units of source code are tested to determine if they are fit for use. A unit is the smallest
testable part of an application. In procedural programming a unit may be an individual function or
procedure.

The testing of individual program or module is called unit testing.

The objective is to identify and eliminate execution errors that could cause the program to terminate
abnormally, and errors that could have been missed during the checking

56
Test date should contain both correct date and erroneous date and should test all possible situations
that could occur. For example, for a field that allows a range of numeric values outside that contain
minimum values, maximum values outside the acceptable range, and alphanumeric characters.

During system testing, user enter data including samples of actual, or live, data, perform queries, and
produce report to simulate actual operating condition.

The Login page

Figure 5.3 shows the main page of the system; where the users login to the system. If the users key
in wrong username and password the system notify them that the keyed in information is wrong
and they should try again.

5.3.2 Integration testing

Integration testing: is the phase in software testing in which individual software modules are
combined and tested as a group. It occurs after unit testing and before system testing. Integration
testing takes as its input modules that have been unit tested, groups them in larger aggregates,

57
applies tests defined in an integration test plan to those aggregates, Testing more than one program
that depend on each other is called integration testing, or link testing.

Integration testing occurs after unit testing and before system testing. It takes as its input modules
that have been unit tested, groups them in larger aggregates, applies tests defined in an integration
test plan to those aggregates, for example , when we make testing for forms that is used by owners
we need to make integrated.

After completing integration testing, system testing will perform, which involves the entire
information. A system test includes all typical processing situations and is intended to assure users,
developers.

FIGURE 5.3.2 Check Balance PAGE

5.3.3 SYSTEM TESTING

After completing integration testing, system testing will perform, which involves the entire
information. A system test includes all typical processing situations and is intended to assure users,
developers.

58
During system testing, user enter data including samples of actual, or live, data, perform queries, and
produce report to simulate actual operating condition.

5.4 USER DOCUMENTATION

Documentation describes an information system and helps the users who must interact with it.
Accurate documentation can reduce system downtime, cut cost, and speed up maintenance task.
Documentation is essential for successful system operation and maintenance. In addition to
supporting a system’s users, accurate documentation is essential for developers who must modify
the system, add new features or perform maintenance. Documentation includes program
documentation and user documentation. Mostly of the documentations are presented in project as
help and users will get there. There are many types documentations include: program
documentation and system documentation

Program documentation describes the inputs, and processing logic for all program modules, the
program documentation process starts in the system analysis phase and continues during systems
implementation. In the system analysis phase will prepare overall documentation, such as process
description and report layout, early in system development life cycle.

System documentation describes the system’s functions and how they are implemented. System
documentation includes data dictionary entries, data flow diagrams, screen layout, source
documents. System documentation is necessary reference material for Programmers who must
support and maintain the system.

Unlike code documents, user documents are usually far more different with respect to the source
code of the program, and instead simply describe how it is used. In the case of a software library,
the code documents and user documents could be effectively equivalent and are worth conjoining,
but for a general application this is not often true. Typically, the user documentation describes each
feature of the program, and assists the user in realizing these features.

A good user document can also go so far as to provide thorough troubleshooting assistance. It is
very important for user documents to not be confusing, and for them to be up to date. User
documents need not be organized in any particular way, but it is very important for them to have a
thorough index. Consistency and simplicity are also very valuable. User documentation is

59
considered to constitute a contract specifying what the software will do. User documentation includes
the following:-

A system overview that clearly describes all major system features, capabilities, and
limitations.
Description of source document content, preparation, processing and samples.

Overview of menu and data entry screen options, contents, and processing instruction.

Examples of reports that are produced regularly or available at the users request, including
samples.

Explanation of responsibility for specific input, output, and processing requirements.

Explanation of how to get help and procedures for updating user manual.

5.5 IMPLEMENTATION

The implementation phase takes the requirements and design phase products and implements them
using appropriate technologies. In the case of validation testing, it is during this phase that test
cases are completed and automated in preparation for validation testing. Typically, a lot of testing
on the early system versions is also performed during this phase, not only to validate the system,
but to validate that there are no problems with the test cases themselves.

The goal of the implementation phase is to implement a system correctly, efficiently, and quickly
on a particular set or range of computers, using particular tools and programming languages. The
implementation stage is primarily environmental and works with the realities of particular
machines, system, language compilers, tools, developers, and clients necessary to translate a design
into working code. Just as the design phase may include some analysis efforts approached from a
computational standpoint.

In Online Banking System, no person can login with out any user account. so if you login the the
administrator role you see the previllages and do every thing in the system. While the others can
see only their privileged environments only.

60
5.5.1. Hardware and Software Configuration

To have OBS to use and work with correctly, the following different hardware and software specification
are required.

Hardware Specification:
Hardware Specification

Microprocessor Pentium 4
Memory 1GB
Hard Drive 80GB
Screen size 15 inch

Software Specification:
Software Specification
Operating System Window 8
Internet Explorer Version 7, 8 and above
Frame work Microsoft dot net framework4.0
Front-end Active Server Page ASP.net
Back-end Microsoft SQL Server 2008 R2

The welcome page:

The new Online Banking System has many different user roles, every user enters the system from
welcome page which is the first page loads at runtime and the following figure shows the page

61
Figure 5-3: Home Page

Personal Registration

The Personal registration Form is used to register the new Person information; if you click save
Button without entering any Personal information the Form will display empty field is not allowed,
indicating the required fields.

Figure 5-4: Personal Registration

62
Login page form

Enter the administrator username and also the password correctly this page will disappear and you
will see that the administrator can access whole the system, but if you did not provide a correct
username and password, the system will deny the access.

You provide invalid user name and password the system will give a notice message for you incorrectness.

Figure 5-5: Login Page

Deposit Page

The Deposit page Form is used to deposit the money; if you click save Button without entering any
deposit information the system will display error message indicating the required fields

63
Figure 5-6: Deposit Page

5.6 CHAPTER SUMMARY

This chapter discusses about the implementation and testing of the system. Developing the system
requires a server, host to access the portal. The purpose of the testing is to check the errors and
analyze the problem in order to develop a successful system that meets the users’ requirements. In
this we have discussed important points on the system Development starting form introduction of
the chapter then the Coding step of system, Types of testing, User Documentation, and the last
Implementation although we have covered majority of the project now we are going to Conclude
and Summarize our research and for recommendations of the project.

64
 CHAPTER SIX

RECOMMENDATION & CONCLUSION

6.0 Introduction

After much tire and great endeavor we successfully ended the other phases although we recognize
that there can’t be any complete thing done by human being but also we did our best and our project
is completed successfully. According to our effort we really think that we did our best and this
project is completed ninety five per cent (95%) with good user interface design. Such knowledge
may help public authorities and other interested parties plan for the accelerated diffusion of similar
technologies in the future, in Somalia and elsewhere. Finally we would like to identify the strengths
and weak points of our project, because everything has weakness as well as strengths except the
creator of all so we will talk about them as follows.

6.1 CONCLUSION

A. Achievement

Strength: This bank system provides the users store room and right to use his account of customer’s record
with reliability of data safety.

The Customer has ability to change the passwords of his account.

The system considers data protection its goal and is very integrated.

Validations of all inputs are carefully managed and verifications of different user privileges are done
accurately.

This system is very friendly system and it has a good interface that can be usable by every person
who is computer literate.

65
 What is more, if the user make a mistake it generate an error message that easily understandable
by the user and it gives the solution of that problem
B. Limitations

Weaknesses : this project was developed using PHP as front-end and SQL SERVER 2008 as back-
end thus the system may get some run time errors as soon as different version of operating
system is used and these errors are very simple limitation.

The research has presented a simple model of banking functions for making different terms of bank
transactions so this system does not use credit cards but has checks to add or deduct balances.

C. Future enhancement

Many activities known as maintenance are actually enhancements. An enhancement of a system

means adding, modifying and developing the code of that system to support changes.

In the requirement specification of the system it is necessary to keep up with the different changes and
user’s need and their daily work.
The user can easily add to the existing project taking the scope of the project into consideration

We will make an effort to take a credit cards to deduct or add balances.

We will add a good quality reports and also will be improved to this project to fulfill all needs of the

company and the customers

6.3 CONCLUDING REMARKS

The OBS Management information system can increase business transactions when the system shifts
from manual to the automated system.

This also makes convenient for system and their customers as well This

Bank is accessible every time everywhere in the world wide.

66
Recommendation

Although, we developed a system Named: OBS Management information system as we declare

in our problem, a system becomes more reliable, understandable, user friendly and provides
enhanced basic operations.

We however, recommend adding the missing features, in order to become a complete application
performing all activities in OBS SYSTEM.

6.4 REFERENCES

Sites Referred

 Systems Analysis And Design six edition

 RISK MANAGEMENT for ELECTRONIC BANKING AND

ELECTRONIC MONEY ACTIVITIES

 Database management system 4th addition

 Software engineering sixth edition rogers.pressman

 Internet Banking Comptroller‟s Handbook

 Computer-Related Fraud 18 USC 1030

 Bank strategic management and marketing by Derek F. Channon.

 data base System Concept fourth edition SILBERSCHATZ.KORTH.SUDARSHAN

 PHP teach yourself 24 hour
 System analysis and Design 5th edition KENDALL and KENDALL

 PHP Essential Version 4 Julie C. Meloni.

67
  Beginning PHP BY WANKYU CHOI, ALLAN KENT, CHRIS

6.5 APENDIX A

ABBREVIATIONS

ABBREVIATIONS DESCRIPTIONS

GUI Graphical User Interface

WYSIWYG What you see is what you get

SQL Structured Query Language

OBS Online Banking System

PHP Hypertext Preprocessor

WWW World Wide Web

WITHD. Withdrawal

CPU Central Processing Unit

RAM Random Access Memory

GB Giga Byte

HD Hard Disk

UML Unified Modeling Language

ERD Entity Relationship Diagram

URL Resource Locater

VB Visual Basic

68
 6.5.1 APPENDIX B
INTERVIEW QUESTIONS FOR ONLINE BANKING SYSTEM
Some questions that we asked the vice chairman of the Salam Bank Branch Souq Ba’ad In Mogadishu:

1. Which system do the Salam Bank use for managing issues related to Online Banking

System?

2. What are current problems facing for use of manual system?

3. How an old manual system works?

6.5.2 APPENDIX C
No ACTIVITIES JANUARY FEBRUARY MARCH APPRIL MAY

1 Introduction

2 Literature Review

3 Software

Development

Methodology

4 Software Design

5 System

Implementation&

Operation

6 Conclusion &

Enhancement

69