You are on page 1of 44

SOFTWARE REQUIREMENTS SPECIFICATION ON

M-BANKING
Submitted in partial fulfillment of requirement for the award of the degree of

Bachelor of Technology in ( INFORMATION TECHNOLOGY) by: Mrinalini Singh (9760112205) Khushboo Gautam (8171723628)
(Under the guidance of ) Mr.Gaurav Goyal (Asst.Professor,Department of IT)

Department Of Information Technology

MEERUT INSTITUTE OF ENGINEERING AND TECHNOLOGY Approved by A.I.C.T.E. , Affiliated to Gautam Buddha Technical University , Lucknow Meerut-250005

Table of Contents
01. INTRODUCTION 1.1 Purpose 1.2 Scope of project 1.3 Glossary 1.4 References 1.5 Overview of document

02. OVERALL DESCRIPTION 2.1 Project Analysis 2.2 Technologies used 2.3 Configurations 2.4 Tools to be used 2.5 Software engineering methodology 2.6 Application area 2.7 Mobile channel platforms 2.8 Mobile banking services

2.9 Future functionalities in mobile banking 2.10 Challenges for a mobile banking solution

03. SOFTWARE REQUIREMENT SPECIFICATIONS

3.1 Functional requirements 3.2 Non-functional requirements 3.3 Optional features 3.4 User interface priorities 3.5 Reports 3.6 Other important issues 3.7 Final deliverables 3.8 Functions 3.9 System Design 3.10 Use case diagram 3.11 Class diagram 3.12 Activity diagram 3.13 Sequence diagram 3.14 Testing and results 3.15 Feasibility 3.16 Enhancements 3.17 Conclusions

1.INTRODUCTION
m- banking ,an abbreviation for Mobile-Banking, provides banks, savings and loans and other financial institutions with an overview of this sectors opportunities and attributes, including market size, consumer-focussed mobile banking products and services and the mobile media channels available to them today .It also provides considerations for optimizing mobile banking communications and campaign effectiveness within each channel. The mobile banking market has grown significantly over the past several years , particularly in the US , where many financial institutions now offer some form of mobile services for their customers. Today, most large US banks offer a basic mobile banking solution for their consumers .The most common services available today are : Account alerts ,security alerts and reminders

Account balances ,updates and history

Customer service via mobile Branch or ATM location information Bill pay( i.e. electric bill),deliver online payments by secure agents and mobile client applications

Funds Transfers

Transaction Verification

Mortgage alerts

Future services likely will include m-commerce , mobile payments, contactless payments using NFC ( near field communications), mobile coupons and location-based services.

1.1Purpose
In present system, a lot of traditional works are done either in manual process or using internet. The systems like reservations, banking and other things were done using internet or manually so that many times user must go to either outlets or internet service centers but they cannot do all transactions of banking in some special situations like if they are in journeys or if they are busy . But this is the main disadvantage in present situation. To avoid this problem, we have introduced a special type of mobile application called Mobile Banking . The purpose of this document is to present a detailed description of the m-banking system . It will explain the purpose and features of the system, the interfaces of

the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli.

1.2 Scope of Project


In todays age of new opportunities and emerging technologies, there is a new communications infrastructure to transform the way business is done. Using simple and cheaper hardware such as mobiles and handheld devices we can communicate & also we can do business transactions. It provides much better mobility than PCs. Technology is moving towards mobiles which has wide spread usage and acceptability. Lot of protocols and softwares has been developed. We are connecting the mobile to bank database using WML (Wireless Markup Language) scripts and java technology.

This 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 result on the finance industry will be led by a new weapon i.e., the mobile phone. We are providing a wide range of mobile banking for individual clients, including balance checking, amount transfer, stop payment, request check book, mini statement, etc.

All Banking Sector Firms Interfinancial Institutions

1.3 Glossary
Term Database Definition Collection of all the information monitored by this system.

Reviewer

Software Requirements Specification

A person that examines an article and has the ability to recommend approval of the article for publication or to request that changes be made in the article. A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document. Any person with an interest in the project who is not a developer. Any person who uses the system or reviewer.

Stakeholder User

1.4 References

www.gsmworld.com http://www.seminarprojects.com/Thread-mobilebanking#ixzz1ih1HYV7b http://java.sun.com/j2me. //java.sun.com/wireless. http://java.sun.com/products/midp IEEE Std. 830-1998, IEEE Recommended Practice for Software Requirements Specification

1.5 Overview of Document


1. This project is aimed at developing mobile banking system that allows bank customer to use their mobile phone to do banking, paying Bills etc.

2. Two Modules: a) Web application in JSP b) Mobile application in J2ME

3. Users of the System A. Bank customers B. Bank Administrator C. Bank Manager D. Data Manager

02. OVERALL DESCRIPTION 2.1 Project Analysis:


This application consist two modules: Admin Module Reports on existing Customers Customer Module Functionalities provided to the user are:

Check Balance: users may check the balance of account and the latest transactions. Transfer Funds: User may transfer the amount to the required customer of his choice. Stop Payment: user is allowed to stop payment of cheques based on his request. Request Cheque Book: user may request the cheque books according to his requirements (10 leaves, 50 leaves, 100 leaves). Mini statement: user is also allowed to view the transactions made.

Change Pin No.: Pin code no. can be changed by the user based up on the requirement.

One report also suggested that this trend might grow as the number of mobile device users continues to grow, and also those users show more willingness to consider using new applications such as mobile cash and payments.

2.2 Technologies Used


GPRS(general packet radio service) Data packets are transmitted fast communication with the service provider Allows more data

MIDP Extensive Connectivity End-to-End Security

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)

ORACLE 9i

Easy to use. Data Recovery Internet Based

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

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

OTHER TECHNOLOGIES include UML J2EE e-forms AJAX Web 2.0 Web Services etc.

2.4 Tools to be Used


DB2 Database ECLIPSE Development Tool RATIONAL ROSE Design Tool WAS Web Server J2EE Application Architecture J2ME Mobile Application Architecture

2.5 Software Engineering Methodology:


Object Oriented Analysis and Design (OOAD Standards) Software Requirements: Operating System Technology GUI Database Server Tool development tool Windows Java WML, JSP Ms-Access/ORACLE9i Apache Tomcat 5.0. Nokia mobile

Hardware Requirements: Processor processor RAM minimum of P4 minimum of 256MB

MIDP enabled Mobile Device GPRS activated SIM card

Additional Tools: HTML Designing : Dream weaver Tool

2.6 Application Area


Horizontal Hotel Reservations Flight Reservations. Mobile Shopping.

Security Systems

Vertical Basic Transactions Bill Payments Inter Financial Transactions

2.7 Mobile Channel Platforms


In creating a mobile banking solution ,U.S. financial institutions use a variety of mobile media channels including short message service(SMS),mobile web and mobile client applications .Each mobile media channel has its strengths and weaknesses and it is important to identify the delivery mode that is most appropriate for each banking services .One of the goals of this document is to provide an understanding of the type of information that can be delivered across each mobile media channel given their strengths and limitations. 1.SHORT MESSAGE SERVICE (SMS) It has a variety of advantages and disadvantages for financial applications and services. Advantages Easy to use Common messaging tool among consumers

Works across all wireless operators Affordable for consumers Requires no software installation Disadvantages Text-only and limited to 140-160 characters per message Does not offer a secure environment

2.MOBILE WEB It has a variety of advantages and disadvantages for financial applications and services. Advantages User experience of browsing the internet from a mobile device is familiar and offers a rich UI experience. Allows end users to access corporate applications. Secure connection can be established on most of the mobile browsers.

Disadvantages Many non-standard variables including handsets, browsers and Oss. Inconsistent user experience due varying connection speeds and handset limitations

3.MOBILE CLIENT APPLICATIONS It has a variety of advantages and disadvantages for financial applications and services. Advantages It offers organizations more control over the essential experience with a rich user interface capability. Ability to work even when there is no connection to the wireless network. Secure access can be established with applications. Support for access to corporate or customer applications.

Disadvantages Thousands of different combinations for devices, OS and development environments may prevent support for all devices.

Possible increase in customer service and support issues.

4.SMS WITH MOBILE WEB It has a variety of advantages and disadvantages for financial applications and services. Advantages The majority of US wireless carrier networks allow a user to Click on an embedded URL (WAP push) in the SMS message and go directly to their desired webpage. Secure connection can be established on most of the mobile browsers .

Disadvantages User must have a data plan that includes SMS and web access Some wireless operators do not support clickable WAP links in SMS messages No off-line(out of the coverage)capability

5.SECURE SMS It has a variety of advantages and disadvantages for financial applications and services. Advantages Secure, end-to-end encryption of SMS and secure access can be established with applications Allows organization to provide real time information to customers and employees Stored messages can be accessed without a network connection Remote data wipe in case of loss and unauthorized access attempts Message size can be upto 5000 characters

Disadvantages Thousands of different combinations for devices, OS and development environments may prevent support for all devices. Differing handset capabilities and performance causes inconsistent user experience when using or downloading an application Possible increase in customer service and support issues

2.8 Mobile Banking Services


Mobile banking can offer services such as the following:
2.8.1 Account Information

Mini-statements and checking of account history Alerts on account activity or passing of set thresholds Monitoring of term deposits Access to loan statements Access to card statements Mutual funds / equity statements Insurance policy management Pension plan management Status on cheque, stop payment on cheque Ordering cheque books Balance checking in the account Recent transactions Due date of payment (functionality for stop, change and deleting of payments) PIN provision, Change of PIN and reminder over the Internet

2.8.2 Payments , Deposits, Withdrawals, and Transfers

Domestic and international fund transfers Micro-payment handling Mobile recharging Commercial payment processing Bill payment processing Peer to Peer payments Withdrawal at banking agent Deposit at banking agent
2.8.3 Investments

Portfolio management services Real-time stock quotes Personalized alerts and notifications on security prices
2.8.4 Support

Status of requests for credit, including mortgage approval, and insurance coverage Check (cheque) book and card requests Exchange of data messages and email, including complaint submission and tracking ATM Location
2.8.5 Content Services

General information such as weather updates, news Loyalty-related offers

2.9 Future functionalities in Mobile Banking


Based on the 'International Review of Business Research Papers' from World business Institute, Australia, following are the key functional trends possible in world of Mobile Banking. With the advent of technology and increasing use of smartphone and tablet based devices, the use of Mobile Banking functionality would enable customer connect across entire customer life cycle much comprehensively than before. With this scenario, current mobile banking objectives of say building relationships, reducing cost, achieving new revenue stream will transform to enable new objectives targeting higher level goals such as building brand of the banking organization. Emerging technology and functionalities would enable to create new ways of lead generation, prospecting as well as developing deep customer relationship and mobile banking world would

achieve superior customer experience with bidirectional communications. Illustration of objective based functionality enrichment In Mobile Banking Communication enrichment: - Video Interaction with agents, advisors. Pervasive Transactions capabilities: Comprehensive Mobile wallet Customer Education: - Test drive for demos of banking services Connect with new customer segment: Connect with Gen Y Gen Z using games and social network ambushed to surrogate banks offerings Content monetization: - Micro level revenue themes such as music, e-book download Vertical positioning: - Positioning offerings over mobile banking specific industries Horizontal positioning: - Positioning offerings over mobile banking across all the industries Personalization of corporate banking services: - Personalization experience for multiple roles and hierarchies in corporate banking as against the vanilla based segment based enhancements in the current context. Build Brand: - Built the banks brand while enhancing the Mobile real estate.

2.10 Challenges for a Mobile Banking Solution


Key challenges in developing a sophisticated mobile banking application are :
2.10.1 Handset operability

There are a large number of different mobile phone devices and it is a big challenge for banks to offer mobile banking solution on any type of device. Some of these devices support Java ME and others support SIM Application Toolkit, a WAP browser, or only SMS.

Initial interoperability issues however have been localized, with countries like India using portals like RWorld to enable the limitations of low end java based phones, while focus on areas such as South Africa have defaulted to the USSD as a basis of communication achievable with any phone. The desire for interoperability is largely dependent on the banks themselves, where installed applications (Java based or native) provide better security, are easier to use and allow development of more complex capabilities similar to those of internet banking while SMS can provide the basics but becomes difficult to operate with more complex transactions. There is a myth that there is a challenge of interoperability between mobile banking applications due to perceived lack of common technology standards for mobile banking. In practice it is too early in the service lifecycle for interoperability to be addressed within an individual country, as very few countries have more than one mobile banking service provider. In practice, banking interfaces are well defined and money movements between banks follow the IS0-8583 standard. As mobile banking matures, money movements between service providers will naturally adopt the same standards as in the banking world.

2.10.2 Security

Security of financial transactions, being executed from some remote location and transmission of financial information over the air, are the most complicated challenges that need to be addressed jointly by mobile application developers, wireless network service providers and the banks' IT departments.

The following aspects need to be addressed to offer a secure infrastructure for financial transaction over wireless network : Physical part of the hand-held device. If the bank is offering smart-card based security, the physical security of the device is more important. Security of any thick-client application running on the device. In case the device is stolen, the hacker should require at least an ID/Password to access the application. Authentication of the device with service provider before initiating a transaction. This would ensure that unauthorized devices are not connected to perform financial transactions. User ID / Password authentication of banks customer. Encryption of the data being transmitted over the air. Encryption of the data that will be stored in device for later / off-line analysis by the customer. One-time password (OTPs) are the latest tool used by financial and banking service providers in the fight against cyber fraud.
2.10.3 Scalability & Reliability

Another challenge for the CIOs and CTOs of the banks is to scale-up the mobile banking infrastructure to handle exponential growth of the customer base. With mobile banking, the customer may be sitting in any part of the world (true anytime, anywhere banking) and hence banks need to ensure that the systems are up and running in a true 24 x 7 fashion. As customers will find mobile banking more and more useful, their expectations from the solution will increase. Banks

unable to meet the performance and reliability expectations may lose customer confidence. There are systems such as Mobile Transaction Platform which allow quick and secure mobile enabling of various banking services. Recently in India there has been a phenomenal growth in the use of Mobile Banking applications, with leading banks adopting Mobile Transaction Platform and the Central Bank publishing guidelines for mobile banking operations.
2.10.4 Application distribution

Due to the nature of the connectivity between bank and its customers, it would be impractical to expect customers to regularly visit banks or connect to a web site for regular upgrade of their mobile banking application. It will be expected that the mobile application itself check the upgrades and updates and download necessary patches (so called "Over The Air" updates). However, there could be many issues to implement this approach such as upgrade / synchronization of other dependent components.
2.10.5 Personalization

It would be expected from the mobile application to support personalization such as : Preferred Language Date / Time format Amount format Default transactions Standard Beneficiary list Alerts

03. SOFTWARE REQUIREMENTS SPECIFICATIONS: 3.1 Functional Requirements


i. Secure Identification. ii. History of payments. iii. Transfer money from one bank account to another bank account. iv. Financial Information Services v. Payment of Bill via mobile phone vi. Shopping via mobile phone vii. Balance Checking viii. Peer to Peer Payment ix. Encryption of data transmitted and stored x. Alerts and notifications xi. Searching of nearby BANKs and ATMs(Location Based Services)

xii. Support for Exchange of data messages and email, including complaint submission and tracking. xiii. Implementation of basic and advance facility for administrator for generating reports, backup database, add/update user etc. are done. xiv. Integration of J2ME based mobile application with WEB application.

3.2 Non-functional Requirements


i. Secure access of confidential data (users details). SSL can be used. ii. 24 X 7 availability iii. Better component design to get better performance at peak time iv. Flexible service based architecture will be highly desirable for future extension .

3.3 Optional features


a. Web based architecture to integrate with other web application b. Help page for user and administrator

3.4 User interface priorities


A. Professional look and feel B. Use of AJAX at least with all registration forms C. Browser testing and support for IE, Opera, Mozilla, and Firefox. D. Use of Graphical tool like JASPER to show strategic data to admin E. Reports exportable in .XLS, .PDF or any other desirable format8

3.5 Reports
1. For Customer: a) Daily, weekly or monthly report for Payment History b) Customer activity 2. For bank Admin: a) Number of current user login b) Customer Activity statistics c) Employee Activity statistics d) Customer Login statistics

e) Transaction. f) Weekly progress report. 3. For Bank employee a) Demographics analysis of customer

3.6 Other important issues


Website should be highly customizable and flexible enough to easily deploy without much effort.

3.7 Final Deliverables


They must include A. Online or offline help to above said users, Application deployment executive and developer B. Application archive ( .war/.ear and .jar) with source code C. Database backup and DDL Script D. Complete Source code

3.8 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

3.9 System Design

3.10 Use Case Diagram

< extends> < > Relogin < includes> < > Login A uthenticate

< includes> < >

Creating P rofile

< includes> < > < includes> < >

M anage P rofile User

Custom profile ise

Delete P rofile

< includes > < > M S ini tatem ents < includes> < > B asic T ransactions

CLASS DIAGRAM
Clients UserName userId password
< includes > < > B alance E nquires

getName() setName() getpswd() E a ts setpswd()-P ymen Transaction transactionId transactionType time actions result rollbac k() commit() wasSucessfull()

A ccount T A o ccount T ransfers < includes> < >

BalanceEn quries

Acc tToAcctTran sfer


B P ymen ill a ts

senderacctId recipentacctId postbalance setRacct() getRacct() getSacct() setSacct() getbalance() setbalance()

MiniState ments

3.11 Class Diagram


Interface Server generateQuery() checkStatus() senddetails() setvalues() sendreport() sendvalues() BankServer bankName bankId

E-Payments setvalues() getvalues() time() getstatus() recordlog()

BillPayments billId bankid acctId userId setDetails() getDetails()

3.12 Activity Diagram

Ac tiv ity of User

Activ i ty o f Sys te m

User enters the Account number.

User submits the above details.

Ve rifi es the above details. If the above details are correct. No Re-ent er the above det ails.

Yes Balance,list of Transactions are displayed.

3.13 Sequence Diagram

C:Client

:Tranascation : AcctToAcctTrans fer create object s etactions send details()

I:InterfaceServe r

B:Bankserver : Account

validate() if false

send report() send details()

comitt

3.14 Testing and Results

User needs to fill enters in correct details to login

If the user wrong details

User fills the details The transaction is and submits the successful form 3.15 Feasibility

Easy to use GUI Components based

No additional H/W required

3.16 Enhancements

Transactions that could be added are : Loan access facility, Cheque Details, DD orders,

Order of check books etc.

3.17 Conclusion
Faster solutions Database Driven Virtual access to the money

You might also like