Professional Documents
Culture Documents
Introduction: .................................................................................................
.........3 1.1)
Purpose: .......................................................................................................
...................3 1.2)
Scope: ..........................................................................................................
.................3 1.3)
Abbreviations: ..............................................................................................
................4 1.4)
References: ..................................................................................................
.................5 1.5)
Technologies: ...............................................................................................
................6 1.6) Overview
..6 2) Overall
Description: ................................................................................................6
2.01) Product
Perspective: .................................................................................................
...7 2.02) Software
Interface: ......................................................................................................
8 2.03) Hardware
Interface: .....................................................................................................
8 2.04) Communication
Interface: ...........................................................................................8
2.05) Product
Features: ......................................................................................................
..8 2.06) User
Characteristics: ............................................................................................
.......9 2.07) Design and Implementation
Constraints: ....................................................................9 2.08) Use-Case
Model Survey: .............................................................................................9
2.09) Architecture
diagram: ................................................................................................14
2.10) ER-Diagram:
. ........................................................................................................15
2.11) Assumptions and
Dependencies: ................................................................................15 3)
Specific
Requirements: .........................................................................................16
3.1) Use-Case
Reports: ........................................................................................................
.16 3.2) Supplementary
Requirements: .......................................................................................29
4) Supporting Information: ..30
4.1) System in context:
.31 4.2) Class
Diagram: ..32
5) Appendices: .....33
5.1) Appendix B: References
37 5.2)Screen
Shots..38
Introduction
Internet banking system provides is specifically developed for online
banking for Balance Enquiry, Funds Transfer to another account in the
same bank, Request for cheque book/change of address/stop payment of
cheques, Mini statements (Viewing Monthly and annual statements).
Purpose
The Traditional way of maintaining details of a user in a bank was to
enter the details and record them. Every time the user need to perform
some transactions he has to go to bank and perform the necessary
actions, which may not be so feasible all the time. It may be a hard-hitting
task for the users and the bankers too. The project gives real life
understanding of Internet banking and activities performed by various
roles in the supply chain. Here, we provide an automation for banking
system through Internet. Internet banking system project captures
activities performed by different roles in real life banking which provides
enhanced techniques for maintaining the required information up-todate,
which results in efficiency. The project gives real life understanding of
Internet banking and activities performed by various roles in the supply
chain.
Scope
This Project investigates the entry threshold for providing a new
transaction service channel via the real options approach, where the entry
threshold is established by using an Internet banking system designed for
the use of normal users(individuals), Industrialists, Entrepreneurs,
Educational Institutions(Financial sections), Organizations and
Academicians under transaction rate uncertainty.
1.5.Technologies to be used
1.6 Overview
2)Overall Description
The following sections describe the general factors that affect
the product and its requirements.
Customer must have a valid User Id and password to login to the
system. After the valid user logs in he is shown the list of accounts he has
with the bank. On selecting the desired account he is taken to a page
which shows the present balance in that particular account number, user
can request details of the last n number of transactions he has
performed. User can make a funds transfer to another account in the
same bank. User is provided with a transaction password which is different
from the login password.
User can transfer funds from his account to any other
account with this bank. If the transaction is successful a notification
should appear to the customer, in case it is unsuccessful, a proper
message should be given to the customer as to why it failed. User can
request for cheque book/change of address/stop payment of cheques.
User can view his monthly as well as annual statements.
He can also take print out of the same. Appropriate help to be provided as
and when requested by the user.
environment such that he can maintain database & provide backups for
the information in the database. He can register the users by providing
them with username, password & by creating account in the database. He
can view the cheque book request & perform action to issue the cheque
books to the clients.
2.0.3.Communication Interface:
2.0.4.Product Features :
R A
I A
M
G
R A
Users of the system: In this online internet banking system, the users are
Administrators
Customers
Corporate.
1. Administrator:
He is the super user responsible for managing system
users, taking system backup, generating reports, maintaining organization
details, Starting Sessions and ending Sessions and also manages various
requests from different Types of users.
Providing UserName, Password and other information required for
the users to start an account.
Starting Sessions: The Administrator creates the system users and
will be assigned with the different roles. He is also responsible to
start the session when a particular user wants to use the system
every time(It is automatically managed setup).
Managing Data Backup: The Administrator is responsible for
managing entire details by taking the backup periodically. He also
takes the Backup of the database in order to prevent loss of data on
system crashes or inorder to prevent malfunctioning. He can take a
backup of entire database or a particular section.
Crash Recovery: The Administrator manages the crash recovery at
the time of system crash or failure occurs.
Ending session: The administrator is responsible for ending the
session when the particular user logged out of the system(It is
automatically managed setup).
2. Customer(Normal/others):
Ordinary customers have a user name & password with
which they can login into their account. They can perform all the
transactions such as funds transfer, balance enquiry, cheque book
request, etc by sitting at their home on internet.
Login: User can login to the system by providing appropriate
username and password provided by the administrator.
Selecting the Account: After logging in the user is provided
with a screen showing the details of accounts and he selects
one of the account inorder to perform the transaction.
3) Specific Requirements
ii)customer:
Ordinary customers have a user name & password with which they can
login into their account. They can perform all the transactions such as
funds transfer, balance enquiry, cheque book request, etc by sitting at
their home on internet.
iii) Corporate users : The corporate users will have the same
functionalities as that of a customer. The extra functionality of corporate
user is to have an internal administrator
3.2 Supplementary requirements:
1) Performance Requirements :System can withstand even though many
no. of customers request the desired service. Access is given to only valid
users of bank who requires the services such as balance enquiry, update
profile, funds transfer, mini statements, and request for stop payments
and for cheque book