M-BANKING

PROJECT SYNOPSIS
OF MAJOR PROJECT

BACHELOR OF TECHNOLOGY

Computer Science & Engineering

SUBMITTED BY

Anika Gupta - 0806810012 Keshav Gupta - 0806810043 Naveen Nisad - 0806810053 Prateek Saxena - 0806810062

UNDER THE GUIDANCE OF

Paramanand Astya (Head of Department, Computer Science Department)

Meerut Institute of Engineering & Technology

CONTENTS

NOTATION /NOMENCLATURE LIST OF FIGURES LIST OF TABLES

ii iii iii

ABSTRACT INTRODUCTION FEASIBILTY STUDY

1-3 4-6 7-8

FACILITIES REQUIRED FOR PROPOSED WORK BIBLIOGRAPHY

11 12

NOTATION/NOMENCLATURE
1. RAD 2. DB2 3. WAS 4. JSP 5. HTML 6. CSS 7. RAD 8. DB2 9. WAS 10. JSP 11. HTML 12. CSS 13. RDBMS Rational Application Developer Database 2 Web Sphere Application Server Java Server Pages Hyper Text Markup Language Cascaded Style Sheets Rational Application Developer Database 2 Websphere Application Server Java Server Pages Hyper Text Markup Language Cascaded Style Sheets Relational Database Management System

ii

LIST OF FIGURES
1 2 3 Rural Wireless Subscribers in INDIA A Clear Drift from E-Banking to M-Banking Flow Chart

LIST OF TABLES
1 2 3 Technologies Used Functions Of The Proposed System Required Facilities

iii

ABSTRACT
The last time that technology had a major impact in helping banks service their customers was with the introduction of the Internet banking. Internet Banking helped give the customer's anytime access to their banks. Customer's could check out their account details, get their bank statements, perform transactions like transferring money to other accounts and pay their bills sitting in the comfort of their homes and offices.

However the biggest limitation of Internet banking is the requirement of a PC with an Internet connection, not a big obstacle if we look at the US and the European countries, but definitely a big barrier if we consider most of the developing countries of Asia like China and India. Mobile banking addresses this fundamental limitation of Internet Banking, as it reduces the customer requirement to just a mobile phone.

Mobile usage has seen an explosive growth in most of the Asian economies like India, China and Korea. In fact these Countries boasts about a 70% mobile penetration rate and with its techsavvy populace has seen one of the most aggressive rollouts of mobile banking services.

Fig 1: Rural Wireless Subscribers in INDIA 1

Still, the main reason that Mobile Banking scores over Internet Banking is that it enables Anywhere Banking'. Customers now don't need access to a computer terminal to access their banks, they can now do so on the go when they are waiting for their bus to work, when they are traveling or when they are waiting for their orders to come through in a restaurant. For banks, mobile banking has become the most promising medium of reaching out to their customers because of the ability to provide services at any time or place in the world. Mobile banking provides exceptional convenience to all cell phone users.

Fig 2: A Clear Drift from E-Banking to M-Banking

Mobile banking scores over Internet banking specifically because of following reasons: 1. The security implementations possible with mobile banking are much more advanced (especially if the SIM card is utilized). This is because mobile banking security can be based on keys or certificates - the holy grail of electronic banking very difficult to implement with Internet Banking. The notion of carrying your banking keys in a device that you have with you all the time is extremely powerful and enable the deployment of new types of banking solutions. 2. The immediacy of mobile phones and the fact that it can probably be utilized anywhere (very few places do not have mobile phone coverage), allows for new types of solutions. Some of these solutions can be implemented in conjunction with existing banking operations. (E.g. allow 2

clients to block a credit card from a phone, enable a client to authorize access to personal information from the phone etc.)

3. The best mobile banking deployments utilize message-based implementations (rather than session-based implementations which is prevalent in Internet banking). This architecture leads to significant differences in what is possible and how service is to be delivered. 4. The biggest difference is the access that mobile banking have enabled especially to people that never had access to electronic banking before. Internet banking enabled people to access their banking electronically only if they had been banked before, whereas mobile banking is leading to a revolution where people are being banked who never had a banking relationship in the past.

Hence, we can say that this project that we are going to implement is much more relevant as it will provide an ease to the user with respect to the Banking & will help him to access his account anywhere, anytime.

INTRODUCTION

Purpose:

Banking comes in category of human daily needs, where bank provides some facilities related to money like saving, loan, transfer, fixed deposit, demand draft and so more, but with the time number of bank customers is going to increase which increases the crowd in the bank. So Bank Corporation always tries to solve this problem with the help of alternatives of accessing methods of Bank facilities. In this way Bank Corporation get a way to solve this problem with the help of INTERNET in the form of e-Banking (electronic banking). In todays era computer and internet is a common device but not as common as compared to mobile devices. So in this project we try to provide all bank facilities on a mobile device in the form of m-Banking which fills the demand of ubiquitous computing.

Target User:

This project is for those users who want instant access of their account at any time and from anywhere instead of internet banking which cant be handled instantly because Internet banking demands for PC and Internet connection that take more burden than a mobile device.

Technologies to be used Table 1: Technologies Used S.no. 1 2 3 4 5 6 7 Name J2EE J2ME WASCE ServerDB2 Ajax XML RAD 7.0 Description (Servlet, JSP, JAXP, Java Beans) Web Application architecture Mobile Application architecture. (Web Sphere Application Server Community Edition): Web Server Database as Back-End. Asynchronous Java Script and XML. Extension Markup Language. Development tool (IDE).

User Characteristics: User must have an active bank account. User must have a JAVA enabled mobile device with basic requirements like memory space, processor and GPRS or 3G connectivity for m-Banking application. User must be familiar with mobile device.

Security features:

a.

Confidentiality: It will use SSL security system at socket connection and cipher text to encrypt data.

b.

Authentication: It will provide two phase security system for login.

Fig 3: Flow Chart Product Functions: M-Banking is a mobile application which provides services of banking that are given: Table 2: Functions Of The Proposed System 1. Transfer money from one to another account 2. Request for new check book 3. Request for Demand-Draft 4. Check account balance 5. Check account statement 6. Scheduling of payments 7. Handle more than one accounts 8. Handle multiple type of account 9. Complaint box 10. Request to block DEBIT or CREDIT card

FEASIBILITY STUDY
Feasibility study aims at, objectively and rationally, uncover the strengths and weaknesses of the existing business or proposed venture, opportunities and threats as presented by the environment, the resources required to carry through, and ultimately the prospects for success. In its simplest term, the two criteria to judge feasibility are cost required and value to be attained. Technological Feasibility: The m-banking project is a TGMC project so the softwares to be used are the IBMs registered softwares which are easily available. Also the team members own latest configuration systems required for the development. The team members have adequate knowledge of both J2ME and J2EE technologies that are required for this project. Economic Feasibility: The project uses easily available softwares as well as pre-owned systems which imply that the project requires no initial investment, so the project is economically feasible. Operational Feasibility: The proposed system is the mobile based incarnation of internet banking so it can be said that the technique is a well tested and approved one. It aims at providing a majority of functions that are provided by e-banking. Schedule Feasibility: As mentioned earlier that apart from being the final year project it is a TGMC project, so we have been provided with deadlines regarding this project which should be met. This requires the team to follow a strict timetable which ensures the schedule feasibility. In a country, like India, where no. of mobile phone users are increasing at a rate faster than any other nation in the world and the lifestyle of people is changing, it their becomes need to be able to access their bank accounts not just from their home(as facilitated by e-banking) but

from anywhere they are. This makes their life simpler by buying them some extra time which would have otherwise been wasted in long queues at bank counters. The significance of m-banking lies in its benefits and the fact that todays generation prefers to use mobile applications. The most significant facts are that it saves time, efforts, money, paper wastage and requires no additional knowledge if one is familiar with using other mobile based applications.

METHODOLOGY OF WORK
Steps involved for successful completion of our project are as follows: 1) Requirement Analysis: In depth research of existing system via e-banking websites other e-banking sources Various mobile applications relevant for the project.

2) Designing: Clear and precise designing of proposed system: Clearly defining the User Interface i.e., Mobile Application and the functionalities provided to Bank Customers. Clearly defining the functionalities provided to Banks end users i.e., Bank Managers and Bank Administrators. Clearly defining the Database schema i.e., the tables and its attributes. Making the basic diagrams (ER Diagram, Use Case, Context Level Diagrams etc.) of the proposed system that helps in clear understanding of the system. Precise selection of Algorithm involved for Data Encryption and Decryption. Precise selection of Algorithm involved for Hashing Password and User Ids. Precise selection of Algorithms involved for searching.

3) Coding: First division of project into two main modules: Mobile Application (J2ME) for the client end (Bank Customers) J2EE with Database Connectivity for the Bank Managers, Administrator etc. Then division of work (above modules) within the team members & hence coding the basic structure of the system. 9

4) Testing: Unit Testing of Individual Modules. Integration of individual modules developed by Team members. Integration or Cohesive Testing of Integrated Project via Team Members. Alpha Testing of the integrated system & making modifications in it according to the users feedback. 5) Maintenance: Deployment of final proposed system on the web server. Continuous maintenance of proposed system.

10

FACILITIES REQUIRED FOR PROPOSED WORK

Development Languages Database Server Operating System IDE Interface Language

J2EE, J2ME DB2 Express C Web Application Sphere (WAS) Windows XP Rational Application Developer (RAD) HTML, JSP, MIDLets

NOTE: An additional mobile simulator is also required for the development, error detection and correction. It will be decided after support and feedback from IBM officials.

11

BIBLIOGRAPHY
[1] J2ME Complete Reference- By James Keogh, McGraw-Hill Publication, First Edition, 2003 .

[2] J2EE Complete Reference-by Herbalt Schildt,McGraw-Hill Publication,Second Edition 2003. [3] Beginning J2ME- By Sing Li and Jonathan Knudsen, Apress, Third Edition, 2005 [4] http://download.oracle.com/javase/tutorial [5] http://www.javabeginner.com/ [6] http://www.netpnb.com/index.html [7] https://mobile.netpnb.com/mbanking.html

12