Vous êtes sur la page 1sur 34

Online Banking

ACKNOWLEDGEMENT

It gives us great pleasure in expressing thanks and profound gratitude to our Faculty
Guide, Mr.Pratik Modi, Department of Computer Engineering, L.D.R.P Institute of
Technology and Research, Gandhinagar for her valuable guidance and continual
encouragement throughout the project. We are heartily thankful to her for her time to time
suggestion and the clarity of the concepts of the topic that helped us a lot during this study.

We are also thankful to Prof. A K Goyal, Head of Computer Engineering


Department, for his continual kind words of encouragement and motivation throughout the
major Project.

The blessings of God and our respective family members makes the way for
completion of major project. We are very much grateful to them.

The friends, who always bear and motivate us throughout this course, we are thankful
to them.

Dadhaniya Julyars (06CE008)


Parmar Kalpesh J. (06CE031)

2|Page
Online Banking

ABSTRACT

This 'Online Banking' Project is a model Internet Banking Site. This site enables the
customers to perform the basic banking transactions by sitting at their office or at homes
through PC or laptop. The customers can access the banks website for viewing their Account
details and perform the transactions on account as per their requirements.

With Internet Banking, the brick and mortar structure of the traditional banking gets
converted into a click and portal model, thereby giving a concept of virtual banking a real
shape. Thus today's banking is no longer confined to branches. E-banking facilitates banking
transactions by customers round the clock globally.

The primary aim of this software is to provide an improved design methodology,


which envisages the future expansion, and modification, which is necessary for a core sector
like banking. This necessitates the design to be expandable and modifiable and so a modular
approach is used in developing the software. Anybody who is an Account holder in this bank
can become a member of online banking. He has to fill a form with his personal details and
Account Number.

All transactions are carried out online by transferring from accounts in the same Bank.
The software is meant to overcome the drawbacks of the manual system. The software has
been developed using the most powerful and secure backend MS SQL Server 2005 and the
most widely accepted web oriented as well as application oriented .Net Platform 2008.

3|Page
Online Banking

Table Of Contents

Chapter 1: Introduction
1.1.Project Profile ………………………………………………………….6
1.2.Scope of System………………………………………………………...6
1.3.Technological Review…………………………………………………..7

Chapter 2: Project Management


2.1.Project Model…………………………………………………………8
2.2.Project Plan……………………………………………………………9
2.3.Schedule Representation………………………………………………9
2.4.Risk Analysis………………………………………………………….11

Chapter 3: System Analysis


3.1. Problem definition……………………………………………………12
3.2. Existing System Study………………………………………………..12
3.3. Problem & Weaknesses of Current System………………………….12
3.4. Proposed New System………………………………………………..12
3.5. Requirement Analysis………………………………………………..13
3.5.1. Functional Requirements…………………………………...13
3.5.2. Non-Functional Requirements……………………………...13
3.6. Hardware & software requirements……………………………………14
3.7. Validations……………………………………………………………..14
3.8. Feasibility Study……………………………………………………….15
3.8.1. Technical Feasibility…………………………………………15
3.8.2. Operational Feasibility……………………………………….15
3.8.3. Schedule Feasibility……………………………………………16
3.8.4. Economical Feasibility…………………………………………16

Chapter 4: System Design


4.1. Functions of the system………………………………………………….17
4.1.1. Use Case Diagram………………………………………………17
4.2. Data Modeling……………………………………………………………18
4.2.1. Class /E-R Diagram……………………………………………..18
4.2.2. System Activity Diagram……………………………………….19
4.2.3. Data Dictionary…………………………………………………22
4.2.4. Sequence Diagram ………….………………………………….23
4.3. Functional Modeling……………………………………………………..25
4.3.1. Context Diagram……………………………………………….25
4.3.2. Data Flow Diagram…………………………………………….26

4|Page
Online Banking

Chapter 5:Functional Modeling


5.1. Input & Output Design………………………………………………….28
5.1.1 Screen Layout………………………………………………….28
5.1.2 Reports…………………………………………………………28

Chapter 6:Testing
6.1. Test cases & Results……………………………………………………..33

Enhancement …………………………………………………………………….34

Bibliography………………………………………………………………………34

5|Page
Online Banking

Chapter 1: Introduction

1.1 Project Profile:

Title : “Online Banking System”

Description : This system carries out account creation and transaction processing
through internet that provides an entire range of banking services
online.

Platform : Front- End : ASP.NET using C# lang.


Back-End : SQL SEVER 2005.

Hardware Intel Pentium -4


Requirement : 512 MB of RAM
80 GB of HDD

Software Microsoft Windows 2007


Requirement: Visual studio 2008(compact frame work 3.5)
SQL server management studio 2005

1.2 Scope Of System :

The Online Banking System is being developed to maintain various types of bank
accounts like Saving, Current, Fixed deposit etc.

 Various functionality provided by this system are as bellows:-

• The System maintains the details of the customers (bank users), transaction details
of each accounts, account details etc.
• User can create a new bank account of particular type using this system.
• User can perform various banking transaction online.
• User can enter his/her personal details like name, birth date, address etc as
well as his account information online.
• User can modify his/her personal details.

6|Page
Online Banking

• User can request for chequebook for his current account online.
• If user forgot his/her password then he or she can know his/her password
using this system.
• User can view and print various reports using this system.

1.3 Technological Review:

• The system operates in Windows 95/98/XP/Vista environment. Also it


requires IE8 / Mozilla Firefox.
• Platform Used : ASP.NET 3.5
• Database : SQL Server 2005 Express Edition.
• Framework : .NET 3.5
• Server : IIS
• Technologies :
Internet(HTML, Java Script, ASP.NET, C#)
• Tools : Visual Studio 2008 Team System

7|Page
Online Banking

Chapter 2: Project Management

2.1 Project Model :

Process Model: Linear Sequential Model


Model Suggest a systematic ,sequential approach to software development,
that begins at system level and progress through Analysis, Design, Coding Testing
and also Support. Also called water fall model

SYSTEM/INFORMATION
ANALYSIS DESIGN CODE TEST
ENGINEERING

[Linear Sequential Model]


System /Information Engineering and Modeling:
Works begin by establishing requirement for all system elements and software
must interact with elements like hardware people and database. System engineering
and analysis encompass requirement gathering at some level.
Software Requirement Analysis:
In requirement analysis annalist must understand information domain for s/w
as well as required function, behavior, performance, interface. Requirement for
documents and review with customer.
Design:
It focus on Data structure, s/w architecture, interface representation, and
algorithm. It translate requirement into software representation.
Code generation:
Design must translate into machine readable form it is task og code
generation.
Testing:
Once code generated, program testing begins. It focus on logical internal of
software ensure statement is tested. To uncover error and define i/p will produce
actual results.

8|Page
Online Banking

Support:
Customer required functional or performance enhance, or error have been
uncounted so software support / maintenance required.

2.2 Project Plan:


It is efficient to secure for the administrator for their data wrapping and
another miss use of their details. The customers can access the banks website for
viewing their Account details and perform transactions on account as per their
requirements. Also One prime objective to save papers.

2.3 Schedule Representation


Generalized project scheduling tools and technique can be applied with little
modification to software projects.
Program evolution and review techniques (PERT) and critical path method
(CPM) are two project scheduling method that can be applied to software
development. Both techniques are driven by information already developed in earlier
project planning activities:
 Estimate of effort.
 A decomposition of the product function.
 The selection of appropriate process model and task set.
 Decomposition of tasks.

ACTIVITY START DATE FINISH DATE

Requirement Analysis 20-02-2010 23-02-2010

System Analysis 24-02-2010 2-03-2010

System Design 3-03-2010 23-03-2010

System Coding 24-03-2010 17-04-2010

Testing and Integration 18-04-2010 29-04-2010

9|Page
Online Banking

Final Implementation
Coding & Testing
Coding & Testing
System Design
System Design

Analysis

Requirement Gathering

System study

0 10 20 30
Days

10 | P a g e
Online Banking

Actual
Days

Estimated
Days
Final Implementation

Coding & Testing

System Design

Analysis

Requirement Gathering

System study

0 10 20 30

2.4 Risk Analysis

 There are three main categories of risks which can affect a software project.

Project Risk:

 Project Risk concern various forms of budgetary, schedule, personnel,


resource, and customer-related problems.

 An important projects risk is schedule slippage.

 Since software is intangible, it is very difficult to monitor and control a


software project.

11 | P a g e
Online Banking

 It is very difficult to control something which cannot be seen,

 Unlike in a manufacturing plant where the product taking shape can be seen.

 The invisibility of the software product being developed is an important


reason why many software projects suffer from the risk of schedule slippage.

Technical Risks:

 Technical risks concern potential design, implementation, interfacing, testing


and maintenance problems.

 Technical risk also include ambiguous specification, incomplete specification,


changing specification, technical uncertainty, and technical obsolescence.

 Most technical risks occur due to the development team’s insufficient


knowledge about the product.

Business Risks:
 Business Risks include risks of building an excellent product that no one
wants, losing budgetary or personnel commitments etc.

Chapter 3: System Analysis

3.1 Problem definition


The Online Banking System is being developed to maintain various types of
bank accounts like Saving, Current, Fixed deposit etc.It is efficient to secure for the
administrator for their data wrapping and another miss use of their details.

3.2 Existing System Study

12 | P a g e
Online Banking

The existing system involves the following activities:


The present system consists of networking environment wherein regular activities
are automated. Further the status of a pay order whether the same has been honored or
not cannot be accessed, in case, if required. Readability of the records, which are
maintained manually, is also constrained in the present system.Since record are kept
on a paper registers, again is also a problem. Further retrieving information from such
records for a period is tedious, as the storage place restricts, old records will be kept
off the disk.Also report generation of the various areas is done manually using great
amount of manpower and time. Erroneous records may lead to misleading
information, which is more likely in manual system.

3.3 Problem & Weaknesses of Current System


The great limitation to the existing system is that the service to the customers
is limited to the bank hours only. The online banking facility provides 24 hours
service to the customer.
Limitations of the existing system. Leads to tedious manual work.
Amount of time consumption for recording all transactions. Error can occur during
the manipulation of several records..Economic justification is not obvious..The
technique adopted in this system is more complicated..Lack of technical background
towards the system.

3.4 Proposed New System


• In order to overcome the drawbacks in the existing system database is created which
is:
>Integrated
>Accessibility
>Reliable
>Consistent
>Flexible
>Secure
The present database
> Helps in speedy information retrieval
> Extract information from tables using menus
> Offers options of the online updation and in main ting up to date information. The
proposed system is
> Menu driven and user friendly
> It assists in quick deletion of errors by issuing appropriate error message.
> Validity of input data is automatically checked and error will be immediately
signaled
> Efficient utilization of resources.

3.5 Requirement Analysis

13 | P a g e
Online Banking

3.5.1 Functional Requirements


Functional Requirements for the Recruitment Process System are as follow:
1. Employee:
a) Log in to the system through the start up page.
b) Select appropriate city and post (Accountant, Manager,
Depositor and Executive).
c) Accountant can create an account for user.
d) Executive can show user record who has applied for
account and for net banking.
e) Depositor can perform transaction like Credit and Debit
according to customer requirement.
2. User (Customer):
a) Log in to the system through the start up page.
b) User can view account and operative status information.
c) User can transfer balance through our bank.
d) User can see ministatement.
e) User can edit profile.(change password)
f) User can ask question to bank executive via mail.

3.5.2 Non-Functional Requirements


1. Security
a. Confidentiality
b. Integrity: Extent to which data and procedures are
protected from unauthorized changes.
2. Reliability
a. Non-deficiency: Degree to which software doesn’t
contain undetected defects.
b. Fault-tolerance: Degree to which software works
without system failure.
3. Maintainability

a. Corrective: Finding and fixing faults.


b. Adaptive: Modify software for a change in
requirement. New functionality is added.

3.6 Hardware & software requirements

Hardware Interfaces:
• Operating System : Windows 95/98/XP
• Processor : Core2Duo 1.8 GHz or higher
• RAM : 1 GB or more

14 | P a g e
Online Banking

• Hard Drive : 80 GB or more

Software Interfaces:
 Database : Sql Server 2005 Express Edition
 Server : IIS
 Tools : Visual Studio 2008 Team System.
 Framework : .NET 3.5, java script

3.7 Validation

 If there’s a universal task in a programming web application, it’s the validation of the
value of the various controls. Most sites validate the controls on the server, and if
there’s any problem with the user-supplied data, they display the same page along
with the message description the error. To simplify the validation of the data
submitted to the server, ASP.NET provides control.
Required Filed Validator:
 This validator ensures that all required filed have value.

Compare Validator:
 This validator compares a control’s value to a constant value, a property of another
control, or even a database filed. If the comparison fails, the control is in error and
the user must supply a different value.

Range Validator:
 This validator ensures that that value entered by the User in a control falls within a
lower and upper bound. If not, the control is in error.

Regular Expression Validator:


 This validator compares the value of a control against a Regular expression. If the
comparison fails, the control is in error.

Custom Validator:
 This control allows you to supply your own validation Logic and it’s the most
flexible validator. However, you must supply your own code.
3.8 Feasibility Study
Feasibility analysis is basically the measure of how beneficial or practical the
development of information system will be to an organization and the developers of the
system. That is the organization will come to know that whether the project is feasible to
develop further or not.

The feasibility analysis tests are basically of four types as follows:


1. Technical feasibility
2. Operational feasibility

15 | P a g e
Online Banking

3. Schedule feasibility
4. Economic feasibility

3.8.1. Technical Feasibility:


Technical feasibility can be evaluated only when evaluations and design phases of life
cycle have been completed.

 The system we have proposed for transferring the data is practical as the user
just have to click once to transfer the file from one system to another system
within a small network. Any person who is not aware of use of the system and
technical terms can also use the system as it is just a one-click operation.
 The technologies used in today’s life is proposed for this software so that the
required functionalities are easily performed .It becomes easy and user friendly
system for any user to transfer the data with the maximum securities and
protection.
 The technical expertise for the proposed system is also there to guide the end
user to solve any non-technical or technical queries and also user’s queries easily
while any operations are performed during transfer of data. The time taken for the
system to be design is quite worth, because it is better to provide software with
errors within a short period of time. As we are trying to make FTP on our own, it
may takes more time.

3.8.2 Operational feasibility:


Operational feasibility focuses on whether the system will work when it is develop
and installed operationally system feasible.

 There is sufficient support for the project from manager and user. The system
is well liked and used to the extend that person will not be able to see reasons for
change.
 The proposed system will not cause any harm to its users.
 The response time of the system is satisfactory and not very time consuming.
 The system will provide to the end users with accurate information about the
system.
 The system will provide the security by providing the control on login a valid
user by checking his or her UserId and password.
 No special training required for the user it has self explanatory interface.
 Validation of data input is taken care of by system not by user.

3.8.3 Schedule Feasibility:


Schedule feasibility is the measure of how reasonable the project time-table is and to
determine whether the deadlines are mandatory or desirable.

16 | P a g e
Online Banking

 The schedule decides for this project to work properly without any errors are 3
months. As the project is an extension of an application already in existence and is
of more importance, the schedule decides for this development is quite worth.

 It is preferable to deliver an error-properly functioning information system two


months late then to deliver an error-prove useless information system on-time. So,
the time table is quite worth for each of the development phase of the project.
Missed schedules are bad. Inadequate systems are worth to provide to the user.

3.8.4 Economic Feasibility:


Economic feasibility is a measure of the cost-effectiveness of a project or solutions.
This is often called a cost-benefit analysis.
 The feasibility deals with the costs and benefits of information of the system.
The early phases of the project, i.e. project analysis and gathering the system
requirements costs and all the diagrams explaining the system more deeply to the
user is more.
 Costs are practically impossible to estimate at that stage because the end-user
requirements and alternate technical solutions may<not be identified at that stage.
 No extra cost for the modification or additional of software and hardware will
require in case of future expansion of the current system.
<Include>>

Chapter
<<Include>> 4: System Design

4.1Functions of the system


4.1.1Use Case Diagram

1. Manage <<Include>>
Transactions
17 | P a g e
Online Banking

2. Manage Accounts

Create , Update , Delete


Employee

4. Perform
Transactions

5. View & Print Reports

6. Manage
Account
User
Update

Delete

7. To open account of particular type


(saving, current ,FD)
particular type

Generate appropriate
messages Verify Data

System
Generate Unique
Account No.

4.2 Data Modeling


4.2.1 Class /E-R Diagram

18 | P a g e
Online Banking

Branch Info
-B_name
-B_Address
-B_city
+Insert()()
+Update()()

Customer Info
Account Info
-C_name
-Acc No -Acc No
-Birthdate
* * -C_name
-Address -Open date
-City -Address
-EmailId -Pincode
-Office No -City
-Mobile No -EmailId
-Branch -Mobile No
+Insert()() +Insert()()
+Update()() +Update()()

Current Acc
Saving Acc
-C_name
-C_name
-Acc no
-Acc No
-Date of open
-Date Of Open
-Nominee name
-Operative status
-Operative Stastus
-Branch_name
-Address
-Acc Status
-City
-Nominee name
-Pincode
+Insert()() -Branch name
+Update()()
+Insert()()
+Update()()

Saving Transaction
-Acc No Current Transaction
-Transaction Date -Acc No
-Type of transaction -Transaction Date
-Amount -Type of transaction
+Credit()() -Amount
+Debit()() +Credit()()
+Debit()()

4.2.2 System Activity Diagram

19 | P a g e
Online Banking

1) Access To System:

Enter Password and


User-ID

Is he/she
authorized
User?
Invalid
Valid User-ID &

Inputs try remains


Password &
Password User-ID

Employee performs
activities Prompt for
with banking system Reentry
Give command to open a Select category either
new A/C of particular Existing customer or
type. 2) New Customer

No Input try
Exit the
remains
System
Yes Is he/she new
customer?

User enter all of his


personal details & give No
commad to submit that
data.
User enter all of his A/C
details & if she/he is a
new customer then enter
login details.

2)Open Account of particular type: Save

System view details of


newly created A/C.
20 | P a g e
Online Banking

3)Transaction

21 | P a g e
Online Banking

Give command for


transaction in particular
A/C. type.

I/P try
Enter User-ID and remains
Password

Yes Is he/she No
authorized
user?

Prompt for Reentry


User enter all of his
personal details &
give commad to
submit that data.
No I/P try
remains
Give command to
perform transaction.

Invalid
transaction

Valid
transaction
System generate
Save appropriate message.

22 | P a g e
Online Banking

4.2.3 Data Dictionary

 Name of the tables:


1) ac_record
2) password
3) ministatement
4) citypass
5) netapply
6) netbanking
7) city
8) cu_apply

23 | P a g e
Online Banking

4.2.4 Sequence Diagram

For Transaction:

User
User Interface
Login System Transaction
Enter User Reading
and
Password Requirement
Lookup

Comparing Response

User ID
Requirement
Password correct
activation
‘activation successful ‘

Response

Transaction Details
Acknowledgement

24 | P a g e
Online Banking

To open new Account:

<<System>> <<User>> Customer Info. Account Login


Master

New Personal
Customer Details User Name &
Password
Selecting
Existing Customer

Activation Successful

Ack. of
newly Viewing
Created
A/C.

25 | P a g e
Online Banking

4.3 Functional Modeling

4.3.1 Context Diagram

• Context Diagram For Online Banking System:

Login
Bank

User Name,
Documents like Password
Cheque/DD etc.

Employee
Details like Personal & Accounting
Customer A/C’s. System

A/C. Details

Account Master

26 | P a g e
Online Banking

4.3.2 Data Flow Diagram

 Level 1:

Transaction type,
Amount, Acc No

Customer
Selection A/C. type,
Criteria A/C. No. + Customer ID
Customer ID A/C. Details + Cheque
& Personal
details

View/ Close Open Chang


Print an an e Data
Report A/C. A/C.

Details
Details
A/C.
Closed A/C.

Personal
Details

Changes
Data Data

Transactio
n
(Deposit, A/C Master Customer info.
Withdraws)

Details New
Record
Verify
Data

Collection
Statement

New record, changed System


A/C. status

Transaction Master

27 | P a g e
Online Banking

 Level 2:

Choose Insert all


Customer
Customer category either his/her
New Cust. Info.
1) New Cust or personal
2) Existing details.
cust.

Existing Cust.

Give
Acc Insert all of
No his A/C.
details & if
Invalid Acc new cust.
No Then login
details
Validate
Acc No Valid Acc
No
Command of Submit

Submission
Of Data
Login

A/C Master

1Generation
of Ack. of
new A/C.

28 | P a g e
Online Banking

Chapter 5: Functional Modeling

5.1 Input & Output Design


5.1.1 Screen Layout

 Account Information Page

29 | P a g e
Online Banking

Current Account Page:

Executive Form:

30 | P a g e
Online Banking

Depositor Page:

Net Banking Page:

31 | P a g e
Online Banking

User’s Account Summary after Login in net banking:

Ministatement Information:

32 | P a g e
Online Banking

Transfer fund page:

33 | P a g e
Online Banking

Chapter 6: Testing

6.1 Test cases & Results:


Testing
 From the psychological point view the designer, testing can be considered to be
destructive. If the software engineer doesn’t find them, the customer will find them.

Objective of Testing
 Error Detection
 Error Removal
 Error Tracking
 Regression Testing

White Box Testing :


 Knowing the internal working of a product, tests can be conducted to ensure that “all
gears mesh”, that is, that internal operation performs according to specification and all
internal components have been adequately exercised.

Black Box Testing


 Mainly black box testing consists of assuming that the logic structure of the code is
unknown – that it is a “black box”. This is a point at which the function of a module is
tested. Black – box testing involve looking at the functionality of the code. Here in
our system there several tests we had made at this point. Some of them are:

 Error Guessing
 Boundary Value Analysis
 Module Interface Testing
 Command Line Testing

Unit Testing
 Testing procedure takes into consideration for the all paths traversed during program
execution. Inputting appropriate values in the forms tests all paths, which can lead to
errors. All variable names were checked for all procedure used in programming.
Order of item in all insert statements are checked and corrected by displaying it in
temporary message box.

34 | P a g e
Online Banking

 Enhancement (Limitations of the Project) :

We think that not a single Project is ever considered as complete forever because our
mind is always thinking new and our necessities also are growing
Day by day. We always want something more that what we have. Our Application also, if
you see at the first glance that you find it to be complete but we want to make it still
mature and fully automatic.
As system is flexible you can generate more reports and screen as and when required.
 Online email can be implemented for inform the user about the profiles.

 More fields can be added for searching the profiles.

 Bibliography :

http://www.hdfcbank.com/
http://www.bobibanking.com/
http://www.axisbank.com/personal/accounts/accounts.asp
http://www.w3schools.com/default.asp.html
http://www.dotnetspider.com/
http://www.microsoft.com/

The programming language of ORACLE by IVAN BAYROSS.

35 | P a g e