Escolar Documentos
Profissional Documentos
Cultura Documentos
Table of Contents
Table of Contents.............................................................................................................................
Revision History...............................................................................................................................
1. Introduction................................................................................................................................
1.1 Purpose...............................................................................................................................
1.2 Document Conventions......................................................................................................
1.3 Intended Audience and Reading Suggestions....................................................................
1.4 Project Scope.....................................................................................................................
1.5 References/Definitions/Acronyms...........................................................................................
2. Overall Description....................................................................................................................
2.1 Product Perspective............................................................................................................
2.2 Product Features.................................................................................................................
2.3 User characteristics
2.4 Assumptions and dependencies
3. Specific requierments........................................
3.1 Operating Environment......................................................................................................
3.2 Interfaces Requierment..
1. Introduction
1.1 Purpose
This requirement document contains general information about E-Banking. For this
intended stake holders would be as follows:-
Developer
Customer
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.
1.4 References/Definitions/Acronyms
Acronym Definition/Meaning
Secure Mobile Secure Mobile Banking, which is the name given to tool
Banking
2. Overall Description
2.1 Product Perspective
Authentication
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>>
Change Pin
<extend> <<extend>>
<<extend>>
<< include>>
Request cheque book
Stop payment
Logout Configuration
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.
-NA
3. Specific requirements
Hardware Requirements
Processor : Intel P-IV based system
Processor Speed : 250 MHz to 833MHz
RAM : 64MB to 256MB
Hard Disk : 2GB to 30GB
Software Requirements
Platform : Windows ( NT/XP)
Languages : Java,JSP, wml,
Database : My SQL 4.0
Software : Tomcat 6
Nokia tool kit
J2SDK 1.6
3.2 Interface Requirements
3.2.1 Hardware Interfaces
NA