CONTENTS

1. Project

1.1 Introduction1.2 Objectives1.3 Scope1.4 Description of project

2. Requirement Specifications 2.1 Hard ware Requirements 2.2 Software Requirements

3. Data Analysis3.1 Data dictionary

3.2 ERD 3.3 DFD

4. Software Design 4.1 Development Model

5. Snapshots 5.1 Input

5.2 Output

6. Testing & Modifications

7. Likely Benefits

8. Limitations and Future Enhancements

9. Conclusion

10. Bibliography (Give detailed references)

PROJECT

1.Project

1.1 IntroductionOnline Banking -The execution of financial services via internet, reduces cost and increases convenience for the customer to access the transaction. Online banking is an umbrella term for the process by which a customer may perform banking transactions electronically without visiting a brick-and-mortar institution.

Banks enables customers lifestyle needs by changing and increasing preference for speed and convenience are eroding the traditional affinity between customer and branch offices as a new technology disinter mediates traditional channels, delivering the value proposition hinges on owing or earning the customer interface and bringing the customer a complete solution which satisfies their needs. Banks are well positioned to play central role unit in future M-commerce market. Banks have strong relationships with corporate and business customers and a wide experience in providing them with corporate banking services. Bank provides a multimedia of small and large retailers with acquiring functionality in credit card transactions. Customers have trusted relationships with banks and a lower propensity to switch banking providers.

1.2 Objectives

To develop a core-banking as well as an e-banking solution for a bank. These applications must be in conformance with one another as well as with the common backend database.

The core-application is basically a GUI which acts as an interface between the bank personnel and the backend database to cater to the needs to the various customers arriving at the bank. It allows an administrator to carry out various tasks, like opening a new account, deposit money, withdraw money, transfer money from one account to another, requesting a cheque book, closing an account etc., for the various customers coming to the bank. The administrator is able to work on the application only once he/she has been checked for authenticity.

The e-banking is an extension to the already existing core application. It is a kind of extra facility for the customers to perform various functions without the need of actually visiting the bank. The online facilities available to the customers are checking his balance in his various accounts, viewing the details of transactions carried out on a particular account, requesting a new cheque book, transferring money between his accounts; querying etc. the customer is allowed access to his account details after having checked him for authenticity through a unique user-id and password.

The online banking is also meant for the administrator to log onto the website to view the pending requests to update the same but only after having checked his identity through a login-id and password meant exclusively for the administrator.

1.3 Scope

The basic task to be performed is the development of the e-banking framework. This framework is to be integrated with the already existing core banking solution. The deliverables include the web application and the core banking application. The resource

set is a predefined set of technologies among which appropriate choices had been made in order to conform to the team skill set. The schedule of the project is fixed. Functionality is to be delivered in phases. Each phase has a fixed timeframe. The success of the project depends upon the delivery of the required functionality in due time.

1.4 Description of Project

The project is to develop an e-banking system for a bank already running a core banking application. The new e-banking services are required to fully integrate with the core banking solution. The main aim is to provide a facility of Internet banking to the customer, so that he/she doesn’t need to visit the bank each time he/she has to perform some transaction. The problem requires the application to be absolutely secure and reliable. It requires that all the basic facilities such as withdrawal, account information, inter account transfers be provided to the user. The system is required to give a unique identification to each customer, which is valid across all his accounts. The system also asks for all database modifications to be done through the online application without any need for the core-banking module to intervene. The basic requirements of the system can be summarized through the following points

E-banking service to be available only to savings account holders. A customer allowed having multiple accounts. All basic transactions to be included in the core banking solution. Unique identification of bank accounts through account numbers. E-banking solution to have 3 basic functionalities, Querying, Transfer and Request

for a new cheque book. Each user to have a unique Login ID and Password. Core banking solution to implement – Registration of new customers, opening new

savings bank account for customers, deposit transactions, withdrawal transactions. Maintaining security password information, maintaining information on bank branches, recording cheque book requests and sent status and to maintain a central banking database.

E- banking solution to implement – user id and password, verification of above, provide customer account summary, provide transaction details for a particular account, to provide monthly details, to provide details according to given date range, to provide printer friendly version of each page. It requires each transaction to update the core banking database.

For the cheque book request facility the customer is asked to specify the cheque book size and urgency of request. The administrator is required to take care of all the pending requests, sending the cheque books, updating the request records and to send these details to the customer.

The system is also required to generate answers both in the form of report and query/response form.

Following details are to be generated by the system for the system administrator - last two days login details, all request details, list of customers with account balance less than a specified amount and details of the services used.

RequirementSpecifications

Chapter 1 2. Requirement Specifications

2.1 Hardware Requirements

RAM: 512 MB (Recommended)Processor: Pentium III 450 MHzOperating System: Windows 2000 or Windows XP Hard Disk Space: 3.5 GB (Includes 500 MB free space on disk)

2.2 Software Requirements

FRONT END : ASP.NET USING C#.NET

BACK END : SQL SERVER / MS-ACCESS

Data Analysis

3. Data Analysis

3.1 Data Dictionary

The data content is generally not more different in this software than any other software.

This project is used for text modification, so when the text is inserted for modification, first It

contains the data and functions which help to modify or to process the text. We want with

the provided functions. The text formats such as txt form etc. can be processed. This cannot

be processed or change the animated text. It is not used for three dimensional.

3.2 Entity Relationship Diagram (ERD)

3.3 Data Flow Diagrams (DFD)

Data flow diagrams from level 0 to level 6 are designed. They are shown below.

3.4 Use Case Diagram

SoftwareDesign

4. Software Design

4.1 Development Model

To develop this software we have used the basic life cycle model which have been proposed is waterfall

Model, in which all the works are done in straight forward pattern. The basic idea behind interactive

enhancement is to develop is to develop a software system incrementally, allowed the developed to

take advantages of what was being learnt during the development of earlier, increment, deliverable,

version of the system. Learning comes from both the development of earlier, incremental, deliverable

version of the system. Learning comes from both the development and use of system, where possible.

Key step in the process were to start with a simple implementation of a subnet of the software

requirements and iteratively enhance the evolving sequence of versions until the full system is

implemented. At each iteration design modification are made and new functional capabilities are added.

In system engineering and requirement we iteratively enhance the evolving sequence of versions until

the full system is implemented. At each iteration design modifications are made and new functional

capabilities are added .In system engineering and the requirement engineering a non-functional

requirement is a requirement that specifies criteria that can be used judge the operation of a system

rather than specific behavior .This should be considered contrast with function requirement that define

specifies behavior function.

Waterfall Model

Requirement

Project Plan

Design

Documents

Coding

Testing

Snapshots

5.Snapshots

WELCOME, this is the TNB Bank website

Login id:

normal user

Password:

CUSTOMER table

LOGIN PAGE

DATABASE

GO!

1. The login id and password are checked and verified from the customer table in the database.

2. If the valid user -id ands password do not exist then user is taken to error page where he can again log in.

3. If the user is the normal customer of the bank , then he is directly taken to the page where his accounts and their respective balances are outlined in a table.

4. If the user is an ADMINISTRATOR , then he is taken to the page where usage history of the site, e.g. no. of users active since last 2 days , customers asking for cheque book, list of customers whose balance is less than 3000,which service of the site is used most.

ADMINISTRATOR LOGIN

What do u want to do?

1. see when max. no. of users were online and login history for the past 2 days 2. check the service used maximum 3. users who have balance less than 3000.00 4. chequebook requests

All the above entries are hyperlinks and show following things when clicked

Information about chequebooks

Information about customers having balance less than 3000.00

S.no. Account no. Status

1 J3567 issued

2 G6899 Pending

3 H7600 Issued

4 H8996 Pending

5 V4578 Issued

6 B5689 issued

S.no. Account no. Balance

1. H4565 577.00

2. D4677 1245.00

3. D5896 2999.00

4. L6778 2677.00

Used for displaying various no. of users using different services.

Used to show how many users were online on a given date.

1. User clicks on the link2. System extracts the current date and time3. Database uses TRANSACTION table to extract the

account’s transactions from the 1st of that month (using system date) to the current date.

DATABASE

4. The transactions are outlined in a table in next page.

5. If no entry for that account exists for that month ,NO TRANSACTIONS IN THIS MON TH will be shown on the page.

TRANSACTION

table

Field blank bcos there’s no need for dest account in a withdrawal transaction

Enter starting and ending transaction dates:

There’s no mode while transferring the funds

Starting date(dd/mm/yyyy) Ending date(dd/mm/yyyy)

1. These dates are used for giving details of transactions done

from starting date to ending date.

2. The dates are taken and compared with the account’s entry in the TRANSACTION DATABASE.

3. The transactions done by the account from starting date to ending date are tabulated and shown to the customer.

Transfer of accounts

Source account no.

Destination account no.

DATABASE

DATABASE

GO!

GO

Amount

CUSTOMER TRANSACTION

If the amount to be transferred is greater than the amount that the user is having in the bank OR the destination account no. does not exist, then an error is returned otherwise updates are made in the databases.

Changes are made to both the tables in the database

Chequebook

Account no.

No. of leaves

CHEQ

UE BOOK

Table in the database gets updated.

DATABASE

Go!

Testing&

Modifications

6. Testing & Modifications

Next phase in the project development is testing. Testing phase basically involves two types of testing, namely α - testing and β - testing.

α–testing comprised of extensive testing by the team members. All the modules and code segments were extensively tested for errors. The errors found during this phase of testing are listed below. The errors can be broadly classified into 2 categories namely,

Planning errors Designing errors Coding errors

Planning Errors

Planning errors are the errors which occurred during the planning and requirement analysis phase of project development. These errors came into attention when the ideas developed during the planning phase were actually implemented in coding. These errors included

1. Error in Database design: During coding it was discovered that some of the tables in the database didn’t have all the attributes needed to implement some of the functionalities of the project. The database tables were then subsequently modified.

2. Error in code planning: There were some code planning errors like applying transactions at every place where database updating or insertion was made. These transactions were later inserted at proper places.

Designing Errors

Designing errors are the errors which occurred in the designing phase of the project development. These errors included

1. Error in E-R diagram design: Some aspects of E-R diagram design were missed during the design phase. These errors cropped up when this E-R Diagram was actually implemented as the database in SQL Server2000.

2. Error in module designing: There were some inherent errors in dividing the entire project into user modules. The modules had to be redesigned once the group started working on the modules.

Coding Errors

The major part of errors encountered during the project designing belonged to this phase of project development. This phase encountered a vast array of errors ranging from simple coding mistakes to big logical blunders. The errors can be listed as

1. Error in Database connectivity: This error was frequently encountered when the code was migrated from one terminal to another. The root cause of this error was the difference in server names at the respective terminals.

2. Error in the implementation of website security: This was realized when the values were posted between different forms and they were visible in the

query string. This was resolved by encrypting this secretive information and by avoiding passing these values wherever possible.

3. Error in the usage of web controls: In some portions of our code there was error in selection of the type of control i.e. dropdown list, textboxes, data grids, etc. We used HTML controls where web controls had to be used.

4. Error in usage of application variables: Error was encountered when we tried to create application variables and embed them in our functionality.

5. Error in keeping track of user sessions: We faced errors initially while trying to keep track of the different users visiting the website. This error was dealt with by creating a session table and session variables and using them as and when required.

6. Error in date range validation: Since this part of the code involved intensive usage of nested “if” and “while” loops it became tedious to work with this part of the code to achieve the desired end results.

7. Error in implementing session logout: We encountered a problem in which even after a user logged out he could access the sensitive content of the website.

LikelyBenefits

7.Likely Benefits

Opening and closing of accounts.

It gives reliefs to their customer from carrying heavy cash. Enables prompt & speedy operation to clients. It saves lot of time to their customers &convenient to access.

Transfer of funds between accounts

It brings efficiency in CRM(Customer relationship management)

Make Payment of bill

Introduces new & innovative products &services.

View balance and statements.

Brings door to door services.

LimitationsAnd Future

Enhancement

8.Limitations and Future Enhancements

8.1 Limitation1. Due to use of one-way MD5 Hash algorithm we cannot use forgot password option in

the website. This is because password decryption cannot be done by selecting corresponding user-id from the database and we have no way of validating the user without knowing his password.

2. Only intra-account (accounts of same customer) funds transfer can be done through internet, inter-account transfer has not been implemented.

3. There’s no limit to number of accounts a customer can have.

4. There isn’t any minimum amount which is required to transfer. A transfer of Re 1 would also be allowed wasting the network resources.

5. Since only password has been encrypted a fraudulent person can view other details of the customer.

8.2 Future Enhancements1. Debit and Credit cards facility can be provided.

2. Bank drafts and bank slips can also be used.

3. ATM facility can be used provided satellite connections are there.

4. A bank branch can have a maximum of 100,000 accounts. To increase capacity many modifications need to be done to the database.

Conclusion

9.ConclusionThus reaching to the conclusion of our project we observe that Traditional banks offer many services to their customers, including accepting customer money deposits, providing various banking services to customers, and making loans to individuals and companies. Compared with traditional channels of offering banking services through physical branches, online banking uses the Internet to deliver traditional banking services to their customers, such as opening accounts, transferring funds, and electronic bill payment. Online banking can be offered in two main ways. First, an existing bank with physical offices can also establish an online site and offer Online banking services to its customers in addition to the regular channel. For example, Citibank is a leader in online banking, offering walk-in, face-to-face banking at its branches throughout many parts of the world as well as online banking services through the World Wide Web. Generally, online banking is provided without extra cost to customers. Customers are attracted by the convenience of e-banking through the Internet, and in turn, banks can operate more efficiently when customers perform transactions by themselves rather than going to a branch and dealing with a branch representative.

Bibliography

10.Bibliography Asp.Net Unleashed: Stephen Walther SQL Server 2000: Mike Gunderloy SAMS Teach yourself C#.net in 21 days Programming Asp.Net: Jesse Liberty Beginning C#.Net: Richard Blair