Secure Mobile Banking

Table of Contents
1. Introduction....................................................................................................................2 1. Overall Description........................................................................................................4 3.2 Interfaces Requierment..

1. Introduction
0.1 Purpose
This In todays age of new opportunism and emerging technologies, there is a new communications infrastructure on offer to transform the way business is done. opportunity is mobile commerce, and it will drive new levels of intense competition in the finance industry. Mobile commerce achieves this by removing the traditional restrictions of geographical location and high entry costs. This time the assault on the finance industry will be led by a new weapon, the mobile phone. This system offers certain advantages over traditional banking methods.

1.1

Document Conventions
When writing this document it was inherited that all requirements have the same priority.

0.2

Intended Audience and Reading Suggestions

This requirement document contains general information about E-Banking. For this intended stake holders would be as follows: Developer Customer

0.3

Project Scope

This application is designed to implement the banking solution on the mobile to enable the customers to transact, making their account available to them 24 hours a day. Mobile banking provides convenient options needed to manage your finances from wherever life takes you. While the customer has all the options of transactions, the administrative functions are still limited to the bank officials.

0.4

References/Definitions/Acronyms
Definition/Meaning Secure Mobile Banking, which is the name given to tool

Acronym Secure Mobile Banking

1.
1.1

Overall Description
Product Perspective

User

Authentication

Authentication & Registered User Use Case: Login, Logout, Check Balance, Change Pin, Transfer Fund, Change User, Request Cheque Book, Stop Payment, Mini statement, Configuration.

Description: The Users can login by giving their Account Number and Password. If system find is valid and allowed to perform actions and otherwise, System should prompt message 'Invalid user'. After authentication user can perform the following actions: user can take the mini statement, balance, change the pin, transfer the fund by entering the account number and amount, user can request cheque book, stop payment, user can do configuration.

Use case Diagram:

Balance

Mini Statement <<extend>> <extend> <<extend>>

Change Pin

<<extend>> <<extend>> <<extend>> << include>> Transfer Fund

User

Authentication

Request cheque book Stop payment

Logout

Configuration

Pre condition: For Account Holder Flow of Events: Primary Flow: 1. Enter the Username and password. 2. Validate the Username, Password 3. If Validate Success, he/she should be allowed to perform action. 4. Balance of account holder. 5. Account Holder can view the Mini Statement. 6. Account Holder can change pin 7. Account Holder can transfer the amount to other Account Holder. 8. Account Holder can request Cheque Book. 9. Account Holder can Stop Payment. 10. Account Holder can configure the functions concerning account payment and code. Etc.

1.2

Product Features
This application serves the customer to perform balance enquiry, transfer of fund, request for check book, stop payment, and change Pin. With mobile banking the solutions are right at hand, and it provides convenient options needed to manage your finances from wherever.

1.3

User Classes and Characteristics

Assumed that User should aware of how to operate mobile. Along with this project bank would be responsible to providing helping documents. Bank is not responsible to give training for each member of the customer organization. One of the users from customer organization should test at least for 15 days as a part of User acceptance testing. Other than the following requirements, others would be considered as new requirements. Always any addition to the requirements, it would be considered as Change Request. That may incur additional cost based on severity.

1.4

Assumptions and dependencies

-NA

3.

Specific requirements

3.1 Operating Environment

Hardware Requirements Processor Processor Speed RAM Hard Disk Software Requirements Platform Languages Database Software : : : : Windows ( NT/XP) Java,JSP, wml, Tomcat 6 Nokia tool kit J2SDK 1.6 : : : : Intel P-IV based system 250 MHz to 833MHz 64MB to 256MB 2GB to 30GB

My SQL 4.0

3.2 Interface Requirements 3.2.1 Hardware Interfaces

NA

3.2.2 Software Interfaces

A software requirement is an idea for developing the parts of Java Page (GUI) JSP, wml. Nokia tool kit for simulation. through