Mobile Banking

Presented by A.Swetha V.Navya Massarath

Current Scenarios
Computerized Banking-Vicinity of Banks Use of ATMs-Vicinity of ATMs Internet banking-Need for Connection

Solutions

Exploiting the penetration of mobile phones E-Cash Traveling Money Round the clock Transactions

Technology involved

J2ME GPRS MIDP Oracle 9i CDLC Configuration

J2ME

Java platform for small devices Introduced by sun in 1999 for mobile devices A subset of Java 2 Standard Edition For programming the mobile device (e.g mobile phones or WinCE)

GPRS(general packet radio service)

Allows more data fast communication with the service provider Data packets are transmitted

MIDP

Extensive Connectivity End-to-End Security

ORACLE 9i

Easy to use. Data Recovery Internet Based

Configurations
CDLC Constrained devices 160 - 512 KB of memory 16-bit or 32-bit processor Low power consumption Connectivity with limited bandwidth

Configuration

CDC
2 MB or more memory 32-bit processor High bandwidth using TCP/IP

CLDC

CDC

Application Area
Horizontal Hotel Reservations Flight Reservations. Mobile Shopping. Security Systems
Vertical Basic Transactions Bill Payments Inter Financial Transactions

Scope
All Banking Sector Firms Interfinancial Institutions

SRS
Software Requirements
Database-ORACLE9i Programming Language-J2ME Modeling Tool-Rational Rose Web Server-Apache Tomcat

Hardware Requirements
MIDP enabled Mobile Device GPRS activated SIM card

System Design
Wap Request

Wap Response

HTTP request
search

search Database Server update

Interface Server

Bank Server
HTTP response

Database Server update

UseCase Diagram
<<extends>> Relogin <<includes>> Login Authenticate

<<includes>> Creating Prof ile <<includes>> <<includes>> Manage Prof ile User Customise prof ile

Delete Prof ile

<<includes>> Mini Statements <<includes>> Basic Transactions

Balance Enquires

<<includes>> Account To Account Transf ers <<includes>> E-Pay ments

Bill Pay ments

Class Diagram

Activ ity of User

Activ ity of System

Acitvity Diagram
User enters the Account number.

User submits the above details.

Verifies the above details. If the above details are correct. No Re-enter the above details.

Yes Balance,list of Transactions are displayed.

Sequence Diagram
C:Client :T ranascation : AcctToAcctT ransfer create object setactions vali date() if false I:InterfaceServe r B:Bankserver : Account

send details()

send report() send details()

comitt

Functions
Subscription Module
User Login Creating a New User Account Module for basic transactions Balance Enquiries Mini statements E-payments Module Account to Account Transfers Bill Payments

Testing and Results

User needs to fill in Correct details to login

If the user enters wrong details

Testing/Results

User fills the details And submits the form

The Transaction is successful

Feasibility
Easy to use GUI Components based No additional h/w required

Enhancements
Transactions that could be added are Loan access facility, Cheque Details, DD orders, Order of check books etc.

Conclusions
Faster solutions Database Driven Virtual access to the money

References
www.gsmworld.com

http://java.sun.com/j2me. //java.sun.com/wireless. http://java.sun.com/products/midp IEEE Std. 830-1998, IEEERecommendedPractice for Software Requirements Specifications.

Queries?

Thank you