Introduction:

What is E-Banking?
E-banking is defined as the automated delivery of new and traditional banking products and
services directly to customers through electronic, interactive communication channels. Ebanking includes the systems that enable financial institution customers, individuals or
businesses, to access accounts, transact business, or obtain information on financial products
and services through a public or private network, including the Internet. Customers access ebanking services using an intelligent electronic device, such as a personal computer (PC),
personal digital assistant (PDA), automated teller machine (ATM), kiosk, or Touch Tone
telephone. While the risks and controls are similar for the various e-banking access channels.
Two primary types of Internet websites that are used for e-banking: informational and
transactional.

a. Informational Website:
Informational websites provide customers access to general information about the financial
institution and its products or services. Risk issues examiners should consider when
reviewing informational websites include:

Potential liability and consumer violations for inaccurate or incomplete information

about products, services, and pricing presented on the website;
Potential access to confidential financial institution or customer information if the
website is not properly isolated from the financial institutions internal network;
Potential liability for spreading viruses and other malicious code to computers
communicating with the institutions website; and
Negative public perception if the institutions on-line services are disrupted or if its
website is defaced or otherwise presents inappropriate or offensive material.

b. Transactional Website:
Transactional systemites provide customers with the ability to conduct transactions through
the financial institutions website by initiating banking transactions or buying products and
services. Banking transactions can range from something as basic as a retail account balance
inquiry to a large business-to-business funds transfer. E-banking services, like those delivered

1|P a g e

through other delivery channels, are typically classified based on the type of customer they
support.
The following table lists some of the common retail and wholesale e-banking services
offered by financial institutions.

Table 1: Common E-Banking Services

Retail Services

Wholesale Services

Account management

Account management

Bill payment and presentment

Cash management

New account opening

Small business loan applications,

Consumer wire transfers

approvals, or advances

Investment/Brokerage services

Commercial wire transfers

Loan application and approval

Business-to-business payments

Account aggregation

Employee benefits/pension
administration

Examiners reviewing transactional e-banking services should consider the following issues:

Security controls for safeguarding customer information;

Authentication processes necessary to initially verify the identity of new customers and
authenticate existing customers who access e-banking services;
Liability for unauthorized transactions;
Losses from fraud if the institution fails to verify the identity of individuals or
businesses applying for new accounts or credit on-line;
Possible violations of laws or regulations pertaining to consumer privacy, anti-money
laundering, anti-terrorism, or the content, timing, or delivery of required consumer
disclosures; and Negative public perception, customer dissatisfaction, and potential
liability resulting from failure to process third-party payments as directed or within
2|P a g e

specified time frames, lack of availability of on-line services, or unauthorized access to

confidential customer information during transmission or storage

1.1Purpose:
The aim of this project is to develop a secured online banking system with the following
objectives:
1. Create a banking system that is easily accessible by customers from the comfort of
their homes, offices etc.
2. Reduce the flow of human traffic and long queues at banks
3. Reduce the time wasted in going to banks to stay on queues.
4. Promote efficient and effective banking for the banks by focusing on those services
that still require physical presence at the banking hall.

1.2Document Convention:

Main Section Title: Font: Times New Roman: Bold: Size: 16

Sub Section Title: Font: Times New Roman Bold: Size: 14
Other Text matter: Font: Times New Roman: Size: 12

1.3Intended Audience and Reading Suggestions:

This SRS would be used by the following persons :

Bank Employees: They would be using the Core Banking Solution to perform the
variousbanking functionalities.
Bank Customers: They would be using the e-Banking Solution to view their account
details.
Research Students: Research students are advised to read all the sections of this
document to get an overall idea of the workflow and technicalities of the software.
Testers: It can be used as a documentation to know the interfaces.

1.4Product Scope:
This project has the following scope.
3|P a g e

1. Administrator has full information about a particular customer because the database is
in his hands and can see any particular record through the database.
2. Online updating of customer details.
3. Online shopping of items, tickets, charity and paying of bills.
4. Customer can complaint and contact us online about the different features being
posted online. A 24 hrs calling service has been provided which the customers can use
to contact the customer service.
5. Online downloading of different forms for issuing ATM cards, applying for different
kinds of loan, opening different kinds of accounts, bonds and insurance.

1.5References:

www.mySql.com
www.BlogEngine.net
www.W3Cschool.com

Software Life Cycle Model

2.1. Waterfall Model:
This model states that phases are organized in linear order. That is
why it is called linear sequential model. As shown in fig-1.2.The project begins with
feasibility study than requirement analysis than design than coding. Each one is done after the
completion of other. After coding, testing is done and system is installed than regular
operation of system and maintenance is done

Feasibility Study:
The purpose of this phase is to produce the feasibility study
document that evaluated cost and benefit of the system. The result of feasibility study is a
document that should contain following:
1) Definition of problem
2) The goals to be achieved
3) Alternative solutions and expected result
4) Required resources
5) Benefit from the solution
6) Scope of the solution.

Requirement Analysis:
4|P a g e

In this phase communication gap is minimized. Requirement

analysis is undertaken after feasibility study has performed. The study may be performed by
the developer or organization. As shown in fig-1.1,Two parties are involved in software
development.
1) Client
2) Developer

Figure-1.1 (Requirement Analysis)

The developer usually does not understand the problem domain of the client and the client
does not understand the issue involved in the software development. This causes a
communication gap .in this phase where requirements are not clear, much interaction is
needed between two parties and output of this phase is called SRS.

Figure-1.2(Waterfall model)

5|P a g e

Design:
The goal of this phase is to transform the req. specification into a structure
that is suitable for implementation in some programming language. Overall software
architecture is defined and the high level and detailed design work is performed.

Coding:
Coding is a phase in which programs are written by using same programming
language. Output of this phase is document called program but this document is executable.

Testing:
Testing focuses on the logical internals of software and assuring that all the
statements have been tested.

Installation:
After testing software is installed and any modification to the software is
related to this phase.

Advantages:
It has well defined stages and activities. It detects error due to validation and verification.

Limitation:
1) Freezing the requirements required fusing the hardware. A large project might take few
years to complete. If the hardware selected early then due to speed at which hardware
techniques changes it is likely that final software will use a technique which is on the
verge of becoming obsolete.
2) It leads to blocking state. According to this model some team member must wait for other
members to complete the development task.
3) When to use:
When the developing organization is quite familiar with the problem domain than
waterfall approach works well.

2.2 Agile Model:

Agile SDLC model is a combination of iterative and incremental process models with focus
on process adaptability and customer satisfaction by rapid delivery of working software
product.
Agile Methods break the product into small incremental builds. These builds are provided in
iterations. Each iteration typically lasts from about one to three weeks. Every iteration
involves cross functional teams working simultaneously on various areas like planning,
requirements analysis, design, coding, unit testing, and acceptance testing.
At the end of the iteration a working product is displayed to the customer and important
stakeholders.

What is Agile?
Agile model believes that every project needs to be handled differently and the existing
methods need to be tailored to best suit the project requirements. In agile the tasks are divided
to time boxes (small time frames) to deliver specific features for a release.
Iterative approach is taken and working software build is delivered after each iteration. Each
build is incremental in terms of features; the final build holds all the features required by the
customer.
6|P a g e

Here is a graphical illustration of the Agile Model:

Agile thought process had started early in the software development and started becoming
popular with time due to its flexibility and adaptability.
The most popular agile methods include Rational Unified Process (1994), Scrum (1995),
Crystal Clear, Extreme Programming (1996), Adaptive Software Development, Feature
Driven Development, and Dynamic Systems Development Method (DSDM) (1995). These
are now collectively referred to as agile methodologies, after the Agile Manifesto was
published in 2001.
Following are the Agile Manifesto principles
Individuals and interactions - in agile development, self-organization and
motivation are important, as are interactions like co-location and pair programming.
Working software - Demo working software is considered the best means of
communication with the customer to understand their requirement, instead of just depending
on documentation.
Customer collaboration - As the requirements cannot be gathered completely in the
beginning of the project due to various factors, continuous customer interaction is very
important to get proper product requirements.
Responding to change - agile development is focused on quick responses to change
and continuous development.

Agile Vs Traditional SDLC Models:

Agile is based on the adaptive software development methods whereas the traditional SDLC
models like waterfall model is based on predictive approach.

7|P a g e

Predictive teams in the traditional SDLC models usually work with detailed planning and
have a complete forecast of the exact tasks and features to be delivered in the next few
months or during the product life cycle. Predictive methods entirely depend on the
requirement analysis and planning done in the beginning of cycle. Any changes to be
incorporated go through a strict change control management and prioritization.
Agile uses adaptive approach where there is no detailed planning and there is clarity on future
tasks only in respect of what features need to be developed. There is feature driven
development and the team adapts to the changing product requirements dynamically. The
product is tested very frequently, through the release iterations, minimizing the risk of any
major failures in future.
Customer interaction is the backbone of Agile methodology, and open communication with
minimum documentation are the typical features of Agile development environment. The
agile teams work in close collaboration with each other and are most often located in the
same geographical location.

3.Overall Description:
3.1 Product perspective:
The project can be divided in to nine main modules.

Loans
Online Services
Deposits
Insurance
Branch Locator
Withdrawal

Loans:
This module stores the information regarding the various loans on offer now. We have three
loans namely HOME LOAN, PERSONAL LOAN, EDUCATION LOAN, And
AGRICULTURAL LOAN. Under HOME LOANS we have home, land and home equity
loans which have their own eligibility criterias and the loan amount. Sanctioning will only be
done after the verification is complete. Now taking loans is made simple by just filling up a
form which is available online for downloads free of cost. Once the form is filled and sent to
any of the branches listed on the site, verification will begin within 3 working days and only
after full verification the loan process will begin. The customer at any point of time can
change/withdraw his application for loan.
Under Education loan CBC helps for students to continue their higher education. Thats why
every student has the financial support for their degree if their parents are not able to pay so
much expensive tuition fee of higher degrees. Procedure would be almost same for all types
of loan.

Online Services:
This module works with the online payment of bills. The customer has to just sit at his house
and get the comfort of paying his bills online. Under online services we have paying of bills,
charity, shopping online and tickets. The only requirement is that the customer should have
an INTERNET ID. This can be applied for online also. The amount will get deduced from
the customers account immediately. Bill payment includes electricity, phone, mobile,
insurance premium etc.

8|P a g e

An extra feature which has been added o this site is that if the customer wants he can
allow the bank to pay his bills on a regular basis without him worrying. A reminder will also
be sent to his account once the payment is done and once before the payment is to be done.
Cooperation bank has many esteemed partners like EBAY, INDIAN RAILWAYS, AIR
DECCAN, REDIFF etc and many other companies which facilitate online shopping. For
charity also the partners are FIVE INDIA, THE CLAUSE, VOLUNTEER,
INFOCHANGE etc.

Deposits:
This department deals with the different kinds of accounts a customer can retain namely:
savings, current, fixed deposits, multiple and recurring. The customers can open such
accounts online also but only after verification. The criterias and features for different types
of accounts have been provided and one can read them before creating an account, say for
example a fixed deposit account will repay a customer a higher amount than a savings
account.

Insurance:
In this section the customers are provided with 2 types of insurance life and general. General
consists of motor, health and home. Motor insurance consists of both 2 and 4 wheeler.
Claiming conditions are given under which these insurances can be claimed. These
insurances can be bought online by applying for it.

Bonds:
Under this section 2 kinds of bond schemes are embedded non taxable and taxable.8%
savings (taxable) bond schemes are issued in demat form and tax shall be deducted at source.
Schemes are available at multiples of Rs.1000/-.customers can apply online by visiting the
RBI website. 6.5% savings (non taxable) bond schemes are repayable after expiration of 5
years. Premature encashment is allowed after minimum lock-in period of 3 years from the
date of issue.

Branch Locator:
The various ATM branches and the various branch centers can be located using this section.
The customer can just type in the name of the city to get the names of the exact branches in
that particular city.

3.2 Product Functions:

MAIN FUNCTIONS OF THE SYSTEM

Login System of the SYSTEM

New General Account Creation
New Customer Registration
Update Customer Info & Account Info
Close General Account
Display Account Info
New Loan Account Creation
Loan Account Closing
9|P a g e

Update Branch Info

New Bank Employee Registration
Add New Account Type
Add New Loan Account Type
Display Branch Information
Display Employee Information
Logout System

3.3 User Classes and Characteristics:

Bank employee: The Bank Employees would be the sole users of the system. They
wouldalso use the SYSTEM for their personal accounts in that Bank.
Bank Customers: The customers would use the SYSTEM.
Research Students: Research students need to get acquainted with characteristics of boththe
SYSTEM as well as SYSTEM , before they can suggest any new enhancements to them.
They shouldhave enough understanding of this product so as to identify shortcomings in it.
Moreverin this project a certain task would be accomplished by different ways in different
places. This would be done in order to put forth an array of options before the Students who
would be aspiring to do something similar .
Open Source Community: The Open Source Community would be a major user class ofthis
product. The users could go through the document for adding extra functionalities to
theproduct.

3.4 Operating Environment:

Hardware Requirements:
Intel Pentium III processor at 750 MHz or faster, minimum of 1G available disk space for
installation (including IBM SDK), minimum of 512 MB memory, CD-ROM drive.

Software Requirements:
Software tools used:Microsoft visual studio2010
Language: C#
Platform: ASP.NET,Sql Management Studio Express.

3.5 Design and Implementation Constraints:

Enhancements to the security features might lead to performance overhead.

Recommended bandwidth is 64 Kbps.
10|P a g e

Central Server should be online round the clock.

3.6 User Documentation:

After the completion of the project, a well documented user manual will be provided.

4.External interface requirements:

4.1 User Interfaces:
It mainly consists of the main page which consists of various menus and options.Besides this
they consist of hierarchies of options in the left corner for managing the account.when user
choose the menus and options they are shown to the various data related to the selected
option.
On clicking on the desired button or menu item, the user will be shown the respective screen.
The user would then enter the required data for processing and press the 'Submit button, after
which the processing would be done and the user would be returned to the main page.
There would also be a Logoff button which would help the user to end his session with the
system and he will be transferred back to the Login screen.

4.2 Hardware Interfaces:

Not Applicable

4.3 Software Interfaces:

The product is implemented in the Windows Operating System Environment (intel Pentium
III processor) on Microsoft visual studio,framework 4.0.

4.4 Communications Interfaces:

This product uses an internet connection to connect to the main database server of the bank.

5. System Features:
5.1LogIn:
5.1.1 Description and Priority:
This feature will be used to LOG IN into the system (only permitted users can use the
system). It is done inorder to prevent any misuse of system.

5.1.2 Stimulus/Response Sequence:

When the user gives the correct username and password combination, he/she is
transferred to the main screen or the main page.

5.1.3 Functional Requirements:

Purpose:
To check the credibility of an user and to prevent any misuse of the product.

11|P a g e

Inputs:
The input will be username and password combination

Output:
The user will be transferred to the main page on successful validation and will be alerted if
the validation is unsuccessful.

5.2New Customer Registration:

5.2.1 Description and Priority:
Its purpose is to create a new customer of the Bank. A Customer must be registered
before he/she can create any new accounts in any of the branches.

5.2.2 Stimulus/Response Sequence:

On successful validation of each data field (customer details), the registration takes place and
the success message is displayed.

5.2.3 Functional Requirements:

Purpose:
To register a new customer.

Inputs:
The required data for registration of a new customer in the bank (Like Name, Address
,Designation etc).

Output:
A Success Message be displayed on successful registration or else an error message will be
displayed.

5.3 New account Creation:

5.3.1 Description and Priorit:
Its purpose is to create a new account of a customer.

5.3.2 Stimulus/Response Sequence:

On successful validation of each data field, the registration takes place and the
accountnumber is displayed.

5.3.3 Functional Requirements:

Purpose:
To create a new account for the customer.
12|P a g e

Inputs:
The required data for registration of a new account (Joint Account Details, Balance,Account
Type etc) in the bank.

Output:
Account Number & Pass Book Number will be displayed on successful registration or
else error message will b e displayed.

5.4Updating Customer Information:

5.4.1 Description and Priority:
To update and change the Customer profile

5.4.2 Stimulus/Response Sequence:

On successful validation of each data field, the updation procedure takes place.

5.4.3 Functional Requirements:

Purpose:
To update the Customer profile.

Inputs:
The required data for updating the information of a customer would be given

Output:
Either a successful acknowledgment is displayed or else an error message is displayed
.5.5Updating account Information:

5.5.1 Description and Priority:

To update and change certain features of an Account like Overdraft Status, Overdraft
Limit, Operation Mode etc..

5.5.2 Stimulus/Response Sequence:

On successful validation of each data field, the updation procedure to occurs.

5.5.3 Functional Requirements:

Purpose:
13|P a g e

To update and change the selected Account Details

Inputs:
The required data for updating the information of an Account would be given

Output:
Either a successful acknowledgment is displayed or else an error message is displayed.

5.6Account Closing System:

5.6.1Description and Priority:
Its purpose is to close the account of a customer.

5.6.2Stimulus and Response:

On successful validation of each data field, the closing procedure takes place and the
account is closed.

5.6.3Functional Requirements:
Purpose:
To close the account of a customer.

Inputs:
The required data for closing an account in the bank i.e. the Account Number.

Output:
Either a successful acknowledgment is displayed or else an error message is displayed.

5.7 View Details of an account:

5.7.1 Description and Priority:
This feature would be used to view the details of a an Account (customer info and
account info).

5.7.2 Stimulus Response/Sequences:

On successful validation of the Account Number, the respective details are displayed.

5.7.3 Functional Requirements:

Purpose:
To view the details of an account.

14|P a g e

Inputs:
The required data for viewing the information of an account i.e. Account Number

Output:
On successful verification, the details of the respective entities are displayed or else an
error message is displayed.

6.Non-Functional Environment:
6.1 Performance Requirements:
The most important factor in the working of the whole project is its Connectivity with the
Serverand the Mode of Connection. If the connection is a 64 Kbps one then the performance
of the Products (SYSTEM & SYSTEM) would be much better than that with a 10 Kbps
connection.

6.2 Safety Requirements:

Not Applicable

6.3 Security Requirements:

The Central Server comprises of the Apache Server 2.2 and MySqlServer . Both are open
source software solutions and the best among their fields. They have their respective Security.
Mechanism which would prevent any unauthorised access or exploitation of the Server.

6.4 Software Quality Attributes:

This project would be developed completely using open source software and platforms.
So,anybody can use and enhance the software further without spending any money.

6.5 Business Rules-Not Applicable

DATA FLOW DIAGRAM

15|P a g e

The Data Flow Diagram is the graphical representation that depicts information flow

and the

transforms that are applied as data move from input to output. DFD is a model, which gives
the insight into the information domain and functional domain at the same time. DFD is refined
into different levels. The more refined DFD is, more details of the system are incorporated. In
the process of creating a DFD, we decompose the system into different functional subsystems.
The DFD refinement results in a corresponding refinement of data. After going through the
current working process of the department, we can create the Data Flow Diagram (DFD). We
have refined the system up to two levels. Each break-up has been numbered as per the rule of
DFD. We have tried to incorporate all the details of the system but there is some chance of
further improvisation because of the study that is still going on for the project
development.These are the some symbols that are used to show some specific process in the
DFD. Some company may have their own symbols to show the unique one task in the process.
Now let us discuss Abut the flow Diagrams of E-BANKING system.
DFD is quit important as its records in a pictorial form all the information flow within the
system. With the help of DFD we can identify the current information structure of the system.
The structure of the system can thus be analyzed and it helps in making improvement within
the current system. We can group a few processing sites together or reduce expenditure; we
redirect the flow of the information to make the system more efficient.DFD allows us
understand the flow of the data such that we can understand the way that a data should flow.
7.1 Data Dictionary:
In our data flow diagrams, we give names to data flows, processes and data stores. Although
the names are descriptive of the data, they do not give details. So following the DFD, our
interest is to build some structural place to keep details of the contents of data flows, processes
and data stores. A data dictionary is a structured repository of data about data. A data dictionary
has many advantages. The most obvious is documentation; it is valuable in any organization.
Another advantage is improving analyst and user communication. If we choose words that
represent the general thinking of common vocabulary, there are three classes of items to be
defined.
7.1.1 Data Element- The smallest unit of data that provides no further decomposition. For
example, date consists of day, month and year.
7.1.2 Data Structure -A group of data elements handled as a unit. For example, phone
is a data structure consisting of four data elements.
16|P a g e

7.1.3 Data flows and Data Store-Data flows are data structures in motion, whereas
data stores are data structures at rest.
After discussing about the symbol we can easily understand the Data flow diagrams Related
to E-Banking modules. We have System flow diagram of E-banking, of each module which
we are going to discuss below:
7.2 Database Design:
A database is a collection of logically related data, data records or a set of related data files
about some entity. The data records are stored with minimum data redundancy and are
organizes such that an end user gets the information quickly out of it.
In the project, the database being used is the Sql Server. Database system and the connection
to the database are made by Asp.Net interface. The tables will be created using SQL
statements; the runtime SQL will be sent to database and the query result will be sent back to
application by Connection strin
7.3 DATABASE TABLES:
7.3.1 SIGN UP:
COULMN NAME

DATA TYPE

Name

VARCHAR(50)

Age

INT

Gender

VARCHAR(50)

Country

VARCHAR(50)

State

VARCHAR(50)

City

VARCHAR(50)

Account_no

NUMARIC(18,0)

Required_password

VARCHAR(50)

Confirm_password

VARCHAR(50)

7.3.2 JOB_APPLY:
COULMN NAME

DATA TYPE

17|P a g e

NAME

VARCHAR(50)

AGE

NCHAR(10)

GENDER

VARCHAR(50)

EMAIL-ID

VARCHAR(50)

COUNTRY

VARCHAR(50)

STATE

VARCHAR(50)

CITY

VARCHAR(50)

HIGHER

VARCHAR(50)

QUALIFICATION
MARKS OBTAIN

INT

OUT OF

INT

SUBJECT

VARCHAR(50)

APPLYING FOR

VARCHAR(50)

ADDRESS

VARCHAR(50)

7.3.3 OPENING ACCOUNT REQUEST:

COULMN NAME

DATA TYPE

18|P a g e

NAME

VARCHAR(50)

AGE

INT

GENDER

VARCHAR(50)

EMAIL-ID

VARCHAR(50)

MOBILE_NUMBER

NUMARIC(18,0)

COUNTRY

VARCHAR(50)

STATE

VARCHAR(50)

CITY

VARCHAR(50)

ACCOUNT TYPE

VARCHAR(50)

ADDRESS

VARCHAR(50)

7.3.4 QUERY TABLE:

COULMN_NAME

DATA_TYPE

NAME

VARCHAR(50)

19|P a g e

AGE

INT

GENDER

VARCHAR(50)

MOBILE-NO

NUMARIC(18,0)

COUNTRY

VARCHAR(50)

STATE

VARCHAR(50)

CITY

VARCHAR(50)

QUERY_TYPE

VARCHAR(50)

ASK_QUERY

VARCHAR(50)

7.3.5 TRANSACTION TABLE:

COULMN NAME

DATA TYPE

DATE

DATETIME

ACCOUNT_ID

NUMARIC(18,0)

20|P a g e

TID

NUMARIC(18,0)

TRANSACTION_TYPE

VARCHAR(50)

WITHDRAWAL

VARCHAR(50)

DEPOSITE

VARCHAR(50)

BALANCE

NUMARIC(18,0)

7.3.6 USERS_ACCOUNT:
COULMN NAME

DATA TYPE

NAME

VARCHAR(50)

21|P a g e

AGE

INT

SEX

VARCHAR(50)

COUNTRY

VARCHAR(50)

STATE

VARCHAR(50)

CITY

VARCHAR(50)

ACCOUNT_NO

NUMARIC(18,0)

PASSWORD

VARCHAR(50)

APPENDIX:Analysis Models
UML DIAGRAM OF EBANKING SYSTEM
Use Case diagram for Banking System:

22|P a g e

System

transaction
<<include>>
<<extend>>
invalid card
insert card
user

<<include>>
atm transaction

retail institution
invalid pin
<<extend>>
<<include>>

pin validation

invalid login
bank employee
web merchant

<<extend>>

online transaction
<<include>>

Bank Database

<<include>>
login
<<include>>

logout
<<include>>

client desktop transaction

1.OnlineTransaction - use case specifications:

Brief Description:
Account transaction begins when customer is successfully logged in to the site. Several
menus where displayed related to profile of customer and the recent transactions and the
current account balance. The main purpose of using online account transactions is to transfer
cash from one account to another for this purpose the customer is provided fields to specify
the accounts to which he is transferring amount. After every transaction a confirmation is
displayed to customer. The customer is also provided the possibility to change the account
login password, but not the user id, every transaction is added to the bank database.

Flow of Events:
Basic flow:
1. User enters username and password.
2. Bank Database validates the user.
23|P a g e

3. On success user can transfer money, change his password and view his profile.

Alternate Flow:
If in the basic flow, the details specified by user are invalid then he is informed that his login is failed
.Then the user may quit the system or he may create a new account.

Pre Conditions:
The user should have a valid account in the bank.

Post Conditions:

The account database is modified after transaction.

2. Login Use Case Specifications:

Brief Description:
The online customer or a bank employee has to login to access their accounts from bank
database. A vendor is provided for communication with banks database and this vendor
provides safety and atomicity. A user may be an invalid user so the system has to prompt the
person appropriately.

Flow of Events:

Basic flow:

1.User enters username and password.

2. Bank Database validates the user.
3. On success user can precede the transaction.

Alternate Flow
If in the basic flow, the details specified by user are invalid the he is informed that his login is
failed.

Pre Conditions - The user must possess a login id and password.

Post Conditions
3. Logout Use Case Specification:
Brief Description:
The person who ever logged in to the system or bank database has to logout after all the work
is over. The vendor provided for communication is now closed from database.
24|P a g e

Flow of Events:

Basic Flow:

1. User clicks the logout

2. All the transactions he performed are reflected in the bank database.

Alternate Flow:

If in the basic flow, if the internet connection is lost user must refresh the page again.

Pre Conditions - The user should have been logged in already.

Post Condition- None.
4 .Invalid Login-Use Case Specification:
Brief Description:
If a person with a invalid user id or password details want login to the system, the system has
to prompt the person about failure and should not open the vendor of communication until he
furnishes valid user id & password.

Flow of Events:
Basic flow:
1. User enters username and password.
2. Bank Database validates that the login is invalid.
3. Further he may not be allowed to proceed until enters a valid login.

Alternate Flow:
If the user enters a valid login he must be allowed to proceed further.

Pre Conditions -None.

Post Condition-None

ONLINE TRANSACTION EBANKING

EBANKING COLLABORATION DIAGRAM
25|P a g e

Online Transaction Activity Diagram:

open web page

create account

enter id and pwd

no
valid login

furnish details
yes

choice menu

no
valid details

yes
submit

amount transfer

view details

change pwd

finished

Component Diagram for Banking System:

26|P a g e

Deployment Diagram for Banking System:

27|P a g e

28|P a g e